mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Michael Madore" <michael.madore@gmail.com>
To: discuss@amd64.org
Cc: linux-kernel@vger.kernel.org
Subject: Lockup/reboots on multiple dual core Opteron systems
Date: Fri, 14 Apr 2006 09:48:13 -0700	[thread overview]
Message-ID: <d4b6d3ea0604140948l36c8048ha819a6611c8fdad3@mail.gmail.com> (raw)

Hi,

I have several dozen systems based on the AMD 8111/8131 chipset which
are experiencing lockups or reboots while under heavy stress.  All
systems are configured identically:

(2) dual core Opteron 285 processors
8 GB RAM
1 IDE hard disk

When the lockup occurs, there is no information printed to the screen,
and magic sysrq does not work.   The systems will often lockup within
a matter of hours, but sometimes they can run for several days before
locking up.

The testing involves:

1) Allocate several GB of memory from each node and read/write to it.
2) Perform lots of disk I/O
3) Keep all cores busy

I see the lockup no matter which kernel I try:

2.6.5 (SLES 9)
2.6.9 (RHEL 4)
2.6.16 (kernel.org)

The systems will run perfectly stable under the following conditions:

1) Use a 32-bit kernel
or
2) Boot 64-bit kernel with mem=3000M
or
3) Don't perform any disk I/O during the test

I have also tested the dual core 8GB combination on both NForce and
Serverworks based motherboards with the same results.  In this case
both systems were using SATA hard disks instead of IDE.

Any ideas what the culprit could be?

Mike

             reply	other threads:[~2006-04-14 16:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-14 16:48 Michael Madore [this message]
2006-04-14 16:39 ` David Lang
2006-04-14 18:02   ` Michael Madore
2006-04-14 18:00     ` David Lang

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=d4b6d3ea0604140948l36c8048ha819a6611c8fdad3@mail.gmail.com \
    --to=michael.madore@gmail.com \
    --cc=discuss@amd64.org \
    --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®