Trying initial boot of FreeBSD (main so: 15) of Ryzen 9 7950X3D on an ASUS Prime X670-P WIFI: various dmesg -a lines; more

Discussion:

(too old to reply)

Mark Millard

2023-11-01 06:00:22 UTC

Permalink

FreeBSD context:

# uname -apKU
FreeBSD amd64-ZFS 15.0-CURRENT FreeBSD 15.0-CURRENT #126 main-n266130-d521abdff236-dirty: Tue Oct 24 18:17:40 PDT 2023 ***@amd64-ZFS:/usr/obj/BUILDs/main-amd64-nodbg-clang/usr/main-src/amd64.amd64/sys/GENERIC-NODBG amd64 amd64 1500002 1500002

I moved my FreeBDSS boot media from a ThreadRipper 1950X to a Ryzen 9 7950X3D and tried
booting. It booted but some of the following might be of some note. Is any of it likely
to be problematical? Any of it of particular interest to anyone?

. . .
Firmware Error (ACPI): Could not resolve symbol [\134_SB.PCI0.GPP7.UP00.DP40.UP00.DP68], AE_NOT_FOUND (20221020/dswload2-315)
ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20221020/psobject-372)
. . .
pci0: <base peripheral, IOMMU> at device 0.2 (no driver attached)
. . .
pci8: <network, ethernet> at device 0.0 (no driver attached)
. . .
pci9: <network> at device 0.0 (no driver attached)
. . .
pci15: <encrypt/decrypt> at device 0.2 (no driver attached)
. . .
ns8250: UART FCR is broken
ns8250: UART FCR is broken
. . .
intsmb0: <AMD FCH SMBus Controller> at device 20.0 on pci0
intsmb0: Could not allocate I/O space
device_attach: intsmb0 attach returned 6
intsmb0: <AMD FCH SMBus Controller> port 0xff00-0xff0f at device 20.0 on pci0
intsmb0: Could not allocate I/O space
device_attach: intsmb0 attach returned 6
. . .
intsmb0: <AMD FCH SMBus Controller> at device 20.0 on pci0
intsmb0: Could not allocate I/O space
device_attach: intsmb0 attach returned 6
intsmb0: <AMD FCH SMBus Controller> port 0xff00-0xff0f at device 20.0 on pci0
intsmb0: Could not allocate I/O space
device_attach: intsmb0 attach returned 6
acpi_wmi0: <ACPI-WMI mapping> on acpi0
acpi_wmi0: cannot find EC device
acpi_wmi0: Embedded MOF found
ACPI: \134AWW0.WQMO: 1 arguments were passed to a non-method ACPI object (Buffer) (20221020/nsarguments-361)
acpi_wmi1: <ACPI-WMI mapping> on acpi0
acpi_wmi1: cannot find EC device
acpi_wmi1: Embedded MOF found
ACPI: \134ABAW.WQMO: 1 arguments were passed to a non-method ACPI object (Buffer) (20221020/nsarguments-361)
acpi_wmi2: <ACPI-WMI mapping> on acpi0
acpi_wmi2: cannot find EC device
acpi_wmi2: Embedded MOF found
ACPI: \134RMTW.WQMO: 1 arguments were passed to a non-method ACPI object (Buffer) (20221020/nsarguments-361)
acpi_wmi3: <ACPI-WMI mapping> on acpi0
acpi_wmi3: cannot find EC device
acpi_wmi3: Embedded MOF found
ACPI: \134AOD.WQBA: 1 arguments were passed to a non-method ACPI object (Buffer) (20221020/nsarguments-361)
driver bug: Unable to set devclass (class: ppc devname: (unknown))
. . .
acpi_wmi4: <ACPI-WMI mapping> on acpi0
acpi_wmi4: cannot find EC device
acpi_wmi4: Embedded MOF found
ACPI: \134_SB.ATKD.WQMO: 1 arguments were passed to a non-method ACPI object (Buffer) (20221020/nsarguments-361)
driver bug: Unable to set devclass (class: ppc devname: (unknown))
. . .
mixer: speaker: no such device
mixer: speaker: no such device
mixer: line: no such device
mixer: line: no such device
mixer: mic: no such device
mixer: mic: no such device
mixer: mic: no such device
mixer: mix: no such device
mixer: mix: no such device
mixer: rec: no such device
mixer: rec: no such device
mixer: igain: no such device
mixer: igain: no such device
mixer: ogain: no such device
mixer: ogain: no such device
mixer: rec: no such device
mixer: rec: no such device
mixer: igain: no such device
mixer: igain: no such device
mixer: ogain: no such device
mixer: ogain: no such device
mixer: monitor: no such device
mixer: monitor: no such device
mixer: monitor: no such device
. . .
uhid2 on uhub0
uhid2: <Corsair CORSAIR iCUE COMMANDER Core, class 0/0, rev 2.00/1.00, addr 3> on usbus1
devmatch: devinfo_init: Invalid argument
uhid3 on uhub4
uhid3: <Corsair CORSAIR M55 RGB PRO Gaming Mouse, class 0/0, rev 2.00/4.07, addr 1> on usbus0
. . .
uhid4 on uhub4
uhid4: <Corsair CORSAIR K55 RGB PRO Gaming Keyboard, class 0/0, rev 1.10/1.02, addr 2> on usbus0
devmatch: devinfo_init: Invalid argument
uhid6 on uhub4
uhid6: <Corsair CORSAIR K55 RGB PRO Gaming Keyboard, class 0/0, rev 1.10/1.02, addr 2> on usbus0
. . .
pci0:8:0:0: no VPD ident found
. . .

I used a USB3 Ethernet dongle in order to have Ethernet available.

For reference:

# pciconf -lvV | less
. . .
***@pci0:0:0:2: class=0x080600 rev=0x00 hdr=0x00 vendor=0x1022 device=0x14d9 subvendor=0x1043 subdevice=0x8877
vendor = 'Advanced Micro Devices, Inc. [AMD]'
class = base peripheral
subclass = IOMMU
. . .
***@pci0:0:20:0: class=0x0c0500 rev=0x71 hdr=0x00 vendor=0x1022 device=0x790b subvendor=0x1043 subdevice=0x8877
vendor = 'Advanced Micro Devices, Inc. [AMD]'
device = 'FCH SMBus Controller'
class = serial bus
subclass = SMBus
. . .
***@pci0:8:0:0: class=0x020000 rev=0x05 hdr=0x00 vendor=0x10ec device=0x8125 subvendor=0x1043 subdevice=0x87d7
vendor = 'Realtek Semiconductor Co., Ltd.'
device = 'RTL8125 2.5GbE Controller'
class = network
subclass = ethernet
***@pci0:9:0:0: class=0x028000 rev=0x00 hdr=0x00 vendor=0x10ec device=0xb852 subvendor=0x1a3b subdevice=0x5471
vendor = 'Realtek Semiconductor Co., Ltd.'
class = network
. . .
***@pci0:15:0:2: class=0x108000 rev=0x00 hdr=0x00 vendor=0x1022 device=0x1649 subvendor=0x1043 subdevice=0x8877
vendor = 'Advanced Micro Devices, Inc. [AMD]'
device = 'VanGogh PSP/CCP'
class = encrypt/decrypt
. . .

Example temperatures (while idle, ambient around 20 DegC):

# kldload amdtemp
# sysctl dev.amdtemp
dev.amdtemp.0.ccd1: 33.0C
dev.amdtemp.0.ccd0: 34.6C
dev.amdtemp.0.core0.sensor0: 39.6C
dev.amdtemp.0.sensor_offset: 0
dev.amdtemp.0.%parent: hostb0
dev.amdtemp.0.%pnpinfo: dev.amdtemp.0.%location: dev.amdtemp.0.%driver: amdtemp
dev.amdtemp.0.%desc: AMD CPU On-Die Thermal Sensors
dev.amdtemp.%parent:

Example during llvm build activity during buildworld:

# sysctl dev.amdtemp
dev.amdtemp.0.ccd1: 60.5C
dev.amdtemp.0.ccd0: 67.2C
dev.amdtemp.0.core0.sensor0: 77.1C
. . .

(Of course, the cooling system in place contributes greatly.)

Example from scratch builds (of my usual style of personal builds):

ThreadRipper 1950X: World built in 1345 seconds, ncpu: 32, make -j32
Ryzen 9 7950X3D: World built in 545 seconds, ncpu: 32, make -j32

ThreadRipper 1950X: Kernel(s) GENERIC-NODBG built in 123 seconds, ncpu: 32, make -j32
Ryzen 9 7950X3D: Kernel(s) GENERIC-NODBG built in 51 seconds, ncpu: 32, make -j32

Note: It is the same media in use: PCIe Optane moved from the 1950X
to the 7950X3D, ZFS (for bectl use, not other reasons ZFS is commonly
used for).

ThreadRipper 1950X: 128 GiBytes of RAM. Swap parition was 480 GiBytes at the time.
Ryzen 9 7950X3D: 96 GiBytes of RAM. Swap parition changed to 364 GiBytes.

(That avoids the swapon warning about possibly being out of tune vs. the amount of
RAM.)

===
Mark Millard
marklmi at yahoo.com

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

Mark Millard

2023-11-01 12:39:30 UTC

Permalink

