> I got severe filesystem corruption on an Sii3112 system (Supermicro
> E7505 with 2 onboard SiI3112) but I later memtested the machine and
> found bad ram, so I dont think it is a valid example of corruption.
> However I am still slightly suspicious. Did you have
The memory is stable, no problems in memtest.
> echo "max_kb_per_request:15" > /proc/ide/hdXX/settings
> set for the relevant drives? This is a known bug (I didnt have this
> either, another reason why this is not a valid datapoint...)
These were not set when the error occured. I found this option after the
crash somewhere on the net, but I can't find any references to it on
google at the moment :( Can it cause that severe filesystem corruption ?
Was DMA enabled on your system, and what drives did you use ?
I tested several firmware revisions, disabled mmio in the driver,
nothing helped. No DMA at boot, and the crash is easy to reproduce, for
example:
console1: dd if=/dev/hda of=/dev/null
console2: hdparm -X66 -d1 /dev/hda
result without max_kb_per_request:
---
/dev/hda:
setting using_dma to 1 (on)
blk: queue c0468b00, I/O limit 4095Mb (mask 0xffffffff)
setting xfermode to 66 (UltraDMA mode2)
hda: dma_intr: status=0x58 { DriveReady SeekComplete DataRequest }
hda: dma_intr: status=0xd0 { Busy }
hda: DMA disabled
--
result with max_kb_per_request:
---
/dev/hda:
setting using_dma to 1 (on)
blk: queue c0468b00, I/O limit 4095Mb (mask 0xffffffff)
setting xfermode to 66 (UltraDMA mode2)
hda: dma_timer_expiry: dma status = 0x21
hda: timeout waiting for DMA
hda: timeout waiting for DMA
hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
--
The system hangs and nothing is written to syslog.
I don't know where to look next.
--
Adriaan Peeters <apeeters@lashout.net>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/