From: "Colin Bayer" <colin_bayer@compnerd.net>
To: linux-kernel@vger.kernel.org
Cc: rddunlap@osdlab.org
Subject: Re: Sticky IO-APIC problem
Date: Wed, 4 Jul 2001 21:12:08 -0700 [thread overview]
Message-ID: <200107050412.VAA04157@mail15.bigmailbox.com> (raw)
"Randy.Dunlap" <rddunlap@osdlab.org> wrote:
>I can't find an Intel BN810E board at intel.com or by searching
>at google.com. Are you sure that's the correct name/ID for it?
>Do you have any web page references for it?
Sorry, it was an Intel CA810E board.
(http://www.intel.com/support/motherboards/desktop/ca810e/)
-- Colin
------------------------------------------------------------
The CompNerd Network: http://www.compnerd.com/
Where a nerd can be a nerd. Get your free webmail@compnerd.net!
next reply other threads:[~2001-07-05 4:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-05 4:12 Colin Bayer [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-07-09 12:38 Sticky IO-APIC problem Colin Bayer
2001-07-04 0:19 Colin Bayer
2001-07-03 23:03 Manfred Spraul
2001-07-03 21:58 Randy.Dunlap
2001-07-02 9:25 Colin Bayer
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=200107050412.VAA04157@mail15.bigmailbox.com \
--to=colin_bayer@compnerd.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdlab.org \
/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