9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Missing interrupts in 9pxeload?
Date: Fri,  5 Jun 2009 22:18:06 -0400	[thread overview]
Message-ID: <5557ac66b8ce61ab8ec505beefdcd20e@quanstro.net> (raw)
In-Reply-To: <aa7e41150906051518neddb215y7ebf69b2499f5777@mail.gmail.com>

> Hmm, I don't think so.  There basically are no other peripherals in
> the machine, and I disabled everything except the Ethernet and video
> in the BIOS with the same results.  My suspicion is that the interrupt
> vector isn't being initialized properly.

i think there are two general possiblities.
(a) the southbridge is not recognized and irq routing is not
properly initialized
(b) 9load is stepping on low memory that bios tells us
is not available.  in general x86 platforms have been shrinking
the amount of low memory available.

to tell what is going on, i think it would make sense to strip
everything out of 9load and just get to main() and set up
a clock interrupt at the default 86Hz and print something each
time through.  then call HLT.

i can't see how this could fail (i.e. print nothing), but if it does
at least we know where to start.

if it works, then we can start investigating other possibilties.

- erik



  reply	other threads:[~2009-06-06  2:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-04 20:38 Dan Cross
2009-06-05 18:28 ` erik quanstrom
2009-06-05 20:49   ` Dan Cross
2009-06-05 21:30     ` balaji
2009-06-05 22:18       ` Dan Cross
2009-06-06  2:18         ` erik quanstrom [this message]
2009-06-06  6:57           ` Dan Cross
2009-06-06 15:00             ` erik quanstrom
2009-06-06  2:19     ` 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=5557ac66b8ce61ab8ec505beefdcd20e@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).