Date: Thu, 18 Apr 2002 11:20:27 -0400 From: <freebsd-current@tcpipbitch.net> To: <sos@freebsd.dk>, "'Alexander Leidinger'" <Alexander@Leidinger.net> Cc: <DougB@FreeBSD.ORG>, <ache@nagual.pp.ru>, <sos@FreeBSD.ORG>, <current@FreeBSD.ORG> Subject: RE: i386 ATA is very broken after sparc64 ATA mega-commit (April 5) Message-ID: <001801c1e6ec$93deb140$0300000a@desktop> In-Reply-To: <200204180918.g3I9IBjC047037@freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
This won't help people using similair drives (in one of my machines) that I am using, I have the same problem in current that I have in RELENG_4, It times out and drops to PIO4 mode after a few min. I dropped "atacontrol mode 0 pio4 none" (I only have the 1 drive on the chain) before the fsck check in /etc/rc to avoid the timeouts and boot normally). I'm sure there is probably a better way to do it, but I'm lazy :) Anyways, it=92s a maxtor drive, I can send someone the drive info if = that will help. I don't have the problem though on my Western Digital ata100 drive in another machine. Jason -----Original Message----- From: owner-freebsd-current@FreeBSD.ORG [mailto:owner-freebsd-current@FreeBSD.ORG] On Behalf Of S=F8ren Schmidt Sent: Thursday, April 18, 2002 5:18 AM To: Alexander Leidinger Cc: DougB@FreeBSD.ORG; ache@nagual.pp.ru; sos@FreeBSD.ORG; current@FreeBSD.ORG Subject: Re: i386 ATA is very broken after sparc64 ATA mega-commit (April 5) It seems Alexander Leidinger wrote: > On 18 Apr, Doug Barton wrote: > > Given the impending 4.6-release, might it make sense to back off ata > > in -stable to the last known-good state? >=20 > We have some time until the code freeze, so give him some days to=20 > track it down. If he is able to fix it: fine, else he can still back=20 > it out. I'll see what I can do, but my time is VERY limitted for the next 2-3 weeks, if I get any spare time at all... However, if its decided to back out whats in -stable, remember that it will bring ATA support back to what was in 4.5, which will severely reduce our chipset support etc, which is alot worse IMNHO. The right solution would be to just disable tagged queing, and state that in the docs, but I'm not the RE@ :) -S=F8ren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?001801c1e6ec$93deb140$0300000a>