From owner-freebsd-current@FreeBSD.ORG Fri Feb 6 23:06:55 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 87EF516A4CE for ; Fri, 6 Feb 2004 23:06:55 -0800 (PST) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1C62843D1F for ; Fri, 6 Feb 2004 23:06:54 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) i1776rTA028760; Fri, 6 Feb 2004 23:06:53 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)i1776rVO028759; Fri, 6 Feb 2004 23:06:53 -0800 (PST) (envelope-from sgk) Date: Fri, 6 Feb 2004 23:06:53 -0800 From: Steve Kargl To: Doug White Message-ID: <20040207070653.GA28676@troutmask.apl.washington.edu> References: <20040205231737.GB17451@troutmask.apl.washington.edu> <20040206231933.GA25826@troutmask.apl.washington.edu> <20040206224459.G20729@carver.gumbysoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040206224459.G20729@carver.gumbysoft.com> User-Agent: Mutt/1.4.1i cc: freebsd-current@freebsd.org Subject: Re: mtrash_ctor panic caused by ACPI and ATAng was Re: Interrupts, ATAng, and wayward pointers, oh my! 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: Sat, 07 Feb 2004 07:06:55 -0000 On Fri, Feb 06, 2004 at 10:46:03PM -0800, Doug White wrote: > On Fri, 6 Feb 2004, Steve Kargl wrote: > > > Via trial and error, I have determined that the above panic is > > caused by ACPI and ATAng. This is a Dell 4150 laptop. I can > > build a working kernel with sources checked out via cvsup with > > date=2004.01.30.19.00.00. If I use a date of 2004.01.30.20.00.00, > > I retrieve only revision 1.203 of ata-all.c and revision 1.19 of > > ata-queue.h. No other files are changed in sys/ and the resulting > > kernel produces the above panic. Finally, if I set > > hint.acpi.0.disabled="1" in /boot/loader.conf. The kernel that > > previously panicked will boot fine. > > Intriguing. Yes, intriguing. I used the better part of 1 day to eliminate possibilities for the problem. I forgot to mention the problem does not depend on APIC or no APIC support in the kernel. > > PS: No, I can't get a core dump because the disk subsystem isn't > > ready for a dump when the panics occurred and I can't hook > > up a serial console. I can panic the machine as needed. > > You can say 'set dumpdev=/dev/foo0s1b' in loader to set the dump target. > This doesn't work unless I can get a near instantaneous dump. That is, db> call dumpsys returns in under a second. Revision 1.19 of ata-queue.c (note the typo of ata-queue.h above) reworked the locking of ATA. I suspect that my laptop is tickling some race that Soren hasn't seen. -- Steve