Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 12 May 1999 17:54:11 +0200
From:      Geoff Rehmet <geoffr@is.co.za>
To:        "'Poul-Henning Kamp'" <phk@critter.freebsd.dk>, Geoff Rehmet <geoffr@is.co.za>
Cc:        luoqi@watermarkgroup.com, current@FreeBSD.ORG
Subject:   RE: panic ! panic ! panic ! 
Message-ID:  <3D5EC7D2992BD211A95600A0C9CE047F0308D9A5@isjhbex01.is.co.za>

next in thread | raw e-mail | index | archive | help
Only one problem with that - screen and keyboard are not responding when
it panics.  I'm hoping that I will be able to get a dump which I can
look at post mortem.

I'm going to try again though.  The kernel I have at the moment is
totally messing up my keyboard, and I cannot even get a single user
login!

Geoff.

> -----Original Message-----
> From: Poul-Henning Kamp [mailto:phk@critter.freebsd.dk]
> Sent: 12 May 1999 05:56
> To: Geoff Rehmet
> Cc: luoqi@watermarkgroup.com; current@FreeBSD.ORG
> Subject: Re: panic ! panic ! panic ! 
> 
> 
> 
> 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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3D5EC7D2992BD211A95600A0C9CE047F0308D9A5>