On Sat, Sep 25, 2004 at 01:42:50AM +1000, Stuart Longland wrote:
> > The 64 bit kernel should work so far - With the ip22zilog.c fixes
> > tsbogend just committed the console begins to work again.
> > Includeing the patch i sent earlier my R5k Indy boots fine a 64bit
> > current cvs head and goes into userspace.
> > Using the "soo to be" rtc and statfs64 fixes everything seems to be
> > fine for o32 userspace.
> Tried the patch, for some reason 'patch' couldn't find some of the
> files, and was expecting me to enter the paths in by hand... but once I
> did that, it applied cleanly.
The last file has a bogus path (Hand crafted patch) and needs the first
path element removed IIRC.
> Exception: <vector=Normal>
> Status register: 0x30004803<CU1,CU0,IM7,IM4,IPL=???,MODE=KERNEL,EXL,IE>
> Cause register: 0x8010<CE=0,IP8,EXC=RADE>
> Exception PC: 0x830f018, Exception RA: 0x88804514
> Read address error exception, bad address: 0x830f018
>Local I/O interrupt register 1: 0x80 <VR/GIO2>
> Saved user regs in hex (&gpda 0xa8740e48, &_regs 0xa8741048):
> arg: a8740000 88002000 88001fe0 18
> tmp: a8740000 2 8880e0b4 8360020 8880e0b0 887fe53c 887fe234 9fc55064
> sve: a8740000 3 400000 8000000 16 3f80 0 10000000
> t8 a8740000 t9 ffffffff at ffffffff v0 ffffffff v1 ffffffff k1 8360020
> gp a8740000 f0 ffffffff sp ffffffff ra ffffffff
> PANIC: Unexpected exception
This should be a crash in free_bootmem_core because of the non correct
> I can't rule out it being something with my config though. Has someone
> got a working config for mips64 on this class of machine? (even a
> binary) Seeing as it works on R5k, could we be dealing with an R4x00
> bug here?
Florian Lohoff firstname.lastname@example.org +49-171-2280134
Heisenberg may have been here.
Description: PGP signature