From owner-freebsd-current@FreeBSD.ORG Fri Feb 6 22:46:05 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 C253516A4CE for ; Fri, 6 Feb 2004 22:46:05 -0800 (PST) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 391F943D48 for ; Fri, 6 Feb 2004 22:46:03 -0800 (PST) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 2BC3A72DCA; Fri, 6 Feb 2004 22:46:03 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 2A00472DC7; Fri, 6 Feb 2004 22:46:03 -0800 (PST) Date: Fri, 6 Feb 2004 22:46:03 -0800 (PST) From: Doug White To: Steve Kargl In-Reply-To: <20040206231933.GA25826@troutmask.apl.washington.edu> Message-ID: <20040206224459.G20729@carver.gumbysoft.com> References: <20040205231737.GB17451@troutmask.apl.washington.edu> <20040206231933.GA25826@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 06:46:05 -0000 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. > 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. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org