https://bugzilla.kernel.org/show_bug.cgi?id=214259 Bjorn Helgaas (bjorn@xxxxxxxxxxx) changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|DUPLICATE |--- --- Comment #37 from Bjorn Helgaas (bjorn@xxxxxxxxxxx) --- Regarding the delay, i.e., this from Konrad's attachment at comment 27: [ 6.837625] DMAR: DRHD: handling fault status reg 2 [ 6.837629] DMAR: [DMA Write NO_PASID] Request device [07:00.0] fault addr 0x69935000 [fault reason 0x05] PTE Write access is not set [ 26.937996] DMAR: DRHD: handling fault status reg 2 [ 26.944592] DMAR: [DMA Write NO_PASID] Request device [07:00.0] fault addr 0x69935000 [fault reason 0x05] PTE Write access is not set [ 47.417982] DMAR: DRHD: handling fault status reg 2 [ 47.424711] DMAR: [DMA Write NO_PASID] Request device [07:00.0] fault addr 0x69935000 [fault reason 0x05] PTE Write access is not set [ 67.897999] DMAR: DRHD: handling fault status reg 2 [ 67.904639] DMAR: [DMA Write NO_PASID] Request device [07:00.0] fault addr 0x69935000 [fault reason 0x05] PTE Write access is not set [ 88.372827] thunderbolt 0000:07:00.0: failed to send driver ready to ICM [ 88.380241] thunderbolt: probe of 0000:07:00.0 failed with error -110 This all involves the same device (07:00.0) and it's all likely related, so I think we should reserve *this* bug report for this DMAR/timeout issue. As far as I can tell, this is unrelated to bug 206459 and the E820 issues addressed by Hans de Goede's patches, so I'm going to reopen this bug report. If we're lucky, maybe the DMAR/timeout stuff has been fixed by something between v5.15 and v6.0. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
