> > i am not sure, whether it is really problem of the usb subsystem or with > > some other layer, but i am regularly experiencing problems with usb > > devices. searching on the lkml, i came across a very similar problem > > and the only common point is that it also mentions the usb_hcd_irq > > interrupt handler [1]. > It's easy enough to test. Unload the various drivers using that IRQ, > one at a time, until the problem stops occurring. ok, after first unloading the snd-hdsp driver, it still produces an error, although this time in the bad interrrupt comes from ahci: [ 1626.002271] Pid: 305, comm: irq/16-ahci Tainted: P 3.1.0-rc8+ #15 [ 1626.002274] Call Trace: [ 1626.002283] [<ffffffff810d27b6>] __report_bad_irq+0x36/0xe0 [ 1626.002287] [<ffffffff810d2bfd>] note_interrupt+0x14d/0x210 [ 1626.002293] [<ffffffff81069527>] ? local_bh_enable+0x57/0xc0 [ 1626.002297] [<ffffffff810d17d0>] ? irq_thread_fn+0x50/0x50 [ 1626.002301] [<ffffffff810d174f>] irq_thread+0x1af/0x1e0 [ 1626.002305] [<ffffffff810d15a0>] ? irq_finalize_oneshot+0x120/0x120 [ 1626.002310] [<ffffffff8108566c>] kthread+0x8c/0xa0 [ 1626.002317] [<ffffffff815e7674>] kernel_thread_helper+0x4/0x10 [ 1626.002321] [<ffffffff810855e0>] ? kthread_worker_fn+0x190/0x190 [ 1626.002326] [<ffffffff815e7670>] ? gs_change+0x13/0x13 [ 1626.002328] handlers: [ 1626.002333] [<ffffffff810d0d90>] irq_default_primary_handler threaded [<ffffffff81434790>] usb_hcd_irq [ 1626.002342] [<ffffffff810d0d90>] irq_default_primary_handler threaded [<ffffffffa00e9d10>] ahci_interrupt [ 1626.002356] Disabling IRQ #16 > > we both get the message irq XX: nobody cared (see below). and for both > > of us the problem started with the 3.0 kernel (i've also experienced it > > with 3.1-rc8). on my machine it happens not very often ... sometimes it > > takes a few hours to occur. however i am currently running on a kernel > > which is booted without threadirq without any problems. > > > > i once tried to boot with the irqpoll option, but the machine didn't > > boot at all. both issues occurred on different irqs, the only common > > interrupt handler is usb_hcd_irq. > > > > how can i help to resolve this issue? > > If you remove ohci-hcd and uhci-hcd but the problem remains, then > you'll know it's not related to USB. not sure, whether this is an option for me, as i am using usb mouse/keyboard ... so i cannot use the machine anymore :/ tim -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
