Subject: Re: port-sparc/14180: random segfault on IPC with -current
To: None <port-sparc@netbsd.org>
From: Izumi Tsutsui <tsutsui@ceres.dti.ne.jp>
List: port-sparc
Date: 10/08/2001 00:21:28
In article <200110071048.f97Amjf00764@rochebonne.antioche.eu.org>
bouyer@antioche.eu.org wrote:
> >Number: 14180
> >Category: port-sparc
> >Synopsis: random segfault on IPC with -current
:
> >Description:
> On a sparc IPC, processes get memory corruption under moderate load
> (like a 'make -j2' kernel compile).
> This usually results in process cc1 getting a signal 11, but I've
> also seen spurious syntax error report from cpp or cc.
> Restarting the build make it go a little bit further.
> I get this with both 1.5.1 and -current userland; the machines are
> rock solid under 1.5.1 (I tested it on 2 different IPC, I also swapped
> simms, initially suspecting a hardware problem).
> I've not experienced any filesystem corruption, so it really seems
> to be a problem in the VM of the proccess itself. I can reproduce this
> with 16, 32 or 48MB of RAM installed.
Does anyone else see these random coredumps?
My SS1+ has been annoyed by this problem since I updated the kernel
from 1.5_ALPHA to 1.5K (or 1.5L). 1.5-release kernel had no problem.
I tried to track this problem for long time, but got no clue..
There were some reports that IPX and SS1 had the same problem.
(sun4c only problem?)
---
Izumi Tsutsui
tsutsui@ceres.dti.ne.jp