From owner-freebsd-current Wed Jan 7 14:11:14 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA17072 for current-outgoing; Wed, 7 Jan 1998 14:11:14 -0800 (PST) (envelope-from owner-freebsd-current) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA16992; Wed, 7 Jan 1998 14:10:26 -0800 (PST) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id OAA16740; Wed, 7 Jan 1998 14:07:00 -0800 (PST) Message-Id: <199801072207.OAA16740@implode.root.com> To: Kevin Day cc: ady@warpnet.ro (Penisoara Adrian), freebsd-current@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: Fatal trap 12 & debugging info ?? In-reply-to: Your message of "Wed, 07 Jan 1998 14:19:25 CST." <199801072019.OAA18158@home.dragondata.com> From: David Greenman Reply-To: dg@root.com Date: Wed, 07 Jan 1998 14:07:00 -0800 Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> For quite a while I'm bugged by sudden panics/reboots (all of them are >> 'fatal trap 12'); here it is the last one I had (hand rewritten): >> >> ============================================================ >> >> Fatal trap 12: page fault while in kernel mode >> mp_lock = 00000002; cpuid = 0; lapic.id = 00000000 >> fault virtual address = 0x0 >> fault code = supervisor read, page not present >> instruction pointer = 0x8:0xf01a9273 >> stack pointer = 0x10:0xf49cbe48 >> frame pointer = 0x10:0xf49cbe54 >> code segment = base 0x0, limit 0xfffff, type 0x1b >> = DPL 0, pres 1, def32 1, gran 1 >> processor eflags = interrupt enabled, resume, IOPL = 0 >> current process = 1594 (cron) >> interrupt mask = net tty bio cam <- SMP:XXX >> trap number = 12 >> panic: page fault >> mp_lock = 00000002; cpuid = 0; lapic.id = 00000000 >> boot called on cpu#0 >> >> syncing disks... >> > >I've had about 5 panics about exactly the same.... > >A trace shows free, execve, syscall, xsyscall then the debugger locks up >before showing any more... There was a bug in execve() that was fixed recently that would have looked like this. You need rev 1.70 or newer of /sys/kern/kern_exec.c. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project