On Wed, 7 May 2008, David Miller wrote: > From: Alan Stern <stern@xxxxxxxxxxxxxxxxxxx> > Date: Wed, 7 May 2008 19:31:50 -0400 (EDT) > > > On Wed, 7 May 2008, David Miller wrote: > > > > > I looked through the changesets since v2.6.25 in drivers/usb/host/ > > > and there are a couple refactorings of how OHCI and EHCI are > > > programmed in various situations which would be useful to audit. > > > > But the problem occurred when a UHCI controller was registered. What > > makes you think OHCI or EHCI has anything to do with it? > > Read the reporter's boot logs. Their system (Sun Fire V100) has OHCI > host controllers. > > And right after registerring OHCI is when it hangs: Ah yes, I see. So why did I think this was related to UHCI? <Goes back and re-reads old email messages...> Answer: Because you said so in your original posting to linux-usb. This means that the routine to look at is ohci_hub_status_data() in drivers/usb/host/ohci-hub.c, not the corresponding UHCI routine. But everything else is pretty much the same; it would still help to add printk statements before and after the spin_lock_irqsave() call. Maybe also a printk just before the final "return" statement. Alan Stern -- To unsubscribe from this list: send the line "unsubscribe sparclinux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
