From: "Gerhard Pircher" <gerhard_pircher@gmx.net>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Kernel locks up after calling kernel_execve()
Date: Thu, 15 Nov 2007 09:48:19 +0100 [thread overview]
Message-ID: <20071115084819.162500@gmx.net> (raw)
In-Reply-To: <18235.28312.88899.861687@cargo.ozlabs.ibm.com>
-------- Original-Nachricht --------
> Datum: Thu, 15 Nov 2007 08:54:32 +1100
> Von: Paul Mackerras <paulus@samba.org>
> An: "Gerhard Pircher" <gerhard_pircher@gmx.net>
> CC: benh@kernel.crashing.org, linuxppc-dev@ozlabs.org
> Betreff: Re: Kernel locks up after calling kernel_execve()
> No it's not just for ppc64. We had a patch that went in some time ago
> to ensure that the M bit was set on various 32-bit platforms because
> otherwise we got data corruption (due to a small cache in the
> northbridge not being kept coherent with the processor cache).
Ah, I thought this was due to a CPU errata, where L2 cache prefetching
causes data corruption with the coherent bit set to 0.
Gerhard
--
Psssst! Schon vom neuen GMX MultiMessenger gehört?
Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger
prev parent reply other threads:[~2007-11-15 8:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-08 21:47 Kernel locks up after calling kernel_execve() Gerhard Pircher
2007-11-08 23:20 ` Benjamin Herrenschmidt
2007-11-09 7:41 ` Gerhard Pircher
2007-11-09 7:50 ` Benjamin Herrenschmidt
2007-11-10 17:11 ` Gerhard Pircher
2007-11-11 3:55 ` Benjamin Herrenschmidt
2007-11-13 21:23 ` Gerhard Pircher
2007-11-13 21:43 ` Benjamin Herrenschmidt
2007-11-13 22:06 ` Gerhard Pircher
2007-11-13 23:37 ` Benjamin Herrenschmidt
2007-11-14 9:39 ` Gerhard Pircher
2007-11-14 10:04 ` Benjamin Herrenschmidt
2007-11-14 10:15 ` Gerhard Pircher
2007-11-14 21:54 ` Paul Mackerras
2007-11-15 8:48 ` Gerhard Pircher [this message]
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=20071115084819.162500@gmx.net \
--to=gerhard_pircher@gmx.net \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).