Subject: kern/34699: panic: kernel diagnostic assertion "fault_flag != UVM_FAULT_WIREMAX"
To: None <kern-bug-people@netbsd.org, gnats-admin@netbsd.org,>
From: Christian Biere <christianbiere@gmx.de>
List: netbsd-bugs
Date: 10/02/2006 21:35:00
>Number:         34699
>Category:       kern
>Synopsis:       kernel diagnostic assertion "fault_flag != UVM_FAULT_WIREMAX"
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Oct 02 21:35:00 +0000 2006
>Originator:     Christian Biere
>Release:        NetBSD 4.99.3
>Environment:
System: NetBSD cyclonus 4.99.3 NetBSD 4.99.3 (STARSCREAM) #0: Mon Oct 2 23:04:22 CEST 2006 src@cyclonus:/o/NetBSD/obj/sys/arch/i386/compile/STARSCREAM i386
Architecture: i386
Machine: i386
>Description:
The following panic occurred with the sources as of today/yesterday after
a couple hours of uptime. What's worse is, the kernel paniced again after
each reboot whilst running the startup scripts. I escaped the panic cycle by
booting the GENERIC kernel. The crashing kernel has DIAGNOSTIC and DEBUG
enabled. My userland is up-to-date now but I had no chance to get a
stacktrace or coredump.

panic: kernel diagnostic assertion "fault_flag != UVM_FAULT_WIREMAX" failed:
 file "/s/NetBSD/src/sys/uvm/uvm_fault.c", line 801
Begin traceback...
_prop_array_pool(0,0,30002,1,804b82c) at 0xcb601ed4
uvm_fault(0xca9ca7e0, 0x464c4000, 1) -> 0xe
fatal page fault in supervisor mode
trap type 6 code 0 eip c0278c23 cs 8 eflags 10246 cr2 464c457f ilevel 0
panic: trap
Faulted in mid-traceback; aborting...
dumping to dev 0,1 offset 1573767
>How-To-Repeat:
>Fix: