Messages in this thread | | | From | "Rafael J. Wysocki" <> | Subject | Re: AMD64 Machine hardlocks when using memset | Date | Wed, 6 Apr 2005 09:02:11 +0200 |
| |
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/
| |