Date: Fri, 6 Feb 2004 22:46:03 -0800 (PST) From: Doug White <dwhite@gumbysoft.com> To: Steve Kargl <sgk@troutmask.apl.washington.edu> Cc: freebsd-current@freebsd.org Subject: Re: mtrash_ctor panic caused by ACPI and ATAng was Re:Interrupts, ATAng, and wayward pointers, oh my! Message-ID: <20040206224459.G20729@carver.gumbysoft.com> In-Reply-To: <20040206231933.GA25826@troutmask.apl.washington.edu> References: <20040205231737.GB17451@troutmask.apl.washington.edu> <20040206231933.GA25826@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040206224459.G20729>