From: Florian Lohoff <flo@rfc822.org>
To: "Kevin D. Kissell" <kevink@mips.com>
Subject: Re: MIPS32 patches breaking DecStation
Date: Tue, 9 Jan 2001 09:54:38 +0100 [thread overview]
Message-ID: <20010109095438.A10683@paradigm.rfc822.org> (raw)
In-Reply-To: <000501c079d3$fefe1a60$0deca8c0@Ulysses>; from kevink@mips.com on Tue, Jan 09, 2001 at 01:34:47AM +0100
On Tue, Jan 09, 2001 at 01:34:47AM +0100, Kevin D. Kissell wrote:
> Florian,
>
> Could you do me a huge favor and try a build that
> uses 3 or 4 nops instead of the branch to the instruction
> after the delay slot? There was a reason that I eliminated
No problem - Done - doesnt work
> the branch construct from the MIPS internal Linux source
> base - it's a hack that works perfectly on R4000's, but
> it's pretty much a coincidence that it does so. Yes,
> the code fragment in question is R4K-specific, but
> we really need to migrate towards the use of consistent
> mechanisms that work across the full range of MIPS
> CPUs. Ideally, *all* CP0 hazards should some day be
> padded out with "ssnops" (sll $0,$0,1, if I recall), which
> force a 1 cycle delay per instruction even on superscalar
> MIPS CPUs.
It immediatly after starting init goes crazy with "Illegal instruction"
and dies like this:
[ ... a couple hundret Illegal instruction ... ]
[init:1] Illegal instruction 8f9983d4 at 0fb68df8 ra=0fb68a20
[init:1] Illegal instruction 8fbc0018 at 0fb68e08 ra=0fb68a20
[init:1] Illegal instruction 02402021 at 0fb68e10 ra=0fb68a20
[init:1] Illegal instruction 00000000 at 0fb68e18 ra=0fb68a20
Kernel panic: Attempted to kill init!
BUG IN DYNAMIC LINKER ld.so: dl-minimal.c: 67: malloc: Assertion `n <= _dl_page!
It seems we need a R4000 2.0/3.0 special except_vec_r4000 like we already
have for the R4600 and some other kinds of mips CPUs.
Flo
--
Florian Lohoff flo@rfc822.org +49-5201-669912
Why is it called "common sense" when nobody seems to have any?
next prev parent reply other threads:[~2001-01-09 8:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-08 23:41 MIPS32 patches breaking DecStation Florian Lohoff
2001-01-08 23:41 ` Florian Lohoff
2001-01-09 0:34 ` Kevin D. Kissell
2001-01-09 0:34 ` Kevin D. Kissell
2001-01-09 8:54 ` Florian Lohoff [this message]
2001-01-09 17:11 ` Harald Koerfgen
2001-01-09 18:28 ` Ralf Baechle
2001-01-09 19:30 ` Kevin D. Kissell
2001-01-09 19:30 ` Kevin D. Kissell
2001-01-09 19:54 ` Ralf Baechle
2001-01-09 19:54 ` Ralf Baechle
2001-01-09 20:33 ` Kevin D. Kissell
2001-01-09 20:33 ` Kevin D. Kissell
2001-01-09 15:09 ` Ralf Baechle
2001-01-09 15:09 ` Ralf Baechle
2001-01-09 15:50 ` Kevin D. Kissell
2001-01-09 15:50 ` Kevin D. Kissell
2001-01-09 16:43 ` Harald Koerfgen
2001-01-09 17:01 ` Ralf Baechle
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=20010109095438.A10683@paradigm.rfc822.org \
--to=flo@rfc822.org \
--cc=kevink@mips.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