mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andi Kleen <ak@muc.de>
To: Andreas Klein <Andreas.C.Klein@physik.uni-wuerzburg.de>
Cc: Andrew Walrond <andrew@walrond.org>,
	linux-kernel@vger.kernel.org,
	Sergei Haller <Sergei.Haller@math.uni-giessen.de>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	discuss@x86-64.org
Subject: Re: lost memory on a 4GB amd64
Date: 23 Oct 2004 18:43:52 +0200	[thread overview]
Date: Sat, 23 Oct 2004 18:43:52 +0200	[thread overview]
Message-ID: <20041023164352.GA52982@muc.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0410231137450.3885@pluto.physik.uni-wuerzburg.de>

[cc'ed to discuss@x86-64.org for future reference. If you find
this message in google and you have the same problem, talk
to your BIOS vendor, not to your Linux vendor]

On Sat, Oct 23, 2004 at 12:02:10PM +0200, Andreas Klein wrote:
> - Tyan S2885 pre-production model with a 1.01 pre-release bios
> 6 mb ram (4x512mb, 4x1gb)
> The machine is running SuSE Linux Enterprise Server 8 (32bit).
> We use this machine as our primary mail-server without problems for over a 
> year.
> 
> - Now we ordered 45 Tyan S2885 and 4 S2875S board.
> Both board do not run stable with more than 2GB ram usable.
> 4GB will only be recognized if the MTRR setting is set to Continuous and 
> the Adjust Memory setting is set to Auto.
> If the bios is configured this way and two 1gb ram modules are installed 
> for each CPU on the 2885, the machine will not even load and unpack a 
> SLES 9 kernel. Memtest sees 0-2GB mem usable and 4-6GB unusable (complains 
> about each memory address).
> If all four modules are installed for CPU0, then memtest seems to work 
> without problems (0-2GB, 4-6GB), but SLES9 will crash during boot-up.
> If all four modules are installed for CPU1, then memtest seems to work 
> without problems too. SLES 9 will run a few minutes before a crash.
> I will try to install SLES 8 (32bit) on the new boxes to see if it runs 
> stable. If yes, there is something broken in the 2.6 kernels for amd64, if 
> not, the pre-production bios is better that the final ones.

It all sounds very much like a BIOS problem. I doubt 2.4 will
run stable on this setup - if memtest86 doesn't like the memory, Linux 
won't like it neither. All I can recommend is to talk to Tyan or
live with the lost memory. 

-Andi


  reply	other threads:[~2004-10-23 16:44 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-16  4:48 Sergei Haller
2004-09-16 13:30 ` Andrew Walrond
2004-09-16 13:48 ` Andrew Walrond
2004-09-16 14:09   ` Sergei Haller
2004-09-16 14:28     ` Andrew Walrond
2004-09-16 14:56       ` Sergei Haller
2004-09-16 15:19         ` Andrew Walrond
2004-09-16 15:52           ` Sergei Haller
2004-09-18 14:18             ` Sergei Haller
2004-09-19 20:01               ` Jon Masters
2004-09-19 21:47                 ` Sergei Haller
2004-09-19 22:00                   ` Jon Masters
2004-09-19 22:19                     ` Sergei Haller
2004-09-20 10:26                       ` Sergei Haller
2004-09-24  4:38                         ` Sergei Haller
2004-09-24  8:15                         ` Andrew Walrond
2004-09-24  8:23                           ` Sergei Haller
2004-09-24  8:31                             ` Andrew Walrond
2004-09-24  8:57                               ` Sergei Haller
2004-09-24  9:27                                 ` Rafael J. Wysocki
2004-09-24  9:41                                   ` Andrew Walrond
2004-09-24 11:42                                     ` Sergei Haller
2004-09-24 12:15                                       ` Andrew Walrond
2004-10-22  8:59                                         ` Sergei Haller
2004-10-22  9:26                                           ` Andrew Walrond
2004-10-22 18:24                                             ` Andi Kleen
2004-10-23 10:02                                               ` Andreas Klein
2004-10-23 16:43                                                 ` Andi Kleen [this message]
2004-10-26 11:25                                                   ` Andreas Klein
2004-10-23 10:26                                               ` Sergei Haller
2004-10-23 16:49                                                 ` Andi Kleen
2004-10-24  9:53                                                   ` Sergei Haller
     [not found]                                                     ` <Pine.LNX.4.58.0410271704050.3903@pluto.physik.uni-wuerzburg.de>
2004-10-27 15:39                                                       ` solution " Sergei Haller
2004-10-27 16:05                                                         ` Andreas Klein
2004-10-27 16:17                                                           ` Sergei Haller
2004-10-28 13:32                                                             ` Andreas Klein
2004-10-27 16:44                                                           ` linux-os
2004-10-27 17:47                                                             ` Andrew Walrond
2004-09-24 11:50                                   ` Sergei Haller
     [not found] <2EWxl-7CI-13@gated-at.bofh.it>
2004-09-16  7:01 ` Andi Kleen
2004-09-16 12:15   ` Sergei Haller
2004-09-16 12:34     ` Andi Kleen
2004-09-18 14:07       ` Sergei Haller

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=20041023164352.GA52982@muc.de \
    --to=ak@muc.de \
    --cc=Andreas.C.Klein@physik.uni-wuerzburg.de \
    --cc=Sergei.Haller@math.uni-giessen.de \
    --cc=andrew@walrond.org \
    --cc=discuss@x86-64.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    /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

Powered by JetHome