On Sun, 5 Jun 2005, Heitzso wrote: > At first we pulled the hub but still had the problem. > Then compiled and ran 2.6.12-rc5 with patches noted > below and the USB2 storage device now seems to be > working. On the other hand, we've only moved about > 35G (3 DV files) so far. I'll post a follow up note if things > break while running with the patches, but, for now, > hopeful that everything is fixed. THANKS! > > It is hard to find out what the actual device is in > a store box item, e.g. PCI USB card. Could someone post > a couple of names of card/model that would have the > mentioned NEC chip set? If current setup breaks > that's my next move. > > Pieter, cc'ing you because these patches may solve > the problem you researched awhile back and wrote up > on your web page. > > Alan, from my perspective, if your patches fix this > problem then those patches belong in the production > kernel ASAP, i.e. 2.6.12. If not 2.6.12 official, then all > of the distros should roll the patch in. The bug > (and I understand the problem is in out-of-spec hardware) > is nasty when it bites. > > What we are doing: > turn on usb2 drive > it auto mounts (ubuntu) > umount it > fsck.ext3 -f it > mount it > cp -p files over to it > umount it > fsck.ext3 -f it > if it is clean then rm the files that were copied > etc. > Have to until we've managed to move 3 or 4 hundred G > back and forth without a problem. Then I'll start to relax. > This is a hassle. But we cannot afford to lose the files. > If an enterprise got bit by this problem and lost data > they aren't going to leave Linux on their system. Hence > my urging the kernel gods to roll the patch in quickly. > > And, thanks again for your help.
I'm glad the patches seem to help on your system, but like you say, it's too soon to be sure. Some people have found those patches don't really make much difference, or they help some but not enough. As for when the patches will get included in the kernel -- that's out of my hands. I've submitted them to Matt Dharm, the maintainer for the usb-storage driver. When he decides they are safe and effective, he will forward them to Greg Kroah-Hartman, the overall USB maintainer. In turn, Greg will send them in for use in the -mm kernel series for some time before they get accepted into the "official" kernel. That's why I said they might make it into 2.6.13. It would be great if we could figure out why so many devices seem to have these problems, especially when running at high speed. It's all very well to chalk things up to "hardware incompatibility" or "out-of-spec hardware", but Linux really ought to be as reliable as Windows when it comes to questionable devices. Unfortunately so far these problems have managed to avoid bothering anyone with the expensive equipment needed to perform a thorough analysis of the hardware issues. If you're interested, take a look at this message: https://lists.one-eyed-alien.net/pipermail/usb-storage/2005-March/001504.html It illustrates the kind of hardware problems that crop up when vendors skimp on the proper support components. Alan Stern ------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput a projector? How fast can you ride your desk chair down the office luge track? If you want to score the big prize, get to know the little guy. Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20 _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
