From: Manfred Spraul <manfred@colorfullife.com>
To: Jason Czerak <Jason-Czerak@Jasnik.net>, linux-kernel@vger.kernel.org
Subject: Re: ECC memory and SMP lockups on Gateway 6400 server
Date: Mon, 01 Apr 2002 11:44:43 +0200 [thread overview]
Message-ID: <3CA82C0B.98CD7275@colorfullife.com> (raw)
> Recently got the goahead to upgrade the Gateway Win2K server to a linux
> box to replace out old webserver. It's a 6400 server. 2 PIII-733's, 704
> megs ECC registered ram.. NT ran fine on this box. not a hitch.
>
Could you check /proc/interrupts? Is one number extremely high?
And try to boot with "mem=690M". My sis boards become extremely slow if
I don't limit the memory. I guess the e820 map is wrong, and one of the
pages are actually power managmenet registes/NVS.
--
Manfred
next reply other threads:[~2002-04-01 9:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-01 9:44 Manfred Spraul [this message]
2002-04-01 22:25 ` ECC memory and SMP lockups on Gateway 6400 server Jason Czerak
-- strict thread matches above, loose matches on Subject: below --
2002-04-01 22:51 Ed Vance
2002-04-01 6:16 Jason Czerak
2002-04-01 8:41 ` Alan Cox
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=3CA82C0B.98CD7275@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=Jason-Czerak@Jasnik.net \
--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