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 -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 chances that -stable is affected as well? > > I'm seeing similar errors on -current on my AMD K6-2 machine: > > CPU: AMD-K6(tm) 3D processor (400.91-MHz 586-class CPU) > Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 > Features=0x8021bf<FPU,VME,DE,PSE,TSC,MSR,MCE,CX8,PGE,MMX> > AMD Features=0xffffffff80000800<SYSCALL,3DNow!> > Data TLB: 128 entries, 2-way associative > Instruction TLB: 64 entries, 1-way associative > L1 data cache: 32 kbytes, 32 bytes/line, 2 lines/tag, 2-way associative > L1 instruction cache: 32 kbytes, 32 bytes/line, 2 lines/tag, 2-way associative > Write Allocate Enable Limit: 384M bytes > Write Allocate 15-16M bytes: Enable > > I am seeing make or /usr/libexec/cc1 intermittently coredump with SIG 11 or > SIG 10 errors when trying to do a buildworld. > I wasn't sure if it was because I had flaky hardware or not.
It is likely that those aren't related. Mine K6-2/500, which I had while back, was also causing SIG 11, due to overheating. Another possible reason is memory - you should check that you have PC100, not PC66 installed, because K6-2/400 runs with 100MHz FSB. In this case, the possible overheating is eliminated by keeping the case fully opened but it doesn't help much. -Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
