Port-sgimips archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: kernel panic on IP32 R12000

Quoting Luc Pernot <lpernot%magma.ca@localhost>:

yes I think so because I switched the netbsd kernell fie with generic
ip32 kernell one and every thing work's
i'm installing the X set right now... and when i restarted sysinst
and whent in install additionnal sets it was saying yes to ip2x kernel
...? Luc.

The kernel selection in sysinst should be fixed as of a few minutes ago in -current.


Stephen M. Rumble wrote:

Quoting Martin Husemann <martin%duskware.de@localhost>:

On Sun, Jan 27, 2008 at 11:01:38AM -0500, Michael Lorenz wrote:

Is the R12k really /that/ different from the R10k?
The panic was about cache support, the R10k code might just work here.

Besides the early "cache not supported" panic, which does not happen on
R10k, the cpu is not realy better supported - on my R10k O2 I get a
panic as soon as something uses dma (not quite unexpected). A simple
"ping" is enough.

Looking at the code, regardless of whether the R12k support is broken or not, this panic shouldn't be happening with GENERIC32_IP3x, no? It looks like `ENABLE_MIPS4_CACHE_R10K' is in the config and should handle R10000, R12000 and R14000 cases.

I think somebody reported this a while back and I suspected they were running the wrong kernel (maybe GENERIC_IP2x). Perhaps our installer is not choosing the appropriate one by default...


Home | Main Index | Thread Index | Old Index