Hi all I am (still) having problems with my system locking up randomly and requiring a hard reset (or even a power off for several seconds). This sometimes does not happen for a few days but sometimes does it every few minutes for a while. The system stops responding - even ctrl-alt-F2/del does not do anything. ctrl-alt-esc returns a corrupt graphics screen and nothing else happens. A hard reset usually works but sometimes the BIOS cannot recognize the IDE0 boot record and I have to power off the box for 20 seconds or so. I am using SuSE 8.1 with the latest athlon kernel (SuSE patched rpm version - k_athlon-2.4.19-167 I think). I have the KT333 VIA chipset with the 8235 southbridge, which has some issues, but that should have been addressed by the patched kernel. Examining /var/log/messages the kernel issues (sometimes, I guess if it has time before it cannot write to the disk at all) errors. Below is a typical set: Mar 8 10:36:59 system001 kernel: hda: status error: status=0x51 { DriveReady SeekComplete Error } Mar 8 10:36:59 system001 kernel: hda: status error: error=0x04 { DriveStatusError } Mar 8 10:36:59 system001 kernel: hda: no DRQ after issuing MULTWRITE Mar 8 10:36:59 system001 kernel: hda: status error: status=0x51 { DriveReady SeekComplete Error } Mar 8 10:36:59 system001 kernel: hda: status error: error=0x04 { DriveStatusError } Mar 8 10:36:59 system001 kernel: hda: no DRQ after issuing MULTWRITE Mar 8 10:36:59 system001 kernel: hda: status error: status=0x51 { DriveReady SeekComplete Error } Mar 8 10:36:59 system001 kernel: hda: status error: error=0x04 { DriveStatusError } Mar 8 10:36:59 system001 kernel: hda: no DRQ after issuing MULTWRITE Mar 8 10:36:59 system001 kernel: hda: status error: status=0x51 { DriveReady SeekComplete Error } Mar 8 10:36:59 system001 kernel: hda: status error: error=0x04 { DriveStatusError } Mar 8 10:36:59 system001 kernel: hda: no DRQ after issuing WRITE Mar 8 10:36:59 system001 kernel: ide0: reset: success After the ide0 reset is when the system totally locks I have tried a different HD and the same thing occurs. The system is fine under Windows (using a different HD in a caddy - and I have tried swapping the caddies too!). Does anyone have any ideas? I have turned off ACPI APIC APM - anything else I should try turning off? I have the DMA mode to "force off" in Yast2. Yours -- Ray