From: "Rico Tudor" <rico@patrec.com>
To: linux-kernel@vger.kernel.org
Subject: Re: APIC errors ...
Date: Wed, 18 Apr 101 21:27:12 -0500 (CDT) [thread overview]
Message-ID: <20010419022712.21723.qmail@pc7.prs.nunet.net> (raw)
In-Reply-To: <E14q39x-00068C-00@the-village.bc.nu> from "Alan Cox" at Apr 19, 1 02:22:58 am
Another problem area is ECC monitoring. I'm still waiting for info from
ServerWorks, and so is Dan Hollis. Alexander Stohr has even submitted
code to Jim Foster for approval, without evident effect. I have 18GB of
RAM divided among five ServerWorks boxes, so the matter is not academic.
next prev parent reply other threads:[~2001-04-19 2:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-18 22:21 Dr. Kelsey Hudson
2001-04-05 22:50 ` Kurt Garloff
2001-04-17 12:12 ` Bruce Harada
2001-04-19 1:22 ` Alan Cox
2001-04-19 2:27 ` Rico Tudor [this message]
2001-04-19 4:43 ` Chris Wedgwood
2001-04-19 12:15 ` Steffen Persvold
2001-04-19 2:02 ` Kurt Garloff
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=20010419022712.21723.qmail@pc7.prs.nunet.net \
--to=rico@patrec.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®