From owner-freebsd-current@FreeBSD.ORG Sun Dec 28 17:49:46 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2D51A16A4CE for ; Sun, 28 Dec 2003 17:49:46 -0800 (PST) Received: from moof.zeroth.org (moof.zeroth.org [203.117.131.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id A8FCF43D2F for ; Sun, 28 Dec 2003 17:49:43 -0800 (PST) (envelope-from jclark@metaparadigm.com) Received: from metaparadigm.com (neon.zeroth.org [203.117.131.24]) (authenticated bits=0) by moof.zeroth.org (8.12.9/8.12.9) with ESMTP id hBT1ndCg051732 for ; Mon, 29 Dec 2003 09:49:40 +0800 (SGT) (envelope-from jclark@metaparadigm.com) Message-ID: <3FEF882E.6080800@metaparadigm.com> Date: Mon, 29 Dec 2003 09:49:34 +0800 From: Jamie Clark User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031107 Debian/1.5-3 X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org References: <86u14cwqrf.wl@bougainvillea.FromTo.Cc> In-Reply-To: <86u14cwqrf.wl@bougainvillea.FromTo.Cc> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Sun, 28 Dec 2003 18:30:48 -0800 Subject: Re: SATA disks on 5.2-CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Dec 2003 01:49:46 -0000 Tatsumi Hosokawa wrote: >atapci2@pci0:31:2: class=0x01018f card=0x24d11458 chip=0x24d18086 rev=0x02 >hdr=0x00 > vendor = 'Intel Corporation' > device = '82801EB (ICH5) SATA Controller' > class = mass storage > subclass = ATA > >Disks sometimes work, and sometimes don't work, and sometimes the >system hangs in boot process (these disks work fine on 4.9-RELEASE). > > FWIW (if a 'me too' is worth anything) I have exactly the same problem with my Intel 865PERL mainboard. Same error messages as below, almost always hangs on boot. Last tested with -CURRENT around 26 Dec. My reason for using the SATA channels was because I had already fully populated PATA - so using legacy mode was not an option. The SATA did work ok in Windows. Solution was found in a 3ware controller. I'd be happy to re-connect and collect some further verbose messages if anyone's interested. -Jamie >Error messages: > > Case 1: > Dec 7 21:52:02 nekodaisuki kernel: ad4: FAILURE - READ_DMA status=51 error=40 > Dec 7 21:52:02 nekodaisuki kernel: ad6: FAILURE - READ_DMA status=51 error=10 > > Case 2: > Dec 8 00:27:48 nekodaisuki kernel: ad4: WARNING - READ_DMA recovered from missing interrupt > Dec 8 00:27:48 nekodaisuki kernel: ad4: FAILURE - READ_DMA status=ff error=0 > Dec 8 00:27:48 nekodaisuki kernel: ad4: timeout sending command=c8 > Dec 8 00:27:48 nekodaisuki kernel: ad4: error issuing DMA command > Dec 8 00:27:48 nekodaisuki kernel: ad4: WARNING - READ_DMA recovered from missing interrupt > Dec 8 00:27:48 nekodaisuki kernel: ad4: FAILURE - READ_DMA status=ff error=0 > > >