Date: Wed, 5 Apr 2000 14:56:44 -0400 (EDT) From: Matt Heckaman <matt@ARPA.MAIL.NET> To: Coleman Kane <cokane@one.net> Cc: John Baldwin <jhb@FreeBSD.org>, Warner Losh <imp@village.org>, FreeBSD-STABLE <freebsd-stable@FreeBSD.org>, lioux@uol.com.br Subject: Re: How stable is the ATA code? Message-ID: <Pine.BSF.4.21.0004051453290.50365-100000@epsilon.lucida.qc.ca> In-Reply-To: <20000405145559.A6856@evil.2y.net>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 And to add one of those annoying "me too" posts, I absolutely cannot get my setup to work. It's as follows: 4.0-STABLE as of April 3 2000 atapci0: <Intel PIIX4 ATA33 controller> port 0xf000-0xf00f at device 7.1 on pci0 ad0: 8063MB <WDC AC38400L> [16383/16/63] at ata0-master using UDMA33 ad1: 1549MB <WDC AC21600H> [3148/16/63] at ata0-slave using WDMA2 acd0: CDROM <MATSHITA CR-589> at ata1-master using WDMA2 ad0 and acd0 work fine, ad1 does not. It bombs with the following error: ad1: HARD READ ERROR blk# 0ata0-slave: WARNING: WAIT_READY active=ATA_ACTIVE_ATA ad1: HARD READ ERROR blk# 0 status=59 error=04 ad1: DMA problem fallback to PIO mode ad1: reading primary partition table: error reading fsbn 0 sysctl settings: hw.atamodes: dma,pio,dma,---, I know the drive is fine, it works under the wd? drivers but that's a less than ideal situation. My original posting about this got a reply from Jordon saying that it was the rollover reason for 4.0-RELEASE, but the bug is still there and I'm at a loss and quite frustrated. Regards, Matt On Wed, 5 Apr 2000, Coleman Kane wrote: : Date: Wed, 5 Apr 2000 14:55:59 -0400 : From: Coleman Kane <cokane@one.net> : To: John Baldwin <jhb@FreeBSD.org> : Cc: Warner Losh <imp@village.org>, freebsd-stable@FreeBSD.org, : lioux@uol.com.br : Subject: Re: How stable is the ATA code? : : You are incorrect. The 586B is the southbridge which incorporates the ATA : controller, PCI-ISA bridge, ACPI interface, and various other functions. The : original 82c586 was part of the non-Super 7 VP3 chipset that was the first : Socket7 AGP. The 82c586A was a laeter revision of the southbridge, and the : 82c586B is the latest and it's been around for awhile. The notation 82C586x : denotes x as a dynamic variable, which can exist or not, and can be whatever. : The featureset of the original 586 is very close to that of the newest 586B. : : --cokane : : John Baldwin had the audacity to say: : > chip0: <VIA 82C597 (Apollo VP3) system controller> rev 0x04 on pci0.0.0 : > chip1: <VIA 82C598MVP (Apollo MVP3) PCI-PCI bridge> rev 0x00 on pci0.1.0 : > chip2: <VIA 82C586 PCI-ISA bridge> rev 0x41 on pci0.7.0 : > ide_pci0: <VIA 82C586x (Apollo) Bus-master IDE controller> rev 0x06 on pci0.7.1 : > chip3: <VIA 82C586B ACPI interface> rev 0x10 on pci0.7.3 : > : > Perhaps the 82C586x is the problem child? Note that the -B chip is the power : > management chip. :) : > : > > Warner : : : To Unsubscribe: send mail to majordomo@FreeBSD.org : with "unsubscribe freebsd-stable" in the body of the message : Matt Heckaman matt@arpa.mail.net http://www.lucida.qc.ca -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.1 (FreeBSD) Comment: http://www.lucida.qc.ca/pgp iD8DBQE464xtdMMtMcA1U5ARAovLAKCcmZQFfYAVNlZwL6Aw1AfH7RQmHgCgk5ZI MgOx6FDoyEPbH152RogKbpw= =gpQi -----END PGP SIGNATURE----- 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?Pine.BSF.4.21.0004051453290.50365-100000>