Post by Mark Millard
# uname -apKU
I moved my FreeBDSS boot media from a ThreadRipper 1950X to a Ryzen 9 7950X3D and tried
booting. It booted but some of the following might be of some note. Is any of it likely
to be problematical? Any of it of particular interest to anyone?
. . .
Firmware Error (ACPI): Could not resolve symbol [\134_SB.PCI0.GPP7.UP00.DP40.UP00.DP68], AE_NOT_FOUND (20221020/dswload2-315)
ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20221020/psobject-372)
. . .
pci0: <base peripheral, IOMMU> at device 0.2 (no driver attached)
. . .
pci8: <network, ethernet> at device 0.0 (no driver attached)
. . .
pci9: <network> at device 0.0 (no driver attached)
. . .
pci15: <encrypt/decrypt> at device 0.2 (no driver attached)
. . .
ns8250: UART FCR is broken
ns8250: UART FCR is broken
. . .
intsmb0: <AMD FCH SMBus Controller> at device 20.0 on pci0
intsmb0: Could not allocate I/O space
device_attach: intsmb0 attach returned 6
intsmb0: <AMD FCH SMBus Controller> port 0xff00-0xff0f at device 20.0 on pci0
intsmb0: Could not allocate I/O space
device_attach: intsmb0 attach returned 6
. . .
intsmb0: <AMD FCH SMBus Controller> at device 20.0 on pci0
intsmb0: Could not allocate I/O space
device_attach: intsmb0 attach returned 6
intsmb0: <AMD FCH SMBus Controller> port 0xff00-0xff0f at device 20.0 on pci0
intsmb0: Could not allocate I/O space
device_attach: intsmb0 attach returned 6
acpi_wmi0: <ACPI-WMI mapping> on acpi0
acpi_wmi0: cannot find EC device
acpi_wmi0: Embedded MOF found
ACPI: \134AWW0.WQMO: 1 arguments were passed to a non-method ACPI object (Buffer) (20221020/nsarguments-361)
acpi_wmi1: <ACPI-WMI mapping> on acpi0
acpi_wmi1: cannot find EC device
acpi_wmi1: Embedded MOF found
ACPI: \134ABAW.WQMO: 1 arguments were passed to a non-method ACPI object (Buffer) (20221020/nsarguments-361)
acpi_wmi2: <ACPI-WMI mapping> on acpi0
acpi_wmi2: cannot find EC device
acpi_wmi2: Embedded MOF found
ACPI: \134RMTW.WQMO: 1 arguments were passed to a non-method ACPI object (Buffer) (20221020/nsarguments-361)
acpi_wmi3: <ACPI-WMI mapping> on acpi0
acpi_wmi3: cannot find EC device
acpi_wmi3: Embedded MOF found
ACPI: \134AOD.WQBA: 1 arguments were passed to a non-method ACPI object (Buffer) (20221020/nsarguments-361)
driver bug: Unable to set devclass (class: ppc devname: (unknown))
. . .
acpi_wmi4: <ACPI-WMI mapping> on acpi0
acpi_wmi4: cannot find EC device
acpi_wmi4: Embedded MOF found
ACPI: \134_SB.ATKD.WQMO: 1 arguments were passed to a non-method ACPI object (Buffer) (20221020/nsarguments-361)
driver bug: Unable to set devclass (class: ppc devname: (unknown))
. . .
mixer: speaker: no such device
mixer: speaker: no such device
mixer: line: no such device
mixer: line: no such device
mixer: mic: no such device
mixer: mic: no such device
mixer: mic: no such device
mixer: mix: no such device
mixer: mix: no such device
mixer: rec: no such device
mixer: rec: no such device
mixer: igain: no such device
mixer: igain: no such device
mixer: ogain: no such device
mixer: ogain: no such device
mixer: rec: no such device
mixer: rec: no such device
mixer: igain: no such device
mixer: igain: no such device
mixer: ogain: no such device
mixer: ogain: no such device
mixer: monitor: no such device
mixer: monitor: no such device
mixer: monitor: no such device
. . .
uhid2 on uhub0
uhid2: <Corsair CORSAIR iCUE COMMANDER Core, class 0/0, rev 2.00/1.00, addr 3> on usbus1
devmatch: devinfo_init: Invalid argument
uhid3 on uhub4
uhid3: <Corsair CORSAIR M55 RGB PRO Gaming Mouse, class 0/0, rev 2.00/4.07, addr 1> on usbus0
. . .
uhid4 on uhub4
uhid4: <Corsair CORSAIR K55 RGB PRO Gaming Keyboard, class 0/0, rev 1.10/1.02, addr 2> on usbus0
devmatch: devinfo_init: Invalid argument
uhid6 on uhub4
uhid6: <Corsair CORSAIR K55 RGB PRO Gaming Keyboard, class 0/0, rev 1.10/1.02, addr 2> on usbus0
. . .
pci0:8:0:0: no VPD ident found
. . .
I used a USB3 Ethernet dongle in order to have Ethernet available.
# pciconf -lvV | less
. . .
vendor = 'Advanced Micro Devices, Inc. [AMD]'
class = base peripheral
subclass = IOMMU
. . .
vendor = 'Advanced Micro Devices, Inc. [AMD]'
device = 'FCH SMBus Controller'
class = serial bus
subclass = SMBus
. . .
vendor = 'Realtek Semiconductor Co., Ltd.'
device = 'RTL8125 2.5GbE Controller'
class = network
subclass = ethernet
vendor = 'Realtek Semiconductor Co., Ltd.'
class = network
. . .
vendor = 'Advanced Micro Devices, Inc. [AMD]'
device = 'VanGogh PSP/CCP'
class = encrypt/decrypt
. . .
# kldload amdtemp
# sysctl dev.amdtemp
dev.amdtemp.0.ccd1: 33.0C
dev.amdtemp.0.ccd0: 34.6C
dev.amdtemp.0.core0.sensor0: 39.6C
dev.amdtemp.0.sensor_offset: 0
dev.amdtemp.0.%parent: hostb0
dev.amdtemp.0.%pnpinfo: dev.amdtemp.0.%location: dev.amdtemp.0.%driver: amdtemp
dev.amdtemp.0.%desc: AMD CPU On-Die Thermal Sensors
# sysctl dev.amdtemp
dev.amdtemp.0.ccd1: 60.5C
dev.amdtemp.0.ccd0: 67.2C
dev.amdtemp.0.core0.sensor0: 77.1C
. . .
(Of course, the cooling system in place contributes greatly.)
ThreadRipper 1950X: World built in 1345 seconds, ncpu: 32, make -j32
Ryzen 9 7950X3D: World built in 545 seconds, ncpu: 32, make -j32
ThreadRipper 1950X: Kernel(s) GENERIC-NODBG built in 123 seconds, ncpu: 32, make -j32
Ryzen 9 7950X3D: Kernel(s) GENERIC-NODBG built in 51 seconds, ncpu: 32, make -j32
Note: It is the same media in use: PCIe Optane moved from the 1950X
to the 7950X3D, ZFS (for bectl use, not other reasons ZFS is commonly
used for).
ThreadRipper 1950X: 128 GiBytes of RAM. Swap parition was 480 GiBytes at the time.
Ryzen 9 7950X3D: 96 GiBytes of RAM. Swap parition changed to 364 GiBytes.
(That avoids the swapon warning about possibly being out of tune vs. the amount of
RAM.)

An ongoing poudriere bulk -a test looks to have a stuck objdump ( used for building
www/node18 ):

