From owner-freebsd-current Thu Feb 17 0:47:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 82D1C37B671 for ; Thu, 17 Feb 2000 00:47:50 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) id BAA00651; Thu, 17 Feb 2000 01:16:00 -0800 (PST) Date: Thu, 17 Feb 2000 01:16:00 -0800 From: Alfred Perlstein To: Andrew Maltsev Cc: freebsd-current@FreeBSD.ORG Subject: Re: 4.0 hangs (fwd) Message-ID: <20000217011600.N3509@fw.wintelcom.net> References: <200002170533.AAA07811@amsoft.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200002170533.AAA07811@amsoft.ru>; from am@amsoft.ru on Thu, Feb 17, 2000 at 12:31:02AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Andrew Maltsev [000216 22:00] wrote: > Hi, guys! > > Any comments? I had to downgrade back to 3.4 yesterday.. which works > absolutely without problems. If you're going to say ``it's hardware > problem'' -- this was my first thought too. I tried to change memory and > it did not help. Ideas? If you have a serial console available (all you need is a second computer with a terminal program and a null modem adapter) then you can boot the system with a serial console and see what the panic message is. You could also enable crashdumps and provide a traceback, see: http://www.freebsd.org/handbook/kerneldebug.html -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message