From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-mips@oss.sgi.com
Subject: Re: [Oops] Indy R4600 Oops(es) w/ 2.4.19-rc1
Date: Sun, 30 Jun 2002 19:47:17 +0200 [thread overview]
Message-ID: <20020630174717.GI17216@lug-owl.de> (raw)
In-Reply-To: <20020629220513.GC17216@lug-owl.de>
[-- Attachment #1: Type: text/plain, Size: 653 bytes --]
On Sun, 2002-06-30 00:05:13 +0200, Jan-Benedict Glaw <jbglaw@lug-owl.de>
wrote in message <20020629220513.GC17216@lug-owl.de>:
[...]
> 10: bc600060 0xbc600060
> Code; 88016ce0 <r4k_flush_cache_range_d32i32+e4/16c>
> 14: bc600080 0xbc600080
Well, I've bulid the same kernel with CONFIG_MIPS_UNCACHED and the box
is running^Wsnailing fine with it. I'm experiencing a little peformance
drop (100 BogoMips -> 2.79 BogoMips), but it comes up in finite time:-)
MfG, JBG
--
Jan-Benedict Glaw . jbglaw@lug-owl.de . +49-172-7608481
-- New APT-Proxy written in shell script --
http://lug-owl.de/~jbglaw/software/ap2/
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2002-06-30 17:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-29 22:05 [Oops] Indy R4600 Oops(es) w/ 2.4.19-rc1 Jan-Benedict Glaw
2002-06-30 17:47 ` Jan-Benedict Glaw [this message]
2002-07-01 9:13 ` Jan-Benedict Glaw
2002-07-01 9:43 ` Jan-Benedict Glaw
2002-07-01 14:28 ` Maciej W. Rozycki
2002-07-01 15:13 ` Jan-Benedict Glaw
2002-07-01 17:02 ` Maciej W. Rozycki
2002-07-01 17:22 ` Jan-Benedict Glaw
2002-07-01 17:24 ` Karel van Houten
2002-07-01 17:27 ` Jan-Benedict Glaw
2002-07-01 17:46 ` Maciej W. Rozycki
2002-07-01 15:55 ` Buggy R4600 support (was: [Oops] Indy R4600 Oops(es) w/ 2.4.19-rc1) Jan-Benedict Glaw
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=20020630174717.GI17216@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=linux-mips@oss.sgi.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