On Sat, 15 Jan 2005, Marc-Christian Petersen wrote: > > Alt-SysRq-T is needed. Usually it's captured with a serial console or > > netconsole. > > This is most probably a result of exclusive_access. A process took that > > semaphore > > and scheduled somewhere. If so, we have to know what process it was and > > what it > > was doing. > > that's the problem. The machine is _dead_. Nothing works, sysrq is dead > too. After I saw that even sysrq is dead, I applied kdb and tried to > capture it, but even kdb is not usable because the kernel is completely > locked up. I'm out of ideas, like Marcelo, I don't know USB at all. > > I even tried an UP kernel (compiled as UP), even nosmp boot parameter (it > might be an SMP problem) but it isn't, even UP locks up hard. I also > disabled ACPI, apic and friends, same problem. It's also not a problem of > my USB Controllers nor USB 1.1 or 2.0. Doesn't matter where I plug the > stick in.
One thing that might help is to turn on the verbose USB debugging option in the kernel configuration and to set the console logging level very high, maybe even use a serial console if you can. There may be useful information written to the system log just before the machine crashes. Alan Stern ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Linux-usb-users@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
