Source-Changes-D archive

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

Re: CVS commit: src/sys/arch/mips/mips



Hello,

On Wed, 30 Apr 2014 14:35:46 +0100
Nick Hudson <skrll%netbsd.org@localhost> wrote:

> On 04/30/14 11:01, Michael wrote:

> > On Wed, 23 Apr 2014 20:57:15 +0000
> > "Nick Hudson"<skrll%netbsd.org@localhost>  wrote:
> >
> >> Module Name:       src
> >> Committed By:      skrll
> >> Date:              Wed Apr 23 20:57:15 UTC 2014
> >>
> >> Modified Files:
> >>    src/sys/arch/mips/mips: pmap.c vm_machdep.c
> > ...
> >> Hopefully this addresses the instability reported in the following PRs:
> >>
> >> PR/44900 - R5000/Rm5200 mips ports are broken
> >> PR/46170 - NetBSD/cobalt 6.0_BETA does not boot
> >> PR/46890 - upcoming NetBSD 6.0 release is very unstable / unusable on 
> >> cobalt qube 2
> >> PR/48628 - cobalt and hpcmips ports are dead
> > I can no longer reproduce the data corruption issues I've seen on sgimips 
> > in the last few years.
> 
> Can you post your dmesg | grep ^cpu

It's an O2:
cpu0 at mainbus0: MIPS R5000 CPU (0x2321) Rev. 2.1 with built-in FPU Rev. 1.0
cpu0: 48 TLB entries, 1TB (40-bit) VAs, 64GB (36-bit) PAs, 16MB max page size
cpu0: 32KB/32B 2-way set-associative L1 instruction cache
cpu0: 32KB/32B 2-way set-associative write-back L1 data cache
cpu0: 1024KB/32B direct-mapped write-through L2 unified cache

> I'm still seeing issues with my cobalt, but I'll keep hunting.

I cvs updated, built a new kernel and saw problems again. Older kernel
( sources from just after this commit) is ok. No clue why, I'll keep
digging, might be local crap or PEBCAK.

Also, what I've been messing with is both kernel and userland built as
n32, guess I should try o32 too. With n32 I get the same compiler
problems as on Loongson - SIGBUS from gmp whenever optimization is
enabled. One built without .asm routines in gmp seems to work so far
( managed to build a working tcsh )

There's a possibly related issue on Loongson - nfs writes get corrupted
in much the same way. No such problem with the working kernel on the O2
though.

have fun
Michael


Home | Main Index | Thread Index | Old Index