Re: any images for freebsd-current?

[Steve Kargl]

On Mon, Feb 08, 2021 at 03:03:10AM +, Glen Barber wrote:
> On Sat, Feb 06, 2021 at 11:59:27AM -0800, Steve Kargl wrote:
> > Any one aware of where images from freebsd-current?
> > freebsd.org appears to offer no images.
> > 
> 
> Some juggling needs to be done to the release build machines, which
> I hope to have done this week before the weekly snapshots.
> 

FYI.  I downloaded the 20210218 memstick image for FreeBSD-14
amd64, and re-installed FreeBSD on the problematic laptop.  So
far, the laptop has been rock solid.  Rebuilt 547 ports from 
source.

I suspect that there is vm or ufs or clang/llvm bug(s) that
make running FreeBSD i386 on this laptop a nightmare.  From 
early Jan 2021 until this passed weekend, I was having daily
(sometime multiple) panics.  Panics pointed at issues with
vm (but required drm-kmod to be loaded) and massively scrambled
my SU ufs filesystems.  I also know that clang miscompiles
libm, so by extension it may be miscompiling others parts of
FreeBSD (leading to the panics).  YMMV.

-- 
Steve
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: apt install failures with /compat/ubuntu

[Graham Perrin]

On 24/02/2021 18:49, Graham Perrin wrote:

After following /compat/ubuntu advice in the FreeBSD wiki, …


Please ignore my previous e-mail. I lost sight of the last part of the 
wiki, which was relevant.



___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: /etc/rc: ERROR: /etc/rc: no interface specified

[Paul Mather]

On Feb 24, 2021, at 11:18 AM, Jung-uk Kim  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.
>> 
>> 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:
>> 
>> =
>> 324 0x82e95000 25a8 ng_bluetooth.ko
>> 331 0x82e98000 a238 ng_hci.ko
>> 343 0x82ea3000 aac8 netgraph.ko
>> 351 0x82eae000 e250 ng_l2cap.ko
>> 361 0x82ebd0001be48 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


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

Cheers,

Paul.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

apt install failures with /compat/ubuntu

[Graham Perrin]

After following /compat/ubuntu advice in the FreeBSD wiki, I attempted 
installation of two things. Both failed in the same way.


The second example:

root@mowa219-gjp4-8570p:/# apt install htop
Reading package lists... Done
Building dependency tree
Reading state information... Done
htop is already the newest version (2.1.0-3).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up rsyslog (8.32.0-1ubuntu4) ...
The user `syslog' is already a member of `adm'.
Failed to fstat() file /var/spool/rsyslog: Invalid argument
Failed to fstat() file /var/log: Invalid argument
dpkg: error processing package rsyslog (--configure):
 installed rsyslog package post-installation script subprocess returned 
error exit status 1

Errors were encountered while processing:
 rsyslog
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@mowa219-gjp4-8570p:/# exit
exit
root@mowa219-gjp4-8570p:~ # date ; uname -v
Wed Feb 24 18:41:54 GMT 2021
FreeBSD 14.0-CURRENT #87 main-5ac839029d: Mon Feb 22 04:02:26 GMT 2021 
root@mowa219-gjp4-8570p:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG

root@mowa219-gjp4-8570p:~ # freebsd-version -kru
14.0-CURRENT
14.0-CURRENT
14.0-CURRENT
root@mowa219-gjp4-8570p:~ # cat /etc/fstab
# Device    Mountpoint  FStype 
Options  Dump  Pass#
/dev/ada0p3.eli none    swap 
sw,late  0 0
# linprocfs /compat/linux/proc  linprocfs 
rw   0 0
# linsysfs  /compat/linux/sys   linsysfs 
rw   0 0
# tmpfs /compat/linux/dev/shm   tmpfs 
rw,mode=1777 0 0
tmpfs   /tmp    tmpfs 
rw,mode=01777    0 0
fdescfs /dev/fd fdescfs 
rw   0 0
proc    /proc   procfs 
rw   0 0

# 
devfs   /compat/ubuntu/dev  devfs 
rw,late  0   0
tmpfs   /compat/ubuntu/dev/shm  tmpfs 
rw,late,size=1g,mode=1777    0   0
fdescfs /compat/ubuntu/dev/fd   fdescfs 
rw,late,linrdlnk 0   0
linprocfs   /compat/ubuntu/proc linprocfs 
rw,late  0   0
linsysfs    /compat/ubuntu/sys  linsysfs 
rw,late  0   0
/tmp    /compat/ubuntu/tmp  nullfs 
rw,late  0   0
/home   /compat/ubuntu/home nullfs 
rw,late  0   0

root@mowa219-gjp4-8570p:~ # chroot /compat/ubuntu /bin/sh
# apt install htop
Reading package lists... Done
Building dependency tree
Reading state information... Done
htop is already the newest version (2.1.0-3).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up rsyslog (8.32.0-1ubuntu4) ...
The user `syslog' is already a member of `adm'.
Failed to fstat() file /var/spool/rsyslog: Invalid argument
Failed to fstat() file /var/log: Invalid argument
dpkg: error processing package rsyslog (--configure):
 installed rsyslog package post-installation script subprocess returned 
error exit status 1

Errors were encountered while processing:
 rsyslog
E: Sub-process /usr/bin/dpkg returned an error code (1)
# exit
root@mowa219-gjp4-8570p:~ #

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: /etc/rc: ERROR: /etc/rc: no interface specified

[Jung-uk Kim]

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:
> 
> =
> 324 0x82e95000 25a8 ng_bluetooth.ko
> 331 0x82e98000 a238 ng_hci.ko
> 343 0x82ea3000 aac8 netgraph.ko
> 351 0x82eae000 e250 ng_l2cap.ko
> 361 0x82ebd0001be48 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
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

/etc/rc: ERROR: /etc/rc: no interface specified

[Paul Mather]

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:

=
324 0x82e95000 25a8 ng_bluetooth.ko
331 0x82e98000 a238 ng_hci.ko
343 0x82ea3000 aac8 netgraph.ko
351 0x82eae000 e250 ng_l2cap.ko
361 0x82ebd0001be48 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.

Cheers,

Paul.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"