In article <20171117165032.ga1...@mail.soc.lip6.fr>,
Manuel Bouyer wrote:
>Hello
>http://www-soc.lip6.fr/~bouyer/NetBSD-tests/xen/HEAD/amd64/201711142340Z_atf.html#failed-tcs-summary
>
>all zfs tests fails, with:
>panic: kernel diagnostic assertion "!(flags & PR_NOWAIT)
Hi,
I just got:
...
/var/crash crash -M netbsd.9.core -N netbsd.9
Crash version 8.99.7, image version 8.99.7.
System panicked: kernel diagnostic assertion
"uvm_page_locked_p(old_pg)" failed: file
"/home/sysbuild/src/sys/arch/x86/x86/pmap.c", line 4251
Backtrace from time of crash is available.
Hello
http://www-soc.lip6.fr/~bouyer/NetBSD-tests/xen/HEAD/amd64/201711142340Z_atf.html#failed-tcs-summary
all zfs tests fails, with:
panic: kernel diagnostic assertion "!(flags & PR_NOWAIT) != !(flags &
PR_WAITOK)" failed: file
"/usr/src/lib/librump/../../sys/rump/../kern/subr_pool.c", line
Following this commit:
http://mail-index.netbsd.org/source-changes/2017/11/16/msg089749.html
the stock kernels in a release build fine, but when trying to build the
first of my custom kernels, "nbconfig" spins, consuming most of the CPU.
It doesn't seem to be eating memory, however.
In the
On Fri, 17 Nov 2017, Christos Zoulas wrote:
> Well, put the spinning kernel in the PR :-)
Just saw the above in the mailing list archive as I'm not on the default
distribution list for this PR (not originator).
I appended to it as the commit and the behavior seemed relevant.
Kernel config
Hello Jaromir,
actually I did a forced fsck on the respective FS while it was unmounted
upfront. To be sure I just ran the command again - it passes with no
errors the second time. When I run dump -X again, the panic still occurs.
Best regards,
Matthias
nuc# fsck -P /dev/mapper/vg0-photo
Updating src tree:
P src/doc/3RDPARTY
P src/doc/CHANGES
P src/external/bsd/tre/Makefile.inc
U src/external/bsd/tre/tre2netbsd
cvs update: `src/external/bsd/tre/dist/ABOUT-NLS' is no longer in the repository
cvs update: `src/external/bsd/tre/dist/ChangeLog' is no longer in the repository
U