#13381: ACPI crash on UEFI Ryzen 7 X370 system
----------------------------+----------------------------
Reporter: kallisti5 | Owner: tqh
Type: bug | Status: new
Priority: normal | Milestone: Unscheduled
Component: Drivers/ACPI | Version: R1/Development
Resolution: | Keywords:
Blocked By: | Blocking:
Has a Patch: 0 | Platform: All
----------------------------+----------------------------
Description changed by kallisti5:
Old description:
I've seen this crash a few times booting from an AMD Ryzen 7 system.
Haiku hrev51008 x86_64
{{{
ACPI: Executed 1 blocks of module-level executable AML code
ACPI: 7 ACPI AML tables successfully acquired and loaded
ACPI Error: Needed [Integer/String/Buffer], found [Region]
0xffffffff82b0d460 (20160729/exresop-514)
ACPI Exception: AE_AML_OPERAND_TYPE, Could not execute arguments for
[IOB2] (Region) (20160729/nsinit-515)
add_memory_type_range(177, 0xfed80000, 0x1000, 0)
add_memory_type_range(178, 0xdb135000, 0x1000, 0)
ACPI: Enabled 4 GPEs in block 00 to 1F
add_memory_type_range(179, 0xce477000, 0x1000, 0)
found io-apic with address 0xfec00000, global interrupt base 0, apic-id
17
mapping io-apic 0 at physical address 0xfec00000
add_memory_type_range(180, 0xfec00000, 0x1000, 0)
io-apic 0 has range 0-23, 24 entries, version 0x00178021, apic-id 17
found io-apic with address 0xfec01000, global interrupt base 24, apic-id
18
mapping io-apic 1 at physical address 0xfec01000
add_memory_type_range(181, 0xfec01000, 0x1000, 0)
io-apic 1 has range 24-55, 32 entries, version 0x001f8021, apic-id 18
setting ACPI interrupt model to APIC
PANIC: unable to find irq routing for PCI 0:0:2
Welcome to Kernel Debugging Land...
Thread 1 "idle thread 1" running on CPU 0
stack trace for thread 1 "idle thread 1"
kernel stack: 0xffffffff8253d000 to 0xffffffff82542000
frame caller <image>:function + offset
0 ffffffff82541a98 (+ 24) ffffffff80147a2c <kernel_x86_64>
arch_debug_call_with_fault_handler() + 0x16
1 ffffffff82541ab0 (+ 80) ffffffff800aa118 <kernel_x86_64>
debug_call_with_fault_handler() + 0x68
1 ffffffff82541ab0 (+ 80) ffffffff800aa118 <kernel_x86_64>
debug_call_with_fault_handler() + 0x68
2 ffffffff82541b00 (+ 80) ffffffff800abbdc <kernel_x86_64>
_ZL20kernel_debugger_loopPKcS0_P13__va_list_tagi() + 0x30c
3 ffffffff82541b50 (+ 80) ffffffff800abcee <kernel_x86_64>
_ZL24kernel_debugger_internalPKcS0_P13__va_list_tagi() + 0x6e
4 ffffffff82541ba0 (+ 240) ffffffff800ac03e <kernel_x86_64> panic() +
0xbe
5 ffffffff82541c90 (+ 192) ffffffff8015c439 <kernel_x86_64>
_ZL28ensure_all_functions_matchedP15pci_module_infohR6VectorI17irq_routing_entryES4_RS1_I11pci_addressE()
+ 0x569
6 ffffffff82541d50 (+ 416) ffffffff8015c62e <kernel_x86_64>
_ZL22read_irq_routing_tableP16acpi_module_infoR6VectorI17irq_routing_entryEPFbiE()
+ 0x1ae
7 ffffffff82541ef0 (+ 48) ffffffff8015d1fb <kernel_x86_64>
_Z19prepare_irq_routingP16acpi_module_infoR6VectorI17irq_routing_entryEPFbiE()
+ 0x1b
8 ffffffff82541f20 (+ 144) ffffffff8015ae18 <kernel_x86_64>
_Z11ioapic_initP11kernel_args() + 0x1d8
9 ffffffff82541fb0 (+ 32) ffffffff80155b09 <kernel_x86_64>
arch_int_init_io() + 0x19
10 ffffffff82541fd0 (+ 32) ffffffff8006111c <kernel_x86_64> _start() +
0x22c
11 ffffffff82541ff0 (+2108416016) 00000000ce4196d8
}}}