From: "Andrew Lyon" <andrew.lyon@gmail.com>
To: "Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [RFC][PATCH] Re: 4Gb ram not showing up
Date: Thu, 7 Jun 2007 18:37:21 +0100 [thread overview]
Message-ID: <f4527be0706071037l5278fe61v1a733ab874aec136@mail.gmail.com> (raw)
In-Reply-To: <46682FED.2080506@zytor.com>
On 6/7/07, H. Peter Anvin <hpa@zytor.com> wrote:
> Andrew Lyon wrote:
> >
> > Could this also cause a system to be unstable? my abit athlon64 at
> > work will not run x64 with more than 1gb ram, and i have a colo server
> > with supermicro & 2 x dual core xeons that will not run with more than
> > 2gb.
> >
> > Both systems have long uptimes but if i add ram they crash within
> > minutes of booting.
> >
>
> That's much more likely to be caused by bad memory bus layout so that it
> doesn't handle the higher loading.
>
> Run memtest86+ on the expanded memory for some time.
>
> -hpa
>
I have run memtest86+ for days at a time on both systems with no errors at all.
broken hardware i guess, i am not surprised about the abit board, ive
had nothing but trouble with abit motherboards and do not use them any
more, but the supermicro is a xeon server board and i was using
kingston ram, i wouldnt expect that to have issues.
latest bios on both.
Andy
next prev parent reply other threads:[~2007-06-07 17:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-06 12:12 Bodo Eggert
2007-06-06 14:37 ` Lennart Sorensen
2007-06-06 21:55 ` Wakko Warner
2007-06-06 22:12 ` H. Peter Anvin
2007-06-06 22:41 ` Andrew Lyon
2007-06-07 16:18 ` H. Peter Anvin
2007-06-07 17:37 ` Andrew Lyon [this message]
2007-06-09 0:47 ` H. Peter Anvin
2007-06-09 20:38 ` Matt Keenan
2007-06-07 13:49 ` Tom Moore
[not found] <fa.KfNZpadRG0eZUXpSEPaw6ru0bsI@ifi.uio.no>
[not found] ` <fa.onZVzrCKi+mc+cmivZh4BhVROlY@ifi.uio.no>
[not found] ` <fa./NQsJ0P5QQw7SMr++Q5kkRcAJHs@ifi.uio.no>
[not found] ` <fa.v/tV4BtD9VBbszRCBALGEBt2uUw@ifi.uio.no>
2007-06-07 0:09 ` Robert Hancock
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=f4527be0706071037l5278fe61v1a733ab874aec136@mail.gmail.com \
--to=andrew.lyon@gmail.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®