Hardware or software error ?

[Lowell Gilbert]

Heinrich Rebehn <rebehn at ant.uni-bremen.de> writes:

> Hi list,
> 
> does anybody have a clue, if the following is a hard or software error?
> 
> #########################################################################
>   syslogd: kernel boot file is /boot/kernel/kernel
>   kernel:
>   kernel:
>   kernel: Fatal trap 12: page fault while in kernel mode
>   kernel: cpuid = 0; apic id = 00
>   kernel: fault virtual address   = 0x4
>   kernel: fault code              = supervisor read, page not present
>   kernel: instruction pointer     = 0x8:0xc0533f98
>   kernel: stack pointer           = 0x10:0xe11f6b3c
>   kernel: frame pointer           = 0x10:0xe11f6b64
>   kernel: code segment            = base 0x0, limit 0xfffff, type 0x1b
>   kernel: = DPL 0, pres 1, def32 1, gran 1
>   kernel: processor eflags        = interrupt enabled, resume, IOPL = 0
>   kernel: current process         = 29 (swi1: net)
>   kernel: trap number             = 12
>   kernel: panic: page fault
>   kernel: cpuid = 0;
>   kernel:
>   kernel: syncing disks, buffers remaining...
>   kernel:
>   kernel: Fatal trap 12: page fault while in kernel mode
>   kernel: cpuid = 0; apic id = 00
>   kernel: fault virtual address   = 0x4
>   kernel: fault code              = supervisor read, page not present
>   kernel: instruction pointer     = 0x8:0xc0533f98
>   kernel: stack pointer           = 0x10:0xe124bbcc
>   kernel: frame pointer           = 0x10:0xe124bbf4
>   kernel: code segment            = base 0x0, limit 0xfffff, type 0x1b
>   kernel: = DPL 0, pres 1, def32 1, gran 1
>   kernel: processor eflags        = interrupt enabled, resume, IOPL = 0
>   kernel: current process         = 26 (irq15: xl0 ata1+)
>   kernel: trap number             = 12
>   kernel: panic: page fault
>   kernel: cpuid = 0;
>   kernel: Uptime: 3d10h11m49s
> #########################################################################
> 
> The system is running FreeBSD 5.2.1-RC2

More likely to be a software problem, although it could be either.  
Could you take a kernel dump to the -CURRENT list?