Re: Pinebook pro IOMMU enabled crashes

On Sat, 18 Sep 2021 13:15:45 +0200
Jesper Schmitz Mouridsen <[email protected]> wrote:

> Hi
> 
> Perhaps this one 
> https://www.mail-archive.com/[email protected]/msg126068.html is 
> giving troubles?
> 
> main-n249225-f673cc5edac3-dirty
> nvme0: <Generic NVMe Device> at device 0.0 on pci1
> Fatal data abort:
>    x0:                0
>    x1:             1000
>    x2:            10040
>    x3:             2000
>    x4:                1
>    x5: ffff00009a7a0168
>    x6: 1d00000000000000
>    x7:   10000000000000
>    x8:             1168
>    x9:                1
>   x10:                0
>   x11: ffff000000f35140
>   x12: ffff000000f350c0
>   x13:                1
>   x14:            10000
>   x15:                1
>   x16:            10000
>   x17: ffff000000f350dc
>   x18: ffff00000110d180
>   x19: ffff00000110d248
>   x20:                0
>   x21: ffff00009a79f000
>   x22: ffffa000010b0a00
>   x23: ffffa000010a2880
>   x24: ffffa0000116da00
>   x25: ffff000000b4fd78
>   x26: ffffa0000116db00
>   x27: ffff000000e83000
>   x28:                7
>   x29: ffff00000110d190
>    sp: ffff00000110d180
>    lr: ffff00000077520c
>   elr: ffff0000007a03ac
> spsr:         200000c5
>   far:                0
>   esr:         96000004
> panic: vm_fault failed: ffff0000007a03ac error 1
> cpuid = 0
> time = 1
> KDB: stack backtrace:
> db_trace_self() at db_trace_self
> db_trace_self_wrapper() at db_trace_self_wrapper+0x30
> vpanic() at vpanic+0x184
> panic() at panic+0x44
> data_abort() at data_abort+0x23c
> handle_el1h_sync() at handle_el1h_sync+0x78
> --- exception, esr 0x96000004
> iommu_map_msi() at iommu_map_msi+0x20
> gicv3_iommu_init() at gicv3_iommu_init+0x4c
> intr_alloc_msix() at intr_alloc_msix+0x13c
> rk_pcie_alloc_msix() at rk_pcie_alloc_msix+0xfc
> pci_alloc_msix_method() at pci_alloc_msix_method+0x1a8
> nvme_pci_attach() at nvme_pci_attach+0x378
> device_attach() at device_attach+0x400
> device_probe_and_attach() at device_probe_and_attach+0x7c
> bus_generic_attach() at bus_generic_attach+0x18
> pci_attach() at pci_attach+0xe8
> device_attach() at device_attach+0x400
> device_probe_and_attach() at device_probe_and_attach+0x7c
> bus_generic_attach() at bus_generic_attach+0x18
> device_attach() at device_attach+0x400
> device_probe_and_attach() at device_probe_and_attach+0x7c
> bus_generic_attach() at bus_generic_attach+0x18
> pci_attach() at pci_attach+0xe8
> device_attach() at device_attach+0x400
> device_probe_and_attach() at device_probe_and_attach+0x7c
> bus_generic_attach() at bus_generic_attach+0x18
> rk_pcie_attach() at rk_pcie_attach+0x14cc
> device_attach() at device_attach+0x400
> device_probe_and_attach() at device_probe_and_attach+0x7c
> bus_generic_new_pass() at bus_generic_new_pass+0xf8
> bus_generic_new_pass() at bus_generic_new_pass+0xa8
> bus_generic_new_pass() at bus_generic_new_pass+0xa8
> bus_set_pass() at bus_set_pass+0x4c
> mi_startup() at mi_startup+0x12c
> virtdone() at virtdone+0x6c
> 

 That's an old commit. Did you see this panic only recently or ?

-- 
Emmanuel Vadot <[email protected]> <[email protected]>