From owner-freebsd-current@freebsd.org Tue Sep 24 21:41:39 2019 Return-Path: Delivered-To: freebsd-current@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 DBC6EF2514 for ; Tue, 24 Sep 2019 21:41:39 +0000 (UTC) (envelope-from lausts@laus.org) Received: from cdptpa-cmomta01.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 46dF4y4m0tz43Sq; Tue, 24 Sep 2019 21:41:38 +0000 (UTC) (envelope-from lausts@laus.org) Received: from mail.laus.org ([65.29.112.189]) by cmsmtp with ESMTP id CsYvicJrAwchrCsYyilYTy; Tue, 24 Sep 2019 21:41:37 +0000 Received: from mail.laus.org (localhost [127.0.0.1]) by mail.laus.org (8.15.2/8.15.2) with ESMTPS id x8OLfXSi061905 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Tue, 24 Sep 2019 17:41:33 -0400 (EDT) (envelope-from lausts@laus.org) Received: (from lausts@localhost) by mail.laus.org (8.15.2/8.15.2/Submit) id x8OLfXad061904; Tue, 24 Sep 2019 17:41:33 -0400 (EDT) (envelope-from lausts) Date: Tue, 24 Sep 2019 17:41:33 -0400 From: Thomas Laus To: Ian Lepore Cc: freebsd-current@freebsd.org Subject: Re: Booting anything after r352057 kills console Message-ID: <20190924214133.GA61889@mail.laus.org> Reply-To: lausts@acm.org References: <11db909b-57ee-b452-6a17-90ec2765c36e@acm.org> <18332.1569268545@critter.freebsd.dk> <20190923213222.GA57158@mail.laus.org> <0eb339eb-5eb2-b75b-7fef-c22d02b824af@nomadlogic.org> <93d9c5bf-8269-ba44-655e-f079b311e29c@acm.org> <06a455da-1c7a-84f3-f4e4-64b50ca769bb@nomadlogic.org> <9ce93cb3283ee900eb63393f7bdb747001743cad.camel@freebsd.org> <20190924205706.GA61788@mail.laus.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190924205706.GA61788@mail.laus.org> X-Operating-System: FreeBSD 12.0-RELEASE-p10 on an amd64 User-Agent: Mutt/1.12.1 (2019-06-15) X-CMAE-Envelope: MS4wfPrOVF43l3XdChZJkS/wfIOyqVX5LwzBgJtrbIngZvghvKHEvtC8q38TVRXFI908g6YEFGiShJTk669SOgr/yZ7MQ5Uq1K7XJ7oFMqJ7rV/+FxXFXtl2 4W4rnpwCmkxONPnHgNxy4MHC+KBLUeNt+JpNVoHr0MbCAO14Bm6AF14aVSozkMkJW7eyRpNmyfFOulEjn/fMwhZZsVIVG6xl0eY= X-Rspamd-Queue-Id: 46dF4y4m0tz43Sq X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of lausts@laus.org has no SPF policy when checking 107.14.166.228) smtp.mailfrom=lausts@laus.org X-Spamd-Result: default: False [-1.60 / 15.00]; ARC_NA(0.00)[]; HAS_REPLYTO(0.00)[lausts@acm.org]; NEURAL_HAM_MEDIUM(-0.96)[-0.959,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-0.99)[-0.993,0]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[acm.org]; AUTH_NA(1.00)[]; REPLYTO_ADDR_EQ_FROM(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; IP_SCORE(-0.85)[ipnet: 107.14.160.0/20(-2.33), asn: 14065(-1.87), country: US(-0.05)]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[228.166.14.107.list.dnswl.org : 127.0.5.0]; R_SPF_NA(0.00)[]; FORGED_SENDER(0.30)[lausts@acm.org,lausts@laus.org]; RWL_MAILSPIKE_POSSIBLE(0.00)[228.166.14.107.rep.mailspike.net : 127.0.0.17]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:14065, ipnet:107.14.160.0/20, country:US]; FROM_NEQ_ENVFROM(0.00)[lausts@acm.org,lausts@laus.org]; RECEIVED_SPAMHAUS_PBL(0.00)[189.112.29.65.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.10] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Tue, 24 Sep 2019 21:41:39 -0000 > Ian Lepore [ian@freebsd.org] wrote: > > > > On my system, a whole lotta stuff happens between ntpd and syscons (the > > thing that configures blanktime). Try setting rc_debug=YES in rc.conf, > > that should write more info to syslog about what's happening between > > ntpd and the lockup point. > > > The results were not very informative. The 'bad' release did not show any > additional log entries with the rc_debug turned on. The working release > was very chatty. Maybe this will get closer to finding the root cause? > I just realized that the rc.conf file is part of the BEADM boot environment and when I switch releases, rc.conf comes with it. I will need to grab my ZFS admin book and find out how to mount a zfs filesystem from the loader prompt and remove the 'read only' attribute so that I can edit the rc.conf that will be used to load the 'bad' release. Maybe then I will have something useful to report Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF