>From another post: >>There was a change made to the ehci-hcd timeout for port resets, just >>before 2.6.12 was released. Try using 2.6.12 and see if things improve. >>Alan Stern
And from this thread: >> This is consistent with your computer's USB controller not working. The >> best way to verify it would be to plug the same devices (using the same >> cables!) into another computer and get no errors. >>>> Alan Stern Unfortunately, I don't have another linux box to test against... Seems like I'm not the only one with USB controller issues. Kinda stinks that a brand-new MB would have these problems. Is there any tiny little chance that a new kernel version might help (2.6.12)? Steve ============================================ On 6/24/05, Steve Listopad <[EMAIL PROTECTED]> wrote: > [forgot to reply-all to send to list...] > > Dang. That's bad news. > > Would there be any chance of a BIOS update "fixing" the USB controller? > > By the way, wen I was testing with the external HD, and flipping > between USB and firewire... well... the computer froze up again early > this morning after doing backups to the HD via the firewire > connection... > > Would anyone happen to know if this is a known issue with my MB (MSI > K8N Neo4 Platinum/SLI)? > > Steve > > > On 6/24/05, Alan Stern <[EMAIL PROTECTED]> wrote: > > On Thu, 23 Jun 2005, Steve Listopad wrote: > > > > > Now, for the latest testing: > > > > > > I had a revelation that I could use my external Western Digital HD to > > > test things; hadn't thought > > > about it before, because I use firewire, but the case has both USB 2.0 > > > and Firewire conntections. > > > Note that I had the HD working fine on my FC1 box (2.4.x kernel) and > > > USB 2.0. Ironic that back > > > then, I couldn't get firewire working... > > > > > > At any rate, Alan stated that there wasn't much to do without a > > > "smoking gun," so I'm hoping that > > > the snippets of my logs below are just that... Side note: I like the > > > "badness" message; reminds > > > me of when my inkjet printer ran out of ink, and the logs clearly and > > > concisely stated that > > > something was on fire :) > > > > > > Note that nothing was ever mounted in /media when attempting to plug > > > in anything in the USB > > > 2.0 ports; It did show up both times in my diagnostic step #2 above. > > > > > > ---------------------------------------------------------------------------------------------- > > > Attempt to plug in WD external USB Hard Drive to same USB port that SD > > > Card reader fails in > > > ---------------------------------------------------------------------------------------------- > > > > > > Jun 23 19:46:07 mybox kernel: usb 1-3: new high speed USB device using > > > ehci_hcd and address 4 > > > Jun 23 19:46:12 mybox kernel: usb 1-3: khubd timed out on ep0out > > > Jun 23 19:46:17 mybox kernel: usb 1-3: khubd timed out on ep0out > > > Jun 23 19:46:17 mybox kernel: usb 1-3: device not accepting address 4, > > > error -110 > > > Jun 23 19:46:17 mybox kernel: usb 1-3: new high speed USB device using > > > ehci_hcd and address 5 > > > Jun 23 19:46:22 mybox kernel: usb 1-3: khubd timed out on ep0out > > > Jun 23 19:46:22 mybox kernel: usb 1-3: device not accepting address 5, > > > error -71 > > > Jun 23 19:49:17 mybox fstab-sync[12880]: removed mount point > > > /media/ieee1394disk for /dev/sdb1 > > > Jun 23 19:49:38 mybox kernel: usb 1-3: new high speed USB device using > > > ehci_hcd and address 7 > > > Jun 23 19:49:43 mybox kernel: usb 1-3: khubd timed out on ep0out > > > Jun 23 19:49:43 mybox kernel: usb 1-3: can't set config #1, error -110 > > > Jun 23 19:49:43 mybox kernel: usb 1-3: new high speed USB device using > > > ehci_hcd and address 8 > > > Jun 23 19:49:48 mybox kernel: usb 1-3: khubd timed out on ep0out > > > Jun 23 19:49:48 mybox kernel: usb 1-3: can't set config #1, error -110 > > > Jun 23 19:49:48 mybox kernel: usb 1-3: string descriptor 0 read error: -19 > > > Jun 23 19:49:48 mybox kernel: usb 1-3: new high speed USB device using > > > ehci_hcd and address 9 > > > > This is consistent with your computer's USB controller not working. The > > best way to verify it would be to plug the same devices (using the same > > cables!) into another computer and get no errors. > > > > Alan Stern > > > > > > > -- > > steve > [EMAIL PROTECTED] > -- steve [EMAIL PROTECTED] ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
