From: David Brownell <[EMAIL PROTECTED]> Date: Sun, 07 Oct 2007 00:31:41 -0700
> Is this SPARC, or is ACPI potentially in play? PCI, or non-PCI? It's sparc64 on PCI. > Are the other ports still behaving? Is EHCI maybe trying to switch > ownership of that port? Is maybe the (newish) autosuspend stuff > kicking in? I wouldn't know, the machine hangs and doesn't get any further. > Patches accepted. :) I'm 700 patches deep with an additionally large backlog of patches to apply for the networking and sparc64 tree. I don't have the time, which is why I reported the problem to the OHCI maintainer instead of letting it slip through the cracks. > Since the PRS bit is specified as "write one", with writing zero > as no-effect (since the rest is hardware-timed), the only recovery > procedure might involve resetting the whole controller. Messy, > and not something the usb core has historically handled very well. At a minimum you should exit the loop and print out a warning messages and try to continue even without trying to reset the whole controller if that will take some developer effort. Anything is better than just hanging there forever. Not every user knows to hit ALT-SYSRQ then 'P' to get a register dump to figure out why their computer stopped booting. Every register polling loops, without exception, should have a limit and exit with an error indication when that limit is reached. It will never hang someones machine, because although not this time, in many cases these kinds of hangs are absolutely impossible to debug (interrupts disabled, critical lock held, etc.) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
