:> it broke again as I recompiled my system yesterday (This was the first
:> time after it had been fixed, so I don't know when exactly it broke).
:>
:> Harddisks: Western Digital Caviar (2.0 GB), non-DMA and
:> Western Digital Caviar (2.5 GB), DMA-33.
:> Mainboard: Asus P5A-B Super7
:> Chipset: ALi Aladdin V AGPset
:>
:> Taking the UDMA disk out doesn't help. Everything works just
:> fine with the WD driver...
:
:Same here, but with a toshiba laptop disk. I have to comment out a version
:test in ata-disk.c to get it to work.
:
:...
:
:Without this, ata thinks is's an ATA-0 disk and tries to use DMA mode.
:However, it hangs with:
:
:mounting root /dev/ad0s1a
:ata-master: lost disk contact
:ata: resetting devices ..
:
:and never gets to "done" just like you. If I remove the ATA version test and
:just have it look at the "I support UDMA" bit, it runs in UDMA33 mode and
:works fine. I suspect that if it got a CRC error and tried to do a fallback
:that it would hang there too, but I have not seen any.
:
:I think the (plain) DMA code is broken somewhere.
:
:Cheers,
:-Peter
:--
:Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
The thread 'vm_page_remove panic' that Tamiji Homma initiated may be
related. She is getting a panic in the buffer cache subsystem while
using the new ATA driver with softupdates + NFS exported filesystems.
I do not know if it is related, but I can say that I know of no other
vm_page_remove panic related to VM or NFS specifically, and softupdates
is known to stress-test IDE disks.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
