From owner-freebsd-amd64@FreeBSD.ORG Tue Jun 30 00:40:05 2009 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 31037106566C; Tue, 30 Jun 2009 00:40:05 +0000 (UTC) (envelope-from freebsd-current@chrishedley.com) Received: from atmail-6.bnguk.net (atmail-6.bnguk.net [80.74.253.20]) by mx1.freebsd.org (Postfix) with ESMTP id B98B78FC12; Tue, 30 Jun 2009 00:40:04 +0000 (UTC) (envelope-from freebsd-current@chrishedley.com) Received: from 53-233.adsl.zetnet.co.uk ([194.247.53.233] helo=mail.chrishedley.com) by atmail-6.bnguk.net with esmtp (Exim 4.69) (envelope-from ) id 1MLQiA-0008Az-JU; Tue, 30 Jun 2009 00:56:35 +0100 Received: from localhost (localhost [127.0.0.1]) by mail.chrishedley.com (Postfix) with ESMTP id 7F6039342A; Tue, 30 Jun 2009 00:56:32 +0100 (BST) X-Virus-Scanned: amavisd-new at chrishedley.com Received: from mail.chrishedley.com ([127.0.0.1]) by localhost (mail.chrishedley.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id uqWgM9SMJNjY; Tue, 30 Jun 2009 00:56:29 +0100 (BST) Received: from teapot.cbhnet (teapot.cbhnet [192.168.1.1]) by mail.chrishedley.com (Postfix) with ESMTP id 404679340F; Tue, 30 Jun 2009 00:56:29 +0100 (BST) Date: Tue, 30 Jun 2009 00:56:29 +0100 (BST) From: Chris Hedley X-X-Sender: cbh@teapot.cbhnet To: freebsd-current@freebsd.org In-Reply-To: Message-ID: References: <4A2C124A.1050707@freebsd.org> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-amd64@freebsd.org Subject: Re: New builds won't boot (fwd) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Jun 2009 00:40:05 -0000 On Fri, 26 Jun 2009, Chris Hedley wrote: > On Fri, 26 Jun 2009, Chris Hedley wrote: >> On Sun, 7 Jun 2009, Tim Kientzle wrote: >>> * Latest checkout date of a kernel that does boot. >>> * Earliest checkout date of a kernel that doesn't boot. > ... >> As for the versions of the kernel, I've narrowed it down to a half-day >> window, which is hopefully useful: the cvsup-specified dates I have are >> 2009.02.18.12.00.00 (working) and 2009.02.19.00.00.00 (not working). > > Just to pontificate for a moment, I notice that there's quite a few changes > to the ATA subsystem that afternoon. This might be significant as the > Supermicro SATA controllers I use (a pair of AOC-SAT2-MV8 cards, 8 port PCI-X > things) aren't entirely trouble-free: when they're up and running they're > fine, but they don't reset on reboot, even with the current (? 1.0c, anyway) > firmware which causes problems rescanning the drives. This could be a > complete red herring, but I wondered if it may be related. I've been fiddling about with this a bit more and I'm not sure it's just a zfs problem as it seems gmirror also can't find its entries. Attempting to boot of a non-zfs partition also leads to it hanging near the end of the kernel's boot messages. Anybody got any ideas of how I can get my system or AOC-SAT2-MV8 to work with the post 18th Feb kernels? Or of any ddb wizardry to further probe it for what it might be doing while it's apparently thinking about things? Thanks in advance, Chris.