# ps -oetime -alxdww | grep node18
05:48:03 0 44960 53404 21 68 0 18544 2892 select I 0 0:00.03 | | |-- sh: poudriere[main-amd64-bulk_a-default][15]: build_pkg (node18-18.18.2) (sh)
05:47:36 0 76480 44960 21 68 0 18544 2892 wait I 0 0:00.00 | | | `-- sh: poudriere[main-amd64-bulk_a-default][15]: build_pkg (node18-18.18.2) (sh)
05:47:36 0 76485 76480 19 68 0 12896 276 wait IJ 0 0:00.01 | | | `-- /usr/bin/make -C /usr/ports/www/node18 build
05:47:36 0 77304 76485 22 68 0 13356 288 wait IJ 0 0:00.00 | | | `-- /bin/sh -e -c (cd /wrkdirs/usr/ports/www/node18/work/node-v18.18.2; if ! /usr/bin/env CC.host=" cc" CFLAGS.host="-O2 -pipe -g -fstack-protector-strong -isystem /usr/local/include -fno-strict-aliasing " CXX.host=" c++" CXXFLAGS.host="-O2 -pipe -g -fstack-protector-strong -isystem /usr/local/include -fno-strict-aliasing -isystem /usr/local/include " LDFLAGS.host=" -fstack-protector-strong " LINK.host="c++" OPENSSLBASE=/usr OPENSSLDIR=/etc/ssl OPENSSLINC=/usr/include OPENSSLLIB=/usr/lib XDG_DATA_HOME=/wrkdirs/usr/ports/www/node18/work XDG_CONFIG_HOME=/wrkdirs/usr/ports/www/node18/work XDG_CACHE_HOME=/wrkdirs/usr/ports/www/node18/work/.cache HOME=/wrkdirs/usr/ports/www/node18/work TMPDIR="/tmp" PATH=/wrkdirs/usr/ports/www/node18/work/.bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/root/bin PKG_CONFIG_LIBDIR=/wrkdirs/usr/ports/www/node18/work/.pkgconfig:/usr/local/libdata/pkgconfig:/usr/local/share/pkgconfig:/usr/libdata/pkgconfig DONTSTRIP=yes DONTSTRIP=yes MK_DEBUG_FILES=no MK_KERNEL_SYMBOLS=no SHELL=/bin/sh NO_LINT=YES PREFIX=/usr/local LOCALBASE=/usr/local CC="cc" CFLAGS="-O2 -pipe -g -fstack-protector-strong -isystem /usr/local/include -fno-strict-aliasing " CPP="cpp" CPPFLAGS="-isystem /usr/local/include" LDFLAGS=" -fstack-protector-strong " LIBS="-L/usr/local/lib" CXX="c++" CXXFLAGS="-O2 -pipe -g -fstack-protector-strong -isystem /usr/local/include -fno-strict-aliasing -isystem /usr/local/include " MANPREFIX="/usr/local" BSD_INSTALL_PROGRAM="install -m 555" BSD_INSTALL_LIB="install -m 0644" BSD_INSTALL_SCRIPT="install -m 555" BSD_INSTALL_DATA="install -m 0644" BSD_INSTALL_MAN="install -m 444" gmake -f Makefile -j32 all; then if [ -n "Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to the maintainer." ] ; then echo "===> Compilation failed unexpectedly."; (echo "Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to the maintainer.") | /usr/bin/fmt 75 79 ; fi; false; fi)
05:33:34 0 7035 80309 9 26 0 22620 1312 piperd SJ 0 32:56.31 | | | `-- /usr/local/bin/python3.9 tools/genv8constants.py /wrkdirs/usr/ports/www/node18/work/node-v18.18.2/out/Release/obj/gen/v8constants.h /wrkdirs/usr/ports/www/node18/work/node-v18.18.2/out/Release/obj.target/tools/v8_gypfiles/libv8_base_without_compiler.a
05:33:32 0 8045 7035 9 94 0 4443576 15732 - RJ 0 39:43.22 | | | `-- objdump -z -D /wrkdirs/usr/ports/www/node18/work/node-v18.18.2/out/Release/obj.target/tools/v8_gypfiles/libv8_base_without_compiler.a
00:00 0 98535 2129 23 20 0 12784 1836 piperd S+ 2 0:00.00 | `-- grep node18

For reference:

# ~/fbsd-based-on-what-commit.sh -C /usr/ports/
6ec8e3450b29 (HEAD -> main, freebsd/main, freebsd/HEAD) devel/sdts++: Mark DEPRECATED
Author: Muhammad Moinur Rahman <***@FreeBSD.org>
Commit: Muhammad Moinur Rahman <***@FreeBSD.org>
CommitDate: 2023-10-21 19:01:38 +0000
branch: main
merge-base: 6ec8e3450b29462a590d09fb0b07ed214d456bd5
merge-base: CommitDate: 2023-10-21 19:01:38 +0000
n637598 (--first-parent --count for merge-base)

===
Mark Millard
marklmi at yahoo.com

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

Mark Millard

2023-11-01 12:43:48 UTC

Permalink

Post by Mark Millard

