From owner-freebsd-stable@FreeBSD.ORG Tue Feb 22 19:35:46 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2575A16A4CE for ; Tue, 22 Feb 2005 19:35:46 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.199.47.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id D4AC743D5A for ; Tue, 22 Feb 2005 19:35:45 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id C6C3F51240; Tue, 22 Feb 2005 11:35:44 -0800 (PST) Date: Tue, 22 Feb 2005 11:35:44 -0800 From: Kris Kennaway To: Roberto Nunnari Message-ID: <20050222193544.GB40872@xor.obsecurity.org> References: <421475A8.7070003@supsi.ch> <421482C8.1020902@supsi.ch> <20050217180353.GA25609@xor.obsecurity.org> <4217CD12.3040204@supsi.ch> <20050220011428.GA60237@xor.obsecurity.org> <4217E85D.9040209@supsi.ch> <421B394C.9070202@supsi.ch> <421B4710.8020902@supsi.ch> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="wq9mPyueHGvFACwf" Content-Disposition: inline In-Reply-To: <421B4710.8020902@supsi.ch> User-Agent: Mutt/1.4.2.1i cc: freebsd-stable@freebsd.org cc: Kris Kennaway Subject: Re: {Spam?} Re: can't get a crash dump X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Feb 2005 19:35:46 -0000 --wq9mPyueHGvFACwf Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Feb 22, 2005 at 03:52:00PM +0100, Roberto Nunnari wrote: > hehe.. talked to early.. just had another crash.. and as usual > it didn't dump, and it didn't enter ddb.. it just reset! OK, now that we've established that it's not actually panicking, the overwhelmingly most likely cause of 'spontaneous reset' crashes is bad hardware. e.g. your power supply may be marginal and unable to hold up to peak loads, so your system will lose power and reboot when you exceed that load. Kris --wq9mPyueHGvFACwf Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCG4mQWry0BWjoQKURAtXfAKDIGvClCKHhQIpExCokFNOXNjYORACgg9jJ 1SieYSuwIkTBTl8jrkvlIPg= =rTNR -----END PGP SIGNATURE----- --wq9mPyueHGvFACwf--