All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric <eric@cisu.net>
To: gmishkin@bu.edu
Cc: linux-kernel@vger.kernel.org
Subject: Re: ld segfault at end of 2.6.6 compile
Date: Wed, 16 Jun 2004 07:01:15 -0500	[thread overview]
Message-ID: <200406160701.15857.eric@cisu.net> (raw)
In-Reply-To: <1087382494.8675.32.camel@amsa>

On Wednesday 16 June 2004 05:41 am, Geoff Mishkin wrote:
> I couldn't find exactly what I was looking for in the BIOS utility (IBM
> ThinkPad T42), but I turned on Diagnostics mode and the RAM check, so at
> boot it checked the RAM, which all turned out okay.

The bios does very wimpy checking of ram. If it is indeed a RAM problem, you 
should use a tool like memtest86 in linux (you boot to it, its not a linux 
tool per se) or prime95(is that the name?) in windows. 

> Still having the problem, though.
>
> 			--Geoff Mishkin <gmishkin@bu.edu>
>

> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

  reply	other threads:[~2004-06-16 12:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-16  2:24 ld segfault at end of 2.6.6 compile Geoff Mishkin
2004-06-16  6:13 ` Harald Dunkel
2004-06-16 10:41   ` Geoff Mishkin
2004-06-16 12:01     ` Eric [this message]
     [not found]       ` <200406161935.55740.vda@port.imtp.ilyichevsk.odessa.ua>
2004-06-16 23:24         ` Geoff Mishkin
  -- strict thread matches above, loose matches on Subject: below --
2004-06-16 11:23 Geoff Mishkin
2004-06-16 11:49 ` Harald Dunkel
2004-06-16 12:43 Geoff Mishkin
2004-06-17  4:16 Geoff Mishkin

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=200406160701.15857.eric@cisu.net \
    --to=eric@cisu.net \
    --cc=gmishkin@bu.edu \
    --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.