Date: Fri, 26 Jun 2009 19:31:47 +0100 (BST) From: Chris Hedley <freebsd-current@chrishedley.com> To: freebsd-current@freebsd.org Cc: freebsd-amd64@freebsd.org Subject: Re: New builds won't boot (fwd) Message-ID: <alpine.BSF.2.00.0906261926080.1809@teapot.cbhnet> In-Reply-To: <alpine.BSF.2.00.0906261725570.1809@teapot.cbhnet> References: <alpine.BSF.2.00.0906071604540.1724@teapot.cbhnet> <4A2C124A.1050707@freebsd.org> <alpine.BSF.2.00.0906261725570.1809@teapot.cbhnet>
next in thread | previous in thread | raw e-mail | index | archive | help
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. Chris.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.0906261926080.1809>