Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 6 Mar 2001 14:25:52 +0100
From:      Kai Voigt <k@123.org>
To:        Kal Torak <kaltorak@quake.com.au>
Cc:        FreeBSD-stable <freebsd-stable@freebsd.org>
Subject:   Re: Argh! Many sig 11's
Message-ID:  <20010306142551.I1448@abc.123.org>
In-Reply-To: <3AA4E3CA.DF8A0A68@quake.com.au>; from kaltorak@quake.com.au on Wed, Mar 07, 2001 at 12:19:06AM %2B1100
References:  <3AA4E3CA.DF8A0A68@quake.com.au>

next in thread | previous in thread | raw e-mail | index | archive | help
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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010306142551.I1448>