mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Willy Tarreau <willy@w.ods.org>
To: Sanjoy Mahajan <sanjoy@mrao.cam.ac.uk>
Cc: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>,
	linux-kernel@vger.kernel.org
Subject: Re: Thinkpad 560X w/ 160MB memory (2.4.24 kernel): many segfaults
Date: Wed, 24 Mar 2004 01:31:45 +0100	[thread overview]
Message-ID: <20040324003145.GA9637@alpha.home.local> (raw)
In-Reply-To: <E1B5ubY-0003Om-00@coll.ra.phy.cam.ac.uk>

On Tue, Mar 23, 2004 at 10:42:40PM +0000, Sanjoy Mahajan wrote:
> > burnBX (from cpuburn) could detect the problem within 8 seconds.
> > [or burnMMX]
> 
> Thanks for these suggestions.  I ran each for several minutes and got
> no errors.  So I'm still puzzled, but maybe it is a subtle memory
> incompatability that neither program detects (yet somehow Linux works
> the machine so hard and uncovers it?).

Sorry, but IIRC both burnBX and burnMMX don't test a large portion of RAM,
but only a small amount (4 MB ?) by default. So it's fairly possible that
without options, it runs on your on-board RAM only. I believe you had to
specify it a letter as a first and only parameter. I used 'P' which meant
64 MB. I don't remember if you have higher sizes, but at least you can
start several of them in parallel to lock more memory.

Willy


  reply	other threads:[~2004-03-24  0:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200403230847.05533.vda@port.imtp.ilyichevsk.odessa.ua>
2004-03-23 22:42 ` Sanjoy Mahajan
2004-03-24  0:31   ` Willy Tarreau [this message]
2004-03-22 22:34 Sanjoy Mahajan
2004-03-23  5:52 ` Willy Tarreau

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=20040324003145.GA9637@alpha.home.local \
    --to=willy@w.ods.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sanjoy@mrao.cam.ac.uk \
    --cc=vda@port.imtp.ilyichevsk.odessa.ua \
    /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