From owner-freebsd-current@FreeBSD.ORG Fri Nov 19 18:02:25 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7A9AF1065673; Fri, 19 Nov 2010 18:02:25 +0000 (UTC) (envelope-from james-freebsd-current@jrv.org) Received: from mail.jrv.org (rrcs-24-73-246-106.sw.biz.rr.com [24.73.246.106]) by mx1.freebsd.org (Postfix) with ESMTP id 27DD78FC1C; Fri, 19 Nov 2010 18:02:24 +0000 (UTC) Received: from kremvax.housenet.jrv (kremvax.housenet.jrv [192.168.3.124]) by mail.jrv.org (8.14.3/8.14.3) with ESMTP id oAJHHxBE063452; Fri, 19 Nov 2010 11:18:00 -0600 (CST) (envelope-from james-freebsd-current@jrv.org) Authentication-Results: mail.jrv.org; domainkeys=pass (testing) header.from=james-freebsd-current@jrv.org DomainKey-Signature: a=rsa-sha1; s=enigma; d=jrv.org; c=nofws; q=dns; h=message-id:date:from:user-agent:mime-version:cc:subject: references:in-reply-to:content-type:content-transfer-encoding; b=NzmAX76sTSLLZdCcrSWhxpglmhDuswJtwKJjVpDrZpvPLret0MnhOEHDw9M9FLOfB giYpVwhLCPM7Fq+OR6g/W+Vjm+I0v6KLfcWpV38eMPh9tavYkfP9HuWZUstcjGZYl+P 4Z4O2Kc9Qu7aS7gApwYpjNBuiRfsIkJwrqrLgw0= Message-ID: <4CE6B147.4060203@jrv.org> Date: Fri, 19 Nov 2010 11:17:59 -0600 From: "James R. Van Artsdalen" User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228) MIME-Version: 1.0 References: In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, Ivan Voras Subject: Re: A big-ish machine, cannot boot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Fri, 19 Nov 2010 18:02:25 -0000 Ivan Voras wrote: > Unfortunately, the kernel hangs on boot. The loader finishes, the twirly > starts spinning but then hangs. Enabling verbose booting results in > nothing new - no kernel messages at all. I don't think "loader finishes" is correct. Can you break to the loader command line at the beastie menu? At the time of the twirlie I think that the loader is copying the kernel to memory. Perhaps it is having trouble with disk reads, or has a bad memory map. How many disks are attached, and what filesystem type does /boot live on? And what does Fixit mode see (from whatever installed that system)?