An ongoing poudriere bulk -a test looks to have a stuck objdump ( used for building
# ps -oetime -alxdww | grep node18
05:48:03 0 44960 53404 21 68 0 18544 2892 select I 0 0:00.03 | | |-- sh: poudriere[main-amd64-bulk_a-default][15]: build_pkg (node18-18.18.2) (sh)
05:47:36 0 76480 44960 21 68 0 18544 2892 wait I 0 0:00.00 | | | `-- sh: poudriere[main-amd64-bulk_a-default][15]: build_pkg (node18-18.18.2) (sh)
05:47:36 0 76485 76480 19 68 0 12896 276 wait IJ 0 0:00.01 | | | `-- /usr/bin/make -C /usr/ports/www/node18 build
05:47:36 0 77304 76485 22 68 0 13356 288 wait IJ 0 0:00.00 | | | `-- /bin/sh -e -c (cd /wrkdirs/usr/ports/www/node18/work/node-v18.18.2; if ! /usr/bin/env CC.host=" cc" CFLAGS.host="-O2 -pipe -g -fstack-protector-strong -isystem /usr/local/include -fno-strict-aliasing " CXX.host=" c++" CXXFLAGS.host="-O2 -pipe -g -fstack-protector-strong -isystem /usr/local/include -fno-strict-aliasing -isystem /usr/local/include " LDFLAGS.host=" -fstack-protector-strong " LINK.host="c++" OPENSSLBASE=/usr OPENSSLDIR=/etc/ssl OPENSSLINC=/usr/include OPENSSLLIB=/usr/lib XDG_DATA_HOME=/wrkdirs/usr/ports/www/node18/work XDG_CONFIG_HOME=/wrkdirs/usr/ports/www/node18/work XDG_CACHE_HOME=/wrkdirs/usr/ports/www/node18/work/.cache HOME=/wrkdirs/usr/ports/www/node18/work TMPDIR="/tmp" PATH=/wrkdirs/usr/ports/www/node18/work/.bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/root/bin PKG_CONFIG_LIBDIR=/wrkdirs/usr/ports/www/node18/work/.pkgconfig:/usr/local/libdata/pkgconfig:/usr/local/share/pkgconfig:/usr/libdata/pkgconfig DONTSTRIP=yes DONTSTRIP=yes MK_DEBUG_FILES=no MK_KERNEL_SYMBOLS=no SHELL=/bin/sh NO_LINT=YES PREFIX=/usr/local LOCALBASE=/usr/local CC="cc" CFLAGS="-O2 -pipe -g -fstack-protector-strong -isystem /usr/local/include -fno-strict-aliasing " CPP="cpp" CPPFLAGS="-isystem /usr/local/include" LDFLAGS=" -fstack-protector-strong " LIBS="-L/usr/local/lib" CXX="c++" CXXFLAGS="-O2 -pipe -g -fstack-protector-strong -isystem /usr/local/include -fno-strict-aliasing -isystem /usr/local/include " MANPREFIX="/usr/local" BSD_INSTALL_PROGRAM="install -m 555" BSD_INSTALL_LIB="install -m 0644" BSD_INSTALL_SCRIPT="install -m 555" BSD_INSTALL_DATA="install -m 0644" BSD_INSTALL_MAN="install -m 444" gmake -f Makefile -j32 all; then if [ -n "Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to the maintainer." ] ; then echo "===> Compilation failed unexpectedly."; (echo "Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to the maintainer.") | /usr/bin/fmt 75 79 ; fi; false; fi)
05:33:34 0 7035 80309 9 26 0 22620 1312 piperd SJ 0 32:56.31 | | | `-- /usr/local/bin/python3.9 tools/genv8constants.py /wrkdirs/usr/ports/www/node18/work/node-v18.18.2/out/Release/obj/gen/v8constants.h /wrkdirs/usr/ports/www/node18/work/node-v18.18.2/out/Release/obj.target/tools/v8_gypfiles/libv8_base_without_compiler.a
05:33:32 0 8045 7035 9 94 0 4443576 15732 - RJ 0 39:43.22 | | | `-- objdump -z -D /wrkdirs/usr/ports/www/node18/work/node-v18.18.2/out/Release/obj.target/tools/v8_gypfiles/libv8_base_without_compiler.a
00:00 0 98535 2129 23 20 0 12784 1836 piperd S+ 2 0:00.00 | `-- grep node18
# ~/fbsd-based-on-what-commit.sh -C /usr/ports/
6ec8e3450b29 (HEAD -> main, freebsd/main, freebsd/HEAD) devel/sdts++: Mark DEPRECATED
CommitDate: 2023-10-21 19:01:38 +0000
branch: main
merge-base: 6ec8e3450b29462a590d09fb0b07ed214d456bd5
merge-base: CommitDate: 2023-10-21 19:01:38 +0000
n637598 (--first-parent --count for merge-base)

Looks like www/node16 has the same sort of issue as www/node18 :

# ps -oetime -alxdww | grep node16
02:24:49 0 58471 53404 30 68 0 18544 2884 select I 0 0:00.03 | | |-- sh: poudriere[main-amd64-bulk_a-default][17]: build_pkg (node16-16.20.1_1) (sh)
02:15:35 0 1626 58471 18 68 0 18544 2884 wait I 0 0:00.00 | | | `-- sh: poudriere[main-amd64-bulk_a-default][17]: build_pkg (node16-16.20.1_1) (sh)
02:15:35 0 1655 1626 21 68 0 12896 276 wait IJ 0 0:00.02 | | | `-- /usr/bin/make -C /usr/ports/www/node16 build
02:15:34 0 2154 1655 11 68 0 13356 280 wait IJ 0 0:00.00 | | | `-- /bin/sh -e -c (cd /wrkdirs/usr/ports/www/node16/work/node-v16.20.1; if ! /usr/bin/env OPENSSLBASE=/usr OPENSSLDIR=/etc/ssl OPENSSLINC=/usr/include OPENSSLLIB=/usr/lib XDG_DATA_HOME=/wrkdirs/usr/ports/www/node16/work XDG_CONFIG_HOME=/wrkdirs/usr/ports/www/node16/work XDG_CACHE_HOME=/wrkdirs/usr/ports/www/node16/work/.cache HOME=/wrkdirs/usr/ports/www/node16/work TMPDIR="/tmp" PATH=/wrkdirs/usr/ports/www/node16/work/.bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/root/bin PKG_CONFIG_LIBDIR=/wrkdirs/usr/ports/www/node16/work/.pkgconfig:/usr/local/libdata/pkgconfig:/usr/local/share/pkgconfig:/usr/libdata/pkgconfig DONTSTRIP=yes DONTSTRIP=yes MK_DEBUG_FILES=no MK_KERNEL_SYMBOLS=no SHELL=/bin/sh NO_LINT=YES PREFIX=/usr/local LOCALBASE=/usr/local CC="cc" CFLAGS="-O2 -pipe -g -fstack-protector-strong -isystem /usr/local/include -fno-strict-aliasing " CPP="cpp" CPPFLAGS="-isystem /usr/local/include" LDFLAGS=" -fstack-protector-strong " LIBS="-L/usr/local/lib" CXX="c++" CXXFLAGS="-O2 -pipe -g -fstack-protector-strong -isystem /usr/local/include -fno-strict-aliasing -Wno-error=enum-constexpr-conversion -isystem /usr/local/include " MANPREFIX="/usr/local" BSD_INSTALL_PROGRAM="install -m 555" BSD_INSTALL_LIB="install -m 0644" BSD_INSTALL_SCRIPT="install -m 555" BSD_INSTALL_DATA="install -m 0644" BSD_INSTALL_MAN="install -m 444" gmake -f Makefile -j32 CC.host=" cc" CFLAGS.host="-O2 -pipe -g -fstack-protector-strong -isystem /usr/local/include -fno-strict-aliasing " CXX.host=" c++" CXXFLAGS.host="-O2 -pipe -g -fstack-protector-strong -isystem /usr/local/include -fno-strict-aliasing -Wno-error=enum-constexpr-conversion -isystem /usr/local/include " LINK.host=c++ LDFLAGS.host=" -fstack-protector-strong " all; then if [ -n "Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to the maintainer." ] ; then echo "===> Compilation failed unexpectedly."; (echo "Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to the maintaine
01:55:30 0 84603 3452 15 47 0 22620 1312 - RJ 0 14:00.49 | | | `-- /usr/local/bin/python3.9 tools/genv8constants.py /wrkdirs/usr/ports/www/node16/work/node-v16.20.1/out/Release/obj/gen/v8constants.h /wrkdirs/usr/ports/www/node16/work/node-v16.20.1/out/Release/obj.target/tools/v8_gypfiles/libv8_base_without_compiler.a
01:55:27 0 86093 84603 15 101 0 3754296 32540 - RJ 0 16:59.56 | | | `-- objdump -z -D /wrkdirs/usr/ports/www/node16/work/node-v16.20.1/out/Release/obj.target/tools/v8_gypfiles/libv8_base_without_compiler.a
00:00 0 84657 2129 29 20 0 12784 1812 piperd S+ 2 0:00.00 | `-- grep node16

===
Mark Millard
marklmi at yahoo.com

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

Mark Millard

2023-11-03 01:00:18 UTC

Permalink

Post by Mark Millard

# ps -oetime -alxdww | grep node16
02:24:49 0 58471 53404 30 68 0 18544 2884 select I 0 0:00.03 | | |-- sh: poudriere[main-amd64-bulk_a-default][17]: build_pkg (node16-16.20.1_1) (sh)
02:15:35 0 1626 58471 18 68 0 18544 2884 wait I 0 0:00.00 | | | `-- sh: poudriere[main-amd64-bulk_a-default][17]: build_pkg (node16-16.20.1_1) (sh)
02:15:35 0 1655 1626 21 68 0 12896 276 wait IJ 0 0:00.02 | | | `-- /usr/bin/make -C /usr/ports/www/node16 build
02:15:34 0 2154 1655 11 68 0 13356 280 wait IJ 0 0:00.00 | | | `-- /bin/sh -e -c (cd /wrkdirs/usr/ports/www/node16/work/node-v16.20.1; if ! /usr/bin/env OPENSSLBASE=/usr OPENSSLDIR=/etc/ssl OPENSSLINC=/usr/include OPENSSLLIB=/usr/lib XDG_DATA_HOME=/wrkdirs/usr/ports/www/node16/work XDG_CONFIG_HOME=/wrkdirs/usr/ports/www/node16/work XDG_CACHE_HOME=/wrkdirs/usr/ports/www/node16/work/.cache HOME=/wrkdirs/usr/ports/www/node16/work TMPDIR="/tmp" PATH=/wrkdirs/usr/ports/www/node16/work/.bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/root/bin PKG_CONFIG_LIBDIR=/wrkdirs/usr/ports/www/node16/work/.pkgconfig:/usr/local/libdata/pkgconfig:/usr/local/share/pkgconfig:/usr/libdata/pkgconfig DONTSTRIP=yes DONTSTRIP=yes MK_DEBUG_FILES=no MK_KERNEL_SYMBOLS=no SHELL=/bin/sh NO_LINT=YES PREFIX=/usr/local LOCALBASE=/usr/local CC="cc" CFLAGS="-O2 -pipe -g -fstack-protector-strong -isystem /usr/local/include -fno-strict-aliasing " CPP="cpp" CPPFLAGS="-isystem /usr/local/include" LDFLAGS=" -fstack-protector-strong " LIBS="-L/usr/local/lib" CXX="c++" CXXFLAGS="-O2 -pipe -g -fstack-protector-strong -isystem /usr/local/include -fno-strict-aliasing -Wno-error=enum-constexpr-conversion -isystem /usr/local/include " MANPREFIX="/usr/local" BSD_INSTALL_PROGRAM="install -m 555" BSD_INSTALL_LIB="install -m 0644" BSD_INSTALL_SCRIPT="install -m 555" BSD_INSTALL_DATA="install -m 0644" BSD_INSTALL_MAN="install -m 444" gmake -f Makefile -j32 CC.host=" cc" CFLAGS.host="-O2 -pipe -g -fstack-protector-strong -isystem /usr/local/include -fno-strict-aliasing " CXX.host=" c++" CXXFLAGS.host="-O2 -pipe -g -fstack-protector-strong -isystem /usr/local/include -fno-strict-aliasing -Wno-error=enum-constexpr-conversion -isystem /usr/local/include " LINK.host=c++ LDFLAGS.host=" -fstack-protector-strong " all; then if [ -n "Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to the maintainer." ] ; then echo "===> Compilation failed unexpectedly."; (echo "Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to the maintaine
01:55:30 0 84603 3452 15 47 0 22620 1312 - RJ 0 14:00.49 | | | `-- /usr/local/bin/python3.9 tools/genv8constants.py /wrkdirs/usr/ports/www/node16/work/node-v16.20.1/out/Release/obj/gen/v8constants.h /wrkdirs/usr/ports/www/node16/work/node-v16.20.1/out/Release/obj.target/tools/v8_gypfiles/libv8_base_without_compiler.a
01:55:27 0 86093 84603 15 101 0 3754296 32540 - RJ 0 16:59.56 | | | `-- objdump -z -D /wrkdirs/usr/ports/www/node16/work/node-v16.20.1/out/Release/obj.target/tools/v8_gypfiles/libv8_base_without_compiler.a
00:00 0 84657 2129 29 20 0 12784 1812 piperd S+ 2 0:00.00 | `-- grep node16

# truss -p 86093
write(1," 2ff853: 74 61 "...,74) = 74 (0x4a)
write(1," 2ff855: 45 4e "...,50) = 50 (0x32)
write(1," 2ff857: 53 "...,51) = 51 (0x33)
write(1," 2ff858: 30 5f 36 "...,61) = 61 (0x3d)
write(1," 2ff85b: 48 61 "...,50) = 50 (0x32)
write(1," 2ff85d: 6e "...,58) = 58 (0x3a)
write(1," 2ff85e: 64 6c "...,61) = 61 (0x3d)
write(1," 2ff860: 65 49 4e "...,50) = 50 (0x32)
write(1," 2ff863: 53 "...,51) = 51 (0x33)
write(1," 2ff864: 30 5f 39 "...,61) = 61 (0x3d)
write(1," 2ff867: 42 79 74 "...,75) = 75 (0x4b)
write(1," 2ff86a: 65 41 72 72 "...,74) = 74 (0x4a)
. . .
# truss -p 8045
write(1," 16f4ca: 01 00 "...,58) = 58 (0x3a)
write(1," 16f4cc: 00 00 "...,57) = 57 (0x39)
write(1," 16f4ce: 00 00 "...,57) = 57 (0x39)
write(1," 16f4d0: ed "...,54) = 54 (0x36)
write(1," 16f4d1: ae "...,62) = 62 (0x3e)
write(1," 16f4d2: 0b 00 "...,57) = 57 (0x39)
write(1," 16f4d4: 00 00 "...,57) = 57 (0x39)
write(1," 16f4d6: 00 00 "...,57) = 57 (0x39)
write(1," 16f4d8: 0a 00 "...,56) = 56 (0x38)
write(1," 16f4da: 00 00 "...,57) = 57 (0x39)
write(1," 16f4dc: 09 00 "...,57) = 57 (0x39)
write(1," 16f4de: 00 00 "...,57) = 57 (0x39)
write(1," 16f4e0: d7 "...,46) = 46 (0x2e)
write(1," 16f4e1: a8 03 "...,56) = 56 (0x38)
. . .

Turns out that my rare poudriere bulk -a runs are sometimes
WITH_DEBUG experiments where most things are built using
WITH_DEBUG. This was such an example.
I stopped the bulk -a and started a new from-scratch one
based on not using WITH_DEBUG . node18 and node16 worked
fine in this context. (The bulk -a is still running,
building other ports into packages.)
(I've a gradually growing list of ports that end up with
WITH_DEBUG nearly always undefined. Build failures and
resource use can both lead to such a choice.)

The non-WITH_DEBUG bulk -a now has one thing left:

ID TOTAL ORIGIN PKGNAME PHASE PHASE TMPFS CPU% MEM%
[23] 01:25:09 textproc/stardict-quick | stardict-quick-2.4.2_9 fetch 01:24:39 1.33 GiB 0% 0%

that looks like the fetch may time out.

The last Finish to this point was:

[33:10:00] [32] [04:37:23] Finished emulators/libretro-mame | libretro-mame-20220124_1: Success

After which:

[main-amd64-bulk_a-default] [2023-11-01_07h14m50s] [parallel_build:] Queued: 34683 Built: 33825 Failed: 179 Skipped: 358 Ignored: 320 Fetched: 0 Tobuild: 1

So a mean of somewhat over 1000 port->package builds per hour, ignoring
textproc/stardict-quick .

As for the ports vintage:

# ~/fbsd-based-on-what-commit.sh -C /usr/ports/
6ec8e3450b29 (HEAD -> main, freebsd/main, freebsd/HEAD) devel/sdts++: Mark DEPRECATED
Author: Muhammad Moinur Rahman <***@FreeBSD.org>
Commit: Muhammad Moinur Rahman <***@FreeBSD.org>
CommitDate: 2023-10-21 19:01:38 +0000
branch: main
merge-base: 6ec8e3450b29462a590d09fb0b07ed214d456bd5
merge-base: CommitDate: 2023-10-21 19:01:38 +0000
n637598 (--first-parent --count for merge-base)

I do have a environment that avoids various LLVM builds taking
as long to build :

llvm1[3-7] : no MLIR, no FLANG
llvm1[4-7] : use BE_NATIVE
other llvm* : use defaults (so, no avoidance)

I also prevent the builds from using strip on most of the install
materials built (not just toolchain materials).

I have a munged up top that records and reports various "maximum
observed" (MaxObs...) figures (or other such) based on its sampling.
This explains some notation below.

ALLOW_MAKE_JOBS=yes was used. No explicit restriction on PARALLEL_JOBS
or MAKE_JOBS_NUMBER (or analogous). So 32 builders allowed, each allowed
32 make jobs. This explains the high load average style of bulk -a :

load averages . . . MaxObs: 360.70, 267.63, 210.84
(Those need not be all from the same time frame during the bulk -a .)

Most of the reported load averages were 96+ for all 3 durations, at least
when I was looking.

The build used USE_TMPFS=all . 96 GiBytes of RAM (total across the 2 DIMMs).
372736Mi swap partition. ZFS on single partition on single drive, ZFS used
just for bectl reasons, not other typical use-ZFS reasons. I've not
controlled the ARC size-range explicitly.

Swap-involved MaxObs figures:
173310Mi MaxObsUsed
56332Mi MaxObs(Act+Lndry+SwapUsed)
265551Mi MaxObs(Act+Wir+Lndry+SwapUsed)

So: having more than 260 GiBytes for RAM+SWAP is appropriate to the style
of build at the 32 hardware-thread scale with ZFS and the amount of RAM. I
had basically: 96 GiBytes RAM + 364 GiBytes swap partition == 460 GiBytes
RAM+SWAP.

The media is a PCIe Optane 905P card with 1.5T of space and it has the
372736Mi swap partition, not just the file system.

Just-RAM MaxObs figures:
81066Mi MaxObsActive
21483Mi MaxObsWired
94493Mi MaxObs(Act+Wir+Lndry)

I looked at the error logs for the failed builds and saw no evidence of
corruptions being involved. So far this system looks to be stable for
use for building software and such.

I may do a similar expriment on the UFS Optane 905P 1.5T
U2-in-PCIe-adapter media as well. (This configuration uses the swap
partition from the ZFS Optane media.)

Note: MaxObs(A+B+C) <= MaxObs(A)+MaxObs(B)+MaxObs(C)

===
Mark Millard
marklmi at yahoo.com

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

Mark Millard

2023-11-04 12:53:35 UTC

Permalink

Post by Mark Millard

ID TOTAL ORIGIN PKGNAME PHASE PHASE TMPFS CPU% MEM%
[23] 01:25:09 textproc/stardict-quick | stardict-quick-2.4.2_9 fetch 01:24:39 1.33 GiB 0% 0%
that looks like the fetch may time out.
[33:10:00] [32] [04:37:23] Finished emulators/libretro-mame | libretro-mame-20220124_1: Success
[main-amd64-bulk_a-default] [2023-11-01_07h14m50s] [parallel_build:] Queued: 34683 Built: 33825 Failed: 179 Skipped: 358 Ignored: 320 Fetched: 0 Tobuild: 1
So a mean of somewhat over 1000 port->package builds per hour, ignoring
textproc/stardict-quick .
# ~/fbsd-based-on-what-commit.sh -C /usr/ports/
6ec8e3450b29 (HEAD -> main, freebsd/main, freebsd/HEAD) devel/sdts++: Mark DEPRECATED
CommitDate: 2023-10-21 19:01:38 +0000
branch: main
merge-base: 6ec8e3450b29462a590d09fb0b07ed214d456bd5
merge-base: CommitDate: 2023-10-21 19:01:38 +0000
n637598 (--first-parent --count for merge-base)
I do have a environment that avoids various LLVM builds taking
llvm1[3-7] : no MLIR, no FLANG
llvm1[4-7] : use BE_NATIVE
other llvm* : use defaults (so, no avoidance)
I also prevent the builds from using strip on most of the install
materials built (not just toolchain materials).
I have a munged up top that records and reports various "maximum
observed" (MaxObs...) figures (or other such) based on its sampling.
This explains some notation below.
ALLOW_MAKE_JOBS=yes was used. No explicit restriction on PARALLEL_JOBS
or MAKE_JOBS_NUMBER (or analogous). So 32 builders allowed, each allowed
load averages . . . MaxObs: 360.70, 267.63, 210.84
(Those need not be all from the same time frame during the bulk -a .)
Most of the reported load averages were 96+ for all 3 durations, at least
when I was looking.
The build used USE_TMPFS=all . 96 GiBytes of RAM (total across the 2 DIMMs).
372736Mi swap partition. ZFS on single partition on single drive, ZFS used
just for bectl reasons, not other typical use-ZFS reasons. I've not
controlled the ARC size-range explicitly.
173310Mi MaxObsUsed
56332Mi MaxObs(Act+Lndry+SwapUsed)
265551Mi MaxObs(Act+Wir+Lndry+SwapUsed)
So: having more than 260 GiBytes for RAM+SWAP is appropriate to the style
of build at the 32 hardware-thread scale with ZFS and the amount of RAM. I
had basically: 96 GiBytes RAM + 364 GiBytes swap partition == 460 GiBytes
RAM+SWAP.
The media is a PCIe Optane 905P card with 1.5T of space and it has the
372736Mi swap partition, not just the file system.
81066Mi MaxObsActive
21483Mi MaxObsWired
94493Mi MaxObs(Act+Wir+Lndry)

I should have explained the MaxObsWired figure that I reported. It is messy
to report usefully because of ARC use of wired that increase when the machine
does not have RAM use pressure restricting its size and decreases when there
is such memory pressure.
The 21483Mi figure is from a time later in the bulk -a where the pressure was
still in place (but monitoring had started before the ARC had grown
significantly after the boot).
[main-amd64-bulk_a-default] [2023-11-01_07h14m50s] [committing:] Queued: 34683 Built: 33826 Failed: 179 Skipped: 358 Ignored: 320 Fetched: 0 Tobuild: 0 Time: 35:37:55
90443Mi MaxObsWired
MaxObsActive did not change but 94493Mi MaxObs(Act+Wir+Lndry) was slightly
smaller in the 21483Mi MaxObsWired time frame: 94437Mi MaxObs(Act+Wir+Lndry) .
The "Swap-involved MaxObs figures" did not change.
Note: textproc/stardict-quick did lead to the overall mean being more like
949 port->package builds per hour, spanning somewhat under 1.5 days.

Post by Mark Millard
I looked at the error logs for the failed builds and saw no evidence of
corruptions being involved. So far this system looks to be stable for
use for building software and such.
I may do a similar expriment on the UFS Optane 905P 1.5T
U2-in-PCIe-adapter media as well. (This configuration uses the swap
partition from the ZFS Optane media.)

The experiment failed: "Too many links" under logs/bulk/latest-per-pkg/
and then "Failed: starting". (Lots of such messages.)

In other words, UFS hits a 16 bit field limitation associated with:

/usr/include/ufs/ufs/dinode.h:#define UFS_LINK_MAX 32767

and poudriere bulk does nothing to avoid hitting the limitation,
given that there are more buildable ports than that now.

Post by Mark Millard

Post by Mark Millard
Note: MaxObs(A+B+C) <= MaxObs(A)+MaxObs(B)+MaxObs(C)

===
Mark Millard
marklmi at yahoo.com

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

Mark Millard

2023-11-09 03:19:15 UTC

Permalink

[Just supplying a missing leading digit in a numeral.]

Post by Mark Millard

The above line should have been:

256332Mi MaxObs(Act+Lndry+SwapUsed)

Post by Mark Millard

Post by Mark Millard
265551Mi MaxObs(Act+Wir+Lndry+SwapUsed)
So: having more than 260 GiBytes for RAM+SWAP is appropriate to the style
of build at the 32 hardware-thread scale with ZFS and the amount of RAM. I
had basically: 96 GiBytes RAM + 364 GiBytes swap partition == 460 GiBytes
RAM+SWAP.
The media is a PCIe Optane 905P card with 1.5T of space and it has the
372736Mi swap partition, not just the file system.
81066Mi MaxObsActive
21483Mi MaxObsWired
94493Mi MaxObs(Act+Wir+Lndry)

The experiment failed: "Too many links" under logs/bulk/latest-per-pkg/
and then "Failed: starting". (Lots of such messages.)
/usr/include/ufs/ufs/dinode.h:#define UFS_LINK_MAX 32767
and poudriere bulk does nothing to avoid hitting the limitation,
given that there are more buildable ports than that now.

Post by Mark Millard

Post by Mark Millard
Note: MaxObs(A+B+C) <= MaxObs(A)+MaxObs(B)+MaxObs(C)

===
Mark Millard
marklmi at yahoo.com

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

Mark Millard

2023-11-01 13:02:14 UTC

Permalink

Post by Mark Millard

For reference (node16's objdump then node18's):

# truss -p 86093
write(1," 2ff853: 74 61 "...,74) = 74 (0x4a)
write(1," 2ff855: 45 4e "...,50) = 50 (0x32)
write(1," 2ff857: 53 "...,51) = 51 (0x33)
write(1," 2ff858: 30 5f 36 "...,61) = 61 (0x3d)
write(1," 2ff85b: 48 61 "...,50) = 50 (0x32)
write(1," 2ff85d: 6e "...,58) = 58 (0x3a)
write(1," 2ff85e: 64 6c "...,61) = 61 (0x3d)
write(1," 2ff860: 65 49 4e "...,50) = 50 (0x32)
write(1," 2ff863: 53 "...,51) = 51 (0x33)
write(1," 2ff864: 30 5f 39 "...,61) = 61 (0x3d)
write(1," 2ff867: 42 79 74 "...,75) = 75 (0x4b)
write(1," 2ff86a: 65 41 72 72 "...,74) = 74 (0x4a)
. . .

# truss -p 8045
write(1," 16f4ca: 01 00 "...,58) = 58 (0x3a)
write(1," 16f4cc: 00 00 "...,57) = 57 (0x39)
write(1," 16f4ce: 00 00 "...,57) = 57 (0x39)
write(1," 16f4d0: ed "...,54) = 54 (0x36)
write(1," 16f4d1: ae "...,62) = 62 (0x3e)
write(1," 16f4d2: 0b 00 "...,57) = 57 (0x39)
write(1," 16f4d4: 00 00 "...,57) = 57 (0x39)
write(1," 16f4d6: 00 00 "...,57) = 57 (0x39)
write(1," 16f4d8: 0a 00 "...,56) = 56 (0x38)
write(1," 16f4da: 00 00 "...,57) = 57 (0x39)
write(1," 16f4dc: 09 00 "...,57) = 57 (0x39)
write(1," 16f4de: 00 00 "...,57) = 57 (0x39)
write(1," 16f4e0: d7 "...,46) = 46 (0x2e)
write(1," 16f4e1: a8 03 "...,56) = 56 (0x38)
. . .

===
Mark Millard
marklmi at yahoo.com

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

Mark Millard

2023-11-03 02:26:31 UTC

Permalink

Post by Mark Millard

I should have explained the MaxObsWired figure that I reported. It is messy
to report usefully because of ARC use of wired that increase when the machine
does not have RAM use pressure restricting its size and decreases when there
is such memory pressure.

The 21483Mi figure is from a time later in the bulk -a where the pressure was
still in place (but monitoring had started before the ARC had grown
significantly after the boot).

Now that the bulk -a is done:

[main-amd64-bulk_a-default] [2023-11-01_07h14m50s] [committing:] Queued: 34683 Built: 33826 Failed: 179 Skipped: 358 Ignored: 320 Fetched: 0 Tobuild: 0 Time: 35:37:55

and the tail of the activity did not cause such pressure the figure is:

90443Mi MaxObsWired

MaxObsActive did not change but 94493Mi MaxObs(Act+Wir+Lndry) was slightly
smaller in the 21483Mi MaxObsWired time frame: 94437Mi MaxObs(Act+Wir+Lndry) .

The "Swap-involved MaxObs figures" did not change.

Note: textproc/stardict-quick did lead to the overall mean being more like
949 port->package builds per hour, spanning somewhat under 1.5 days.

===
Mark Millard
marklmi at yahoo.com

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

Mark Millard

2023-11-02 00:32:00 UTC

Permalink

Post by Mark Millard

Turns out that my rare poudriere bulk -a runs are sometimes
WITH_DEBUG experiments where most things are built using
WITH_DEBUG. This was such an example.

I stopped the bulk -a and started a new from-scratch one
based on not using WITH_DEBUG . node18 and node16 worked
fine in this context. (The bulk -a is still running,
building other ports into packages.)

(I've a gradually growing list of ports that end up with
WITH_DEBUG nearly always undefined. Build failures and
resource use can both lead to such a choice.)

===
Mark Millard
marklmi at yahoo.com

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

Paul Floyd

2023-11-02 21:08:21 UTC

Permalink

Hi Mark

I'm interested. I recently started speccing an upgrade (well, keeping
the case and maybe a couple of disks) for my ancient Solaris 11 AMD
Opteron system.

