Date: Wed, 10 Jun 2009 16:01:22 -0700 From: Kip Macy <kmacy@freebsd.org> To: "Paul B. Mahol" <onemda@gmail.com> Cc: FreeBSD-Current <freebsd-current@freebsd.org> Subject: Re: panic: blockable sleep lock (sleep mutex) 32 @ /usr/src/sys/vm/uma_core.c:1990 Message-ID: <3c1674c90906101601q68285c4ehad44dadc0d1a28e5@mail.gmail.com> In-Reply-To: <3a142e750906090625r6586f15fn234e539dbbd57e73@mail.gmail.com> References: <3a142e750906090625r6586f15fn234e539dbbd57e73@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
A M_WAITOK allocation while holding a lock will do this. -Kip On Tue, Jun 9, 2009 at 6:25 AM, Paul B. Mahol<onemda@gmail.com> wrote: > #0 =A0doadump () at pcpu.h:246 > #1 =A00xc04acb4e in boot (howto=3D260) at /usr/src/sys/kern/kern_shutdown= .c:419 > #2 =A00xc04ace22 in panic (fmt=3DVariable "fmt" is not available.) at > /usr/src/sys/kern/kern_shutdown.c:575 > #3 =A00xc04ecba0 in witness_checkorder (lock=3D0xc1094788, flags=3D9, > file=3D0xc06429a7 "/usr/src/sys/vm/uma_core.c", line=3D1990, > interlock=3D0x0) at /usr/src/sys/kern/subr_witness.c:1063 > #4 =A00xc049ded4 in _mtx_lock_flags (m=3D0xc1094788, opts=3D0, > file=3D0xc06429a7 "/usr/src/sys/vm/uma_core.c", line=3D1990) at > /usr/src/sys/kern/kern_mutex.c:200 > #5 =A00xc05b3eb3 in uma_zalloc_arg (zone=3D0xc108c700, udata=3D0x0, flags= =3D1) > at /usr/src/sys/vm/uma_core.c:1990 > #6 =A00xc049a564 in malloc (size=3Ddwarf2_read_address: Corrupted DWARF > expression.) at uma.h:305 > #7 =A00xc09cc51f in AcpiOsExecute (Type=3DOSL_GPE_HANDLER, > Function=3D0xc099c100 <AcpiEvAsynchExecuteGpeMethod>, > Context=3D0xc3d49618) at > /usr/src/sys/modules/acpi/acpi/../../../dev/acpica/Osd/OsdSchedule.c:103 > #8 =A00xc099c448 in AcpiEvGpeDispatch (GpeEventInfo=3D0xc3d49618, > GpeNumber=3D2) at > /usr/src/sys/modules/acpi/acpi/../../../contrib/dev/acpica/events/evgpe.c= :863 > #9 =A00xc099c66b in AcpiEvGpeDetect (GpeXruptList=3D0xc3d4b400) at > /usr/src/sys/modules/acpi/acpi/../../../contrib/dev/acpica/events/evgpe.c= :586 > #10 0xc099e699 in AcpiEvSciXruptHandler (Context=3D0xc3d4b400) at > /usr/src/sys/modules/acpi/acpi/../../../contrib/dev/acpica/events/evsci.c= :172 > #11 0xc0487955 in intr_event_execute_handlers (p=3D0xc3d0aa90, > ie=3D0xc3d09300) at /usr/src/sys/kern/kern_intr.c:1146 > #12 0xc04885bf in ithread_loop (arg=3D0xc3d4b3f0) at > /usr/src/sys/kern/kern_intr.c:1159 > #13 0xc0485728 in fork_exit (callout=3D0xc0488520 <ithread_loop>, > arg=3D0xc3d4b3f0, frame=3D0xc39e7d38) at /usr/src/sys/kern/kern_fork.c:82= 8 > #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@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= " > --=20 When bad men combine, the good must associate; else they will fall one by one, an unpitied sacrifice in a contemptible struggle. Edmund Burke
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3c1674c90906101601q68285c4ehad44dadc0d1a28e5>