Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 24 Feb 2021 14:11:46 -0500
From:      Paul Mather <paul@gromit.dlib.vt.edu>
To:        Jung-uk Kim <jkim@FreeBSD.org>
Cc:        freebsd-current@freebsd.org
Subject:   Re: /etc/rc: ERROR: /etc/rc: no interface specified
Message-ID:  <2D5A610C-2908-442A-803F-B6393DABA4DB@gromit.dlib.vt.edu>
In-Reply-To: <c717cf68-571e-766b-4425-d00cd0a8a681@FreeBSD.org>
References:  <B1ED9565-FA33-47C9-B448-12DAAF07282E@gromit.dlib.vt.edu> <c717cf68-571e-766b-4425-d00cd0a8a681@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Feb 24, 2021, at 11:18 AM, Jung-uk Kim <jkim@FreeBSD.org> wrote:

> 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.
>>=20
>> Since the update, the systems do not boot up correctly.  I get this =
late in the boot sequence:
>>=20
>> =3D=3D=3D=3D=3D
>> 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:
>> =3D=3D=3D=3D=3D
>>=20
>> The last line is the final console output prior to the console login =
prompt.
>>=20
>> 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.
>>=20
>> Also, I can't be certain this is new, but I just noticed it: I get a =
bunch of extra KLDs loaded:
>>=20
>> =3D=3D=3D=3D=3D
>> 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
>> =3D=3D=3D=3D=3D
>>=20
>> 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.
>>=20
>> 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.
>=20
> The following commit fixed the problem for me.
>=20
> =
https://cgit.freebsd.org/src/commit/?id=3D6e822e99570fdf4c564be04840a054bc=
cc070222
>=20
> Jung-uk Kim


Thank you.  That fixed the problem for me, too.

Cheers,

Paul.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2D5A610C-2908-442A-803F-B6393DABA4DB>