Alan Stern wrote: >>> You could try putting a printk() just before the BUG() to display the >>> values of ehci->reclaim and qh->qh_state. Maybe also change the BUG() to >>> >>> >> ehci->reclaim=0 >> qh->qh_state=5 >> > > 5 is QH_STATE_COMPLETING. That explains why the BUG() fires. > > At this point it's beyond me. Monty will have to take it from here. > > >> During boot I get lots of those "Hardware error, end-of-data detected" >> messages, but I've never seen it crash during bootup. >> > > Those messages are from the card reader. It doesn't seem to be working > right. It returns the "end-of-data" error in response to a PREVENT MEDIUM > REMOVAL command Unlike a cdrom, it doesn't have the means to prevent media removal. :-) > and it returns a phase error in response to a READ > command. In spite of the fact that it claims to have a 256 MB card > present. > It has slots for several different cards, all the other slots are empty.
Perhaps it is broken, but interesting as a "stress-test". Linux should not crash because of a bad usb thing, just complain. Helge Hafting ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
