Dave,
> Are you sure nothing interesting happened earlier? I
> recognize that usb-storage doesn't normally tell you
> when things go strange ... and storage debug messages
> give so much data that they change i/o timings in
> significant ways, hiding bugs.
Yes, the previous message in all logs is that of reiserfs checking the
transaction log.
> Clearly the fault recovery code should not oops. It's
> not clear from what you've said what the fault is; or
> whether it's avoidable.
I think the oops occurs in reiserfs, and is certainly a secondary
problem.
> Ksymoops info would help. Rule of thumb, don't ever send
> a stack trace without the relevant symbols already decoded.
Thanks for the hint, I'll think of that next time.
> >I can write to the disk for ages without any problems, it's the
> >reading that causes me headaches. I do notice, however, that when I
> >mount the disk read-only (such that the access time isn't updated
> >after every read), the problem occurs much less often. It seems to me
> >that a simultaneous read and write can provoke this fault with
> >relatively high probability.
>
> Curious. This is just one disk? Whose EHCI silicon? Some
> of the VIA hardware seems to really dislike the code paths
> which remove idle entries from the EHCI async schedule ...
> both VT8235 (southbridge) and VT6202 (discrete) have had
> failure modes in those areas. (Hence IAA and I/O watchdogs.)
It's one disk, connected to the EHCI directly or through a USB 2.0 hub
(makes no difference). The EHCI is a VIA southbridge, if I'm not much
mistaken, it's on an ASUS A7V333 mainboard. It has PCI IDs of
1106:3104.
> I'd not be so quick to rule out hardware or thermal issues,
> given that you're driving the hardware so much faster.
The fact that the problem occurs within a minute or so when mounting
the disk read-write and only after half an hour when read-only
suggests that there is something here that is not a thermal issue (the
only writes are the ones that update the access timestamp).
I'm getting a different USB 2.0 enclosure next week, if that shows the
same behaviour, then we can be pretty sure about it not being
hardware-related.
I've just tried running 2.4.20, and it's a lot better: read-only or
read-write doesn't make any difference anymore, and I can go a lot
longer before the error appears. It fails, though, with this message:
ehci-hcd.c: 00:09.2 urb_dequeue e927c740 qh state 1
hcd.c: giveback urb e927c740 status -104 len 0
but takes quite a long time to get there. There is long silence (no
access) before this happens, and the process that's waiting for the
data hangs forever.
How do I enable EHCI logging? If I have the time, I'll play around a
bit more with 2.5.70.
Andras
===========================================================================
Major Andras
e-mail: [EMAIL PROTECTED]
www: http://andras.webhop.org/
===========================================================================
-------------------------------------------------------
This SF.net email is sponsored by: eBay
Get office equipment for less on eBay!
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel