From owner-freebsd-current@FreeBSD.ORG Thu Apr 3 16:07:04 2014 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 849CB152 for ; Thu, 3 Apr 2014 16:07:04 +0000 (UTC) Received: from dmz-mailsec-scanner-8.mit.edu (dmz-mailsec-scanner-8.mit.edu [18.7.68.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 15C01E85 for ; Thu, 3 Apr 2014 16:07:03 +0000 (UTC) X-AuditID: 12074425-f79906d000000cf9-92-533d87202a1f Received: from mailhub-auth-4.mit.edu ( [18.7.62.39]) (using TLS with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by dmz-mailsec-scanner-8.mit.edu (Symantec Messaging Gateway) with SMTP id 52.94.03321.0278D335; Thu, 3 Apr 2014 12:06:56 -0400 (EDT) Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by mailhub-auth-4.mit.edu (8.13.8/8.9.2) with ESMTP id s33G6seW029754; Thu, 3 Apr 2014 12:06:55 -0400 Received: from multics.mit.edu (system-low-sipb.mit.edu [18.187.2.37]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id s33G6pXH022608 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 3 Apr 2014 12:06:53 -0400 Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id s33G6p0Q009385; Thu, 3 Apr 2014 12:06:51 -0400 (EDT) Date: Thu, 3 Apr 2014 12:06:51 -0400 (EDT) From: Benjamin Kaduk To: David Wolfskill Subject: Re: Boot fails @r264070 In-Reply-To: <20140403160031.GD30431@albert.catwhisker.org> Message-ID: References: <20140403160031.GD30431@albert.catwhisker.org> User-Agent: Alpine 1.10 (GSO 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrNIsWRmVeSWpSXmKPExsUixG6nrqvQbhtscOA7h8WEKz+YLE59ucvi wOSx8Ek/s8eMT/NZApiiuGxSUnMyy1KL9O0SuDI2z7vBXjCZp+LVqbtsDYznOLsYOTkkBEwk fsyZyghhi0lcuLeerYuRi0NIYDaTxPz2+UwQzgZGiT8n7rJDOAeZJL4s/sQM0iIkUC/RvPMj O4jNIqAlcerFZrA4m4CKxMw3G9lAbBGgeNeNNyxdjBwczALiEi/7lUDCwgIKEm/+72cGCXMK WEvM2ysOEuYVcJS4dv4oK8R0K4mjO/qZQGxRAR2J1funsEDUCEqcnPkEzGYWsJQ49+c62wRG wVlIUrOQpBYwMq1ilE3JrdLNTczMKU5N1i1OTszLSy3StdDLzSzRS00p3cQIDlMX1R2MEw4p HWIU4GBU4uHlSLcNFmJNLCuuzD3EKMnBpCTKG9kCFOJLyk+pzEgszogvKs1JLT7EKMHBrCTC eywRKMebklhZlVqUD5OS5mBREud9a20VLCSQnliSmp2aWpBaBJOV4eBQkuCd1ArUKFiUmp5a kZaZU4KQZuLgBBnOAzR8L0gNb3FBYm5xZjpE/hSjopQ4bwHIRQIgiYzSPLheWBp5xSgO9Iow 7yqQdh5gCoLrfgU0mAloMPc6K5DBJYkIKakGxlBexsWHy81ZxPJbvpbo7ub8X3Ync6rP06LW FV/3il35wNb7OMcpYNHss4L9Rg8v3HWaKtOQZWL6U1xxZu0epQSmVz5CThe9OlWXsUyctouP Y4rFie2XlVYEJL/WO9Vc6T/RzqXEp2zTktP1e99e/35nqoE6X46RQY9+wCGFU5zizPl/H5p9 VGIpzkg01GIuKk4EAI4nz2j+AgAA Cc: current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.17 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: Thu, 03 Apr 2014 16:07:04 -0000 On Thu, 3 Apr 2014, David Wolfskill wrote: > And on my laptop, I had no problems (using AHCI). The build machine, > though, starts OK, then comes to an inglorious end: > > Trying to mount root from ufs:/dev/aacd0s4a [rw]... > mountroot: waiting for device /dev/aacd0s4a ... > Mounting from ufs:/dev/aacd0s4a failed with error 19. > [...] > > mountroot> > > > So... I have serial console access; is there any debugging I might > do to help figure out what's wrong? Or is what's wrong already > known? > > I have been able to reboot from this point to one of the other > slices; I could probably also unload the default kernel & load > yesterday's (err... make that "the day before's" -- yesterday's > didn't build -- @r263983). I'm also having some trouble booting (into single user mode, so as to run the installworld), at r264039. It seems that ciss never attaches, so my da0 (which is supposed to be on ciss0) does not appear. My kernel.old is much older, __FreeBSD_version 1100005, but does boot. However, attempting to boot kernel.old in either single-user mode or verbse mode also drops me to mountroot> . That would seem to indicate some hardware problem or timing issues more than a problem with the code itself, so I had been holding off on posting until I could get more information. Unfortunately, my serial console is not working at the moment, so getting more information is a bit challenging. Diffing the dmesg from the good and bad boots would probably be helpful for you to do. -Ben