Problems after upgrading to current
Lukas Ertl
le at FreeBSD.org
Sat Jul 24 12:42:21 PDT 2004
On Sat, 24 Jul 2004, Tomas Randa wrote:
> Jul 24 21:02:30 ares kernel: kernel trap 12 with interrupts disabled
> Jul 24 21:02:30 ares kernel:
> Jul 24 21:02:30 ares kernel:
> Jul 24 21:02:30 ares kernel: Fatal trap 12: page fault while in kernel
> mode
> Jul 24 21:02:30 ares kernel: fault virtual address = 0x4
> Jul 24 21:02:30 ares kernel: fault code = supervisor read, page
> not present
> Jul 24 21:02:30 ares kernel: instruction pointer = 0x8:0xc051b57a
> Jul 24 21:02:30 ares kernel: stack pointer =
> 0x10:0xd14adc68
> Jul 24 21:02:30 ares kernel: frame pointer =
> 0x10:0xd14adc70
> Jul 24 21:02:30 ares kernel: code segment = base 0x0,
> limit 0xfffff, type 0
> Jul 24 21:02:30 ares kernel: = DPL 0, pres 1, def32 1, gran 1
> Jul 24 21:02:30 ares kernel: processor eflags = resume, IOPL = 0
> Jul 24 21:02:30 ares kernel: current process = 649
> (evolution-1.4)
> Jul 24 21:02:30 ares kernel: trap number = 12
> Jul 24 21:02:30 ares kernel: panic: page fault
>
> does anybody know what is that?
That's a kernel panic, apparently there's a NULL pointer dereference
somewhere. Without backtrace it's quite impossible to figure out what
causes this panic.
cheers,
le
--
Lukas Ertl http://homepage.univie.ac.at/l.ertl/
le at FreeBSD.org http://people.freebsd.org/~le/
More information about the freebsd-current
mailing list