Re: panic: blockable sleep lock (sleep mutex) 32 _at_ /usr/src/sys/vm/uma_core.c:1990

From: Jung-uk Kim <jkim_at_FreeBSD.org>
Date: Wed, 10 Jun 2009 19:12:42 -0400
On Wednesday 10 June 2009 07:01 pm, Kip Macy wrote:
> A M_WAITOK allocation while holding a lock will do this.

No, it does not because it may be used in interrupt handler context 
with a spin lock held (e.g., GPE handler).  In fact, I already 
committed a workaround:

http://svn.freebsd.org/changeset/base/193963

Please let me know if it does not work for you.

Thanks,

Jung-uk Kim

> -Kip
>
> On Tue, Jun 9, 2009 at 6:25 AM, Paul B. Mahol<onemda_at_gmail.com> 
wrote:
> > #0  doadump () at pcpu.h:246
> > #1  0xc04acb4e in boot (howto=260) at
> > /usr/src/sys/kern/kern_shutdown.c:419 #2  0xc04ace22 in panic
> > (fmt=Variable "fmt" is not available.) at
> > /usr/src/sys/kern/kern_shutdown.c:575
> > #3  0xc04ecba0 in witness_checkorder (lock=0xc1094788, flags=9,
> > file=0xc06429a7 "/usr/src/sys/vm/uma_core.c", line=1990,
> > interlock=0x0) at /usr/src/sys/kern/subr_witness.c:1063
> > #4  0xc049ded4 in _mtx_lock_flags (m=0xc1094788, opts=0,
> > file=0xc06429a7 "/usr/src/sys/vm/uma_core.c", line=1990) at
> > /usr/src/sys/kern/kern_mutex.c:200
> > #5  0xc05b3eb3 in uma_zalloc_arg (zone=0xc108c700, udata=0x0,
> > flags=1) at /usr/src/sys/vm/uma_core.c:1990
> > #6  0xc049a564 in malloc (size=dwarf2_read_address: Corrupted
> > DWARF expression.) at uma.h:305
> > #7  0xc09cc51f in AcpiOsExecute (Type=OSL_GPE_HANDLER,
> > Function=0xc099c100 <AcpiEvAsynchExecuteGpeMethod>,
> > Context=0xc3d49618) at
> > /usr/src/sys/modules/acpi/acpi/../../../dev/acpica/Osd/OsdSchedul
> >e.c:103 #8  0xc099c448 in AcpiEvGpeDispatch
> > (GpeEventInfo=0xc3d49618, GpeNumber=2) at
> > /usr/src/sys/modules/acpi/acpi/../../../contrib/dev/acpica/events
> >/evgpe.c:863 #9  0xc099c66b in AcpiEvGpeDetect
> > (GpeXruptList=0xc3d4b400) at
> > /usr/src/sys/modules/acpi/acpi/../../../contrib/dev/acpica/events
> >/evgpe.c:586 #10 0xc099e699 in AcpiEvSciXruptHandler
> > (Context=0xc3d4b400) at
> > /usr/src/sys/modules/acpi/acpi/../../../contrib/dev/acpica/events
> >/evsci.c:172 #11 0xc0487955 in intr_event_execute_handlers
> > (p=0xc3d0aa90, ie=0xc3d09300) at
> > /usr/src/sys/kern/kern_intr.c:1146
> > #12 0xc04885bf in ithread_loop (arg=0xc3d4b3f0) at
> > /usr/src/sys/kern/kern_intr.c:1159
> > #13 0xc0485728 in fork_exit (callout=0xc0488520 <ithread_loop>,
> > arg=0xc3d4b3f0, frame=0xc39e7d38) at
> > /usr/src/sys/kern/kern_fork.c:828 #14 0xc05ea6e0 in
> > fork_trampoline () at /usr/src/sys/i386/i386/exception.s:270
> >
> > Some recent change in acpi is causing this.
> >
> > --
> > Paul
> > _______________________________________________
> > freebsd-current_at_freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-current
> > To unsubscribe, send any mail to
> > "freebsd-current-unsubscribe_at_freebsd.org"
Received on Wed Jun 10 2009 - 21:13:05 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:49 UTC