From: geoff@collyer.net
To: 9fans@cse.psu.edu
Subject: Re: [9fans] file server install
Date: Wed, 19 Dec 2001 16:52:48 -0800 [thread overview]
Message-ID: <20011220005256.961B6199BE@mail.cse.psu.edu> (raw)
What I noticed first was this:
scsi#0: ncr53c8xx: port 0xe1906000 irq 11
I believe port numbers are limited to 16 bits even for PCI devices,
and given that your ether is at 0x6100, that 0xe1906000 should
probably be 0x6000. Perhaps your BIOS's PCI P'n'P code is broken?
I've seen breakage in assigning IRQs before.
The 0Mbps thing is also worrying; have you tried plugging your
machines into a switch (they're pretty cheap now)?
next reply other threads:[~2001-12-20 0:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-20 0:52 geoff [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-12-20 3:08 jmk
[not found] <20011219141904.5F49E19A67@mail.cse.psu.edu>
2001-12-19 23:52 ` William Gunnells
2001-12-19 8:52 forsyth
2001-12-18 22:32 Russ Cox
[not found] <20011218154004.0E3A619A2C@mail.cse.psu.edu>
2001-12-18 22:18 ` William Gunnells
2001-12-18 23:06 ` Sam Ducksworth
[not found] <20011214170104.C9FF719A0C@mail.cse.psu.edu>
2001-12-18 1:36 ` William Gunnells
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=20011220005256.961B6199BE@mail.cse.psu.edu \
--to=geoff@collyer.net \
--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).