atom feed27 messages in org.freebsd.freebsd-stableSignal 11 on 4-Stable buildworld; bad...
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:Signal 11 on 4-Stable buildworld; bad memory or what?
From:Shawn Barnhart (sw@grasslake.net)
Date:Jul 17, 2000 7:26:49 am
List:org.freebsd.freebsd-stable

My buildworld is failing, often in the same places, and always with a signal 11, which I think is a segmentation violation (SIGSEGV). When I first attempted buildworld it died right away. I rebooted the machine and it got further, but died again with the same error. Subsequent attempts died early; reboot and it dies later.

I've recently moved this system to an Asus TXP4 motherboard with an AMD K6-233 CPU and a single 128MB stick of PC100 SDRAM. No overclocking or other hardware hackery is being used. The same machine had been running (blush) Windows 2000 since March with little or no problems -- no problem with lockups, blue screens, etc.

The FreeBSD install I'm using had previously been running on a generic Dell Pentium 200 and lived through a half-dozen buildworlds without breaking.

Since I haven't seen a anyone else's world breaking this way, I'm assuming that this is a hardware problem -- but what kind? Memory? I have a spare Pentium 166 CPU and extra SDRAM I can swap, any clues as to where to start?

FWIW, I cvsup'd numerous times throughout 16-July, in case I caught things during a commit.

To Unsubscribe: send mail to majo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message