Date: Fri, 20 Oct 2000 14:05:25 +0000 (GMT) From: Matthew Emmerton <matt@gsicomp.on.ca> To: "Andresen,Jason R." <jandrese@mitre.org> Cc: kris@grinz.com, questions@FreeBSD.ORG Subject: Re: ATA 640 bug help Message-ID: <Pine.BSF.4.21.0010201403090.11603-100000@xena.gsicomp.on.ca> In-Reply-To: <39F073E7.62136D7B@mitre.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 20 Oct 2000, Andresen,Jason R. wrote: > kris@grinz.com wrote: > > > > I have the following in dmesg: > > > > atapci0: <CMD 640 ATA controller !WARNING! buggy chip data > > loss possible> irq 14 at device 1.0 on pci0 > > > > I have recently switched to FreeBSD from about 5 - 6 years of > > Linux. I know that the Linux kernel had a bugfix for this but I > > couldn't find anything about it in the FreeBSD kernel config file > > GENERIC or LINT. Is there a bugfix? If so, can you email an href > > (URL) to some info? > > I know there used to be an option "CMD640" that worked around this > problem, but it seems to have gone away in LINT. According to the CVS comments of LINT (aka NOTES), the new ata driver made a bunch of old kernel options (including CMD640) implicit; this means that the driver will automatically enable the CMD640 option if such a controller is detected on the system.\ What the detect message means is that the chipset itself is buggy. The ata drive (and the old 'options CMD640') try their best to work around the bugs. -- Matthew Emmerton GSI Computer Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0010201403090.11603-100000>