All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Fleming <matt@console-pimps.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] sh: mach-ecovec24: update ecovec24 defconfig
Date: Mon, 30 Nov 2009 19:58:24 +0000	[thread overview]
Message-ID: <20091130195824.GA26460@console-pimps.org> (raw)
In-Reply-To: <uws1cuyrg.wl%morimoto.kuninori@renesas.com>

On Mon, Nov 30, 2009 at 07:11:29PM +0900, Kuninori Morimoto wrote:
> 
> Dear Paul
> 
> > > because currect kernel can not use CONFIG_CACHE_WRITEBACK
> > >
> > Uhm, why not? Where is the bug report on this?
> 
> Now I searched by git bisect
> I tested on ms7724se / ecovec24
> 
> -------------------------
> eb3118f652ea7751ecf6a7e467bb637895e3be3b is first bad commit
> commit eb3118f652ea7751ecf6a7e467bb637895e3be3b
> Author: Matt Fleming <matt@console-pimps.org>
> Date:   Thu Oct 29 21:53:30 2009 +0000
> 
> sh: Do not apply virt_to_phys() to a physical address
> 

Could you apply this patch and post the backtrace?

diff --git a/arch/sh/mm/cache-sh4.c b/arch/sh/mm/cache-sh4.c
index 6bfd08d..8440b12 100644
--- a/arch/sh/mm/cache-sh4.c
+++ b/arch/sh/mm/cache-sh4.c
@@ -89,6 +89,8 @@ static inline void flush_cache_one(unsigned long start, unsigned long phys)
 {
 	unsigned long flags, exec_offset = 0;
 
+	WARN_ON(!(phys >= __MEMORY_START && phys < __MEMORY_START + __MEMORY_SIZE));
+
 	/*
 	 * All types of SH-4 require PC to be uncached to operate on the I-cache.
 	 * Some types of SH-4 require PC to be uncached to operate on the D-cache.

  parent reply	other threads:[~2009-11-30 19:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-27  9:01 [PATCH] sh: mach-ecovec24: update ecovec24 defconfig Kuninori Morimoto
2009-11-30  2:56 ` Paul Mundt
2009-11-30  4:21 ` Kuninori Morimoto
2009-11-30 10:11 ` Kuninori Morimoto
2009-11-30 19:58 ` Matt Fleming [this message]
2009-12-01  0:18 ` Kuninori Morimoto
2009-12-01 22:00 ` Matt Fleming
2009-12-02  1:35 ` Kuninori Morimoto

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=20091130195824.GA26460@console-pimps.org \
    --to=matt@console-pimps.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 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.