I'm thinking of the 7950X3D and an x670 or x670e board. I'm planning on
using the onboard graphics, which I understand don't work in accelerated
mode requiring the use of scfb. I'm not too bothered with the wifi as
long as ethernet works. I don't often use the DVD-ROM drive but it would
ne nice if it worked. I think I can finally lay to rest the floppy drive
(I said that it was old).

I'll keep following this thread and the bugzi item mentioned earlier.

A+

Paul

Paul Floyd

2023-11-03 16:26:05 UTC

Permalink

Hi Mark

I'm interested. I recently started speccing a new system to replace my
ancient Solaris 11 AMD Opteron system

I'm thinking of the 7950X3D and an x670 or x670e board. I'm planning on
using the onboard graphics, which I understand don't work in accelerated
mode requiring the use of scfb. I'm not too bothered with the wifi as
long as ethernet works. I don't often use the DVD-ROM drive but it would
ne nice if it worked. I think I can finally lay to rest the floppy drive
(I said that it was old).

I'll keep following this thread and the bugzi atime that was mentioned.

A+

Paul

Daniel Engberg

2023-11-04 20:10:36 UTC

Permalink

Â Â
Â Â #Â unameÂ -apKU
Â Â
Â Â IÂ movedÂ myÂ FreeBDSSÂ bootÂ mediaÂ fromÂ aÂ ThreadRipperÂ 1950XÂ toÂ aÂ RyzenÂ 9Â 7950X3DÂ andÂ tried
Â Â booting.Â ItÂ bootedÂ butÂ someÂ ofÂ theÂ followingÂ mightÂ beÂ ofÂ someÂ note.Â IsÂ anyÂ ofÂ itÂ likely
Â Â toÂ beÂ problematical?Â AnyÂ ofÂ itÂ ofÂ particularÂ interestÂ toÂ anyone?

