linux-mips
[Top] [All Lists]

Re: MIPS - 64bit woes

To: Linux MIPS List <linux-mips@linux-mips.org>
Subject: Re: MIPS - 64bit woes
From: Kumba <kumba@gentoo.org>
Date: Wed, 09 Nov 2005 08:36:06 -0500
In-reply-to: <4371B87A.9040101@jg555.com>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <436D0061.5070100@jg555.com> <Pine.LNX.4.55.0511071143210.28165@blysk.ds.pg.gda.pl> <4371B87A.9040101@jg555.com>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Thunderbird 1.5 (Windows/20051025)
Jim Gifford wrote:
Here is what I did to track down the errors.

I created a diff between the last working kernel 2.6.12 and the current kernel. Started with cpu-probe.c, that to me seemed the logical choice.

After patching the rest of files needed to support the patch in cpu-probe.c, I was finally able to produce a kernel under 2.6.12 with the same problem.

The files that I ported from 2.6.14 to 2.6.12 are the following
cpu-probe.c
cpu.h
mipsregs.h
cache.c
cpu-features.h

Here is a link to the patches I used http://ftp.jg555.com/errors

Looking at mipsregs.h, something doesn't look right for a 64 bit system. But I'm not the expert.

Here are my findings, I hope someone out there has an idea.

Stanislaw pretty much figured it out last night.

See the if statement in the 'void __init cpu_cache_init(void)' function in arch/mips/mm/cache.c. IP30, IP27, and cobalt didn't define the appropriate cache type in cpu-features.h, thus failed that check and panicked. I believe it's fixed in the newest IP30 patches, of which I have yet to take a look at.


--Kumba

--
Gentoo/MIPS Team Lead
Gentoo Foundation Board of Trustees

"Such is oft the course of deeds that move the wheels of the world: small hands do them because they must, while the eyes of the great are elsewhere." --Elrond

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