ATA Patch #6

[YONETANI Tomokazu]

On Wed, Nov 24, 2004 at 11:18:09PM +0900, YONETANI Tomokazu wrote:
> I'm going to try other DragonFly machines to make sure
> that this is the only box that has the problem.

Here's part of dmesg message from another DragonFly machine
(my laptop I mainly use):

|ad0: success setting UDMA4 on Acer chip
|ar: FreeBSD check1 failed
|ad0: <TOSHIBA MK6021GAS/GA024A> ATA-5 disk at ata0-master
|ad0: 57231MB (117210240 sectors), 116280 C, 16 H, 63 S, 512 B
|ad0: 16 secs/int, 1 depth queue, UDMA66
|ad0: piomode=4 dmamode=2 udmamode=5 cblid=1
|bootdev: a0200000 type=0 unit=0 slice=2 part=0 major=3
|Mounting root from ufs:/dev/ad0s1a
|ad0s1: type 0xa5, start 63, end = 96164207, size 96164145 : OK
|ad0s2: type 0x7, start 96164208, end = 117209231, size 21045024 : OK
|start_init: trying /sbin/init
|ad0: READ command timeout tag=0 serv=0 status 50 dmastatus 00 - resetting
|ata0: resetting devices .. ata0: mask=03 ostat0=50 ostat2=00
|ad0: ATAPI 00 00
|ata0-slave: ATAPI 00 00
|ata0: mask=03 stat0=50 stat1=00
|ad0: ATA 01 a5
|ata0: devices=01
|ad0: success setting UDMA4 on Acer chip
|done
|ad0: READ command timeout tag=0 serv=0 status 50 dmastatus 00 - resetting
|ata0: resetting devices .. ata0: mask=03 ostat0=50 ostat2=00
|ad0: ATAPI 00 00
|ata0-slave: ATAPI 00 00
|ata0: mask=03 stat0=50 stat1=00
|ad0: ATA 01 a5
|ata0: devices=01
|ad0: success setting UDMA4 on Acer chip
|done

It didn't lock up, but reading from the disk always timed out.
If I change the mode to ATA33 or one of PIO mode, the timeout doesn't
occur. The drive can do ATA100 but the controller only supports up to ATA66,
Unpatched ata driver has no problem anyway.

I've only tested ATA Patch #6, so I'll try older patches from you later to
determine which version worked and which version didn't.