[Bug 238729] head -r347549 on aorus gaming 7 F12e BIOS (Threadripper 1950X): boot attempts hang (but boots for fedora/Windows 10 Pro)

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238729

            Bug ID: 238729
           Summary: head -r347549 on aorus gaming 7 F12e BIOS
                    (Threadripper 1950X): boot attempts hang (but boots
                    for fedora/Windows 10 Pro)
           Product: Base System
           Version: CURRENT
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: kern
          Assignee: bugs at FreeBSD.org
          Reporter: marklmi26-fbsd at yahoo.com

[This extracts notes from bugzilla 237063 for a different issue with the F11e
BIOS.]

Windows 10 Pro and Fedora 27/28/29/30 still boot fine
with the F12e BIOS update. But FreeBSD hangs, including
the older 12-current copies I still had around, not 
ust the 13-current that I've been using. This might be
some form of "quality of error handling" issue. (The
only reason for the fedora 27/.../30 is that I did the
upgrade sequence under F12e and they all worked.)

I can still boot all the FreeBSD's under Hyper-V
(same media plugged in the same places either way).

Boot verbose for a debug kernel with BIOS F12e
reported (typed from screen picture):

. . .
crypto: cryptsoft0 registers alg ?? flags 0 maxoplen 0
...
acpi0: <AMD> on motherboard
ACPI: 8 ACPI AML tables successfully acquired and loaded
PCIe: Memory mapped configuration base @ 0xf0000000
ioacpi0: routing intpin 9 (ISA IRQ 9) to lapic 0 vector 48
acpi0: Power Button (fixed)
acpi0: wakeup code va 0xfffffe0005dff000 pa 0x98000

And that was all that was output.

With Verbose SYSINIT instead it reported:
(the 3 hpt_init(0)'s are not typos)

. . .
   module_register_init(&nvd_mod)... done.
subsystem 3800000
   hpt_init(0)... done.
   hpt_init(0)... done.
   configure_first(0)... done.
   hpt_init(0)... done.
   module_register_init(&cam_moduledata)... done.
   fbd_evh_init(0)... done.
   module_register_init(&ata_moduledata)... done.
   configure(0)... nexus0
vtvga0: <VT VGA driver> on motherboard
cryptosoft0: <software crypto> on motherboard
acpi0: <AMD> on motherboard
acpi0: Power Button (fixed)

And that was all that was output for this context.
(Mixing in boot verbose scrolls the SYSINIT
information off screen and so does not show anything
new.)

I got a dsdt.dat from fedora and decoded it using
FreeBSD's acpidump -f so I'll upload that. (So less
information than what freebsd would show for
acpiudump -dt .)

-- 
You are receiving this mail because:
You are the assignee for the bug.