misc/164565: kernel crash when kldunload'ing padlock
Stefan Krueger
stadtkind2 at gmx.de
Sun Jan 29 19:30:15 UTC 2012
The following reply was made to PR kern/164565; it has been noted by GNATS.
From: Stefan Krueger <stadtkind2 at gmx.de>
To: bug-followup at FreeBSD.org
Cc: Patrick Lamaiziere <patfbsd at davenulle.org>
Subject: Re: misc/164565: kernel crash when kldunload'ing padlock
Date: Sun, 29 Jan 2012 20:23:20 +0100
> > Unloading the padlock kernel module makes the kernel crash.
> Do you have a panic or there is just a crash without information?
> If it panics, a back trace would be helpful, see
> http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html
> Are you using padlock (ipsec?) when unloading?
> Regards.
Hi Patrick,
thanks for fast reply.
I get a backtrace indeed:
# kldunload padlock
panic: rw lock 0xfffffe00019a2698 not unlocked
cpuid = 0
KDB: stack backtrace:
#0 0xffffffff8049822e at kdb_backtrace+0x5e
#1 0xffffffff80460d57 at panic+0x187
#2 0xffffffff8045fa84 at rw_destroy+0x34
#3 0xffffffff80baa848 at padlock_detach+0x108
#4 0xffffffff804919e4 at device_detach+0x94
#5 0xffffffff80491c80 at devclass_driver_deleted+0x70
#6 0xffffffff80491da1 at devclass_delete_driver+0x51
#7 0xffffffff80491fad at driver_module_handler+0x14d
#8 0xffffffff8044fc05 at module_unload+0x35
#9 0xffffffff8044592b at linker_file_unload+0x16b
#10 0xffffffff80446513 at kern_kldunload+0xf3
#11 0xffffffff8063eea3 at amd64_syscall+0x313
#12 0xffffffff80629f07 at Xfast_syscall+0xf7
Uptime: 31s
Automatic reboot in 15 seconds - press a key on the console to abort
Padlock is not in use (i.e. I netbooted a freebsd 9.0 kernel into
single-user, so no IPSEC, no GELI, no nothing at that point)
I'm pretty sure I could get a crashdump if you need one.
Regards
More information about the freebsd-bugs
mailing list