From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] snapshot fails to boot
Date: Sun, 8 Aug 2010 23:49:28 -0400 [thread overview]
Message-ID: <96d5fa2d066c7912a6bbeb0e78e4c742@plug.quanstro.net> (raw)
In-Reply-To: <AANLkTimz_KGEGQtSe-PbTZjwrYmu9_m-sNbR=LS7gaWi@mail.gmail.com>
> Press almost any key to reset... FLAGS=10202 TRAP=6 ECODE=0 PC=3
> AX 800116e1 BX 00000f3e CX 8006407 DX 000003d5
> SI 800b8fa0 DI 800b8fa0 BP 0000002e
> CS 0010 DS 0008 ES 0008 FS 0008 GS 0008
> CR0 80000011 CR2 00000000 CR3 0000c000
> panic: exception/interrupt 6
very difficult to say anything useful, since the pc is
nonsense and the error is "invalid opcode". is
anything printed before the fatail error?
- erik
next prev parent reply other threads:[~2010-08-09 3:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-09 2:29 David Hoskin
2010-08-09 3:49 ` erik quanstrom [this message]
2010-08-10 6:12 ` David Hoskin
2010-08-10 6:30 ` David Hoskin
2010-08-10 12:13 ` erik quanstrom
2010-08-11 6:03 ` David Hoskin
2010-08-11 11:02 ` erik quanstrom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=96d5fa2d066c7912a6bbeb0e78e4c742@plug.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).