Date: Fri, 01 Feb 2002 13:52:29 +0100 From: Matthias Andree <ma@dt.e-technik.uni-dortmund.de> To: freebsd-stable@freebsd.org Subject: Re: 4.4/4.5-STABLE and ATA tags? Message-ID: <m3sn8lxt2q.fsf@emma1.emma.line.org> In-Reply-To: <m3sn8lo4wk.fsf@emma1.emma.line.org> (Matthias Andree's message of "Fri, 01 Feb 2002 11:47:07 %2B0100") References: <m3sn8lo4wk.fsf@emma1.emma.line.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Matthias Andree <ma@dt.e-technik.uni-dortmund.de> writes: > Is there any workaround possible around the Promise 20265 lock-up bugs > with tagged queueing? Does the chip need to "support" queueing after > all? (In the meanwhile, I'll hack up 4.5-STABLE's ad_tagsupported and > see if tagged queueing on the WDC eats my data.) OK, I whitelisted that driver for tagged queueing on 4.5-RELEASE, here's what it reports on boot -v: ata0-master: success setting UDMA4 on VIA chip Creating DISK ad0 ad0: <WDC AC420400D/J58OA30K> ATA-4 disk at ata0-master ad0: 19470MB (39876480 sectors), 39560 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 32 depth queue, tagged UDMA66 ad0: piomode=4 dmamode=2 udmamode=4 cblid=1 ad0: 19470MB <WDC AC420400D> [39560/16/63] at ata0-master tagged UDMA66 However, tagged queueing does not work quite right: ata0: resetting devices .. ata0: mask=01 ostat0=51 ostat2=00 ata0-master: ATAPI probe a=00 b=00 ata0-slave: ATAPI probe a=00 b=00 ata0: mask=01 status0=50 status1=00 ata0-master: ATA probe a=01 b=a5 ata0: devices=01 ad0: invalidating queued requests ata0-master: success setting UDMA4 on VIA chip done ad0: WRITE command timeout tag=1 serv=0 - resetting ad0: invalidating queued requests ata0: resetting devices .. ata0: mask=01 ostat0=51 ostat2=00 ata0-master: ATAPI probe a=00 b=00 ata0-slave: ATAPI probe a=00 b=00 ata0: mask=01 status0=50 status1=00 ata0-master: ATA probe a=01 b=a5 ata0: devices=01 ad0: invalidating queued requests ata0-master: success setting UDMA4 on VIA chip done ad0: no request for this tag=3?? ad0: invalidating queued requests ad0: no request for this tag=0?? Is this a problem with FreeBSD or with the drive? I read in the archives that IBM IC35L... had troubles in 4.5-PRE, and I tend to believe that IBM don't break all their tagged queueing firmware. Any help appreciated. -- Matthias Andree "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?m3sn8lxt2q.fsf>