From: Philip Lawatsch <philip@lawatsch.at>
To: Philip Lawatsch <philip@lawatsch.at>
Cc: Robert Hancock <hancockr@shaw.ca>, linux-kernel@vger.kernel.org
Subject: Re: AMD64 Machine hardlocks when using memset
Date: Wed, 06 Apr 2005 13:22:39 +0200 [thread overview]
Message-ID: <4253C67F.3010802@lawatsch.at> (raw)
In-Reply-To: <4253C0FC.6070402@lawatsch.at>
Philip Lawatsch wrote:
>>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..
>
> It seems that mov'ing does not kill my machine while simply using movnti
> does.
Forget about what I just wrote, I've been able to reproduce this in
32bit mode too although it did take a long while to happen.
And glibc in 32bit mode simply uses mov in a normal loop to write to the
memory.
Looks like using mov in 64bit mode polluted my cache and crippled
performance (have been running some other programs in the background)
and thus perhaps didnt trigger the problem.
I'm going nuts with this.
kind regards Philip
next prev parent reply other threads:[~2005-04-06 11:22 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 ` AMD64 Machine hardlocks when using memset 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 [this message]
[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=4253C67F.3010802@lawatsch.at \
--to=philip@lawatsch.at \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox