From owner-freebsd-current@freebsd.org Wed Feb 24 16:18:07 2021 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 42DED5619B7 for ; Wed, 24 Feb 2021 16:18:07 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Dm1L60V27z3kVB; Wed, 24 Feb 2021 16:18:05 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Received: from freefall.freebsd.org (pool-100-8-53-238.nwrknj.fios.verizon.net [100.8.53.238]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: jkim/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 22BBABB0F; Wed, 24 Feb 2021 16:18:05 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Subject: Re: /etc/rc: ERROR: /etc/rc: no interface specified To: Paul Mather , freebsd-current@freebsd.org References: From: Jung-uk Kim Organization: FreeBSD.org Message-ID: Date: Wed, 24 Feb 2021 11:18:04 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 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: Wed, 24 Feb 2021 16:18:07 -0000 On 21. 2. 24., Paul Mather wrote: > I have two systems on which I run -CURRENT. I updated them yesterday to the following: FreeBSD 14.0-CURRENT #1 main-n245033-6ab923cbca87: Tue Feb 23 21:29:31 EST 2021. Both use the stock GENERIC-NODEBUG kernel. > > Since the update, the systems do not boot up correctly. I get this late in the boot sequence: > > ===== > Enabling pf. > Updating /var/run/os-release done. > Creating and/or trimming log files. > Clearing /tmp (X related). > Updating motd:. > Starting syslogd. > Security policy loaded: MAC/ntpd (mac_ntpd) > Starting ntpd. > Starting powerd. > Mounting late filesystems:. > Configuring vt: blanktime. > Performing sanity check on sshd configuration. > Starting sshd. > Starting cron. > Starting background file system checks in 60 seconds. > /etc/rc: ERROR: /etc/rc: no interface specified > Usage: /etc/rc [0x00|0x01] > WARNING: attempt to domain_add(bluetooth) after domainfinalize() > /etc/rc: ERROR: Unsupported device: > ===== > > The last line is the final console output prior to the console login prompt. > > As well as the error during boot, none of the local services (installed via pkg with startup scripts under /usr/local/etc/rc.d) start up. > > Also, I can't be certain this is new, but I just noticed it: I get a bunch of extra KLDs loaded: > > ===== > 32 4 0xffffffff82e95000 25a8 ng_bluetooth.ko > 33 1 0xffffffff82e98000 a238 ng_hci.ko > 34 3 0xffffffff82ea3000 aac8 netgraph.ko > 35 1 0xffffffff82eae000 e250 ng_l2cap.ko > 36 1 0xffffffff82ebd000 1be48 ng_btsocket.ko > ===== > > I don't know why it's loading bluetooth-related kernel modules as both systems are rack-mounted servers with no bluetooth hardware in them to my knowledge. > > I've looked in /usr/src/UPDATING for any recent note related to this but can't find anything. My last update (circa 5th February 2021) worked fine. The following commit fixed the problem for me. https://cgit.freebsd.org/src/commit/?id=6e822e99570fdf4c564be04840a054bccc070222 Jung-uk Kim