RELENG_5 panic: mtx_lock() with ACPI

[John Baldwin]

On Tuesday 21 September 2004 03:05 pm, Anish Mistry wrote:
> On Monday 20 September 2004 04:00 pm, you wrote:
> > Anish Mistry wrote:
> > > On Monday 20 September 2004 03:35 pm, you wrote:
> > >>Anish Mistry wrote:
> > >>>On Monday 20 September 2004 03:01 pm, Anish Mistry wrote:
> > >>>>I'm getting the following panic on boot only with ACPI enabled.
> > >>>>On a verbose boot right after: start_init: trying /sbin/init
> > >>>>panic: mtx_lock() of spin mutex(null) @ /usr/src/sys/tty/tty.c:2809
> > >>>>Can't seem to get a dump even if dumpdev is set at the loader prompt.
> > >>>>
> > >>>>Verbose boot without ACPI enabled and ASL attached.
> > >>>
> > >>>Attachments got stripped.
> > >>>http://am-productions.biz/debug/BIGGUY-dmesg.txt.gz
> > >>>http://am-productions.biz/debug/bigguy.asl.gz
> > >>
> > >>Can you send a backtrace ("tr" from ddb)?
> > >
> > > It doesn't break to the ddb prompt.
> >
> > Can you enable options DDB?  If ddb is enabled, all panics should break
> > to the debugger.
>
> Ok, I removed WITNESS and INVARIANTS from my kernel config, and now it's
> dropping to a db> prompt.

You want to keep INVARIANTS as it find problems sooner and in easier to debug
locations.  Can you turn INVARIANTS back on at least and then get a trace?

> BTW, is there a way to set the dump device at the loader that works.

Not that I'm aware of.

-- 
John Baldwin <jhb at FreeBSD.org>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve"  =  http://www.FreeBSD.org