Â
Â HiÂ Mark
Â
Â I'mÂ interested.Â IÂ recentlyÂ startedÂ speccingÂ aÂ newÂ systemÂ toÂ replace
Â myÂ ancientÂ SolarisÂ 11Â AMDÂ OpteronÂ system
Â
Â I'mÂ thinkingÂ ofÂ theÂ 7950X3DÂ andÂ anÂ x670Â orÂ x670eÂ board.Â I'mÂ planning
Â onÂ usingÂ theÂ onboardÂ graphics,Â whichÂ IÂ understandÂ don'tÂ workÂ in
Â acceleratedÂ modeÂ requiringÂ theÂ useÂ ofÂ scfb.Â I'mÂ notÂ tooÂ bothered
Â withÂ theÂ wifiÂ asÂ longÂ asÂ ethernetÂ works.Â IÂ don'tÂ oftenÂ useÂ the
Â DVD-ROMÂ driveÂ butÂ itÂ wouldÂ neÂ niceÂ ifÂ itÂ worked.Â IÂ thinkÂ IÂ can
Â finallyÂ layÂ toÂ restÂ theÂ floppyÂ driveÂ (IÂ saidÂ thatÂ itÂ wasÂ old).
Â
Â I'llÂ keepÂ followingÂ thisÂ threadÂ andÂ theÂ bugziÂ atimeÂ thatÂ was
Â mentioned.
Â
Â A+
Â
Â Paul

Hi,

