public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: "Björn Engelhardt" <bjoern2@xqueue.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel 2.6.17.8 on Quad AMD Opteron 852 with 16x 4GB Modules (64GB RAM)
Date: 23 Aug 2006 23:17:25 +0200	[thread overview]
Message-ID: <p73d5ar5eze.fsf@verdi.suse.de> (raw)
In-Reply-To: <44EC4EE2.6060701@xqueue.de>

Björn Engelhardt <bjoern2@xqueue.de> writes:

> we upgraded a Server from 32 GB RAM to 64 GB. Now we try to get a
> Linux (FC5) with kernel 2.6.17.8 on a Quad Opteron (852; 64bit)-system
> with 16x 4GB modules to run.
> With 32 GB (8x 4GB modules) the system starts without any problems,
> but above I get kernelpanics.

It 99.9+% likely a hardware or BIOS or power supply/VRM/cooling
problem of some sort. So many DIMMs are quite stress full
to the system and can expose issues which were hidden before.
Or you might run into some other BIOS/hardware issue.

You can post the exact text of the panics from a serial console
if you want, but most likely you will get the same answer even then.

I would start talking to your hardware vendor.

> The output then gives me several memoryaddresses bevore the panic
> appears. The board (a Tyan K8QW,model S4881) should support up to 64GB
> Ram. A Memorytest under Linux recognizes the 64GB and continues
> without an error.
> I tried several BIOS-Settings.
> Does the kernel support the new 4GB-Modules by 64GB Ram?

The kernel doesn't know anything about DIMMs, it just gets a memory
map from the BIOS.

-Andi

  parent reply	other threads:[~2006-08-23 21:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-23 12:49 Kernel 2.6.17.8 on Quad AMD Opteron 852 with 16x 4GB Modules (64GB RAM) Björn Engelhardt
2006-08-23 15:51 ` H. Peter Anvin
2006-08-23 21:17 ` Andi Kleen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-08-24 10:30 Maciek Zobniow

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=p73d5ar5eze.fsf@verdi.suse.de \
    --to=ak@suse.de \
    --cc=bjoern2@xqueue.de \
    --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