On Tue, 1 Jan 2013, Udo van den Heuvel wrote: > On 2012-12-31 18:24, Alan Stern wrote: > > Can you provide the entire output? Two lines isn't enough. > > It just happened again. Messages in edited form: > > Jan 1 07:23:46 bobo dbus[3106]: [system] Rejected send message, 2 > matched rules; type="method_return", sender=":1.1" (uid=0 pid=3076 > comm="/usr/lib/systemd/systemd-logind ") interface="(unset)" > member="(unset)" error name="(unset)" requested_reply="0" > destination=":1.34" (uid=500 pid=4183 comm="gnome-session ") > Jan 1 08:51:21 bobo kernel: irq 18: nobody cared (try booting with the > "irqpoll" option) > Jan 1 08:51:21 bobo kernel: Pid: 22652, comm: irq/18-ohci_hcd Not > tainted 3.6.11 #19 > dmesg startingsunday afternoon, edited: ... > hub 2-0:1.0: state 7 ports 5 chg 0000 evt 0010 > ohci_hcd 0000:00:13.0: IRQ: 4 8000005a > ohci_hcd 0000:00:13.0: last IRQ repeated 100 times > ohci_hcd 0000:00:13.0: IRQ: 24 8000005a > ohci_hcd 0000:00:13.0: last IRQ repeated 100 times > > (and nothing more in dmesg as of Tue Jan 1 09:06:45 CET 2013) I don't understand. How can there be nothing more? Above you showed an "irq 18: nobody cared" message that appeared at 8:51 on Jan 1. It certainly ought to be in the dmesg log as of 9:00. Also, I asked you to turn on CONFIG_PRINTK_TIME. Without that, there's no way for me to tell when those IRQ: messages appear in relation to the "nobody cared". In the end, this comes down to two possibilities. Either the OHCI controller is malfunctioning or else some other piece of hardware/software is. Either the unwanted interrupt requests are generated by the OHCI controller or else they are generated by something else. The messages above indicate that lots of IRQs occur at times when the controller has no reason to issue one. Unfortunately, I don't know of any way to tell whether or not the controller actually issued the interrupt requests. If the controller is working correctly and didn't issue those requests then something else did -- and there's no way to tell what. I suppose you could try unplugging all your low-speed and full-speed devices from the OHCI controller. (Get a high-speed hub and plug them into it instead.) Then the controller hardware should be totally quiescent. If the unwanted IRQs still occur then it seems likely that the controller is not the cause -- although this isn't an airtight proof. Alan Stern -- 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
