From: Robert Hancock <hancockr@shaw.ca>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: AMD64 Machine hardlocks when using memset
Date: Tue, 05 Apr 2005 22:05:19 -0600 [thread overview]
Message-ID: <42535FFF.4080503@shaw.ca> (raw)
In-Reply-To: <3PxjH-812-3@gated-at.bofh.it>
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..
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next parent reply other threads:[~2005-04-06 4:06 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
2005-04-06 7:02 ` AMD64 Machine hardlocks when using memset 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
[not found] <3NTHD-8ih-1@gated-at.bofh.it>
[not found] ` <3NVqb-1iK-33@gated-at.bofh.it>
2005-03-31 4:32 ` 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
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
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=42535FFF.4080503@shaw.ca \
--to=hancockr@shaw.ca \
--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.