Now that bug 1154328 has been fixed, the NetBSD OS test suite successfully starts, but it still does not work as expected; actually things have gone from bad to worse. Every test run since the 1154328 fix has either timed out after running only a fraction of the tests, or has ended in a guest kernel panic. For example, here is part of the console output from a recent test run using qemu git revision 93b48c201eb6c0404d15550a0eaa3c0f7937e35e:
msdosfs_symlink_zerolen: [1.172395s] Skipped: symlinks not supported by file system
nfs_access_simple: [9.423184s] Failed: child died
nfs_attrs: fatal double fault in user mode
trap type 269 code 80000000 eip c010cca2 cs 8 eflags ed1fe cr2 b83fd834 ilevel 0
panic: trap
cpu0: Begin traceback...
printf_nolog(c0ba9e6b,c34adf7c,c34adf7c,c010cca2,8,ed1fe,b83fd834,0,0,0) at netbsd:printf_nolog
trap_tss() at netbsd:trap_tss
--- trap via task gate ---
b83ff74c:
cpu0: End traceback...
So either the supposed fix actually made things worse, or some unrelated regression has been introduced while the tests were inoperable due to bug 1154328.
Now that bug 1154328 has been fixed, the NetBSD OS test suite successfully starts, but it still does not work as expected; actually things have gone from bad to worse. Every test run since the 1154328 fix has either timed out after running only a fraction of the tests, or has ended in a guest kernel panic. For example, here is part of the console output from a recent test run using qemu git revision 93b48c201eb6c04 04d15550a0eaa3c 0f7937e35e:
msdosfs_ symlink_ zerolen: [1.172395s] Skipped: symlinks not supported by file system access_ simple: [9.423184s] Failed: child died nolog(c0ba9e6b, c34adf7c, c34adf7c, c010cca2, 8,ed1fe, b83fd834, 0,0,0) at netbsd:printf_nolog
nfs_
nfs_attrs: fatal double fault in user mode
trap type 269 code 80000000 eip c010cca2 cs 8 eflags ed1fe cr2 b83fd834 ilevel 0
panic: trap
cpu0: Begin traceback...
printf_
trap_tss() at netbsd:trap_tss
--- trap via task gate ---
b83ff74c:
cpu0: End traceback...
So either the supposed fix actually made things worse, or some unrelated regression has been introduced while the tests were inoperable due to bug 1154328.