From owner-freebsd-current Wed May 12 8:56: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 4E5EB14FA4 for ; Wed, 12 May 1999 08:56:03 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id RAA26231; Wed, 12 May 1999 17:56:02 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id RAA05819; Wed, 12 May 1999 17:55:59 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: "Geoff Rehmet" Cc: luoqi@watermarkgroup.com (Luoqi Chen), current@FreeBSD.ORG Subject: Re: panic ! panic ! panic ! In-reply-to: Your message of "Wed, 12 May 1999 17:48:54 +0200." <19990512154854.78032.qmail@rucus.ru.ac.za> Date: Wed, 12 May 1999 17:55:59 +0200 Message-ID: <5817.926524559@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At least put DDB in your kernel, type "trace" when it panics and tell us what it says. In message <19990512154854.78032.qmail@rucus.ru.ac.za>, "Geoff Rehmet" writes: >Luoqi Chen writes : > >I'm trying to get a crash dump myself, but the kernel I have >right now, is screwing up my keyboard, and I cannot even log >in! >I will try again. > >Geoff. >> > After make world this morning I received this panic : >> > >> > Fatal trap 12: page fault while in kernel mode >> > fault virtual address = 0x14 >> > fault code = supervisor read, page not present >> > instruction pointer = 0x8:0xc0155ca4 >> > stack pointer = 0x10:0xc6864d64 >> > frame pointer = 0x10:0xc6864d78 >> > code segment = base 0x0, limit 0xfffff, type 0x1b >> > = DPL0, pres 1, def32 1, gran 1 >> > processor eflags = interrupt enabled, resume , IOPL=0 >> > current process = 374 (screen-3.7.6) >> > interrupt mask = tty >> > trap number = 12 >> > panic: page fault >> > >> > I receive this panic with "screen", but before I kept this box resetting >> > itself trying to enter in X... and I was trying Xfree 3.3.3.1 (recompiled >> > and reinstalled) SVGA, Metrolink and Xaccel 5.0 . But I could not seen the >> > panic probably due to X loading. >> > >> Could you show us the symbols around the faulting instruction at 0xc0155ca4? >> It would be even better if you have a crash dump and the gdb backtrace. >> >> -lq >> >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> with "unsubscribe freebsd-current" in the body of the message >> > > >-- >Geoff Rehmet, >The Internet Solution >geoffr@is.co.za; geoff@rucus.ru.ac.za; csgr@freebsd.org >tel: +27-83-292-5800 > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message