linux-mips
[Top] [All Lists]

Re: 2.6 on IP22 (Indy)

To: "Maciej W. Rozycki" <macro@linux-mips.org>
Subject: Re: 2.6 on IP22 (Indy)
From: Markus Dahms <mad@automagically.de>
Date: Mon, 27 Jun 2005 16:18:42 +0200
Cc: linux-mips@linux-mips.org
In-reply-to: <Pine.LNX.4.61L.0506271401280.15406@blysk.ds.pg.gda.pl>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <20050627100757.GA27679@gaspode.automagically.de> <Pine.LNX.4.61L.0506271401280.15406@blysk.ds.pg.gda.pl>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.5.9i
>> My experiments: Indy with R4600PC (133MHz) boots to userspace
>> | INIT: version 2.86 booting
>> and dies then :(. The same machine, but with a R4000PC (100MHz)
>  Hmm, it might be a problem with TLB handlers that have been changed to be 
> built at the run time.  Perhaps the R4600 isn't handled right as a result.  
> What's the CPU revision ID? -- it's printed right at the beginning.

| CPU revision is: 00002020
| FPU revision is: 00002020
| ...
| Synthesized TLB refill handler (30 instructions).
| Synthesized TLB load handler fastpath (43 instructions).
| Synthesized TLB store handler fastpath (43 instructions).
| Synthesized TLB modify handler fastpath (42 instructions).

the TLB stuff, if it's of interest...

| ...
| Calibrating system timer... warning: timer counts differ, retrying...\
| disagreement, using average... 44500 [89.0000 MHz CPU]
| Using 44.500 MHz high precision timer.

this is strange, too. It's a 133MHz CPU as kernel 2.4.x correctly
recognizes.

For the R4000 there are two other things I could try: console on newport
instead of serial port and a 32-bit kernel, which I only tried on the
R4600.
I'll also try the said patch (you're referring to "blast_scache nop ...", do
you?).

Markus

-- 
No RISC - No fun!

<Prev in Thread] Current Thread [Next in Thread>