< Recap >
== I have had problems with 2.5.10 (first few blocks of the root
== filesystem overwritten) and then went back to 2.5.8 that I had
== used for a while already, but then also noticed corruption there.
== Back at 2.4.17 today..
< Optimistic reply >
= It could very well be that the recent changes could have cured this.
< Reality of today >
Booted a vanilla 2.5.12. It did not succeed in mounting the root
filesystem, but instead wrote zeros over the superblock.
hdb: task_out_intr: error=0x04 { DriveStatusError }
Will try 2.5.13 later.
Andries
[So, 2.5.8 causes very slow corruption, and can be used for
several hours, sometimes days, before something bad happens.
And bad things only happen to disks on HPT366.
On the other hand, 2.5.10 and 2.5.12 fail directly at boot
in precisely the same way and with a disk on the mb.]
% grep _IDE .config | grep -v '#'
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_STROKE=y
CONFIG_BLK_DEV_IDECD=y
CONFIG_BLK_DEV_IDEFLOPPY=y
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
CONFIG_BLK_DEV_IDEDMA_PCI=y
CONFIG_BLK_DEV_IDEDMA=y
-
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/
This archive was generated by hypermail 2b29 : Tue May 07 2002 - 22:00:21 EST