Subject: kern/3370: kernel: page fault: _vm_fault
To: None <gnats-bugs@gnats.netbsd.org>
From: Simon J. Gerraty <sjg@quick.com.au>
List: netbsd-bugs
Date: 03/21/1997 10:10:06
>Number: 3370
>Category: kern
>Synopsis: after 2-3 days uptime, system dies with kernel page fault.
>Confidential: no
>Severity: serious
>Priority: high
>Responsible: kern-bug-people (Kernel Bug People)
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Thu Mar 20 15:20:02 1997
>Last-Modified:
>Originator: Simon J. Gerraty
>Organization:
Zen Programming...
>Release: 1.2C (March 08 tar_files)
>Environment:
System: NetBSD zen.quick.com.au 1.2C NetBSD 1.2C (ZEN) #5: Mon Mar 3 16:18:58 EST 1997 root@zen.quick.com.au:/share/usr.src/sys/arch/i386/compile/ZEN i386
>Description:
Kernel: page fault trap, code=0
Stopped at _vm_fault+0x59: mov 0x22(%esi),%ax
In this case a trace showed no more info, and attempts to c (to get a
core dump) or call _boot etc just got another page fault.
This has happend twice this week now. kern/2673 was the only PR I
could find that mentioned _vm_fault, so here we are.
BTW, I've not yet tried the latest sources (I will), though I could
not find any sources under sys/vm which have been updated thince March
8.
Each time this has happened my overnight cron jobs result in a rash of
sh.core files - all from segmentation faults.
I'm sorry I can't provide more useful info.
>How-To-Repeat:
>Fix:
>Audit-Trail:
>Unformatted: