Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!news.kei.com!news.mathworks.com!news.ultranet.com!news.sprintlink.net!pipex!sunic!sunic.sunet.se!trane.uninett.no!nntp.uio.no!ifi.uio.no!aagero From: aagero@ifi.uio.no (Åge Røbekk) Newsgroups: comp.unix.bsd.netbsd.misc Subject: Kernel panic, (kmem_map) Date: 15 Jun 1995 23:06:05 +0200 Organization: Dept. of Informatics, University of Oslo, Norway Lines: 11 Message-ID: <3rq7bt$ojp@delling.ifi.uio.no> NNTP-Posting-Host: delling.ifi.uio.no X-newsreader: xrn 7.03 The problem lies, as the subject says, in a kernel panic. After the new kernel has been built and booted, the system gets as far as starting mountd, and perhaps it touches nfsd too in /etc/rc. But immediately after that, the machine panics and in 1/100 of a second there is some vital information about which system call triggered the panic before the screen clears and the computer reboots. After some retries, i managed to find out that it says 'kmem_map' something, and that message comes from /sys/vm/vm_kern.c. Or does it? I'm clueless. I've gotten this panic from sources dated 8. June (newest files). -aage