Date: Mon, 9 Feb 2004 10:10:26 -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: <20040209100947.K47197@carver.gumbysoft.com> In-Reply-To: <20040207070653.GA28676@troutmask.apl.washington.edu> References: <20040205231737.GB17451@troutmask.apl.washington.edu> <20040206231933.GA25826@troutmask.apl.washington.edu> <20040207070653.GA28676@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 6 Feb 2004, Steve Kargl wrote: > 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. try 'call doadump()' -- 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?20040209100947.K47197>