linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: Probably cache synchronization issue on SH7723
Date: Fri, 04 Dec 2009 06:47:59 +0000	[thread overview]
Message-ID: <20091204064759.GA13603@linux-sh.org> (raw)
In-Reply-To: <4B17B0D6.6020105@emtrion.de>

On Thu, Dec 03, 2009 at 09:45:28PM +0900, Magnus Damm wrote:
> On Thu, Dec 3, 2009 at 9:36 PM, Markus Pietrek
> <Markus.Pietrek@emtrion.de> wrote:
> > when starting bigger graphical applications they suddenly stop with a
> > segmentation fault or a bus error. If I execute the application a second
> > time, everything is fine. Applications that are linked to shared libraries
> > are more likely to fail than statically linked applications.
> >
> > Changing the cache from write-back to write-through fixes it. Maybe the
> > instruction cache and the data cache are not synchronized correctly?
> >
> > I didn't have this problem with the linux-2.6.29 vanilla kernel. 2.6.32rc2
> > from git://git.kernel.org/pub/scm/linux/kernel/git/lethal/sh-2.6 introduced
> > it. And after a pull yesterday even /bin/init is failing.
> 
> I've found that sh7722 and sh7724 doesn't work with copy back cache
> right now, see below. There may be other issues as well, but going
> back to OK fixes it for my initramfs-only case.
> 
I've reverted the problematic parts of this patch for now, so that should
fix up these cases. There's an outstanding issue addressed by Matt's
patch that is being debugged now and which I will push once the remaining
faults on SH7724 have been resolved.

In any event, these changes are bound for 2.6.33, so stock 2.6.32 should
never have been impacted by any of this, and the remaining issues should
be sorted before 2.6.33-rc1. We'll give it another spin for 2.6.34.

  parent reply	other threads:[~2009-12-04  6:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-03 12:36 Probably cache synchronization issue on SH7723 Markus Pietrek
2009-12-03 12:45 ` Magnus Damm
2009-12-04  6:47 ` Paul Mundt [this message]
2009-12-22 16:18 ` AW: " Pietrek, Markus
2009-12-22 16:51 ` Matt Fleming
2009-12-23  8:38 ` AW: " Pietrek, Markus
2009-12-23 23:33 ` Matt Fleming
2009-12-24  5:28 ` Paul Mundt
2009-12-24  9:50 ` AW: " Pietrek, Markus
2009-12-24 10:12 ` Paul Mundt

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=20091204064759.GA13603@linux-sh.org \
    --to=lethal@linux-sh.org \
    --cc=linux-sh@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;
as well as URLs for NNTP newsgroup(s).