On Tue, Sep 20, 2011 at 11:46:00AM -0400, Alan Stern wrote: > On Mon, 19 Sep 2011, Greg KH wrote: > > > On Sun, Sep 18, 2011 at 12:58:49PM -0400, Alan Stern wrote: > > > On Sun, 18 Sep 2011, Greg KH wrote: > > > > If you don't want a novell.com bugzilla id (which I understand if you > > > > don't), I'll dig the data out of the bug and post it here, as it looks > > > > to affect the 2.6.32 kernel, which wasn't all that old. > > > > > > It's been a long time since I used Novell's bugzilla. My computer > > > remembers the ID "stern58". Still, it might be a good idea to post > > > the relevant data publically, if the other people involved don't mind. > > > > The bug seems to be "closed" as it's dealing with a customer's system > > and they don't like public bugs for their hardware for various reasons. > > > > But here's the oops report from the bug, pasted from it: > > > > --- begin quote --- > > > > After I do a > > # rmmod uhci_hcd > > I get the following: > > > > sles11sp1:/tmp/intel/crash-vnc # tail -f /var/log/messages > > Sep 5 15:26:54 sles11sp1 kernel: [ 4647.721936] uhci_hcd 0000:00:1d.2: remove, state 1 > > Sep 5 15:26:54 sles11sp1 kernel: [ 4647.721945] usb usb8: USB disconnect, address 1 > > Sep 5 15:26:54 sles11sp1 kernel: [ 4647.721947] usb 8-1: USB disconnect, address 2 > > Sep 5 15:26:54 sles11sp1 kernel: [ 4647.769335] uhci_hcd 0000:00:1d.2: dma_pool_destroy uhci_qh, ffff880037849000 busy > > Sep 5 15:26:54 sles11sp1 kernel: [ 4647.769338] uhci_hcd 0000:00:1d.2: dma_pool_destroy uhci_td, ffff880037833000 busy > > Sep 5 15:26:54 sles11sp1 kernel: [ 4647.769344] uhci_hcd 0000:00:1d.2: USB bus 8 deregistered > > Sep 5 15:26:54 sles11sp1 kernel: [ 4647.769348] uhci_hcd 0000:00:1d.2: dma_pool_destroy buffer-128, ffff880037822000 busy > ... > > > --- end quote --- > > > > Does that sound like anything that has been fixed in the past few years > > that you can recall? > > Hmmm, nothing especially stands out. There was a similar problem in > ehci-hcd, but I don't remember anything in uhci-hcd. Ok, thanks. > Is there any way to find out if the problem still appears with a > current kernel? Or to find out how the problem can be reproduced? To reproduce it, this system just has its uhci-hcd module unloaded. Now, to be fair, the hardware in this type of system is known to have issues at times, unloading the module was an attempt to work-around another bug that the hardware has, so perhaps something worse really is going on here. And I'll ask to see if they can test a 3.0 kernel on the system, that would be good to find out. thanks for looking at this, greg k-h -- 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
