Re: Problem: irq 217: nobody cared + backtrace

[Sergio Monteiro Basto]

my system is much different, but I got similar problems 
http://bugme.osdl.org/show_bug.cgi?id=6419#c17

irq 201: nobody cared (try booting with the "irqpoll" option)

Call Trace:
 [<ffffffff8026a20a>] dump_stack+0x12/0x17
 [<ffffffff802b6c26>] __report_bad_irq+0x30/0x7d
 [<ffffffff802b6e46>] note_interrupt+0x1d3/0x219
 [<ffffffff802b6383>] __do_IRQ+0xc8/0x107
 [<ffffffff8026b166>] do_IRQ+0xe7/0xf5
 [<ffffffff8025d189>] ret_from_intr+0x0/0xa
DWARF2 unwinder stuck at ret_from_intr+0x0/0xa
Leftover inexact backtrace:
 <IRQ> <EOI> [<ffffffff80230d50>] unix_poll+0x0/0x99
 [<ffffffff802569ed>] mwait_idle+0x36/0x4a
 [<ffffffff8024888d>] cpu_idle+0x95/0xb8
 [<ffffffff806da842>] start_kernel+0x220/0x225
 [<ffffffff806da28a>] _sinittext+0x28a/0x28e

handlers:
[<ffffffff880eaaf5>] (rhine_interrupt+0x0/0xae3 [via_rhine])
Disabling IRQ #201

root@monteirov:~#cat /proc/interrupts
           CPU0       CPU1
  0:     356842     312644    IO-APIC-edge  timer
  1:        586        711    IO-APIC-edge  i8042
  6:          5          0    IO-APIC-edge  floppy
  7:          2          0    IO-APIC-edge  parport0
  8:          0          0    IO-APIC-edge  rtc
  9:          0          0   IO-APIC-level  acpi
 12:      33214      32075    IO-APIC-edge  i8042
 15:      11161      11127    IO-APIC-edge  ide1
193:      65857       9444   IO-APIC-level  libata
201:     100000          0   IO-APIC-level  eth0
         ^^^^^^
209:      91593      91062   IO-APIC-level  uhci_hcd:usb1,
uhci_hcd:usb2, uhci_hcd:usb3, uhci_hcd:usb4, ehci_hcd:usb5
217:       1151        538   IO-APIC-level  VIA8237
225:      49661      49438   IO-APIC-level  nvidia
NMI:        438        403
LOC:     669481     669457
ERR:          0
MIS:          0




On Fri, 2006-08-04 at 16:36 +0200, Jesper Juhl wrote:
> On 03/08/06, Alan Stern <stern@xxxxxxxxxxxxxxxxxxx> wrote:
> >
> > Has this happened more than once?
> 
> Seems to happen consistently after ~100000 interrupts.
> 
> >  In case it happens again, here's how
> > you can get more information.  Turn on CONFIG_USB_DEBUG and
> > CONFIG_DEBUG_FS, and mount a debugfs filesystem somewhere (say
> > /sys/kernel/debug).  Then after the problem occurs, save a copy of
> >
> >         /sys/kernel/debug/uhci/0000:00:1d.1
> >
> 
> # cat /sys/kernel/debug/uhci/0000:00:1d.1
> Root-hub state: auto-stopped   FSBR: 0
> HC status
>   usbcmd    =     0048   Maxp32 CF EGSM
>   usbstat   =     0020   HCHalted
>   usbint    =     0002
>   usbfrnum  =   (1)160
>   flbaseadd = 37428160
>   sof       =       40
>   stat1     =     0080
>   stat2     =     0080
> Most recent frame: 458 (88)   Last ISO frame: 458 (88)
> 
> 
> > That will indicate whether the UHCI controller thinks it is sending an
> > interrupt request.
> >
> 
> And just for completenes, here's the backtrace I got just before
> saving the above info :
> 
> irq 217: nobody cared (try booting with the "irqpoll" option)
>  [<c0103a3c>] show_trace_log_lvl+0x152/0x165
>  [<c0103a5e>] show_trace+0xf/0x13
>  [<c0103b59>] dump_stack+0x15/0x19
>  [<c013846e>] __report_bad_irq+0x24/0x7f
>  [<c0138552>] note_interrupt+0x6b/0xd5
>  [<c0137ca8>] __do_IRQ+0xf4/0x100
>  [<c01050a1>] do_IRQ+0x95/0xbc
>  [<c0103502>] common_interrupt+0x1a/0x20
>  [<c0137b7e>] handle_IRQ_event+0x20/0x56
>  [<c0137c4c>] __do_IRQ+0x98/0x100
>  [<c01050a1>] do_IRQ+0x95/0xbc
>  [<c0103502>] common_interrupt+0x1a/0x20
>  [<c0100e64>] mwait_idle+0x30/0x35
>  [<c0100d45>] cpu_idle+0x78/0x81
>  [<c04cc7fb>] start_kernel+0x173/0x19d
>  [<c0100210>] 0xc0100210
> DWARF2 unwinder stuck at 0xc0100210
> Leftover inexact backtrace:
>  =======================
> handlers:
> [<c02c5c22>] (usb_hcd_irq+0x0/0x53)
> Disabling IRQ #217
> 
>

Attachment: smime.p7s
Description: S/MIME cryptographic signature