Date: Tue, 10 Aug 2004 22:56:35 +0200 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= <sos@DeepCore.dk> To: Nate Lawson <nate@root.org> Cc: Radek Kozlowski <radek@raadradd.com> Subject: Re: Panic on boot with today's CURRENT, ata related Message-ID: <41193683.2090906@DeepCore.dk> In-Reply-To: <41193370.3020302@root.org> References: <4113EB2A.7060401@root.org> <20040806221109.GC55186@werd> <411406AA.3030607@root.org> <20040810203822.GB28585@werd> <41193370.3020302@root.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?41193683.2090906>