Via apollo KX133 ide bug in 2.4.x
I'm sorry I can't be more descriptive than that, but there aren't any errors ever displayed. What happened was after about a day of uptime, I began seeing IO errors when trying to access files. I realized that the IO errors occurred on any file I had created. I rebooted since the computer became impossible to use and fsck removed everything that I had created since upgrading to the release kernel. This is all on ext2fs. I tried making bootdisks but they all showed up as being bad. I tried copying files to another ext2fs but upon fsck, they too were all removed due to corruption. These ext2fs' were not created by the release kernel. I had to go back to 2.4.0-test11 before the kernel would write to the fs correctly. For the record, I disabled DMA in the kernel and i'm compiling for athlon using gcc 2.95.3. I saw the same thing happen
though when I booted for a kernel compiled for Pentium 2. Since
reverting back to 2.4.0-test11, however, no FS corruption has been observed. Anyone have any idea what this is about? i'm compiling with the same options between kernels but 2.4.x (release and newer) do not seem to be able to write to the ext2fs correctly. Could this be because
it was formatted by a 2.2.x kernel? Anyone using this chipset I would
caution to have backups ready when using it with 2.4.x, as I lost hundreds of files to it. Also, no errors were reported anywhere, IO errors when trying to stat dirs just started appearing after a couple days uptime ...then they would occur whenever you wrote to the FS. Even
after a reboot. If you need any extra iinfo about kernel options and
computer config, just ask.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/
Quoted 16 lines · safemode
I'm sorry I can't be more descriptive than that, but there aren't any errors ever displayed. What happened was after about a day of uptime, I began seeing IO errors when trying to access files. I realized that the IO errors occurred on any file I had created. I rebooted since the computer became impossible to use and fsck removed everything that I had created since upgrading to the release kernel. This is all on ext2fs. I tried making bootdisks but they all showed up as being bad. I tried copying files to another ext2fs but upon fsck, they too were all removed due to corruption. These ext2fs' were not created by the release kernel. I had to go back to 2.4.0-test11 before the kernel would write to the fs correctly. For the record, I disabled DMA in the kernel and i'm compiling for athlon using gcc 2.95.3. I saw the same thing happen
though when I booted for a kernel compiled for Pentium 2. Since
reverting back to 2.4.0-test11, however, no FS corruption has been observed. Anyone have any idea what this is about? i'm compiling with the same options between kernels but 2.4.x (release and newer) do not
Quoted 9 lines
seem to be able to write to the ext2fs correctly. Could this be because
it was formatted by a 2.2.x kernel? Anyone using this chipset I would
caution to have backups ready when using it with 2.4.x, as I lost hundreds of files to it. Also, no errors were reported anywhere, IO errors when trying to stat dirs just started appearing after a couple days uptime ...then they would occur whenever you wrote to the FS. Even
after a reboot. If you need any extra iinfo about kernel options and
computer config, just ask.
I think I'm suffering the same thing on my new Asus A7V. Yesterday I got a single "error in bitmap, remounting read only" type error, and today I got some files in /tmp that returned I/O error when stat()ed. I do have DMA enabled, but only UDMA33. I've done several kernel compiles with no problems at all so looks like something is on the edge. Think I might go back to 2.2.x for a bit and see what happens, or maybe just remove the VIA driver :-((.
P.
I've attached lspci -vxxx output, and kernel config, in case anyone is investigating.
/dev/hda is Seagate ST330621A.
----------VIA BusMastering IDE Configuration----------------
Driver Version: 2.1e South Bridge: VIA vt82c686a rev 0x22 Command register: 0x7 Latency timer: 32 PCI clock: 33MHz Master Read Cycle IRDY: 0ws Master Write Cycle IRDY: 0ws
FIFO Output Data 1/2 Clock Advance: off
BM IDE Status Register Read Retry: on
Max DRDY Pulse Width: No limit
-----------------------Primary IDE-------Secondary IDE------
Read DMA FIFO flush: on on End Sect. FIFO flush: on on Prefetch Buffer: on on Post Write Buffer: on on FIFO size: 8 8 Threshold Prim.: 1/2 1/2 Bytes Per Sector: 512 512 Both channels togth: yes yes -------------------drive0----drive1----drive2----drive3----- BMDMA enabled: yes no no no Transfer Mode: UDMA DMA/PIO DMA/PIO DMA/PIO Address Setup: 30ns 120ns 30ns 120ns Active Pulse: 90ns 330ns 90ns 330ns Recovery Time: 30ns 270ns 30ns 270ns Cycle Time: 60ns 600ns 120ns 600ns Transfer Rate: 33.0MB/s 3.3MB/s 16.5MB/s 3.3MB/s
Quoted 9 lines · Peter Horton
I think I'm suffering the same thing on my new Asus A7V. Yesterday I got a single "error in bitmap, remounting read only" type error, and today I got some files in /tmp that returned I/O error when stat()ed. I do have DMA enabled, but only UDMA33. I've done several kernel compiles with no problems at all so looks like something is on the edge. Think I might go back to 2.2.x for a bit and see what happens, or maybe just remove the VIA driver :-((.
I apologise for following up my own E-mail, but there is something I'm missing here (maybe a whole lot of something). Anyone know how come we're seeing silent corruption ... I thought this UDMA stuff was all checksummed ? If there error is outside the data I assume the driver would notice ?
P.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/
Quoted 11 lines · Peter Horton
Quoted 9 lines · Peter Horton
I think I'm suffering the same thing on my new Asus A7V. Yesterday I got a single "error in bitmap, remounting read only" type error, and today I got some files in /tmp that returned I/O error when stat()ed. I do have DMA enabled, but only UDMA33. I've done several kernel compiles with no problems at all so looks like something is on the edge. Think I might go back to 2.2.x for a bit and see what happens, or maybe just remove the VIA driver :-((.
Quoted 6 lines
I apologise for following up my own E-mail, but there is something I'm missing here (maybe a whole lot of something). Anyone know how come we're seeing silent corruption ... I thought this UDMA stuff was all checksummed ? If there error is outside the data I assume the driver would notice ?
P.
The thing is, even with UDMA disabled in the kernel, I still see the corruption with 2.4.x (release) and above. Anything written while using the kernel is
corrupted. Much of the stuff will read fine (files) ... but I believe
directories get the IO error immediately and some files do also. Everything is seen as corrupted when you fsck a partition where this kernel has been run and
created files on. This is a silent corruption without any errors reported and
I've only tested it on ext2. You cannot create FS's with these kernels (at least on the VIA chipsets) since they too are corrupted (note, only tested ext2
fs). I did disable UDMA everywhere and still saw it happen, this problem is
not present in older 2.4.0-test kernels so it's something in the late pre-release stage and into the release stage.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/
Quoted 20 lines · safemode
Quoted 11 lines · Peter Horton
Quoted 9 lines · Peter Horton
I think I'm suffering the same thing on my new Asus A7V. Yesterday I got a single "error in bitmap, remounting read only" type error, and today I got some files in /tmp that returned I/O error when stat()ed. I do have DMA enabled, but only UDMA33. I've done several kernel compiles with no problems at all so looks like something is on the edge. Think I might go back to 2.2.x for a bit and see what happens, or maybe just remove the VIA driver :-((.
Quoted 6 lines
I apologise for following up my own E-mail, but there is something I'm missing here (maybe a whole lot of something). Anyone know how come we're seeing silent corruption ... I thought this UDMA stuff was all checksummed ? If there error is outside the data I assume the driver would notice ?
P.
Quoted 11 lines
The thing is, even with UDMA disabled in the kernel, I still see the corruption with 2.4.x (release) and above. Anything written while using the kernel is
corrupted. Much of the stuff will read fine (files) ... but I believe
directories get the IO error immediately and some files do also. Everything is seen as corrupted when you fsck a partition where this kernel has been run and
created files on. This is a silent corruption without any errors reported and
I've only tested it on ext2. You cannot create FS's with these kernels (at least on the VIA chipsets) since they too are corrupted (note, only tested ext2
fs). I did disable UDMA everywhere and still saw it happen, this problem is
not present in older 2.4.0-test kernels so it's something in the late pre-release stage and into the release stage.
Do you have the via driver compiled in? If yes, try without, if no, try with it ...
Signature · 6 lines
Vojtech Pavlik SuSE Labs - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] Please read the FAQ at http://www.tux.org/lkml/
Quoted 33 lines · Vojtech Pavlik
Quoted 20 lines · safemode
Quoted 11 lines · Peter Horton
Quoted 9 lines · Peter Horton
I think I'm suffering the same thing on my new Asus A7V. Yesterday I got a single "error in bitmap, remounting read only" type error, and today I got some files in /tmp that returned I/O error when stat()ed. I do have DMA enabled, but only UDMA33. I've done several kernel compiles with no problems at all so looks like something is on the edge. Think I might go back to 2.2.x for a bit and see what happens, or maybe just remove the VIA driver :-((.
Quoted 6 lines
I apologise for following up my own E-mail, but there is something I'm missing here (maybe a whole lot of something). Anyone know how come we're seeing silent corruption ... I thought this UDMA stuff was all checksummed ? If there error is outside the data I assume the driver would notice ?
P.
Quoted 11 lines
The thing is, even with UDMA disabled in the kernel, I still see the corruption with 2.4.x (release) and above. Anything written while using the kernel is
corrupted. Much of the stuff will read fine (files) ... but I believe
directories get the IO error immediately and some files do also. Everything is seen as corrupted when you fsck a partition where this kernel has been run and
created files on. This is a silent corruption without any errors reported and
I've only tested it on ext2. You cannot create FS's with these kernels (at least on the VIA chipsets) since they too are corrupted (note, only tested ext2
fs). I did disable UDMA everywhere and still saw it happen, this problem is
not present in older 2.4.0-test kernels so it's something in the late pre-release stage and into the release stage.
Quoted 3 lines
Do you have the via driver compiled in? If yes, try without, if no, try with it ...
Okay, I bit the bullet and rebuilt the kernel with the VIA driver back in. As a test I created one 128M file from /dev/urandom and copied it 26 times. Out of the 26 copies one was damaged. The damage was just one page (eight sectors), aligned on a page boundary. The damaged section bore no resemblance at all to what it should have been. Is it just a coincidence that it looks like an incorrect page got written out ?
P.
PS - just to rule out other factors I ran memtest86 on this box for 10 hours with no error. It's not an overclock either.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/