From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Robert Hancock <hancockr@shaw.ca>
Subject: Re: AMD64 Machine hardlocks when using memset
Date: Wed, 6 Apr 2005 09:02:11 +0200
User-Agent: KMail/1.7.1
Cc: linux-kernel <linux-kernel@vger.kernel.org>
References: <3Ojst-4kX-19@gated-at.bofh.it> <3PxjH-812-3@gated-at.bofh.it> <42535FFF.4080503@shaw.ca>
In-Reply-To: <42535FFF.4080503@shaw.ca>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-2"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200504060902.12066.rjw@sisk.pl>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1266
Lines: 35

Hi,

On Wednesday, 6 of April 2005 06:05, Robert Hancock wrote:
> Alan Cox wrote:
> > On Sad, 2005-04-02 at 05:50, Robert Hancock wrote:
> > 
> >>I'm wondering if one does a ton of these cache-bypassing stores whether 
> >>something gets hosed because of that. Not sure what that could be 
> >>though. I don't imagine the chipset is involved with any of that on the 
> >>Athlon 64 - either the CPU or RAM seems the most likely suspect to me
> > 
> > 
> > The glibc version is essentially the "perfect" copy function for the
> > CPU. If you have any bus/memory problems or chipset bugs it will bite
> > you.
> 
> Anyone have any suggestions on how to track this further? It seems 
> fairly clear what circumstances are causing it, but as for figuring out 
> what's at fault..

Well, I would start from changing memory modules.

Greets,
Rafael


-- 
- Would you tell me, please, which way I ought to go from here?
- That depends a good deal on where you want to get to.
		-- Lewis Carroll "Alice's Adventures in Wonderland"
-
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/