On Mon, 30 Jun 2003, Adam Kessel wrote:

> I will try building 2.4.21 with usb-storage enabled. In the mean time,
> I'm getting a lot of the same problems in 2.5.73, which I have built with
> usb-storage.
> 
> Kernel output from usb-storage for 2.5.73 is here: 
> 
> http://bostoncoop.net/adam/temp/kernel-log-2.5 

I looked at this.  It doesn't show any problems at all.  Did you see 
anything go wrong at the time this log was written?

> The primary problem now seems to be that the process gets stuck when I
> try to unmount drive. If I try to halt or reboot, it gets stuck shutting
> down. Also, the data copied to the drive is sometimes corrupted (causes
> the player to crash and requires reformatting it).  

How about sending the debugging output for when you try to unmount the 
drive?

Don't worry about data corruption for now; it might just be a side-effect 
from this problem.  Or it might be something else entirely unrelated; I've 
heard of at least one device where it turned out the manufacturer 
acknowledged the firmware had bugs that would cause data corruption.

> Also, frequently the drive appears to be full when it's not.  Although
> it's a 128M memory card, it usually maxes out around 60-70M.  

What do you mean, appeared to be full?  What did 'df' show?

> One thing I've noticed is it seems to be write-caching, so that
> operations copying data to the drive appear to happen much faster than
> could over a USB 1.1 connection.  Sometimes running sync also causes the
> process to hang.  

The drive may or may not use write-caching (I can't imagine a memory card
having any use for it), but either way it wouldn't affect the transmission
speed enough to make it appear much faster than the USB max speed.  On the
other hand, Linux itself does plenty of caching.

If you want a good test of the drive's speed, use 'hdparm'.  Or just time 
how long it takes to read a big file off the drive after it has been 
freshly mounted.

> The only way I can successfully reboot or shutdown with umount or sync
> hung is to remove uhci-hcd. This usually causes umount to segfault, and
> then I can shut down. If I try to *remount* the drive at this point or
> reload the uhci-hcd module, the process gets stuck irretrievably.  

Again, debugging output and the kernel log from the segfault would be 
useful.

Alan Stern



-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Reply via email to