Harald Dunkel wrote:
Using the same disk on kernel 2.4.21 together with the patches released on June 20th the disk worked very stable. I had written about 40 GByte on this disk without a small hiccup.
Since test1 and that 2.4.22-pre1 code are essentially the same in terms of the low level code (EHCI), this suggests a problem higher up the driver stack.
Syslog should also tell you what kind of device you're using. That might help sort things out.
Here is some more syslog with debugging output enabled. Again, I tried to format /dev/sdc1 using mkreiserfs after removing the old partition table and creating a maxsize partition. Since this problem affects file I/O, it is possible that the syslog is incomplete.
Hopefully its OK to send 4 KByte compressed data to this mailing list.
Regards
Harri
syslog.gz
Description: Unix tar archive
