From: Dan Cross <crossd@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Missing interrupts in 9pxeload?
Date: Fri, 5 Jun 2009 18:18:35 -0400 [thread overview]
Message-ID: <aa7e41150906051518neddb215y7ebf69b2499f5777@mail.gmail.com> (raw)
In-Reply-To: <948781140906051430x59ca6bbnded211ce55f6df42@mail.gmail.com>
On Fri, Jun 5, 2009 at 5:30 PM, balaji<balaji.srinivasa+plan9@gmail.com> wrote:
> I have had the same problems... With a Dell Precision 470.
> In my case it was a SATA controller that was enabled/connected.
>
> The pxeboot will load the boot agent however after that there
> will be no network activity. What this means is the PXE agent
> on the NIC is good and can bring down the initial agent. However
> once it gets going, it has trouble communicating over the network.
>
> It has to be an interrupt issue, and I could never figure it out. I pulled
> the SATA disk out, disabled the controller via BIOS and all was good.
>
> Something similar is happening in yours... Check what peripherals
> you have and see if anything that is not necessary can be disabled
> till you get past this boot process.
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.
- Dan C.
next prev parent reply other threads:[~2009-06-05 22: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 [this message]
2009-06-06 2:18 ` erik quanstrom
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=aa7e41150906051518neddb215y7ebf69b2499f5777@mail.gmail.com \
--to=crossd@gmail.com \
--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).