Re: [-next-20130204] usb/hcd: irq 18: nobody cared
On Tue, 2013-02-05 at 15:26 -0500, Alan Stern wrote:
On Tue, 5 Feb 2013, Peter Hurley wrote:
With -next-20130204:
[ 33.855570] irq 18: nobody cared (try booting with the irqpoll option)
[ 33.855580] Pid: 0, comm: swapper/4 Not tainted 3.8.0-next-20130204-xeon
#20130204
[ 33.855582] Call Trace:
[ 33.855585] IRQ [810f1076] __report_bad_irq+0x36/0xe0
[ 33.855600] [810f152a] note_interrupt+0x1aa/0x200
[ 33.855606] [8101edf2] ? mwait_idle+0x82/0x1b0
[ 33.855610] [810eed89] handle_irq_event_percpu+0xc9/0x260
[ 33.855614] [810eef68] handle_irq_event+0x48/0x70
[ 33.855618] [810f20ba] handle_fasteoi_irq+0x5a/0x100
[ 33.855624] [810182f2] handle_irq+0x22/0x40
[ 33.855630] [816e2a9a] do_IRQ+0x5a/0xd0
[ 33.855636] [816d97ad] common_interrupt+0x6d/0x6d
[ 33.855638] EOI [810f8e2a] ?
rcu_eqs_enter_common+0x4a/0x320
[ 33.855646] [8101edf2] ? mwait_idle+0x82/0x1b0
[ 33.855649] [8101ed99] ? mwait_idle+0x29/0x1b0
[ 33.855653] [8101f8a6] cpu_idle+0x116/0x130
[ 33.855658] [816c0c0f] start_secondary+0x251/0x258
[ 33.855660] handlers:
[ 33.855664] [814f98a0] usb_hcd_irq
[ 33.855667] Disabling IRQ #18
From earlier in the boot log:
[1.297020] uhci_hcd :00:1d.2: setting latency timer to 64
[1.297032] uhci_hcd :00:1d.2: UHCI Host Controller
[1.297040] uhci_hcd :00:1d.2: new USB bus registered, assigned bus
number 4
[1.297076] uhci_hcd :00:1d.2: irq 18, io base 0xff40
[1.297213] hub 4-0:1.0: USB hub found
[1.297221] hub 4-0:1.0: 2 ports detected
lsusb:
...
Bus 004 Device 002: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS
Bus 004 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
...
Didn't have this problem with -next-20120125. One of these commits, maybe?
next/drivers/usb/core$ git log --oneline next-20130125..next-20130204 -- *
2c2e865 usb: forbid memory allocation with I/O during bus reset
e9121a8 Merge remote-tracking branch 'usb/usb-next'
3b2ab2b Revert usb: Register usb port's acpi power resources
da0aa71 USB: add usb_hcd_{start,end}_port_resume
192fef1 usb: enable usb port device's async suspend.
f6cced1 usb: expose usb port's pm qos flags to user space
ad493e5 usb: add usb port auto power off mechanism
971fcd4 usb: add runtime pm support for usb port device
88bb965 usb: Register usb port's acpi power resources
54a3ac0 usb: Using correct way to clear usb3.0 device's remote wakeup
feature.
None of those commits seems likely to have caused the problem. The
most likely is da0aa71, combined with one you didn't mention:
840008bb USB: UHCI: notify usbcore about port resumes
If you revert these two commits, does that make any difference? What
if you revert all of these commits?
None of these commits are directly causing this. I tested Greg's usb
master and usb-next and both run fine for me.
I didn't see any changes in the drivers/hid/hid-logitech-dj.c or usbhid
but maybe it's doing something wrong anyway?
I'll open a bugzilla if a bunch more info is necessary.
If the suggestion above doesn't work out, bisection may be the best way
to find the answer.
Any pointers on how to one of) build a linear history for -next, get
bisect to work on an integration tree, or third option I haven't thought
of?
Thanks,
Peter Hurley
--
To unsubscribe from this list: send the line unsubscribe linux-usb in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [-next-20130204] usb/hcd: irq 18: nobody cared
On Tue, 5 Feb 2013, Peter Hurley wrote:
With -next-20130204:
[ 33.855570] irq 18: nobody cared (try booting with the irqpoll option)
[ 33.855580] Pid: 0, comm: swapper/4 Not tainted 3.8.0-next-20130204-xeon
#20130204
[ 33.855582] Call Trace:
[ 33.855585] IRQ [810f1076] __report_bad_irq+0x36/0xe0
[ 33.855600] [810f152a] note_interrupt+0x1aa/0x200
[ 33.855606] [8101edf2] ? mwait_idle+0x82/0x1b0
[ 33.855610] [810eed89] handle_irq_event_percpu+0xc9/0x260
[ 33.855614] [810eef68] handle_irq_event+0x48/0x70
[ 33.855618] [810f20ba] handle_fasteoi_irq+0x5a/0x100
[ 33.855624] [810182f2] handle_irq+0x22/0x40
[ 33.855630] [816e2a9a] do_IRQ+0x5a/0xd0
[ 33.855636] [816d97ad] common_interrupt+0x6d/0x6d
[ 33.855638] EOI [810f8e2a] ? rcu_eqs_enter_common+0x4a/0x320
[ 33.855646] [8101edf2] ? mwait_idle+0x82/0x1b0
[ 33.855649] [8101ed99] ? mwait_idle+0x29/0x1b0
[ 33.855653] [8101f8a6] cpu_idle+0x116/0x130
[ 33.855658] [816c0c0f] start_secondary+0x251/0x258
[ 33.855660] handlers:
[ 33.855664] [814f98a0] usb_hcd_irq
[ 33.855667] Disabling IRQ #18
From earlier in the boot log:
[1.297020] uhci_hcd :00:1d.2: setting latency timer to 64
[1.297032] uhci_hcd :00:1d.2: UHCI Host Controller
[1.297040] uhci_hcd :00:1d.2: new USB bus registered, assigned bus
number 4
[1.297076] uhci_hcd :00:1d.2: irq 18, io base 0xff40
[1.297213] hub 4-0:1.0: USB hub found
[1.297221] hub 4-0:1.0: 2 ports detected
lsusb:
...
Bus 004 Device 002: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS
Bus 004 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
...
Didn't have this problem with -next-20120125. One of these commits, maybe?
next/drivers/usb/core$ git log --oneline next-20130125..next-20130204 -- *
2c2e865 usb: forbid memory allocation with I/O during bus reset
e9121a8 Merge remote-tracking branch 'usb/usb-next'
3b2ab2b Revert usb: Register usb port's acpi power resources
da0aa71 USB: add usb_hcd_{start,end}_port_resume
192fef1 usb: enable usb port device's async suspend.
f6cced1 usb: expose usb port's pm qos flags to user space
ad493e5 usb: add usb port auto power off mechanism
971fcd4 usb: add runtime pm support for usb port device
88bb965 usb: Register usb port's acpi power resources
54a3ac0 usb: Using correct way to clear usb3.0 device's remote wakeup feature.
None of those commits seems likely to have caused the problem. The
most likely is da0aa71, combined with one you didn't mention:
840008bb USB: UHCI: notify usbcore about port resumes
If you revert these two commits, does that make any difference? What
if you revert all of these commits?
I didn't see any changes in the drivers/hid/hid-logitech-dj.c or usbhid
but maybe it's doing something wrong anyway?
I'll open a bugzilla if a bunch more info is necessary.
If the suggestion above doesn't work out, bisection may be the best way
to find the answer.
Alan Stern
--
To unsubscribe from this list: send the line unsubscribe linux-usb in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
