Date: Sat, 06 Apr 2019 19:06:57 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 237063] After "kld amdtemp": devinfo missing cpu31 for Ryzen Threadripper 1950X context Message-ID: <bug-237063-227-dNG79yfvv4@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-237063-227@https.bugs.freebsd.org/bugzilla/> References: <bug-237063-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D237063 --- Comment #4 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to Conrad Meyer from comment #2) For reference, from dmesg -a: FreeBSD/SMP: Multiprocessor System Detected: 32 CPUs FreeBSD/SMP: 1 package(s) x 2 groups x 2 cache groups x 4 core(s) x 2 hardw= are threads Rebooting without any equivalent of "kldstat amdtemp": cpu31 is still missi= ng: # devinfo | less nexus0 cryptosoft0 vtvga0 apic0 ram0 acpi0 cpu0 hwpstate0 cpufreq0 cpu1 cpu2 cpu3 cpu4 cpu5 cpu6 cpu7 cpu8 cpu9 cpu10 cpu11 cpu12 cpu13 cpu14 cpu15 cpu16 cpu17 cpu18 cpu19 cpu20 cpu21 cpu22 cpu23 cpu24 cpu25 cpu26 cpu27 cpu28 cpu29 cpu30 pcib0 . . . This is with: # kldstat Id Refs Address Size Name 1 41 0xffffffff80200000 2dafae8 kernel 2 1 0xffffffff83222000 2668 intpm.ko 3 1 0xffffffff83225000 b50 smbus.ko 4 1 0xffffffff83226000 18a0 uhid.ko 5 1 0xffffffff83228000 2928 ums.ko 6 1 0xffffffff8322b000 3ae0 ng_ubt.ko 7 5 0xffffffff8322f000 9e30 netgraph.ko 8 1 0xffffffff83239000 91b8 ng_hci.ko 9 3 0xffffffff83243000 9c0 ng_bluetooth.ko 10 1 0xffffffff83244000 6e20 uftdi.ko 11 1 0xffffffff8324b000 44d8 ucom.ko 12 1 0xffffffff83250000 1aa0 wmt.ko 13 1 0xffffffff83252000 cad0 ng_l2cap.ko 14 1 0xffffffff8325f000 1ba00 ng_btsocket.ko 15 1 0xffffffff8327b000 21c0 ng_socket.ko 16 1 0xffffffff8327e000 acf mac_ntpd.ko 17 1 0xffffffff8327f000 1600 imgact_binmisc.ko https://www.gigabyte.com/us/Motherboard/X399-AORUS-Gaming-7-rev-10#support-= dl-bios lists F11 for "Update AGESA 1.1.0.1a" with date 2018/10/12 as the most rece= nt. That is what the system has. I wonder what the bios technical issue would be and what would be good evidence for reporting such a bios defect (presuming that is what the issue is). Note: I'm going to lose access to the system for a few(?) days. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-237063-227-dNG79yfvv4>