public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Philip Lawatsch <philip@lawatsch.at>
To: linux-kernel@vger.kernel.org
Subject: Re: AMD64 Machine hardlocks when using memset
Date: Thu, 31 Mar 2005 11:37:25 +0200	[thread overview]
Message-ID: <424BC4D5.90204@lawatsch.at> (raw)
In-Reply-To: <20050331001513.3c4321a7.pj@engr.sgi.com>

Paul Jackson wrote:
> Denis wrote:
> 
>>This reminds me on VIA northbridge problem when BIOS enabled
>>a feature which was experimental and turned out to be buggy.
> 
> 
> You were close!
> 
> I changed my Memory Timing from 1T to 2T, and now it is as solid as a
> rock.  It has been up 7 minutes as I type this, without a hiccup.
> 
> Notice this comment, at http://www.vr-zone.com.sg/?i=1641&p=1&s=0
> 
>     Well as most Athlon 64 users know, 1T setting improves performance quite
>     significantly over 2T, but it is also very taxing on the memory and
>     quite a hit-and-miss when matching different memory with different
>     boards. From some users' feedback, the Asus A8N SLI can be a little
>     picky with 1T setting when overclocking, so results might be a little
>     better with other boards.
> 

I've now tried the most conservative settings available. The 32 bit
kernel now hangs after about 150000 Iterations (compared to about 16000
before) but the 64 bit kernel still hangs after about 5000.

After a ~12 hour memtest86 run memtest86 crashed (!), filling the
console with some garbage characters and then hanging.

This is driving me crazy.

Imo memtest86 should not hang onless something screws up the memory area
it is loaded into.

I've also tried the newest beta bios for the board now, didnt change
anything.

kind regards Philip

  reply	other threads:[~2005-03-31  9:40 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3NTHD-8ih-1@gated-at.bofh.it>
     [not found] ` <3NVqb-1iK-33@gated-at.bofh.it>
2005-03-31  4:32   ` AMD64 Machine hardlocks when using memset Robert Hancock
2005-03-31  4:38 ` Robert Hancock
2005-03-31  7:25   ` Denis Vlasenko
2005-03-31  8:15     ` Paul Jackson
2005-03-31  9:37       ` Philip Lawatsch [this message]
2005-03-31 10:15         ` Paul Jackson
2005-03-31  7:41   ` Paul Jackson
2005-03-31 11:40     ` Mikael Pettersson
2005-03-31 18:47       ` Paul Jackson
     [not found] ` <3O99L-40N-9@gated-at.bofh.it>
2005-04-01  4:37   ` Robert Hancock
2005-04-01 10:41     ` Denis Vlasenko
2005-04-01 17:27     ` Ray Lee
2005-04-01 19:14       ` Philip Lawatsch
     [not found] <3Ojst-4kX-19@gated-at.bofh.it>
     [not found] ` <3OGIo-7oY-13@gated-at.bofh.it>
     [not found]   ` <3OGIo-7oY-15@gated-at.bofh.it>
     [not found]     ` <3OGIo-7oY-17@gated-at.bofh.it>
     [not found]       ` <3OGIo-7oY-11@gated-at.bofh.it>
     [not found]         ` <3OIh7-cc-1@gated-at.bofh.it>
     [not found]           ` <3OITV-AR-3@gated-at.bofh.it>
     [not found]             ` <3PxjH-812-3@gated-at.bofh.it>
2005-04-06  4:05               ` Robert Hancock
2005-04-06  7:02                 ` Rafael J. Wysocki
2005-04-06  9:31                   ` Philip Lawatsch
2005-04-06 10:59                 ` Philip Lawatsch
2005-04-06 11:15                   ` Arjan van de Ven
2005-04-06 11:22                   ` Philip Lawatsch
     [not found] <3NZDp-4yY-7@gated-at.bofh.it>
     [not found] ` <3NZN4-4EZ-1@gated-at.bofh.it>
     [not found]   ` <3O2rK-6MU-19@gated-at.bofh.it>
     [not found]     ` <3O34n-7oN-19@gated-at.bofh.it>
     [not found]       ` <3O4tp-8tL-3@gated-at.bofh.it>
2005-04-01  1:33         ` Robert Hancock
     [not found] ` <3OmgF-6HV-17@gated-at.bofh.it>
     [not found]   ` <3OmgF-6HV-15@gated-at.bofh.it>
     [not found]     ` <3Oy8m-74-15@gated-at.bofh.it>
2005-04-02  2:32       ` Robert Hancock
2005-04-02  4:11         ` Paul Jackson
2005-04-02  4:50           ` Robert Hancock
2005-04-04 10:45             ` Alan Cox
2005-04-06  8:47             ` Denis Vlasenko
2005-03-30 22:04 Philip Lawatsch
2005-03-31  0:05 ` Matthias-Christian Ott
2005-03-31 14:45 ` Stelian Pop

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=424BC4D5.90204@lawatsch.at \
    --to=philip@lawatsch.at \
    --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