From owner-freebsd-hackers@FreeBSD.ORG Sun Oct 10 08:59:37 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0516616A4CE for ; Sun, 10 Oct 2004 08:59:37 +0000 (GMT) Received: from spider.deepcore.dk (cpe.atm2-0-53484.0x50a6c9a6.abnxx9.customer.tele.dk [80.166.201.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5A57343D1F for ; Sun, 10 Oct 2004 08:59:36 +0000 (GMT) (envelope-from sos@DeepCore.dk) Received: from [194.192.25.143] (laptop.deepcore.dk [194.192.25.143]) by spider.deepcore.dk (8.12.11/8.12.10) with ESMTP id i9A8xVRV063352; Sun, 10 Oct 2004 10:59:34 +0200 (CEST) (envelope-from sos@DeepCore.dk) Message-ID: <4168F9E7.9040408@DeepCore.dk> Date: Sun, 10 Oct 2004 10:59:19 +0200 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= User-Agent: Mozilla Thunderbird 0.7.2 (X11/20040802) X-Accept-Language: en-us, en MIME-Version: 1.0 To: miha@ghuug.org References: <200410081937.15068.miha@ghuug.org> <41682D3F.4060902@DeepCore.dk> <200410091843.06854.miha@ghuug.org> In-Reply-To: <200410091843.06854.miha@ghuug.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable X-mail-scanned: by DeepCore Virus & Spam killer v1.4 cc: freebsd-hackers@freebsd.org Subject: Re: ad0: FAILURE - WRITE_DMA X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Oct 2004 08:59:37 -0000 Mikhail P. wrote: > On Saturday 09 October 2004 18:26, S=F8ren Schmidt wrote: >=20 >>Hmm, that means that the drive couldn't find the sector you asked for. >>Now, what has me wondering is that it is the exact sector where we >>switch to 48bit adressing mode. Anyhow, I've just checked on the old >>Maxtor preproduktion 48bit reference drive I have here and it crosses >>the limit with no problems. >>What controller are you using ? not all supports 48bit mode correctly..= >=20 >=20 > There's VIA's motherboard (not sure about the model name). >=20 > Here's info regarding ata controller from dmesg: > atapci0: port 0xac00-0xac0f at device 17.= 1 on=20 > pci0 >=20 > I will be able to test the drives (the ones which I thought of as "fail= ed") on=20 > another board within 10 days or so. There is definitly something fishy here, since I dont have either the=20 disks nor any VIA chips here in the lab I cannot do any testing here. However I dont know of any problems with the VIA chips in this regard,=20 so that leaves the disks for scrutiny. One thing to try is change the=20 tripping point where we switch from 28bit mode to 48 bit mode, could be=20 a 1 off error in the firmware... -S=F8ren