From: Ralf Baechle <ralf@linux-mips.org>
To: Steve Graham <stgraham2000@yahoo.com>
Cc: linux-mips@linux-mips.org
Subject: Re: O2 RM7000 Issues
Date: Mon, 24 Sep 2007 12:58:05 +0100 [thread overview]
Message-ID: <20070924115804.GA12300@linux-mips.org> (raw)
In-Reply-To: <12833079.post@talk.nabble.com>
On Fri, Sep 21, 2007 at 08:20:13PM -0700, Steve Graham wrote:
> I've just recently fixed this problem on my E9000 core which is a MSP85XX. I
> did some digging and found that the problem started to occur in 2.6.16 and
> is not there in 2.6.15. I looked into the deltas and found the specific
> change that broke me. The file is c-r4k.c.
>
> In the function "local_r4k_flush_cache_sigtramp" there is a conditional:
>
> if (!cpu_icache_snoops_remote_store && scache_size)
> protected_writeback_scache_line(addr & ~(sc_lsize - 1));
>
> This additional "scache_size" has been added to this conditional. On my
> platform, "scache_size" is set to zero so the
> "protected_writeback_scache_line" is now not being called. I took out the
> "scache_size" from the conditional and now I boot without any illegal
> instructions.
In this case the question is, why is scache_size 0 on your platform? I
suppose that's because sc-rm7k.c has it's own scache_size so c-r4k.c never
gets to see the right value so maybe the sanest fix would be to move
sc-rm7k.c into c-r4k.c.
> As a side note, I also took out the workaround in "war.h". This workaround
> only hid the problem, it didn't fix it. Before I changed the conditional, I
> would crash on every boot without the workaround. The workaround reduced
> the crashes to maybe 1 in 3. Now, without the workaround, and with the
> change in the conditional, I haven't experienced any problems.
>
> I'm sure this change was made for a reason in 2.6.16 so I'm not sure what
> the official fix needs to be but that solved my issues on my platform.
ICACHE_REFILLS_WORKAROUND_WAR is a separate issue - you need to enable it
for all RM7000 and also unless PMC changed mind also all E9000 cores. So
while I can understand that disabling this for testing a fix for the real
issue you definately should reenable this once you're done.
> Let me know if there is anything anyone wants me to try on my platform to
> help come to an official fix for this problem.
I wrote most of that stuff anyway ...
Ralf
next prev parent reply other threads:[~2007-09-24 11:58 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-01 16:57 O2 RM7000 Issues Kumba
2007-07-01 22:07 ` freshy98
2007-07-02 13:08 ` sknauert
2007-07-02 13:08 ` sknauert
2007-07-04 15:27 ` Ralf Baechle
2007-07-04 19:22 ` Ralf Baechle
2007-07-16 11:53 ` Sergey Rogozhkin
2007-07-16 12:33 ` Ralf Baechle
2007-07-16 17:38 ` Andrew Sharp
2007-07-17 14:01 ` Kumba
2007-07-19 18:58 ` Andrew Sharp
2007-07-19 22:26 ` Shane McDonald
2007-07-17 7:54 ` Gleb O. Raiko
2007-07-17 9:04 ` Sergey Rogozhkin
2007-07-17 10:14 ` Ralf Baechle
2007-07-17 12:27 ` Ralf Baechle
2007-09-17 23:04 ` Steve Graham
2007-09-18 8:52 ` Ralf Baechle
2007-09-17 23:20 ` David Daney
2007-09-18 8:47 ` Ralf Baechle
2007-07-02 14:34 ` Maciej W. Rozycki
2007-09-21 6:27 ` Sagar Borikar
2007-09-21 13:47 ` Ralf Baechle
2007-09-22 3:20 ` Steve Graham
2007-09-24 11:58 ` Ralf Baechle [this message]
2007-09-26 17:06 ` Steve Graham
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=20070924115804.GA12300@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=stgraham2000@yahoo.com \
/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