Alan Stern writes:
> On Mon, 16 Jul 2007, Akkana Peck wrote:
> > But if the bad device doesn't
> > have a handler registered, does that mean it might not even show
> > up in /proc/interrupts?
>
> That's right. Or it might have a handler registered for a different
> IRQ number, a wrong one.
Sure enough. My firewire-free kernel worked fine all yesterday, but
after leaving the laptop suspended overnight, the USB mouse failed,
and dmesg says:
hub 1-0:1.0: suspend error -16
suspend_device(): usb_suspend+0x0/0x20() returns -16
Could not suspend device usb1: error -16
PM: Writing back config space on device 0000:02:00.0 at offset f (was 50a0100,
writing 50a0109)
PM: Writing back config space on device 0000:02:00.0 at offset 6 (was 0,
writing 14000080)
PM: Writing back config space on device 0000:02:00.0 at offset 5 (was 0,
writing 14000000)
PM: Writing back config space on device 0000:02:00.0 at offset 4 (was 1,
writing 1401)
PM: Writing back config space on device 0000:02:00.0 at offset 3 (was 0,
writing 4000)
PM: Writing back config space on device 0000:02:00.0 at offset 1 (was 2100000,
writing 2100007)
and although I'm not getting any "nobody cared" messages, the behavior
is the same (flaky mouse, and unplugging/replugging doesn't help).
Any tips on finding the source of the extra IRQ9? Or on what option
might have changed since about 2.6.19 to make the kernel more sensitive
to the problem?
...Akkana
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Linux-usb-users@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users
