Date: Fri, 31 May 2002 14:19:48 -0700 From: "Bruce A. Mah" <bmah@FreeBSD.ORG> To: Matthias Andree <matthias.andree@gmx.de> Cc: freebsd-stable@FreeBSD.ORG Subject: Re: 4.6-RELEASE delayed Message-ID: <200205312119.g4VLJm7d008902@intruder.bmah.org> In-Reply-To: <m3d6vc3vqg.fsf@merlin.emma.line.org> References: <200205311652.g4VGq5YV004136@intruder.bmah.org> <m3d6vc3vqg.fsf@merlin.emma.line.org>
next in thread | previous in thread | raw e-mail | index | archive | help
If memory serves me right, Matthias Andree wrote: > It says ata(4) tags problems were related to motherboard-based ATA > channels. I see that S=F8ren's patch to fix the panic on boot that I > observed has now been merged into 4-STABLE, however, it seems as though > the "timeout and fall-back to PIO" issue is still unfixed in 4-STABLE. This is my understanding of the state of things too. (I haven't=20 experienced this personally...I'm mostly a SCSI person.) > My main board, a Gigabyte 7ZX-R rev. 1.0, offers four ATA channels. Two > are driven by the south bridge, VIA KT133 (VT82C686 stuff), the other > two are driven by a Promise PDC-20265R (in UDMA/100 mode). IIRC, this > Promise chip is in the "doesn't to tags, but freezes" blacklist. VIA > chips are not blacklisted, and AFAICS, tagged queueing not working on m= y > system is a regression over 4.5-RELEASE which had working tagged > queueing. "blacklist" isn't really the right word here (it implies some=20 deliberate malice). I get your point though, you have working tagged=20 queueing on 4.5 but not on 4.6. > S=F8ren said he was able to reproduce the timeout problem with tags, an= d > we should expect a fix "real soon now". This is the only list I follow, > but I haven't yet seen anything ata-related since. What's the release > engineering team's opinion on this ata issue? Will 4.6 be delayed until > the tagged stuff is fixed? Will 4.6 ship with ata tagged stuff disabled > altogether? Or will 4.6 ship with ata as it is today, with the risk tha= t > it breaks some systems 4.5 ata did work on? After much discussion between soren and murray, the conclusion was that soren probably won't be able to fix this in time for the release. (We offered to hold it a few days.) So unless something miraculous happens in the next few days, 4.6-RELEASE will ship with the ata(4) system as it sits today. Please note that: ATA tagged queueing is disabled by default (you need to enable it explicitly). There's also only a few drives (as I understand it) that even support this feature. I tried to capture this in the release notes for 4.6. Yes, it sucks if you happen to use this feature. The alternative (according to soren) is to back out the entire MFC of the ata(4) system, which means we'd lose support for new controllers, atacontrol(8), lots of ATA raid support, and other bugfixes and features I've lost track of. We thought this was a lose, so we're proceeding. Holding up the release indefinitely is not really an alternative. Our calendar from 2002 includes the following releases and snapshots: 4.5-RELEASE, 5.0-DP1, 4.6-RELEASE, 5.0-DP2, 4.7-RELEASE, 5.0-RELEASE. Put another way, the same people trying to get 4.6-RELEASE out the door now are going to try to bring the 5.0-DP2 snapshot to you twenty-six days from today. [1] Cheers, Bruce. [1] Down, not across. 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?200205312119.g4VLJm7d008902>