From owner-freebsd-stable Tue Mar 6 5:26:10 2001 Delivered-To: freebsd-stable@freebsd.org Received: from abc.123.org (123.org [195.244.241.123]) by hub.freebsd.org (Postfix) with ESMTP id 29FEE37B718 for ; Tue, 6 Mar 2001 05:26:03 -0800 (PST) (envelope-from k@abc.123.org) Received: (from k@localhost) by abc.123.org (8.11.1/8.11.1) id f26DPqV07058; Tue, 6 Mar 2001 14:25:52 +0100 (CET) (envelope-from k) Date: Tue, 6 Mar 2001 14:25:52 +0100 From: Kai Voigt To: Kal Torak Cc: FreeBSD-stable Subject: Re: Argh! Many sig 11's Message-ID: <20010306142551.I1448@abc.123.org> References: <3AA4E3CA.DF8A0A68@quake.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3AA4E3CA.DF8A0A68@quake.com.au>; from kaltorak@quake.com.au on Wed, Mar 07, 2001 at 12:19:06AM +1100 Organization: 123.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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