Kernel panic while doing sysctl -a
Matthew Dillon
dillon at apollo.backplane.com
Mon Jan 7 22:05:04 PST 2008
:Hi,
:
:one of my machines running HEAD experienced a kernel panic. The command I
:executed before the panic was "sysctl -a | less" to get a list of sysctls.
:It seems that there is an overflow within the strlen function ...
:
:kernel, crash dump, dmesg and pciconf -lv is available here:
:
:http://www.mathematik.uni-marburg.de/~schmidtm/dfly_crash/
:
:...
:#11 0xc02ddb9a in strlen (str=0xd0686f55 <Address 0xd0686f55 out of bounds>) at /usr/src/sys/libkern/strlen.c:41
:#12 0xc02c2153 in sysctl_vm_zone (oidp=0xc03b42a0, arg1=0x0, arg2=0, req=0xcec0fc08) at /usr/src/sys/vm/vm_zone.c:447
The vm_zone->zname is pointing to illegal storage. Very weird, a whole
bunch of zones have bad zname's. They look like they've come from a
dynamic module, and there are a whole bunch of them. Is there a module
you are loading and unloading a lot? It must be zinit'ing a new zone
and not cleaning it up at unload time.
We don't have a zone unloader. Looks like we'll have to write a
procedure to clean out a zone and remove it from the list in addition
to finding the module that is trying to use the zone.
zlist -> [28 zones with bad zname pointers] -> [system zones with good
zname pointers].
-Matt
More information about the Bugs
mailing list