WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] Re: [Xen-devel] irq 17: nobody cared (try booting with t

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Re: [Xen-devel] irq 17: nobody cared (try booting with the "irqpoll" option)
From: Hans-Christian Armingeon <mog.johnny@xxxxxxx>
Date: Tue, 13 Jun 2006 10:26:27 +0200
Cc: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 13 Jun 2006 01:27:10 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <777a1213cb309e7d9263f6e6372f2f2e@xxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <200606031451.52939.mog.johnny@xxxxxxx> <200606052008.00011.mog.johnny@xxxxxxx> <777a1213cb309e7d9263f6e6372f2f2e@xxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.9.3
Hello Keir,

today I got this error:

[ 1146.202386] irq 17: nobody cared (try booting with the "irqpoll" option)
[ 1146.205607]
[ 1146.205608] Call Trace: <IRQ> <ffffffff801590a5>{__report_bad_irq+53}
[ 1146.208938]        <ffffffff80159333>{note_interrupt+563} <ffffffff80158a36> 
                                                            __do_IRQ+214}
[ 1146.214881]        <ffffffff8010d0d7>{do_IRQ+71} <ffffffff80311b76>{evtchn_d 
                                                            _upcall+166}
[ 1146.220863]        <ffffffff8010b6d2>{do_hypervisor_callback+30} <EOI>
[ 1146.224036]        <ffffffff801073aa>{hypercall_page+938} <ffffffff801073aa> 
                                                            hypercall_page+938}
[ 1146.229934]        <ffffffff8010e987>{safe_halt+119} <ffffffff801097d7>{xen_ 
                                                            dle+119}
[ 1146.235920]        <ffffffff801098a0>{cpu_idle+176} <ffffffff8058f7ca>{start 
                                                            kernel+506}
[ 1146.241780]        <ffffffff8058f102>{_sinittext+258}
[ 1146.247580] handlers:
[ 1146.250393] [<ffffffff88039370>] (ata_interrupt+0x0/0x1b0 [libata])
[ 1146.253445] Disabling IRQ #17

I am using xen unstable 20060610 with a 2.6.16.20 kernel.

I thought, that you made a fix for interrupt sharing between dom0 and domUs.


So what went wrong?

Thanks in advance,

Johnny


Am Montag, 5. Juni 2006 20:15 schrieb Keir Fraser:
> 
> On 5 Jun 2006, at 19:07, Hans-Christian Armingeon wrote:
> 
> > What can I do to debug the problem with the irq?
> 
> Like I said, the issue is known. It can occur whenever an irq is shared 
> by more than one driver domain (including domain 0). A patch will be 
> forthcoming but for now noirqdebug is a perfect workaround.
> 
>   -- Keir
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
> 

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>