Date: Thu, 07 Feb 2036 07:39:56 -0800 (PST) From: Simon Shapiro <shimon@simon-shapiro.org> To: Kevin Day <toasty@home.dragondata.com> Cc: freebsd-questions@FreeBSD.org, freebsd-current@FreeBSD.org, (Penisoara Adrian) <ady@warpnet.ro> Subject: Re: Fatal trap 12 & debugging info ?? Message-ID: <XFMail.360207073956.shimon@simon-shapiro.org> In-Reply-To: <199801072019.OAA18158@home.dragondata.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 07-Jan-98 Kevin Day wrote: >> Hi, >> >> 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... Yup. Only mine locks up on mp_lock = 01000001 and (obviously) CPU 1. ---------- Sincerely Yours, Simon Shapiro Shimon@Simon-Shapiro.ORG Voice: 503.799.2313
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.360207073956.shimon>