From: David Gordon Hogan <dhog@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Standalone cpu/auth..
Date: Thu, 16 May 2002 15:26:47 -0400 [thread overview]
Message-ID: <13a76756cc9c192f2c28632e9e99bfeb@plan9.bell-labs.com> (raw)
> > I just tried the cpu/auth standalone on a dual PIII with Intel
> > server mother board. At boot time, i see the message..
> > .....
> > pcirouting: South bridge FFFF, FFFF not found
> > .....
> > pcirouting: Can't find south bridge PCI 255.37.7
I've just realized that the first message is coming out
of 9load, which has an older version of pcirouting()!
It's generally safe to ignore these messages (assuming
that everything else is working ok). We'll add some
more sanity checking in a future version, which should
get rid of messages like the above.
next reply other threads:[~2002-05-16 19:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-16 19:26 David Gordon Hogan [this message]
2002-05-16 19:34 ` Ish Rattan
-- strict thread matches above, loose matches on Subject: below --
2002-05-17 21:48 Ish Rattan
2002-05-16 18:02 David Gordon Hogan
2002-05-16 18:24 ` Ish Rattan
2002-05-16 1:21 rsc
2002-05-16 1:11 David Gordon Hogan
2002-05-16 13:06 ` Ish Rattan
2002-05-16 13:07 ` Ish Rattan
2002-05-16 0:55 Ish Rattan
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=13a76756cc9c192f2c28632e9e99bfeb@plan9.bell-labs.com \
--to=dhog@plan9.bell-labs.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).