https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237063
--- Comment #16 from Mark Millard ---
(In reply to Mark Millard from comment #13)
I did the upgrade sequence for fedora: 27->28->29->30
and they all booted with the F12e BIOS.
Got a dsdt.dat from fedora and can decode it using
FreeBSD's
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237063
--- Comment #15 from Mark Millard ---
Created attachment 205228
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=205228=edit
The acpidump -dt output for the F11e BIOS version
The acpidump -dt output for the F11e BIOS version for
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237063
--- Comment #14 from Mark Millard ---
(In reply to Mark Millard from comment #13)
[FYI: the context is head r347549 based.]
Boot verbose for a debug kernel with BIOS F12e
reported (typed from screen picture):
. . .
crypto: cryptsoft0
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237063
--- Comment #13 from Mark Millard ---
(In reply to Mark Millard from comment #12)
Well, I captured acpidump -dt output and then
updated to firmware F12e. Windows 10 Pro and the
somewhat old Fedora still boot fine. But FreeBSD
hangs,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237063
--- Comment #12 from Mark Millard ---
(In reply to Mark Millard from comment #11)
Access has not yet happened. I'll quit trying to
predict when. But it should eventually happen.
--
You are receiving this mail because:
You are the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237063
--- Comment #11 from Mark Millard ---
(In reply to Mark Millard from comment #10)
My lack of access has been longer than originally
expected. But I hope of have access back within a
few days.
I looked and Gigabyte now has a newer F12e
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237063
--- Comment #10 from Mark Millard ---
(In reply to Konstantin Belousov from comment #9)
It will be a few days before I again have access to the system
that showed the problem. But I can show some previously
reported/recorded material for
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237063
--- Comment #9 from Konstantin Belousov ---
(In reply to Conrad Meyer from comment #3)
It seems that ACPI misses cpu31 _and hostb30, 31. The later is the cause of
the troubles, if I am reading the code right.
Does temp reading work for
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237063
Ed Maste changed:
What|Removed |Added
CC||ema...@freebsd.org
--- Comment #8 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237063
--- Comment #7 from Andriy Gapon ---
(In reply to Mark Millard from comment #6)
Most likely it's ACPI Processor object that's missing (or has some problem).
Yes, acpidump -dt would be helpful.
--
You are receiving this mail because:
You
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237063
--- Comment #6 from Mark Millard ---
(In reply to Mark Millard from comment #5)
While I do not have access to the system currently, looking
around it appears that acpidump output for the MADT may provide
a way to reasonably report a bios
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237063
--- Comment #5 from Mark Millard ---
(In reply to Mark Millard from comment #4)
Looking with ps I do see 31 for the likes of:
[kernel/softirq_31]
[kernel/if_io_tqg_31]
[kernel/crypto_31]
(I also see 0-30 for them.)
With cpu31 missing
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237063
--- Comment #4 from Mark Millard ---
(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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237063
--- Comment #3 from Conrad Meyer ---
(I have this exact CPU and my devinfo topology is the same, except I am not
missing cpu31...)
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237063
--- Comment #1 from Mark Millard ---
Created attachment 203431
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=203431=edit
pciconf -lvcb outout for 1950X context
--
You are receiving this mail because:
You are the assignee for
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237063
Bug ID: 237063
Summary: After "kld amdtemp": devinfo missing cpu31 for Ryzen
Threadripper 1950X context
Product: Base System
Version: CURRENT
Hardware: amd64
16 matches
Mail list logo
