[Bug 231760] FreeBSD 12.0-ALPHA7 Installations Halts at ACPI on 4 different AMD Ryzen Laptops (HP, DELL, Huawei)

[bugzilla-noreply at freebsd.org]

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

--- Comment #10 from Rajesh <rajfbsd at gmail.com> ---
(In reply to John Baldwin from comment #9)

Hi John,

Sorry for the delayed response. Please find the backtrace below when the BAR
(0x24) is read

pci_cfgregread: amd64 pci4.0.2 reg 0x24 bytes 0x1
pciereg_cfgread: pci4.0.2 reg 0x24 bytes 0x1
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xffffffff826653f0
pciereg_cfgread() at pciereg_cfgread+0x5e/frame 0xffffffff82665430
AcpiOsReadPciConfiguration() at AcpiOsReadPciConfiguration+0x49/frame
0xffffffff82665460
AcpiEvAddressSpaceDispatch() at AcpiEvAddressSpaceDispatch+0x1f5/frame
0xffffffff826654d0
AcpiExAccessRegion() at AcpiExAccessRegion+0xa3/frame 0xffffffff82665520
AcpiExFieldDatumIo() at AcpiExFieldDatumIo+0xfb/frame 0xffffffff82665560
AcpiExExtractFromField() at AcpiExExtractFromField+0xe0/frame
0xffffffff826655d0
AcpiExReadDataFromField() at AcpiExReadDataFromField+0x125/frame
0xffffffff82665610
AcpiExResolveNodeToValue() at AcpiExResolveNodeToValue+0xe7/frame
0xffffffff82665660
AcpiExResolveToValue() at AcpiExResolveToValue+0x1d1/frame 0xffffffff826656a0
AcpiDsEvaluateNamePath() at AcpiDsEvaluateNamePath+0x78/frame
0xffffffff826656e0
AcpiDsExecEndOp() at AcpiDsExecEndOp+0x99/frame 0xffffffff82665720
AcpiPsParseLoop() at AcpiPsParseLoop+0x732/frame 0xffffffff826657a0
AcpiPsParseAml() at AcpiPsParseAml+0x80/frame 0xffffffff826657e0
AcpiPsExecuteMethod() at AcpiPsExecuteMethod+0x13c/frame 0xffffffff82665820
AcpiNsEvaluate() at AcpiNsEvaluate+0x1e7/frame 0xffffffff82665860
AcpiNsInitOneDevice() at AcpiNsInitOneDevice+0xe7/frame 0xffffffff82665890
AcpiNsWalkNamespace() at AcpiNsWalkNamespace+0xc3/frame 0xffffffff826658f0
AcpiNsInitializeDevices() at AcpiNsInitializeDevices+0x63/frame
0xffffffff82665950
AcpiInitializeObjects() at AcpiInitializeObjects+0x27/frame 0xffffffff82665970
acpi_attach() at acpi_attach+0x3d3/frame 0xffffffff82665a10
device_attach() at device_attach+0x3ec/frame 0xffffffff82665a60
bus_generic_attach() at bus_generic_attach+0x5c/frame 0xffffffff82665a90
device_attach() at device_attach+0x3ec/frame 0xffffffff82665ae0
bus_generic_new_pass() at bus_generic_new_pass+0x118/frame 0xffffffff82665b10
root_bus_configure() at root_bus_configure+0x77/frame 0xffffffff82665b40
configure() at configure+0x9/frame 0xffffffff82665b50
mi_startup() at mi_startup+0x118/frame 0xffffffff82665b70
btext() at btext+0x2c


I am not able to get the acpidump properly. When I run "acpidump -t -d", it
prints certain details in stdout and then hangs. Is there any known behavior
like this with acpidump?

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