[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
kern/46096: uvmwait test case sometimes panics kernel
>Synopsis: uvmwait test case sometimes panics kernel
>Arrival-Date: Sat Feb 25 16:10:01 +0000 2012
>Originator: Andreas Gustafsson
>Release: NetBSD-current, source date 2012.02.24.19.40.49
There have now been multiple incidents where a kernel panic has
occurred while running the uvmwait test case of the rump/rumpkern/t_vm
test, for example:
The uvmwait test case has been consistently failing since the vmem
commits of January 29, which would be worthy of a PR in itself, but
this PR is specifically about the kernel panics, not the test failures.
Tracking down the problem should be easier than usual, because the
latest failure occurred on a test system that was built with full
debug symbols (using "build.sh -V MKDEBUG=yes -V DBG=-g"), installed
with full source, and run under a new test fixture that automatically
archived a full disk image of the failed system, including the kernel
This disk image is available for downloading at:
The compressed image is 832 MB in size and decompresses to 4 GB.
To debug the problem while enjoying the comforts of source-level
debugging, download and gunzip the disk image, and then boot it with
qemu -snapshot -nographic -hda i386-debug-2012.02.24.19.40.49.img
Note that you don't need to be running to i386 port, or even NetBSD,
to do this.
Log in as root (there is no password). To help gdb find the kernel
mkdir -p /tmp/bracket/build/2012.02.24.19.40.49-i386-debug
ln -s /usr/src /tmp/bracket/build/2012.02.24.19.40.49-i386-debug/src
target kvm netbsd.0.core
Run the ATF tests enough times. But there should be no need to
reproduce the problem since an exceptionally complete set of evidence
was collected from the latest crime scene.
Main Index |
Thread Index |