9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "ron minnich" <rminnich@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] new 9load panic
Date: Sat, 27 Oct 2007 10:11:29 -0700	[thread overview]
Message-ID: <13426df10710271011k2cd82a0bseb1051f3e78263c4@mail.gmail.com> (raw)
In-Reply-To: <82c890d00710271004n32ad87fdle5b350f75f32021c@mail.gmail.com>

On 10/27/07, Gabriel Diaz <gabidiaz@gmail.com> wrote:
> Hello
>
> I pulled today and tryed a new 9load, and that's what i've got:
>
> MBR...PBS1...Plan9 ....
> ELCR: 0C28
> apm: ax f000 cx f000 dx 0x40
> bios0: drive 0x80...type 3
> bios1: driver 0x81...type3
> islba: drive f2: no dap extensions
> sectread: bios failed to read 512 @....
> biosread: failed to read 512....got -1
> dev A0...
> dev B0...
> sectread:....
> biosread:....
> sectread:....
> biosread:....
> using: sdC0!9fat!plan9.ini
> .FLAGS 10292 TRAP e ECODE 2 PC 8000176fa
> AX acf08123 BX 80001a99 CX 800711d8 DX 0000003d
> SI 00000000 DI 80001377 BP 80001250
> CS 0010 DS 0008 ES 0008 FS 0008 GS 0008
> CR0 80000011 CR2 acf08123 CR3 0000c000
> panic: exception interrupt 14
page fault IIRC? somebody want to correct me?
cr2 is at a weird address: acf08123

hmm. I gotta go but you're taking a page fault in 9load it seems? Any
chance your plan9.ini is messed up?

I keep telling people ... pbs should load a kernel, then we don't have
to debug BOTH 9load and a kernel :-)

ron


  reply	other threads:[~2007-10-27 17:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-27 17:04 Gabriel Diaz
2007-10-27 17:11 ` ron minnich [this message]
2007-10-27 19:03 ` geoff
2007-10-27 19:34   ` Gabriel Diaz
2007-10-28  5:54     ` Tim Wiess
2007-10-28 17:13       ` ron minnich
2007-10-28 20:34         ` geoff

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=13426df10710271011k2cd82a0bseb1051f3e78263c4@mail.gmail.com \
    --to=rminnich@gmail.com \
    --cc=9fans@cse.psu.edu \
    /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).