public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Hoyle <tmh@nothing-on.tv>
To: Anthony DeRobertis <asd@suespammers.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: CONFIG_HIMEM instability?
Date: Tue, 08 Jan 2002 10:01:05 +0000	[thread overview]
Message-ID: <3C3AC361.20302@nothing-on.tv> (raw)
In-Reply-To: <A44AD072-0364-11D6-BB09-00039355CFA6@suespammers.org>

Anthony DeRobertis wrote:

>> Unfortunately memtest86 is incompatible with this mobo, but the memory 
>> checks out on another machine I tried it on, so I expect it's OK.
> 


I've had no other instablility problems, and downgrading gkrellm to the 
previous version seems to have stopped it dying.  Mozilla started being 
very unstable at the same time..  it could just be a coincidence that 
they all happened at the same time.


> I've had DIMMs not get along. So have other people. This little tester 
> seems to find that fairly well, stunningly --- even when Memtest86 can't 
> find them at all. It found mine in about 30min (512mb box); another 
> persons in an hour or two.


I'll run it & see if anything fails.

 
> PS: You did report the failure to the memtest86 people, right?


Their website says not to report bugs unless you're prepared to do a 
fair bit of debugging yourself.  It also says individual problems won't 
normally be dealt with...  I took the hint and didn't bother.

Tony






  reply	other threads:[~2002-01-08 10:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-06 16:57 CONFIG_HIMEM instability? Tony Hoyle
2002-01-06 17:14 ` Alan Cox
2002-01-06 17:11   ` Tony Hoyle
2002-01-07 11:49 ` Anthony DeRobertis
2002-01-08 10:01   ` Tony Hoyle [this message]
     [not found] <20020108184544.62505ea2.skraw@ithnet.com>
2002-01-08 19:36 ` Anthony DeRobertis

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=3C3AC361.20302@nothing-on.tv \
    --to=tmh@nothing-on.tv \
    --cc=asd@suespammers.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