All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockr@shaw.ca>
To: Andrew Lyon <andrew.lyon@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] Re: 4Gb ram not showing up
Date: Wed, 06 Jun 2007 18:09:12 -0600	[thread overview]
Message-ID: <46674CA8.1090700@shaw.ca> (raw)
In-Reply-To: <fa.v/tV4BtD9VBbszRCBALGEBt2uUw@ifi.uio.no>

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.
> 
> Tried several kernels up to 2.6.21 and gave up, I can send dmesg
> output but the crashes are completely random.

That is likely some other problem, like bad RAM or memory timing issues.

-- 
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/


       reply	other threads:[~2007-06-07  0:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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 [this message]
2007-06-06 12:12 [RFC][PATCH] Re: 4Gb ram not showing up 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
2007-06-09  0:47           ` H. Peter Anvin
2007-06-09 20:38           ` Matt Keenan
2007-06-07 13:49 ` Tom Moore

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=46674CA8.1090700@shaw.ca \
    --to=hancockr@shaw.ca \
    --cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.