Date: Wed, 13 Dec 2000 13:17:38 -0800 From: Mike Smith <msmith@freebsd.org> To: John Baldwin <jhb@FreeBSD.ORG> Cc: "Ronald F. Guilmette" <rfg@monkeys.com>, freebsd-hardware@FreeBSD.ORG, Mike Smith <msmith@FreeBSD.ORG> Subject: Re: Help! "Fatal trap 1: privledged instruction trap" while inst Message-ID: <200012132117.eBDLHc310072@mass.osd.bsdi.com> In-Reply-To: Your message of "Wed, 13 Dec 2000 10:47:47 PST." <XFMail.001213104747.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> > Fatal trap 1: privledged instruction fault while in vm86 mode
> > instruction pointer = 0xcc00:0x30d3
> > stack pointer = 0x0:0xff8
> > frame pointer = 0x0:0x0
> > code segment = base 0x0, limit 0x0, type 0x0
...
> Mike, would this address be mapped to 0xc00cf0d3 in the kernel? (And thus in
> /dev/mem?) If so, Ronald, do this as root:
>
> - install nasm from ports/devel/nasm (or from sysinstall)
> # dd if=/dev/mem iseek=0xc00cf0d3 bs=1 count=16 | ndisasm
>
> Then mail back the resulting text you get. This will show us what instruction
> it died on.
Actually, /dev/mem is a 1:1 mapping of physical memory. (You're thinking
of /dev/kmem). But you're almost right; the code in question will be at
0xcf0d3 offset in /dev/mem, so:
# dd if=/dev/mem iseek=0xcf0d3 bs=1 count=16 | ndisasm
--
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also. But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view. [Dr. Fritz Todt]
V I C T O R Y N O T V E N G E A N C E
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200012132117.eBDLHc310072>