Date: Tue, 6 Mar 2001 05:34:38 -0800 From: "oldfart@gtonet" <oldfart@gtonet.net> To: "FreeBSD-stable" <freebsd-stable@FreeBSD.ORG> Subject: RE: Argh! Many sig 11's Message-ID: <BIEHKEFNHFMMJEKCDMLNCEODCFAA.oldfart@gtonet.net> In-Reply-To: <20010306142551.I1448@abc.123.org>
next in thread | previous in thread | raw e-mail | index | archive | help
The CPU could have been zapped as well but RAM would be more likely to die first with a power supply failure. I think it depends on the motherboard somewhat too. Can you swap it with "known good"(TM) memory? Good luck, man. OF > -----Original Message----- > From: owner-freebsd-stable@FreeBSD.ORG > [mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of Kai Voigt > Sent: Tuesday, March 06, 2001 5:26 AM > To: Kal Torak > Cc: FreeBSD-stable > Subject: Re: Argh! Many sig 11's > > > Kal Torak wrote: > > > > One of my machines running 4.0 Stable had its power supply go, > > I since replaced it and now when coping large amounts of data etc > > things start dieing with sig 11's... > > > > Eg. cp -ipRP /usr /newusr (/usr and /newusr are in separate drives) > > after about 10mins of copying syslogd exited on 11, then ntpd then > > getty, then vm caused a panic and the system died... > > > > I thing one of the hdds is on the way out.. But could this cause the > > sig 11's? I dont see what other hardware could of been damaged by the > > power supply dieing... > > Signal 11 usually means hardware problems. Most likely, RAM is > broken, which is not suprising after a power supply damage. > > Read http://www.bitwizard.nl/sig11/ for further details. > > Kai > > -- > kai voigt dreiecksplatz 8 24105 kiel 0431-22199869 > http://k.123.org/ > > 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?BIEHKEFNHFMMJEKCDMLNCEODCFAA.oldfart>