[Bug 88746] Re: ehci_hcd module causes I/O errors in USB 2.0 devices

2008-12-09 Thread David Becker
SNAFU I've installed Fedora 10 Live CD to USB flash media. Installed the i686 as well as the x86_64 version. Installed on an nforce 430 platform and an SB600. Installed to Kingston and Sandisk USB drives and to Sandisk SD card. Every combination here is botched. Decreasing max_sectors seems t

[Bug 88746] Re: ehci_hcd module causes I/O errors in USB 2.0 devices

2008-12-09 Thread David Becker
I don't believe this an Alcor chipset. Bear in mind it occurs with an SB600 (AMD/ATI) and nForce based system. Following lspci/lsusb output is when running the system from harddisk (I'll see if there's a 'diff' between booting from flash and (normal) hard disk booting). David ** Attachment added

[Bug 88746] Re: ehci_hcd module causes I/O errors in USB 2.0 devices

2008-12-09 Thread David Becker
** Attachment added: "lsusb -v" http://launchpadlibrarian.net/20324625/lsusb -- ehci_hcd module causes I/O errors in USB 2.0 devices https://bugs.launchpad.net/bugs/88746 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bug

[Bug 88746] Re: ehci_hcd module causes I/O errors in USB 2.0 devices

2008-12-09 Thread David Becker
Whoops, the previous 'lsusb -v' is secretly just an 'lsusb'. Here's the verbose version. ** Attachment added: "lsusb -v" http://launchpadlibrarian.net/20324739/lsusb -- ehci_hcd module causes I/O errors in USB 2.0 devices https://bugs.launchpad.net/bugs/88746 You received this bug notificati

[Bug 88746] Re: ehci_hcd module causes I/O errors in USB 2.0 devices

2008-12-09 Thread David Becker
BTW, aforementioned output for lspci and lsusb is for the SB600 (laptop) based system. No USB flash media was attached. I've included the output for 'lsusb -v' once again, only now with the (Kingston) USB media attached. I can't reach the other (nforce based) system at the moment, but... ... the '

[Bug 88746] Re: ehci_hcd module causes I/O errors in USB 2.0 devices

2008-12-09 Thread David Becker
Maybe it's better to skip that MSI board. One of the first things I noticed was "Genesys Logic". Didn't various species go to war over Genes(i|y)s in Star Trek movies? Christopher Lloyd described it as "The Genesis Torpedo". Anyway, max_sectors was 240 for the flash device. I set that to 64, the

[Bug 88746] Re: ehci_hcd module causes I/O errors in USB 2.0 devices

2008-12-09 Thread David Becker
** Attachment added: "MSI K9A2 CF lspci -vvnn" http://launchpadlibrarian.net/20325771/lspci2 -- ehci_hcd module causes I/O errors in USB 2.0 devices https://bugs.launchpad.net/bugs/88746 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 88746] Re: ehci_hcd module causes I/O errors in USB 2.0 devices

2008-12-10 Thread David Becker
I also think there's two bugs going on here. Note however, I also use a WD Passport (320GB) drive (on the SB600, the nforce, the MSI and Proliants) and never have had this problem. I transfer large (and many) files to and from the Passport drive and USB flash media with no problems. It's only with

[Bug 88746] Re: ehci_hcd module causes I/O errors in USB 2.0 devices

2008-12-21 Thread David Becker
I seem to have solved (i.e., worked around) my previous issues. Note that the "lost page write" errors I'm getting are likely due to the lvm copyonwrite store I'm using. When the store overflows, all kinds of strange things happen, but this is probably unrelated to the issues going on here. "df" ou

[Bug 88746] Re: ehci_hcd module causes I/O errors in USB 2.0 devices

2008-12-21 Thread David Becker
Sorry for the length ;) >From Wikipedia: "On Linux systems the kernel calls out to udev which in turn provides notifications to HAL through a standard Unix domain socket whenever a device plugs in." So there's communication triggered by the device connecting, which is relayed through udev on to h

[Bug 88746] Re: ehci_hcd module causes I/O errors in USB 2.0 devices

2008-12-21 Thread David Becker
The kernel probably does it right (one space). But the kernel has to communicate with udev which communicates with hal (transmission across several spaces). device_connect . udev_called . hald_reads_connect_from_socket . hald_mounts_device ... What if the device disconnects between hald receiving