From owner-freebsd-stable@freebsd.org Wed Sep 11 03:25:21 2019 Return-Path: Delivered-To: freebsd-stable@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 8E284EC7D6 for ; Wed, 11 Sep 2019 03:25:21 +0000 (UTC) (envelope-from TERRY@glaver.org) Received: from server.glaver.org (server.glaver.org [204.141.35.63]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 46SnN039CJz4MJg for ; Wed, 11 Sep 2019 03:25:20 +0000 (UTC) (envelope-from TERRY@glaver.org) Received: from glaver.org by glaver.org (PMDF V6.7-x04 #37010) id <01RBAKWF29GG000QXF@glaver.org> for freebsd-stable@freebsd.org; Tue, 10 Sep 2019 23:05:02 -0400 (EDT) Date: Tue, 10 Sep 2019 22:59:26 -0400 (EDT) From: Terry Kennedy Subject: Anyone else seeing hangs at "Trying to mount root" after recent commits? To: freebsd-stable@freebsd.org Message-id: <01RBAL5781V8000QXF@glaver.org> MIME-version: 1.0 Content-type: TEXT/PLAIN; CHARSET=us-ascii X-Rspamd-Queue-Id: 46SnN039CJz4MJg X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of TERRY@glaver.org designates 204.141.35.63 as permitted sender) smtp.mailfrom=TERRY@glaver.org X-Spamd-Result: default: False [-1.47 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.98)[-0.982,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:204.141.35.63]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[glaver.org]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-0.997,0]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:22691, ipnet:204.141.35.0/24, country:US]; MID_RHS_MATCH_FROM(0.00)[]; IP_SCORE(-0.20)[asn: 22691(-0.92), country: US(-0.05)]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Sep 2019 03:25:21 -0000 I have a system I updated from r352025 (which worked fine) to r352200. Any attempt to boot r352200 results in the system just sitting there after displaying the normal "Trying to mount root from ufs:/dev/da0p3 [rw]..." message. Nothing further, not even after a half hour. The console is non- responsive (not that I'd really expect anything, but...). This persists across multiple resets, power cycles, etc. Booting the previous r352025 works fine, as expected. Before I start trying to bisect this, is anyone else seeing this? amd64 on a standard Dell PowerEdge R730 if that matters. Terry Kennedy http://www.glaver.org New York, NY USA