On Tue, Oct 21, 2003 at 10:52:47AM -0400, Timothy A. Musson wrote:
> We've had a page fault error on a production machine that caused a kernel
> panic. We dug around a bit and did the obligatory google searching, but we're
> not quite happy with the level of detail we were able to find. I was hoping
> somebody on this list might be able to interpret some of the codes or guess at
> what happened. Due to the location of the machine, the error was likely caused
> by a radiation single even upset. We're just trying to figure out what part of
> the system got corrupted (disk, a lookup table or pointer, etc.) so we can
> give
> as complete a report as possible. BTW, this machine has no disk, it NFS mounts
> another NetBSD machine's drives.
> 
> Here's the relevant output from logs:
> Oct 17 22:41:49 <host> /netbsd: vm_fault(0xf8685400, 0, 3, 0) -> 1
> Oct 17 22:41:49 <host> /netbsd: fatal page fault in supervisor mode
> Oct 17 22:41:49 <host> /netbsd: trap type 6 code f8160002 eip f810829c cs
> f8100008 eflags 10286 cr2 1 cpl 0
> Oct 17 22:41:50 <host> /netbsd: panic: trap
> Oct 17 22:41:50 <host> /netbsd: syncing disks... done
> Oct 17 22:41:50 <host> /netbsd: NetBSD 1.2.1 (<tag>) #6: Thu Feb 17 14:41:16
> EST 2000

Quite hard to say. That's where a core dump or ddb would be usefull :)

If you have an unstripped binary, you can probably find in which function
this happended, tough.

-- 
Manuel Bouyer <bouyer@antioche.eu.org>
     NetBSD: 24 ans d'experience feront toujours la difference
--