Date: Tue, 22 Feb 2000 11:29:56 -0500 From: Alok Dhir <adhir@forumone.com> To: "'Forrest W. Christian'" <forrestc@iMach.com>, "'Ljungqvist, Lennart'" <lennart.ljungqvist@telia.com> Cc: "'freebsd-stable@FreeBSD.ORG'" <freebsd-stable@FreeBSD.ORG> Subject: RE: Signal 11 error when installing 3.4 STABLE Message-ID: <AFD7CFC52B58014B9C0BFAF32EAB48EF014C6E@PLUTO.forumone.com>
next in thread | raw e-mail | index | archive | help
If I could add one thing - its typically difficult to accept that these problems are caused by hardware. "But my machine runs Win9x perfectly" is a typical retort when the finger is pointed at hardware. It is important to note that FreeBSD/Linux/etc are significantly more demanding than Win9x, etc, and are much more likely to bring flaky hardware problems to the surface. I've seen Signal 11 many times over the past several years from various versions of FreeBSD and LInux, and so far, it has been caused by bad hardware (usually memory) every time... Al > -----Original Message----- > From: owner-freebsd-stable@FreeBSD.ORG > [mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of Forrest W. > Christian > Sent: Monday, February 21, 2000 8:31 PM > To: Ljungqvist, Lennart > Cc: freebsd-stable@FreeBSD.ORG > Subject: Re: Signal 11 error when installing 3.4 STABLE > > > On Mon, 21 Feb 2000, Ljungqvist, Lennart wrote: > > > What is this signal 11 error, and why is it turning my > > installation/uppgrading into nothing??? > > I think it's time to add this to some FAQ somewhere. > > Signal 11 is a segmentation fault. > > Although it CAN be a software bug, usually this is caused by > a hardware > fault. > > There is a linux-based faq at: > http://www.bitwizard.nl/sig11/ > > Although some parts are linux-specific, most of the contents > of this page > are useful for FreeBSD. > > If you'd like my recommendation on what to look for, I'd recommend: > > 1) Check/replace your memory and verify related bios settings. > 2) Check for a faulty SCSI/IDE controller > 3) Double check your memory > 4) Try swapping out cards in bus slots, or leaving some out > 5) Try a different set of memory chips and check > bios settings. > 6) Try another processor/motherboard. > 7) Did I mention to check your memory and memory-related bios > settings? > > FWIW, I HAVE had one time where a Adaptec 1542 did not like the > motherboard it was in and that gave me sig 11's. > > But usually it is memory. > > - Forrest W. Christian (forrestc@imach.com) KD7EHZ > ---------------------------------------------------------------------- > iMach, Ltd., P.O. Box 5749, Helena, MT 59604 http://www.imach.com > Solutions for your high-tech problems. (406)-442-6648 > ---------------------------------------------------------------------- > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AFD7CFC52B58014B9C0BFAF32EAB48EF014C6E>