From owner-freebsd-current@FreeBSD.ORG Tue Sep 21 18:30:42 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8099816A4CE for ; Tue, 21 Sep 2004 18:30:42 +0000 (GMT) Received: from blue.host.is (blue.host.is [212.30.222.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2B2E043D2D for ; Tue, 21 Sep 2004 18:30:42 +0000 (GMT) (envelope-from martin@swift.is) Received: by blue.host.is (Postfix, from userid 1001) id 4EE13316; Tue, 21 Sep 2004 18:30:41 +0000 (GMT) Date: Tue, 21 Sep 2004 18:30:41 +0000 From: Martin Swift To: freebsd-current@freebsd.org Message-ID: <20040921183041.GD10593@swift.is> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.6i Subject: BETA5 hangs shortly after boot. Unknown cause. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Sep 2004 18:30:42 -0000 Hi list, Just cvsup-ed to BETA5 tonight and after having built world and built and installed the kernel I rebooted into single user to install world. As I was mounting the filesystem the machine hung. The only way to get to prompt was booting "normally" so that fsck went into background (nice feature, btw). Still that didn't do much, same kind of hangs occurred just 10-20 seconds after login. I wish I could say this was definately not my fault, but before rebuilding the kernel I added apm and disabled acpi in /boot/device.hints ... something that had caused hangs in past BETAs. I know; I must be stupid, stupid, stupid, but in my defence: I used to be able to reenable acpi at boot. Furthermore, booting with set hint.acpi.0.disabled=0 boot /boot/kernel.old doesn't work ... hmmm. Any bright ideas for this novice? Like the rest of you, I don't have infinite amounts of time, but if anyone can point out what to debug (and, importantly: how to get the data before it dissappears off the screen) I'm willing to try and extract what information from the machine that I can. Sincerely, Martin Swift