Date: Fri, 07 Dec 2007 22:41:55 -0500 From: "Alexandre \"Sunny\" Kovalenko" <alex.kovalenko@verizon.net> To: acpi@freebsd.org Subject: Loading hifn.ko causes [panic: lock "ACPI global lock" 0xc08606a0 already initialized] on 7.0-BETA4 Message-ID: <1197085315.5011.1.camel@RabbitsDen>
next in thread | raw e-mail | index | archive | help
Looks like return from device_attach corrupts the stack (see "Stack
trace after panic" and "Stack trace prior to panic" below).
System was built from the cvs sources as of Dec 5 (approx 18:00 EST).
Config is pretty much GENERIC with the full complement of the debugging
options and firewire/dcons for remote debugging.
Messages produced on the console are:
fbsd-dev# kldload hifn
acpi0: <HP-CPC AWRDACPI> on motherboard
panic: lock "ACPI global lock" 0xc08606a0 already initialized
KDB: enter: panic
Stack trace after the panic is:
#0 kdb_enter (msg=0xc0672db4 "panic")
at /usr/src/sys/kern/subr_kdb.c:310
#1 0xc04e28c5 in panic (fmt=0xc06759b1 "lock \"%s\" %p already
initialized") at /usr/src/sys/kern/kern_shutdown.c:547
#2 0xc0509b54 in lock_init (lock=0xc1017808, class=0xc06ab364,
name=0xc0859973 "ACPI global lock", type=0x0,
flags=131072) at /usr/src/sys/kern/subr_lock.c:201
#3 0xc04d6f54 in mtx_init (m=0xc08606a0, name=0xc0859973 "ACPI global
lock", type=0x0, opts=0)
at /usr/src/sys/kern/kern_mutex.c:740
#4 0xc083d49e in ?? ()
#5 0xc08606a0 in ?? ()
#6 0xc0859973 in ?? ()
#7 0x00000000 in ?? ()
#8 0x00000000 in ?? ()
#9 0x00000000 in ?? ()
#10 0x00000000 in ?? ()
#11 0xc297b280 in ?? ()
#12 0xc29299cc in ?? ()
#13 0xd49a1698 in ?? ()
#14 0xc062756f in Xtimerint () at apic_vector.s:108
#15 0xd49a1618 in ?? ()
#16 0xd49a0008 in ?? ()
#17 0x00000028 in ?? ()
#18 0xc2920028 in ?? ()
#19 0xc2929980 in ?? ()
#20 0xc29299cc in ?? ()
#21 0xd49a1698 in ?? ()
#22 0xd49a1644 in ?? ()
#23 0xc297b280 in ?? ()
#24 0xc295d000 in ?? ()
#25 0x00000014 in ?? ()
#26 0xc085e650 in ?? ()
#27 0x00000000 in ?? ()
#28 0xc297b280 in ?? ()
#29 0xc29299cc in ?? ()
#30 0xc2929980 in ?? ()
#31 0xd49a1698 in ?? ()
#32 0xc0504d8f in device_attach (dev=0xc2929980) at device_if.h:178
Previous frame identical to this frame (corrupt stack?)
Stack trace prior to the panic is:
#0 device_attach (dev=0xc2929980) at device_if.h:177
#1 0xc0505890 in device_probe_and_attach (dev=0xc2929980)
at /usr/src/sys/kern/subr_bus.c:2347
#2 0xc0505945 in bus_generic_driver_added (dev=0xc297b280,
driver=0xc2eff270) at /usr/src/sys/kern/subr_bus.c:3087
#3 0xc0503bb8 in devclass_add_driver (dc=0xc28ec1c0, driver=0xc2eff270)
at bus_if.h:183
#4 0xc0504949 in driver_module_handler (mod=0xc2e8fbc0, what=0,
arg=0xc2eff25c) at /usr/src/sys/kern/subr_bus.c:3796
#5 0xc04d64c7 in module_register_init (arg=0xc2eff250)
at /usr/src/sys/kern/kern_module.c:124
#6 0xc04d14ba in linker_load_module (kldname=Variable "kldname" is not
available.
) at /usr/src/sys/kern/kern_linker.c:226
#7 0xc04d1844 in linker_load_dependencies (lf=0xc2d24600)
at /usr/src/sys/kern/kern_linker.c:1935
#8 0xc04fbc61 in link_elf_load_file (cls=0xc06ad700,
filename=0xc2ad6840 "/boot/kernel/hifn.ko", result=0xd49a1c24)
at /usr/src/sys/kern/link_elf.c:780
#9 0xc04d139b in linker_load_module (kldname=Variable "kldname" is not
available.
) at linker_if.h:110
#10 0xc04d1968 in kern_kldload (td=0xc29ba630, file=0xc29ca400 "hifn",
fileid=0xd49a1c70)
at /usr/src/sys/kern/kern_linker.c:869
#11 0xc04d1a24 in kldload (td=0xc29ba630, uap=0xd49a1cfc)
at /usr/src/sys/kern/kern_linker.c:896
#12 0xc063d9e3 in syscall (frame=0xd49a1d38)
at /usr/src/sys/i386/i386/trap.c:1008
#13 0xc0626ff0 in Xint0x80_syscall ()
at /usr/src/sys/i386/i386/exception.s:196
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1197085315.5011.1.camel>