Date: Thu, 11 Sep 1997 21:06:42 -0700 (PDT) From: Doug White <dwhite@gdi.uoregon.edu> To: "Brian D. Howard" <bdh@hfnet.sinai.org> Cc: Problems@hfnet.sinai.org, FreeBSD Questions <questions@FreeBSD.ORG> Subject: Re: Cyrix Message-ID: <Pine.BSF.3.96.970911210441.16497H-100000@localhost> In-Reply-To: <m0x8s7i-0000CgC@hfnet.sinai.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 10 Sep 1997, Brian D. Howard wrote:
> On a new motherboard that an existing pair of IDE drives were moved to
> I get the following error:
>
>
> Fatal trap 1: privileged instruction fault while in kernel mode.
> instruction pointer = 0x8:0xf01b99aa
> stack pointer = 0x10:0xefbfff38
> frame pointer = 0x10:0xefbfff50
> code segment = base 0x0, limit 0xfffff, type 0x1b
> = DPL 0, pres 1, def32 1, gran 1
> processor eflags = resume, IOPL = 0
> current process = 0 ()
> interrupt mask = net tty bio
> panic: privileged instrction fault
>
> When booting the FreeBSD 2.2.2 Walnut Creek June 1997 distribution right
> after the kernel signs on. This occurs also with install floppy made from
> the CD.
Could you be more specific as to where this appears? For instance, a
screenshot showing the lines above this would be really helpful for
pinpointing the problem.
If you don't the CPU probe lines (which look like the following on my
Intel P133):
Copyright (c) 1992-1996 FreeBSD Inc.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
FreeBSD 2.2-970215-GAMMA #19: Thu Jul 24 20:01:33 PDT 1997
dwhite@gdi.uoregon.edu:/usr/src/sys/compile/GDI
Calibrating clock(s) relative to mc146818A clock ... i586 clock: 133272505
Hz, i
8254 clock: 1193213 Hz
CPU: Pentium (133.27-MHz 586-class CPU)
Origin = "GenuineIntel" Id = 0x52c Stepping=12
Features=0x1bf<FPU,VME,DE,PSE,TSC,MSR,MCE,CX8>
real memory = 41943040 (40960K bytes)
avail memory = 38260736 (37364K bytes)
Probing for devices on PCI bus 0:
If you could point out how far down you get before it panics, that would
be great.
If it doesn't make it to the CPU: line I bet your CPU isn't reacting very
nicely to the CPU probe. It may not be known as of yet and a probe
routine needs to be written.
Doug White | University of Oregon
Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant
http://gladstone.uoregon.edu/~dwhite | Computer Science Major
Spam routed to /dev/null by Procmail | Death to Cyberpromo
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.970911210441.16497H-100000>