> > Any thoughts on what could be going wrong? > > Hm, no I don't, this is the first report. What is the error that > happens? > > David, any ideas?
The original poster on this thread showed a completely normal kernel boot, and called it a panic. Then said that it worked OK in a later kernel. It's completely unclear what might be going wrong; if it were a panic there would be a stack trace, and nobody's shown one. Sometimes bug reports can be so ... lacking ... :( As a rule, if a "printk" dies, it's not usually going to be any kind of USB problem. I suspect that maybe the IRQ handler should just completely ignore the wakeup flag when deciding if it should look at the STS_PCD report, but if that matters on a kexec path then the reset mechanisms have been really _seriously_ misbehaving. - Dave ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
