atom feed27 messages in org.freebsd.freebsd-stableRe: Signal 11 on 4-Stable buildworld;...
FromSent OnAttachments
Shawn BarnhartJul 17, 2000 7:26 am 
Walter CampbellJul 17, 2000 7:33 am 
David UhringJul 17, 2000 1:40 pm 
Shawn BarnhartJul 17, 2000 2:19 pm 
Cyrille LefevreJul 17, 2000 2:22 pm 
Richard StanafordJul 17, 2000 3:37 pm 
ChrisJul 17, 2000 4:24 pm 
Kent StewartJul 17, 2000 4:29 pm 
Chad R. LarsonJul 17, 2000 5:01 pm 
R Joseph WrightJul 17, 2000 5:36 pm 
Kent StewartJul 17, 2000 6:29 pm 
Rodney W. GrimesJul 17, 2000 6:51 pm 
Richard StanafordJul 17, 2000 7:01 pm 
David UhringJul 17, 2000 7:08 pm 
Shawn BarnhartJul 17, 2000 9:09 pm 
R Joseph WrightJul 17, 2000 11:04 pm 
Kevin ObermanJul 18, 2000 8:02 am 
Mario Sergio Fujikawa FerreiraJul 19, 2000 1:04 pm 
Shawn BarnhartJul 19, 2000 1:34 pm 
Kent StewartJul 19, 2000 1:43 pm 
Mike MuirJul 19, 2000 3:47 pm 
Mike HoskinsJul 19, 2000 6:32 pm 
Mario Sergio Fujikawa FerreiraJul 20, 2000 5:50 am 
Jeffrey J. MountinJul 21, 2000 11:34 am 
Rodney W. GrimesJul 21, 2000 12:52 pm 
Jeffrey J. MountinJul 22, 2000 3:17 pm 
Rodney W. GrimesJul 22, 2000 5:32 pm 
Subject:Re: Signal 11 on 4-Stable buildworld; bad memory or what?
From:Shawn Barnhart (sw@grasslake.net)
Date:Jul 17, 2000 9:09:02 pm
List:org.freebsd.freebsd-stable

----- Original Message ----- From: "Chad R. Larson" <ch@DCFinc.com>

| You mean, no problems you've noticed. You may very well be right | about no problems, but please be aware that Windows will not | detect/report many errors that will trip up FreeBSD. Quiet data | corruption is the sometimes result.

Well, I wasn't trying to impune the charater of FreeBSD, but this cpu/ram/mobo combo I pushed pretty hard under Win2k without EVER getting errors. I have 128MB of RAM in it and I often had over 300MB total VM in use. Machine was powered up 24 x 7 and seldom rebooted for ANY reason. If there's a memory glitch, I'm sure it was silent as I didn't get the problems I typically associate with low budget kit and Windows.

I've swapped the CPU for an Intel P166 and had another buildworld die, so I don't think the K6 is to blame. I'm going to run memtest all night long and see if it can identify any problems.