On Mon, Aug 06, 2007 at 09:57:33AM -0400, Alan Stern wrote: > On Sun, 29 Jul 2007, Alan Stern wrote: > > > Well, about all I can suggest is bisection. And don't assume that this > > problem was caused by a change to the USB stack. It could be a change > > in the interrupt-handling core or a change to the driver for one of the > > other devices sharing the IRQ. > > > > It might even be caused by a change in the order the modules are > > loaded, which has nothing to do with the kernel directly. In fact, it > > might be worth checking this possibility first. For example, it's > > clear that 2.6.22 loaded ehci-hcd before uhci-hcd whereas 2.6.23-rc1 > > did the reverse. And yenta vs. uhci-hcd is different. > > Any progress? >
I have dug into this and found something completely different! I only get the boot error if I kexec the new kernel from within an xterm. It is not a new regression in 2.6.23, it was just the first time I have used kexec that way and so popped up at the same time. Sorry for the noise. Mark ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Linux-usb-users@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
