Skip site navigation (1)Skip section navigation (2) 
Date:      Tue, 31 Oct 2023 23:00:22 -0700
From:      Mark Millard <marklmi@yahoo.com>
To:        FreeBSD Hackers <freebsd-hackers@freebsd.org>
Subject:   Trying initial boot of FreeBSD (main so: 15) of Ryzen 9 7950X3D on an ASUS Prime X670-P WIFI: various dmesg -a lines; more
Message-ID:  <A7AB0048-40EA-49FE-B204-CD32C79AD8D8@yahoo.com>
References:  <A7AB0048-40EA-49FE-B204-CD32C79AD8D8.ref@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help 
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     =
root@amd64-ZFS:/usr/obj/BUILDs/main-amd64-nodbg-clang/usr/main-src/amd64.a=
md64/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
. . .=20
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
. . .
none0@pci0:0:0:2:       class=3D0x080600 rev=3D0x00 hdr=3D0x00 =
vendor=3D0x1022 device=3D0x14d9 subvendor=3D0x1043 subdevice=3D0x8877
    vendor     =3D 'Advanced Micro Devices, Inc. [AMD]'
    class      =3D base peripheral
    subclass   =3D IOMMU
. . .
none1@pci0:0:20:0:      class=3D0x0c0500 rev=3D0x71 hdr=3D0x00 =
vendor=3D0x1022 device=3D0x790b subvendor=3D0x1043 subdevice=3D0x8877
    vendor     =3D 'Advanced Micro Devices, Inc. [AMD]'
    device     =3D 'FCH SMBus Controller'
    class      =3D serial bus
    subclass   =3D SMBus
. . .
none2@pci0:8:0:0:       class=3D0x020000 rev=3D0x05 hdr=3D0x00 =
vendor=3D0x10ec device=3D0x8125 subvendor=3D0x1043 subdevice=3D0x87d7
    vendor     =3D 'Realtek Semiconductor Co., Ltd.'
    device     =3D 'RTL8125 2.5GbE Controller'
    class      =3D network
    subclass   =3D ethernet
none3@pci0:9:0:0:       class=3D0x028000 rev=3D0x00 hdr=3D0x00 =
vendor=3D0x10ec device=3D0xb852 subvendor=3D0x1a3b subdevice=3D0x5471
    vendor     =3D 'Realtek Semiconductor Co., Ltd.'
    class      =3D network
 . . .
none4@pci0:15:0:2:      class=3D0x108000 rev=3D0x00 hdr=3D0x00 =
vendor=3D0x1022 device=3D0x1649 subvendor=3D0x1043 subdevice=3D0x8877
    vendor     =3D 'Advanced Micro Devices, Inc. [AMD]'
    device     =3D 'VanGogh PSP/CCP'
    class      =3D 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:=20

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.)


=3D=3D=3D
Mark Millard
marklmi at yahoo.com

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A7AB0048-40EA-49FE-B204-CD32C79AD8D8>