From: tsbogend@alpha.franken.de (Thomas Bogendoerfer)
To: Thiemo Seufer <ica2_ts@csv.ica.uni-stuttgart.de>
Cc: linux-mips@linux-mips.org, ralf@linux-mips.org
Subject: Re: Kernel 2.6 for R4600 Indy
Date: Sun, 3 Oct 2004 13:40:47 +0200 [thread overview]
Message-ID: <20041003114047.GA10766@solo.franken.de> (raw)
In-Reply-To: <20041002204014.GO21351@rembrandt.csv.ica.uni-stuttgart.de>
On Sat, Oct 02, 2004 at 10:40:14PM +0200, Thiemo Seufer wrote:
> Thiemo Seufer wrote:
> [snip]
> > > With this fix the machines goes userspace (reverse engineered by sound
> > > of hard disk) but seems to die somewhere. Probably the same bug as seen
> > > on other archs - die on first fork.
> >
> > The last problem happens only on r4000 and r4400, and occasionally
> > also shows up as "illegal instruction" or "unaligned access". It
> > turned out to be a broken TLB handler. I temporarily switched (for
> > 32bit kernels) from except_vec0_r4000 to except_vec0_r45k_bvahwbug.
> > This may cause an avoidable performance loss, but at least it allows
> > my R4400SC-200 (V6.0) Indy to run current 2.6 CVS.
>
> One more nop is enough to make it work. This should probably go in
> a hazard definition.
excellent, this gets up my Indigo 2 with a 200 MHz CPU
and
my M700:
root@(none):/# cat /proc/cpuinfo
system type : Jazz MIPS_Magnum_4000
processor : 0
cpu model : R4000PC V3.0 FPU V0.0
BogoMIPS : 49.76
wait instruction : no
microsecond timers : yes
tlb_entries : 48
extra interrupt vector : no
hardware watchpoint : yes
VCED exceptions : 0
VCEI exceptions : 0
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessary a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2004-10-03 12:36 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-23 13:54 Kernel 2.6 for R4600 Indy Stuart Longland
2004-09-23 14:51 ` Ladislav Michl
2004-09-23 15:00 ` Stephen P. Becker
2004-09-24 0:16 ` Stuart Longland
2004-09-24 9:07 ` Florian Lohoff
2004-09-24 15:42 ` Stuart Longland
2004-09-24 16:44 ` Florian Lohoff
2004-09-24 13:05 ` Stephen P. Becker
2004-09-24 13:17 ` Robin Humble
2004-09-24 13:27 ` Stephen P. Becker
2004-09-24 13:43 ` Robin Humble
2004-09-24 15:13 ` Stephen P. Becker
2004-09-23 15:48 ` Florian Lohoff
2004-10-02 18:50 ` Thiemo Seufer
2004-10-02 20:40 ` Thiemo Seufer
2004-10-02 23:47 ` Thiemo Seufer
2004-10-03 0:58 ` Maciej W. Rozycki
2004-10-04 14:52 ` Ralf Baechle
2004-10-04 23:48 ` Maciej W. Rozycki
2004-10-05 19:04 ` Ralf Baechle
2004-10-05 19:35 ` Maciej W. Rozycki
2004-10-07 12:28 ` Ralf Baechle
2004-10-03 11:40 ` Thomas Bogendoerfer [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=20041003114047.GA10766@solo.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=ica2_ts@csv.ica.uni-stuttgart.de \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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