AM5 works pretty well in general but there are some issues you might
want to be aware of. As mentioned this
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272507 seems to
plauge various models and BIOS versions. I'm not sure it's the same
for B650 series as I only have one data point being ASRock B650M PG
WiFi running Beta BIOS 1.30.AS02/AGESA 1.0.0.7c which according to the
reporter works fine. As far as WIFI goes most uses "AMD RZ616" which
is a Mediatek controller and unsupported however there's work being
done bringing in the mt76 driver that should to my knowledge support
this controller. Regarding ethernet you more or less have three
options using the builtin controllers, Intel i225-V, Realtek RTL8125BG
or Marvell AQC113(C). Intel works out of the box using 14.0, no idea
about Realtek but I suspect that you need to use the port to get it
going and the Marvell controller lacks a driver. There's a NetBSD
developer hacking on a driver if you're interested getting that going
by porting it, https://github.com/ryo/aquantia .

A word of advice, you'll need a beefy CPU cooler for the 95W+ "rated"
CPUs as they boost very aggressively and mid-sized air cooler might
cause it to throttle. Most Asus boards also supports ECC memory which
can be a nice feature.

Here's a good round-up of most if not all available models.

https://docs.google.com/spreadsheets/d/1NQHkDEcgDPm34Mns3C93K6SJoBnua-x9O-y_6hv8sPs/edit#gid=0

I'm personally happy with my ASUS ProArt X670E-CREATOR with 128Gb of
ECC memory (4 x MTC20C2085S1EC48BR) however be aware that you'll see
much slower memory clocks with 4 memory sticks especially dual rank
due to how DDR5 and current memory controllers works. Using the latest
BIOS available as of writing (1710) breaks SATA and USB among a few
other things while 1602 works fine.

Best regards,

Daniel

Paul Floyd

2023-11-12 12:49:49 UTC

Permalink

The MSI board looks decent I guess, the x16/x4/x2 layout isn't great but
it's not horrible either depending on your use case. Never looked into
their lineup due to lack of a decent builtin NIC. You can get a separate
one but it's still an additional cost and takes of at least one PCIe slot.
ASRock boards in general appears to be a bit rough around the edges
(both hardware design and BIOS) especially low-mid range models, their
premium tiers gets great reviews though. I would really think twice
about getting a board with only one slot that has more lanes than 1x in
terms of "full size" PCIe slots and you're again stuck with the Realtek NIC.
As you said, the Asus board is pretty much like the MSI one however I
don't see why you'd go for that over the TUF Gaming X670E-Plus which is
pretty much the same board with some very minor changes such as no
optical output (quite a bit cheaper though).
The ProArt board also has a HDMI output? :-)
https://www.asus.com/motherboards-components/motherboards/proart/proart-x670e-creator-wifi/ <https://www.asus.com/motherboards-components/motherboards/proart/proart-x670e-creator-wifi

