From owner-freebsd-current  Wed May 12  8:49:46 1999
Delivered-To: freebsd-current@freebsd.org
Received: from rucus.ru.ac.za (rucus.ru.ac.za [146.231.29.2])
	by hub.freebsd.org (Postfix) with SMTP id 9D21315179
	for <current@freebsd.org>; Wed, 12 May 1999 08:49:07 -0700 (PDT)
	(envelope-from geoff@rucus.ru.ac.za)
Received: (qmail 78033 invoked by uid 268); 12 May 1999 15:48:54 -0000
Message-ID: <19990512154854.78032.qmail@rucus.ru.ac.za>
Subject: Re: panic ! panic ! panic !
In-Reply-To: <199905121505.LAA12106@lor.watermarkgroup.com> from Luoqi Chen at "May 12, 1999 11: 5:23 am"
To: luoqi@watermarkgroup.com (Luoqi Chen)
Date: Wed, 12 May 1999 17:48:54 +0200 (SAST)
Cc: current@freebsd.org
Reply-To: "Geoff Rehmet" <geoffr@is.co.za>
From: "Geoff Rehmet" <geoffr@is.co.za>
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

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