Date: Tue, 10 Aug 2004 13:43:28 -0700 From: Nate Lawson <nate@root.org> To: Radek Kozlowski <radek@raadradd.com> Cc: sos@deepcore.dk Subject: Re: Panic on boot with today's CURRENT, ata related Message-ID: <41193370.3020302@root.org> In-Reply-To: <20040810203822.GB28585@werd> References: <4113EB2A.7060401@root.org> <20040806221109.GC55186@werd> <411406AA.3030607@root.org> <20040810203822.GB28585@werd>
next in thread | previous in thread | raw e-mail | index | archive | help
Radek Kozlowski wrote: > 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 initialized. >>However, that is in another path (this backtrace is just a symptom >>triggered by the first DMA access to the drive). Someone 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 boot > with ACPI disabled the transfer mode is set to UDMA100. Shall I provide > you with more info? I'm done debugging ATA for now. I spent 8 hours tracking down the first bug (not counting the time lost tracking down a non-existent routing table bug triggered by the ATA bug) and 15 minutes on the second one. ACPI does not affect ATA other than setting up IO ports and IRQs. I have no idea what can cause ATA to use PIO over UDMA. -- Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?41193370.3020302>