My desk has a shelf with a scanner on it, so not much space for the
monitor (I have thought about sawing off 10cm from the shelf so that
there would be space for a 27" monitor). When I work from home with a
Dell Windows laptop I usually use the hdmi socket. I suppose I could get
a miniDP-DP cable instead.

I don't tend to have big RAM or networking requirements. The main things
are decent speed, recent ISA (esp things like avx512 and preferably on
the metal) and probably a fair number of disks. In the past I've
partitioned disks for OSes but these days I usually have one boot disk
per OS and then a few data disks. Right now I have about 400G of data on
my zfs disks, mostly VBox VM images.

I'll have another think about the ProArt and peruse the TUF Gaming
X670E-Plus.

A+
Paul

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

Greg 'groggy' Lehey

2023-11-12 23:22:31 UTC

Permalink

Post by Paul Floyd
MSI MAG X670E Tomahawk

FWIW, I've just got a machine with this motherboard. It seemed the
best option available to me at the time, and I haven't had any issues
with it. Yes, the silly NIC (where do you find 2.5 Gb/s hubs?) is
irritating, but I need 2 NICs anyway, so putting in a second wasn't an
issue. I also couldn't find any motherboard that fitted the other
requirements and didn't have this NIC.

Greg
--
Sent from my desktop computer.
See complete headers for address and phone numbers.
This message is digitally signed. If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA.php

Stefan Esser

2023-11-13 09:19:05 UTC

Permalink

Post by Greg 'groggy' Lehey

Post by Paul Floyd
MSI MAG X670E Tomahawk

Hi Greg,

the 2.5 Gbit/s NIC is downwards compatible with 1 Gbit/s Ethernet
and while there is not much supporting equipment, it is no worse
than a 1 Gbit/s NIC in practice.

10 Gbit/s is too expensive (due to chip and board complexities)
and to power-hungry for integration on typical PC mainboards
(given the high cost of 10 Gbit/s switches, hardly anybody could
make good use of them outside a datacenter environment, anyway).

You do probably know that the Realtek RTL8125 chip is supported
by the official Realtek driver in ports (realtek-re-kmod package).

Too bad that Realtek does not publish programming information for
this chip. There are open source drivers that support it, but they
do not fit well into FreeBSD and they do not provide sufficient
information to make the FreeBSD Realtek 1 Gbit/s NIT driver support
the 2.5 Gbit/s chip ... (I had started a merge of the code for the
new chip into our kernel driver, but there was not enough information
about the PHY and other details and I gave up.)

Every few month I look for a publicly available databook with the
necessary details (full register description, reset sequence etc.)
for the RTL8125 chips on the sites that tend to provide such
information, but nothing has appeared there, yet.

Best regards, STefan

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

Greg 'groggy' Lehey

2023-11-13 06:27:02 UTC

Permalink

Post by Daniel Engberg

Post by Paul Floyd
MSI MAG X670E Tomahawk

Nice! So the sata controller gets initialized correctly even on newer
BIOS versions?

Oh. I don't have any SATA devices, so I can't say for sure, but this
looks concerning:

pcib19: <ACPI PCI-PCI bridge> at device 13.0 on pci11
pcib19: failed to allocate initial memory window: 0xfb200000-0xfb3fffff
pci19: <ACPI PCI bus> on pcib19
ahci0: <AHCI SATA controller> mem 0xfb800000-0xfb8003ff at device 0.0 on pci19
ahci0: AHCI controller reset failure
device_attach: ahci0 attach returned 6

On the other hand, I also have:

pcib21: <ACPI PCI-PCI bridge> at device 13.0 on pci4
pcib21: failed to allocate initial memory window: 0xfb800000-0xfb8fffff
pci21: <ACPI PCI bus> on pcib21
ahci0: <AHCI SATA controller> mem 0xfbb00000-0xfbb003ff at device 0.0 on pci21
ahci0: AHCI v1.31 with 6 6Gbps ports, Port Multiplier supported
ahcich0: <AHCI channel> at channel 0 on ahci0
ahcich1: <AHCI channel> at channel 1 on ahci0
ahcich2: <AHCI channel> at channel 2 on ahci0
ahcich3: <AHCI channel> at channel 3 on ahci0

So at some later date, when I want to connect SATA drives, I may run
into issues.

Post by Daniel Engberg
Does the Realtek NIC work ootb or do you need to use the driver in
ports tree?

It doesn't work OOTB. As I said, I have a second NIC, and that's what
I'm using. I'm planning to try the Realtek NIC later, but currently
I'm trying to catch up on 10 years of main desktop configuration and
multiple monitors. The old machine still works, so I'm planning to
take my time and "do it right", which could take weeks.

Post by Daniel Engberg
2.5G switches aren't that uncommon these days,
...

Thanks for the info. The NIC also does 1000baseT, right? Since this
is the only machine that's faster, it doesn't help much, so I'll use
1000baseT.

Greg
--
Sent from my desktop computer.
See complete headers for address and phone numbers.
This message is digitally signed. If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA.php

Paul Floyd

2023-11-12 08:46:18 UTC

Permalink

Post by Daniel Engberg
AM5 works pretty well in general but there are some issues you might
want to be aware of. As mentioned this
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272507
<https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272507> seems to
A word of advice, you'll need a beefy CPU cooler for the 95W+ "rated"
CPUs as they boost very aggressively and mid-sized air cooler might
cause it to throttle. Most Asus boards also supports ECC memory which
can be a nice feature.

I'm not too woried about that yet.

Post by Daniel Engberg
Here's a good round-up of most if not all available models.
https://docs.google.com/spreadsheets/d/1NQHkDEcgDPm34Mns3C93K6SJoBnua-x9O-y_6hv8sPs/edit#gid=0 <https://docs.google.com/spreadsheets/d/1NQHkDEcgDPm34Mns3C93K6SJoBnua-x9O-y_6hv8sPs/edit#gid=0>
I'm personally happy with my ASUS ProArt X670E-CREATOR with 128Gb of ECC
memory (4 x MTC20C2085S1EC48BR) however be aware that you'll see much
slower memory clocks with 4 memory sticks especially dual rank due to
how DDR5 and current memory controllers works. Using the latest BIOS
available as of writing (1710) breaks SATA and USB among a few other
things while 1602 works fine.

I was thinking of the ProArt but strangely it only has input
DisplayPort. Choosing a motherboard does seem to be the hardest bit. A
lot seem to be expensive and flashy for gamers.

At the moment I'm down to a list of 3

MSI MAG X670E Tomahawk
Looks good but I'm a bit put off by bad reviews on youtube and amazon
regarding quality

ASRock X670E Pro RS
Again not glowing reviews but it does have 6 sata ports 'just in casse'

ASUS Prime X670E-Pro
Much like the MSI Tomahawk

A+
Paul

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

Daniel Engberg

2023-11-12 10:35:47 UTC

Permalink

Â Â AM5Â worksÂ prettyÂ wellÂ inÂ generalÂ butÂ thereÂ areÂ someÂ issuesÂ you
Â Â mightÂ
Â Â
Â Â Â wantÂ toÂ beÂ awareÂ of.Â AsÂ mentionedÂ thisÂ
Â Â
Â Â Â https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272507Â
Â Â
Â Â Â <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272507>
Â Â [https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272507>];Â seems
Â Â to

Â Â AÂ wordÂ ofÂ advice,Â you'llÂ needÂ aÂ beefyÂ CPUÂ coolerÂ forÂ theÂ 95W+
Â Â "rated"Â
Â Â
Â Â Â CPUsÂ asÂ theyÂ boostÂ veryÂ aggressivelyÂ andÂ mid-sizedÂ airÂ cooler
Â Â mightÂ
Â Â
Â Â Â causeÂ itÂ toÂ throttle.Â MostÂ AsusÂ boardsÂ alsoÂ supportsÂ ECCÂ memory
Â Â whichÂ
Â Â
Â Â Â canÂ beÂ aÂ niceÂ feature.

Â
Â Â I'mÂ notÂ tooÂ woriedÂ aboutÂ thatÂ yet.
Â

Â Â Here'sÂ aÂ goodÂ round-upÂ ofÂ mostÂ ifÂ notÂ allÂ availableÂ models.
Â Â
Â Â Â https://docs.google.com/spreadsheets/d/1NQHkDEcgDPm34Mns3C93K6SJoBnua-x9O-y_6hv8sPs/edit#gid=0
Â Â <https://docs.google.com/spreadsheets/d/1NQHkDEcgDPm34Mns3C93K6SJoBnua-x9O-y_6hv8sPs/edit#gid=0>
Â Â [https://docs.google.com/spreadsheets/d/1NQHkDEcgDPm34Mns3C93K6SJoBnua-x9O-y_6hv8sPs/edit#gid=0>];
Â Â
Â Â Â I'mÂ personallyÂ happyÂ withÂ myÂ ASUSÂ ProArtÂ X670E-CREATORÂ withÂ 128Gb
Â Â ofÂ ECCÂ
Â Â
Â Â Â memoryÂ (4Â xÂ MTC20C2085S1EC48BR)Â howeverÂ beÂ awareÂ thatÂ you'llÂ see
Â Â muchÂ
Â Â
Â Â Â slowerÂ memoryÂ clocksÂ withÂ 4Â memoryÂ sticksÂ especiallyÂ dualÂ rank
Â Â dueÂ toÂ
Â Â
Â Â Â howÂ DDR5Â andÂ currentÂ memoryÂ controllersÂ works.Â UsingÂ theÂ latest
Â Â BIOSÂ
Â Â
Â Â Â availableÂ asÂ ofÂ writingÂ (1710)Â breaksÂ SATAÂ andÂ USBÂ amongÂ aÂ few
Â Â otherÂ
Â Â
Â Â Â thingsÂ whileÂ 1602Â worksÂ fine.

Â
Â IÂ wasÂ thinkingÂ ofÂ theÂ ProArtÂ butÂ strangelyÂ itÂ onlyÂ hasÂ inputÂ
Â
Â DisplayPort.Â ChoosingÂ aÂ motherboardÂ doesÂ seemÂ toÂ beÂ theÂ hardestÂ bit.
Â AÂ
Â
Â lotÂ seemÂ toÂ beÂ expensiveÂ andÂ flashyÂ forÂ gamers.
Â
Â AtÂ theÂ momentÂ I'mÂ downÂ toÂ aÂ listÂ ofÂ 3
Â
Â MSIÂ MAGÂ X670EÂ Tomahawk
Â
Â LooksÂ goodÂ butÂ I'mÂ aÂ bitÂ putÂ offÂ byÂ badÂ reviewsÂ onÂ youtubeÂ and
Â amazonÂ
Â
Â regardingÂ quality
Â
Â ASRockÂ X670EÂ ProÂ RS
Â
Â AgainÂ notÂ glowingÂ reviewsÂ butÂ itÂ doesÂ haveÂ 6Â sataÂ portsÂ 'justÂ in
Â casse'
Â
Â ASUSÂ PrimeÂ X670E-Pro
Â
Â MuchÂ likeÂ theÂ MSIÂ Tomahawk
Â
Â A+
Â
Â Paul

The MSI board looks decent I guess, the x16/x4/x2 layout isn't great
but it's not horrible either depending on your use case. Never looked
into their lineup due to lack of a decent builtin NIC. You can get a
separate one but it's still an additional cost and takes of at least
one PCIe slot.

ASRock boards in general appears to be a bit rough around the edges
(both hardware design and BIOS) especially low-mid range models, their
premium tiers gets great reviews though. I would really think twice
about getting a board with only one slot that has more lanes than 1x
in terms of "full size" PCIe slots and you're again stuck with the
Realtek NIC.

As you said, the Asus board is pretty much like the MSI one however I
don't see why you'd go for that over the TUF Gaming X670E-Plus which
is pretty much the same board with some very minor changes such as no
optical output (quite a bit cheaper though).

The ProArt board also has a HDMI output? :-)

https://www.asus.com/motherboards-components/motherboards/proart/proart-x670e-creator-wifi/

Best regards,

Daniel

Daniel Engberg

2023-11-13 05:46:10 UTC

Permalink

On 2023-11-13T00:22:31.000+01:00, Greg 'groggy' Lehey

Â Â

Â Â Â

Â Â Â Â MSIÂ MAGÂ X670EÂ Tomahawk

Â Â Â
Â Â Â Â TheÂ MSIÂ boardÂ looksÂ decentÂ IÂ guess,Â theÂ x16/x4/x2Â layoutÂ isn't
Â Â Â greatÂ but
Â Â Â
Â Â Â Â it'sÂ notÂ horribleÂ eitherÂ dependingÂ onÂ yourÂ useÂ case.Â Never
Â Â Â lookedÂ into
Â Â Â
Â Â Â Â theirÂ lineupÂ dueÂ toÂ lackÂ ofÂ aÂ decentÂ builtinÂ NIC.Â YouÂ canÂ getÂ a
Â Â Â separate
Â Â Â
Â Â Â Â oneÂ butÂ it'sÂ stillÂ anÂ additionalÂ costÂ andÂ takesÂ ofÂ atÂ leastÂ one
Â Â Â PCIeÂ slot.

Â
Â FWIW,Â I'veÂ justÂ gotÂ aÂ machineÂ withÂ thisÂ motherboard.Â ItÂ seemedÂ the
Â
Â bestÂ optionÂ availableÂ toÂ meÂ atÂ theÂ time,Â andÂ IÂ haven'tÂ hadÂ any
Â issues
Â
Â withÂ it.Â Yes,Â theÂ sillyÂ NICÂ (whereÂ doÂ youÂ findÂ 2.5Â Gb/sÂ hubs?)Â is
Â
Â irritating,Â butÂ IÂ needÂ 2Â NICsÂ anyway,Â soÂ puttingÂ inÂ aÂ secondÂ wasn't
Â an
Â
Â issue.Â IÂ alsoÂ couldn'tÂ findÂ anyÂ motherboardÂ thatÂ fittedÂ theÂ other
Â
Â requirementsÂ andÂ didn'tÂ haveÂ thisÂ NIC.
Â
Â Greg
Â
Â --
Â
Â SentÂ fromÂ myÂ desktopÂ computer.
Â
Â SeeÂ completeÂ headersÂ forÂ addressÂ andÂ phoneÂ numbers.
Â
Â ThisÂ messageÂ isÂ digitallyÂ signed.Â IfÂ yourÂ MicrosoftÂ mailÂ program
Â
Â reportsÂ problems,Â pleaseÂ readÂ http://lemis.com/broken-MUA.php

Hi,

Nice! So the sata controller gets initialized correctly even on newer
BIOS versions? Does the Realtek NIC work ootb or do you need to use
the driver in ports tree? 2.5G switches aren't that uncommon these
days,

https://www.zyxel.com/global/en/products/switch/5-8-port-2-5gbe-unmanaged-switch-mg100-series

https://www.zyxel.com/global/en/products/switch/12-port-unmanaged-multi-gigabit-switch-with-2-port-2-5g-and-2-port-10g-sfp-xgs1010-12

https://www.zyxel.com/global/en/products/switch/12-port-web-managed-multi-gigabit-switch-with-2-port-2-5g-and-2-port-10g-sfp-xgs1210-12

https://www.zyxel.com/global/en/products/switch/12-port-web-managed-multi-gigabit-switch-includes-3-port-10g-and-1-port-10g-sfp-xgs1250-12

https://www.zyxel.com/global/en/products/switch/24-port-2-5g-multi-gig-lite-l3-smart-managed-switch-with-6-10g-uplinks-xmg1930-series

https://www.netgear.com/business/wired/switches/unmanaged/ms105/

https://geizhals.de/?cat=switchgi&xf=13266_2G5

Just to mention a few :)

Best regards,

Daniel