From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Gerhard Pircher <gerhard_pircher@gmx.net>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: [RFC] Workaround for G4 CPU data corruption bug
Date: Fri, 17 Nov 2006 19:16:50 +1100 [thread overview]
Message-ID: <1163751410.5826.15.camel@localhost.localdomain> (raw)
In-Reply-To: <20061116084800.132070@gmx.net>
On Thu, 2006-11-16 at 09:48 +0100, Gerhard Pircher wrote:
> Hi,
>
> I need to fix the CPU bug described here:
> http://ozlabs.org/pipermail/linuxppc-dev/2004-August/017440.html
>
> The bug is worked around in Linux (since a long time) by enabling coherency (M bit) for all memory mappings. Unfortunately my AmigaOne crashes badly with this workaround (the system simply stops after setting up the PCI host controller). I'm afraid I don't know about any snoop control settings within the northbridge.
>
> Thus the only workaround I can think of would be to disable the L2 cache prefetch logic. But would this workaround be accepted in the Linux source tree (only for one architecture) or does anybody know another workaround?
Not sure what the best approach is at this point. The platform probing
occurs after the CPU fixups on 32 bits, though I want to change that to
be more like 64 bits in the future, it's not yet done.
Ben.
prev parent reply other threads:[~2006-11-17 8:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-16 8:48 [RFC] Workaround for G4 CPU data corruption bug Gerhard Pircher
2006-11-17 8:16 ` Benjamin Herrenschmidt [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=1163751410.5826.15.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=gerhard_pircher@gmx.net \
--cc=linuxppc-dev@ozlabs.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