> SoboMax
> I'm observing very strange memory corruption problems with 2GHz P4
> system running 4.7 (security branch as of today). Under the load
> (make -j20 buildworld) the compiler or make(1) often die with signal
> 11. I found in mailing lists that there is similarly looking problem
> with -cur
On Sun, Nov 17, 2002 at 07:54:48PM -0500, Craig Rodrigues wrote:
> On Sun, Nov 17, 2002 at 11:16:54PM +0200, Maxim Sobolev wrote:
> > Hi there,
> >
> > I'm observing very strange memory corruption problems with 2GHz P4
> > system running 4.7 (security branch as of today). Under the load
> > (make
On Sun, Nov 17, 2002 at 11:16:54PM +0200, Maxim Sobolev wrote:
> Hi there,
>
> I'm observing very strange memory corruption problems with 2GHz P4
> system running 4.7 (security branch as of today). Under the load
> (make -j20 buildworld) the compiler or make(1) often die with signal
> 11. I found
I had similar problems. Terry Lambert reports that there is a bug
in the P4. DISABLE_PSE and the other work-arounds mentioned didn't help.
The work-around that worked for me was to use:
options MAXFILES=5
Try that and see if it helps.
On Sun, Nov 17, 2002 at 23:16:54 +0200, Maxim Sobolev wrote:
> Hi there,
>
> I'm observing very strange memory corruption problems with 2GHz P4
> system running 4.7 (security branch as of today). Under the load
> (make -j20 buildworld) the compiler or make(1) often die with signal
> 11. I found in
Hi there,
I'm observing very strange memory corruption problems with 2GHz P4
system running 4.7 (security branch as of today). Under the load
(make -j20 buildworld) the compiler or make(1) often die with signal
11. I found in mailing lists that there is similarly looking problem
with -current, any
6 matches
Mail list logo
