From owner-freebsd-current@FreeBSD.ORG Tue Aug 10 20:56:53 2004 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 E036C16A4CF for ; Tue, 10 Aug 2004 20:56:53 +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 3743543D39 for ; Tue, 10 Aug 2004 20:56:53 +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 i7AKukSu058165; Tue, 10 Aug 2004 22:56:51 +0200 (CEST) (envelope-from sos@DeepCore.dk) Message-ID: <41193683.2090906@DeepCore.dk> Date: Tue, 10 Aug 2004 22:56:35 +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: Nate Lawson References: <4113EB2A.7060401@root.org> <20040806221109.GC55186@werd> <411406AA.3030607@root.org> <20040810203822.GB28585@werd> <41193370.3020302@root.org> In-Reply-To: <41193370.3020302@root.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: current@freebsd.org cc: Radek Kozlowski Subject: Re: Panic on boot with today's CURRENT, ata related 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: Tue, 10 Aug 2004 20:56:54 -0000 Nate Lawson wrote: > Radek Kozlowski wrote: >=20 >> On Fri, Aug 06, 2004 at 03:31:06PM -0700, Nate Lawson wrote: >> >>> It looks like the DMA object for the channel is not being=20 >>> initialized. However, that is in another path (this backtrace is just= =20 >>> a symptom triggered by the first DMA access to the drive). Someone=20 >>> who knows more about the control path for going from PIO -> DMA mode = >>> will have to look into this. >> >> >> I would like to stress that it only happens with ACPI enabled. If I bo= ot >> with ACPI disabled the transfer mode is set to UDMA100. Shall I provid= e >> you with more info? >=20 >=20 > I'm done debugging ATA for now. I spent 8 hours tracking down the firs= t=20 > bug (not counting the time lost tracking down a non-existent routing=20 > table bug triggered by the ATA bug) and 15 minutes on the second one. >=20 > ACPI does not affect ATA other than setting up IO ports and IRQs. I=20 > have no idea what can cause ATA to use PIO over UDMA. If the IO ports for DMA are set wrong or just NULL there will be no DMA, = so compare the dmesg from with and without ACPI and check if thats the=20 reason... -S=F8ren