* I got an IOMMU IO page fault. What to do now?
@ 2021-10-25 10:25 ` Paul Menzel
0 siblings, 0 replies; 18+ messages in thread
From: Paul Menzel @ 2021-10-25 10:25 UTC (permalink / raw)
To: Jörg Rödel, Suravee Suthikulpanit
Cc: iommu, Alex Deucher, Christian König, Xinhui Pan, amd-gfx,
Thomas Gleixner, Ingo Molnar, Borislav Petkov, x86, LKML,
it+linux-iommu
Dear Linux folks,
On a Dell OptiPlex 5055, Linux 5.10.24 logged the IOMMU messages below.
(GPU hang in amdgpu issue #1762 [1] might be related.)
$ lspci -nn -s 05:00.0
05:00.0 VGA compatible controller [0300]: Advanced Micro Devices,
Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 OEM] [1002:6611] (rev 87)
$ dmesg
[…]
[6318399.745242] amdgpu 0000:05:00.0: AMD-Vi: Event logged
[IO_PAGE_FAULT domain=0x000c address=0xfffffff0c0 flags=0x0020]
[6318399.757283] amdgpu 0000:05:00.0: AMD-Vi: Event logged
[IO_PAGE_FAULT domain=0x000c address=0xfffffff7c0 flags=0x0020]
[6318399.769154] amdgpu 0000:05:00.0: AMD-Vi: Event logged
[IO_PAGE_FAULT domain=0x000c address=0xffffffe0c0 flags=0x0020]
[6318399.780913] amdgpu 0000:05:00.0: AMD-Vi: Event logged
[IO_PAGE_FAULT domain=0x000c address=0xfffffffec0 flags=0x0020]
[6318399.792734] amdgpu 0000:05:00.0: AMD-Vi: Event logged
[IO_PAGE_FAULT domain=0x000c address=0xffffffe5c0 flags=0x0020]
[6318399.804309] amdgpu 0000:05:00.0: AMD-Vi: Event logged
[IO_PAGE_FAULT domain=0x000c address=0xffffffd0c0 flags=0x0020]
[6318399.816091] amdgpu 0000:05:00.0: AMD-Vi: Event logged
[IO_PAGE_FAULT domain=0x000c address=0xffffffecc0 flags=0x0020]
[6318399.827407] amdgpu 0000:05:00.0: AMD-Vi: Event logged
[IO_PAGE_FAULT domain=0x000c address=0xffffffd3c0 flags=0x0020]
[6318399.838708] amdgpu 0000:05:00.0: AMD-Vi: Event logged
[IO_PAGE_FAULT domain=0x000c address=0xffffffc0c0 flags=0x0020]
[6318399.850029] amdgpu 0000:05:00.0: AMD-Vi: Event logged
[IO_PAGE_FAULT domain=0x000c address=0xffffffdac0 flags=0x0020]
[6318399.861311] AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0
domain=0x000c address=0xffffffc1c0 flags=0x0020]
[6318399.872044] AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0
domain=0x000c address=0xffffffc8c0 flags=0x0020]
[6318399.882797] AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0
domain=0x000c address=0xffffffb0c0 flags=0x0020]
[6318399.893655] AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0
domain=0x000c address=0xffffffcfc0 flags=0x0020]
[6318399.904445] AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0
domain=0x000c address=0xffffffb6c0 flags=0x0020]
[6318399.915222] AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0
domain=0x000c address=0xffffffa0c0 flags=0x0020]
[6318399.925931] AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0
domain=0x000c address=0xffffffbdc0 flags=0x0020]
[6318399.936691] AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0
domain=0x000c address=0xffffffa4c0 flags=0x0020]
[6318399.947479] AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0
domain=0x000c address=0xffffff90c0 flags=0x0020]
[6318399.958270] AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0
domain=0x000c address=0xffffffabc0 flags=0x0020]
As this is not reproducible, how would debugging go? (The system was
rebooted in the meantime.) What options should be enabled, that next
time the required information is logged, or what commands should I
execute when the system is still in that state, so the bug (driver,
userspace, …) can be pinpointed and fixed?
Kind regards,
Paul
[1]: https://gitlab.freedesktop.org/drm/amd/-/issues/1762
"Oland [Radeon HD 8570 / R7 240/340 OEM]: GPU hang"
^ permalink raw reply [flat|nested] 18+ messages in thread* I got an IOMMU IO page fault. What to do now? @ 2021-10-25 10:25 ` Paul Menzel 0 siblings, 0 replies; 18+ messages in thread From: Paul Menzel @ 2021-10-25 10:25 UTC (permalink / raw) To: Jörg Rödel, Suravee Suthikulpanit Cc: x86, Xinhui Pan, LKML, amd-gfx, iommu, Ingo Molnar, Borislav Petkov, Alex Deucher, it+linux-iommu, Thomas Gleixner, Christian König Dear Linux folks, On a Dell OptiPlex 5055, Linux 5.10.24 logged the IOMMU messages below. (GPU hang in amdgpu issue #1762 [1] might be related.) $ lspci -nn -s 05:00.0 05:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 OEM] [1002:6611] (rev 87) $ dmesg […] [6318399.745242] amdgpu 0000:05:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000c address=0xfffffff0c0 flags=0x0020] [6318399.757283] amdgpu 0000:05:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000c address=0xfffffff7c0 flags=0x0020] [6318399.769154] amdgpu 0000:05:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000c address=0xffffffe0c0 flags=0x0020] [6318399.780913] amdgpu 0000:05:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000c address=0xfffffffec0 flags=0x0020] [6318399.792734] amdgpu 0000:05:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000c address=0xffffffe5c0 flags=0x0020] [6318399.804309] amdgpu 0000:05:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000c address=0xffffffd0c0 flags=0x0020] [6318399.816091] amdgpu 0000:05:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000c address=0xffffffecc0 flags=0x0020] [6318399.827407] amdgpu 0000:05:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000c address=0xffffffd3c0 flags=0x0020] [6318399.838708] amdgpu 0000:05:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000c address=0xffffffc0c0 flags=0x0020] [6318399.850029] amdgpu 0000:05:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000c address=0xffffffdac0 flags=0x0020] [6318399.861311] AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x000c address=0xffffffc1c0 flags=0x0020] [6318399.872044] AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x000c address=0xffffffc8c0 flags=0x0020] [6318399.882797] AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x000c address=0xffffffb0c0 flags=0x0020] [6318399.893655] AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x000c address=0xffffffcfc0 flags=0x0020] [6318399.904445] AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x000c address=0xffffffb6c0 flags=0x0020] [6318399.915222] AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x000c address=0xffffffa0c0 flags=0x0020] [6318399.925931] AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x000c address=0xffffffbdc0 flags=0x0020] [6318399.936691] AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x000c address=0xffffffa4c0 flags=0x0020] [6318399.947479] AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x000c address=0xffffff90c0 flags=0x0020] [6318399.958270] AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x000c address=0xffffffabc0 flags=0x0020] As this is not reproducible, how would debugging go? (The system was rebooted in the meantime.) What options should be enabled, that next time the required information is logged, or what commands should I execute when the system is still in that state, so the bug (driver, userspace, …) can be pinpointed and fixed? Kind regards, Paul [1]: https://gitlab.freedesktop.org/drm/amd/-/issues/1762 "Oland [Radeon HD 8570 / R7 240/340 OEM]: GPU hang" _______________________________________________ iommu mailing list iommu@lists.linux-foundation.org https://lists.linuxfoundation.org/mailman/listinfo/iommu ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: I got an IOMMU IO page fault. What to do now? 2021-10-25 10:25 ` Paul Menzel @ 2021-10-25 11:23 ` Christian König -1 siblings, 0 replies; 18+ messages in thread From: Christian König @ 2021-10-25 11:23 UTC (permalink / raw) To: Paul Menzel, Jörg Rödel, Suravee Suthikulpanit Cc: iommu, Alex Deucher, Christian König, Xinhui Pan, amd-gfx, Thomas Gleixner, Ingo Molnar, Borislav Petkov, x86, LKML, it+linux-iommu Hi Paul, not sure how the IOMMU gives out addresses, but the printed ones look suspicious to me. Something like we are using an invalid address like -1 or similar. Can you try that on an up to date kernel as well? E.g. ideally bleeding edge amd-staging-drm-next from Alex repository. Regards, Christian. Am 25.10.21 um 12:25 schrieb Paul Menzel: > Dear Linux folks, > > > On a Dell OptiPlex 5055, Linux 5.10.24 logged the IOMMU messages > below. (GPU hang in amdgpu issue #1762 [1] might be related.) > > $ lspci -nn -s 05:00.0 > 05:00.0 VGA compatible controller [0300]: Advanced Micro Devices, > Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 OEM] [1002:6611] > (rev 87) > $ dmesg > […] > [6318399.745242] amdgpu 0000:05:00.0: AMD-Vi: Event logged > [IO_PAGE_FAULT domain=0x000c address=0xfffffff0c0 flags=0x0020] > [6318399.757283] amdgpu 0000:05:00.0: AMD-Vi: Event logged > [IO_PAGE_FAULT domain=0x000c address=0xfffffff7c0 flags=0x0020] > [6318399.769154] amdgpu 0000:05:00.0: AMD-Vi: Event logged > [IO_PAGE_FAULT domain=0x000c address=0xffffffe0c0 flags=0x0020] > [6318399.780913] amdgpu 0000:05:00.0: AMD-Vi: Event logged > [IO_PAGE_FAULT domain=0x000c address=0xfffffffec0 flags=0x0020] > [6318399.792734] amdgpu 0000:05:00.0: AMD-Vi: Event logged > [IO_PAGE_FAULT domain=0x000c address=0xffffffe5c0 flags=0x0020] > [6318399.804309] amdgpu 0000:05:00.0: AMD-Vi: Event logged > [IO_PAGE_FAULT domain=0x000c address=0xffffffd0c0 flags=0x0020] > [6318399.816091] amdgpu 0000:05:00.0: AMD-Vi: Event logged > [IO_PAGE_FAULT domain=0x000c address=0xffffffecc0 flags=0x0020] > [6318399.827407] amdgpu 0000:05:00.0: AMD-Vi: Event logged > [IO_PAGE_FAULT domain=0x000c address=0xffffffd3c0 flags=0x0020] > [6318399.838708] amdgpu 0000:05:00.0: AMD-Vi: Event logged > [IO_PAGE_FAULT domain=0x000c address=0xffffffc0c0 flags=0x0020] > [6318399.850029] amdgpu 0000:05:00.0: AMD-Vi: Event logged > [IO_PAGE_FAULT domain=0x000c address=0xffffffdac0 flags=0x0020] > [6318399.861311] AMD-Vi: Event logged [IO_PAGE_FAULT > device=05:00.0 domain=0x000c address=0xffffffc1c0 flags=0x0020] > [6318399.872044] AMD-Vi: Event logged [IO_PAGE_FAULT > device=05:00.0 domain=0x000c address=0xffffffc8c0 flags=0x0020] > [6318399.882797] AMD-Vi: Event logged [IO_PAGE_FAULT > device=05:00.0 domain=0x000c address=0xffffffb0c0 flags=0x0020] > [6318399.893655] AMD-Vi: Event logged [IO_PAGE_FAULT > device=05:00.0 domain=0x000c address=0xffffffcfc0 flags=0x0020] > [6318399.904445] AMD-Vi: Event logged [IO_PAGE_FAULT > device=05:00.0 domain=0x000c address=0xffffffb6c0 flags=0x0020] > [6318399.915222] AMD-Vi: Event logged [IO_PAGE_FAULT > device=05:00.0 domain=0x000c address=0xffffffa0c0 flags=0x0020] > [6318399.925931] AMD-Vi: Event logged [IO_PAGE_FAULT > device=05:00.0 domain=0x000c address=0xffffffbdc0 flags=0x0020] > [6318399.936691] AMD-Vi: Event logged [IO_PAGE_FAULT > device=05:00.0 domain=0x000c address=0xffffffa4c0 flags=0x0020] > [6318399.947479] AMD-Vi: Event logged [IO_PAGE_FAULT > device=05:00.0 domain=0x000c address=0xffffff90c0 flags=0x0020] > [6318399.958270] AMD-Vi: Event logged [IO_PAGE_FAULT > device=05:00.0 domain=0x000c address=0xffffffabc0 flags=0x0020] > > As this is not reproducible, how would debugging go? (The system was > rebooted in the meantime.) What options should be enabled, that next > time the required information is logged, or what commands should I > execute when the system is still in that state, so the bug (driver, > userspace, …) can be pinpointed and fixed? > > > Kind regards, > > Paul > > > [1]: https://gitlab.freedesktop.org/drm/amd/-/issues/1762 > "Oland [Radeon HD 8570 / R7 240/340 OEM]: GPU hang" ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: I got an IOMMU IO page fault. What to do now? @ 2021-10-25 11:23 ` Christian König 0 siblings, 0 replies; 18+ messages in thread From: Christian König @ 2021-10-25 11:23 UTC (permalink / raw) To: Paul Menzel, Jörg Rödel, Suravee Suthikulpanit Cc: x86, Xinhui Pan, LKML, amd-gfx, iommu, Ingo Molnar, Borislav Petkov, Alex Deucher, it+linux-iommu, Thomas Gleixner, Christian König Hi Paul, not sure how the IOMMU gives out addresses, but the printed ones look suspicious to me. Something like we are using an invalid address like -1 or similar. Can you try that on an up to date kernel as well? E.g. ideally bleeding edge amd-staging-drm-next from Alex repository. Regards, Christian. Am 25.10.21 um 12:25 schrieb Paul Menzel: > Dear Linux folks, > > > On a Dell OptiPlex 5055, Linux 5.10.24 logged the IOMMU messages > below. (GPU hang in amdgpu issue #1762 [1] might be related.) > > $ lspci -nn -s 05:00.0 > 05:00.0 VGA compatible controller [0300]: Advanced Micro Devices, > Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 OEM] [1002:6611] > (rev 87) > $ dmesg > […] > [6318399.745242] amdgpu 0000:05:00.0: AMD-Vi: Event logged > [IO_PAGE_FAULT domain=0x000c address=0xfffffff0c0 flags=0x0020] > [6318399.757283] amdgpu 0000:05:00.0: AMD-Vi: Event logged > [IO_PAGE_FAULT domain=0x000c address=0xfffffff7c0 flags=0x0020] > [6318399.769154] amdgpu 0000:05:00.0: AMD-Vi: Event logged > [IO_PAGE_FAULT domain=0x000c address=0xffffffe0c0 flags=0x0020] > [6318399.780913] amdgpu 0000:05:00.0: AMD-Vi: Event logged > [IO_PAGE_FAULT domain=0x000c address=0xfffffffec0 flags=0x0020] > [6318399.792734] amdgpu 0000:05:00.0: AMD-Vi: Event logged > [IO_PAGE_FAULT domain=0x000c address=0xffffffe5c0 flags=0x0020] > [6318399.804309] amdgpu 0000:05:00.0: AMD-Vi: Event logged > [IO_PAGE_FAULT domain=0x000c address=0xffffffd0c0 flags=0x0020] > [6318399.816091] amdgpu 0000:05:00.0: AMD-Vi: Event logged > [IO_PAGE_FAULT domain=0x000c address=0xffffffecc0 flags=0x0020] > [6318399.827407] amdgpu 0000:05:00.0: AMD-Vi: Event logged > [IO_PAGE_FAULT domain=0x000c address=0xffffffd3c0 flags=0x0020] > [6318399.838708] amdgpu 0000:05:00.0: AMD-Vi: Event logged > [IO_PAGE_FAULT domain=0x000c address=0xffffffc0c0 flags=0x0020] > [6318399.850029] amdgpu 0000:05:00.0: AMD-Vi: Event logged > [IO_PAGE_FAULT domain=0x000c address=0xffffffdac0 flags=0x0020] > [6318399.861311] AMD-Vi: Event logged [IO_PAGE_FAULT > device=05:00.0 domain=0x000c address=0xffffffc1c0 flags=0x0020] > [6318399.872044] AMD-Vi: Event logged [IO_PAGE_FAULT > device=05:00.0 domain=0x000c address=0xffffffc8c0 flags=0x0020] > [6318399.882797] AMD-Vi: Event logged [IO_PAGE_FAULT > device=05:00.0 domain=0x000c address=0xffffffb0c0 flags=0x0020] > [6318399.893655] AMD-Vi: Event logged [IO_PAGE_FAULT > device=05:00.0 domain=0x000c address=0xffffffcfc0 flags=0x0020] > [6318399.904445] AMD-Vi: Event logged [IO_PAGE_FAULT > device=05:00.0 domain=0x000c address=0xffffffb6c0 flags=0x0020] > [6318399.915222] AMD-Vi: Event logged [IO_PAGE_FAULT > device=05:00.0 domain=0x000c address=0xffffffa0c0 flags=0x0020] > [6318399.925931] AMD-Vi: Event logged [IO_PAGE_FAULT > device=05:00.0 domain=0x000c address=0xffffffbdc0 flags=0x0020] > [6318399.936691] AMD-Vi: Event logged [IO_PAGE_FAULT > device=05:00.0 domain=0x000c address=0xffffffa4c0 flags=0x0020] > [6318399.947479] AMD-Vi: Event logged [IO_PAGE_FAULT > device=05:00.0 domain=0x000c address=0xffffff90c0 flags=0x0020] > [6318399.958270] AMD-Vi: Event logged [IO_PAGE_FAULT > device=05:00.0 domain=0x000c address=0xffffffabc0 flags=0x0020] > > As this is not reproducible, how would debugging go? (The system was > rebooted in the meantime.) What options should be enabled, that next > time the required information is logged, or what commands should I > execute when the system is still in that state, so the bug (driver, > userspace, …) can be pinpointed and fixed? > > > Kind regards, > > Paul > > > [1]: https://gitlab.freedesktop.org/drm/amd/-/issues/1762 > "Oland [Radeon HD 8570 / R7 240/340 OEM]: GPU hang" _______________________________________________ iommu mailing list iommu@lists.linux-foundation.org https://lists.linuxfoundation.org/mailman/listinfo/iommu ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: I got an IOMMU IO page fault. What to do now? 2021-10-25 11:23 ` Christian König @ 2021-10-25 11:38 ` Paul Menzel -1 siblings, 0 replies; 18+ messages in thread From: Paul Menzel @ 2021-10-25 11:38 UTC (permalink / raw) To: Christian König, Jörg Rödel, Suravee Suthikulpanit Cc: iommu, Alex Deucher, Christian König, Xinhui Pan, amd-gfx, Thomas Gleixner, Ingo Molnar, Borislav Petkov, x86, LKML, it+linux-iommu Dear Christian, Thank you for your reply. On 25.10.21 13:23, Christian König wrote: > not sure how the IOMMU gives out addresses, but the printed ones look > suspicious to me. Something like we are using an invalid address like -1 > or similar. > > Can you try that on an up to date kernel as well? E.g. ideally bleeding > edge amd-staging-drm-next from Alex repository. These are production desktops, so I’d need to talk to the user. Currently, Linux 5.10.70 is running. Kind regards, Paul ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: I got an IOMMU IO page fault. What to do now? @ 2021-10-25 11:38 ` Paul Menzel 0 siblings, 0 replies; 18+ messages in thread From: Paul Menzel @ 2021-10-25 11:38 UTC (permalink / raw) To: Christian König, Jörg Rödel, Suravee Suthikulpanit Cc: x86, Xinhui Pan, LKML, amd-gfx, iommu, Ingo Molnar, Borislav Petkov, Alex Deucher, it+linux-iommu, Thomas Gleixner, Christian König Dear Christian, Thank you for your reply. On 25.10.21 13:23, Christian König wrote: > not sure how the IOMMU gives out addresses, but the printed ones look > suspicious to me. Something like we are using an invalid address like -1 > or similar. > > Can you try that on an up to date kernel as well? E.g. ideally bleeding > edge amd-staging-drm-next from Alex repository. These are production desktops, so I’d need to talk to the user. Currently, Linux 5.10.70 is running. Kind regards, Paul _______________________________________________ iommu mailing list iommu@lists.linux-foundation.org https://lists.linuxfoundation.org/mailman/listinfo/iommu ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: I got an IOMMU IO page fault. What to do now? 2021-10-25 11:23 ` Christian König @ 2021-10-25 16:01 ` Robin Murphy -1 siblings, 0 replies; 18+ messages in thread From: Robin Murphy @ 2021-10-25 16:01 UTC (permalink / raw) To: Christian König, Paul Menzel, Jörg Rödel, Suravee Suthikulpanit Cc: x86, Xinhui Pan, LKML, amd-gfx, iommu, Ingo Molnar, Borislav Petkov, Alex Deucher, it+linux-iommu, Thomas Gleixner, Christian König On 2021-10-25 12:23, Christian König wrote: > Hi Paul, > > not sure how the IOMMU gives out addresses, but the printed ones look > suspicious to me. Something like we are using an invalid address like -1 > or similar. FWIW those look like believable DMA addresses to me, assuming that the DMA mapping APIs are being backed iommu_dma_ops and the device has a 40-bit DMA mask, since the IOVA allocator works top-down. Likely causes are either a race where the dma_unmap_*() call happens before the hardware has really stopped accessing the relevant addresses, or the device's DMA mask has been set larger than it should be, and thus the upper bits have been truncated in the round-trip through the hardware. Given the addresses involved, my suspicions would initially lean towards the latter case - the faults are in the very topmost pages which imply they're the first things mapped in that range. The other contributing factor being the trick that the IOVA allocator plays for PCI devices, where it tries to prefer 32-bit addresses. Thus you're only likely to see this happen once you already have ~3.5-4GB of live DMA-mapped memory to exhaust the 32-bit IOVA space (minus some reserved areas) and start allocating from the full DMA mask. You should be able to check that with a 5.13 or newer kernel by booting with "iommu.forcedac=1" and seeing if it breaks immediately (unfortunately with an older kernel you'd have to manually hack iommu_dma_alloc_iova() to the same effect). Robin. > Can you try that on an up to date kernel as well? E.g. ideally bleeding > edge amd-staging-drm-next from Alex repository. > > Regards, > Christian. > > Am 25.10.21 um 12:25 schrieb Paul Menzel: >> Dear Linux folks, >> >> >> On a Dell OptiPlex 5055, Linux 5.10.24 logged the IOMMU messages >> below. (GPU hang in amdgpu issue #1762 [1] might be related.) >> >> $ lspci -nn -s 05:00.0 >> 05:00.0 VGA compatible controller [0300]: Advanced Micro Devices, >> Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 OEM] [1002:6611] >> (rev 87) >> $ dmesg >> […] >> [6318399.745242] amdgpu 0000:05:00.0: AMD-Vi: Event logged >> [IO_PAGE_FAULT domain=0x000c address=0xfffffff0c0 flags=0x0020] >> [6318399.757283] amdgpu 0000:05:00.0: AMD-Vi: Event logged >> [IO_PAGE_FAULT domain=0x000c address=0xfffffff7c0 flags=0x0020] >> [6318399.769154] amdgpu 0000:05:00.0: AMD-Vi: Event logged >> [IO_PAGE_FAULT domain=0x000c address=0xffffffe0c0 flags=0x0020] >> [6318399.780913] amdgpu 0000:05:00.0: AMD-Vi: Event logged >> [IO_PAGE_FAULT domain=0x000c address=0xfffffffec0 flags=0x0020] >> [6318399.792734] amdgpu 0000:05:00.0: AMD-Vi: Event logged >> [IO_PAGE_FAULT domain=0x000c address=0xffffffe5c0 flags=0x0020] >> [6318399.804309] amdgpu 0000:05:00.0: AMD-Vi: Event logged >> [IO_PAGE_FAULT domain=0x000c address=0xffffffd0c0 flags=0x0020] >> [6318399.816091] amdgpu 0000:05:00.0: AMD-Vi: Event logged >> [IO_PAGE_FAULT domain=0x000c address=0xffffffecc0 flags=0x0020] >> [6318399.827407] amdgpu 0000:05:00.0: AMD-Vi: Event logged >> [IO_PAGE_FAULT domain=0x000c address=0xffffffd3c0 flags=0x0020] >> [6318399.838708] amdgpu 0000:05:00.0: AMD-Vi: Event logged >> [IO_PAGE_FAULT domain=0x000c address=0xffffffc0c0 flags=0x0020] >> [6318399.850029] amdgpu 0000:05:00.0: AMD-Vi: Event logged >> [IO_PAGE_FAULT domain=0x000c address=0xffffffdac0 flags=0x0020] >> [6318399.861311] AMD-Vi: Event logged [IO_PAGE_FAULT >> device=05:00.0 domain=0x000c address=0xffffffc1c0 flags=0x0020] >> [6318399.872044] AMD-Vi: Event logged [IO_PAGE_FAULT >> device=05:00.0 domain=0x000c address=0xffffffc8c0 flags=0x0020] >> [6318399.882797] AMD-Vi: Event logged [IO_PAGE_FAULT >> device=05:00.0 domain=0x000c address=0xffffffb0c0 flags=0x0020] >> [6318399.893655] AMD-Vi: Event logged [IO_PAGE_FAULT >> device=05:00.0 domain=0x000c address=0xffffffcfc0 flags=0x0020] >> [6318399.904445] AMD-Vi: Event logged [IO_PAGE_FAULT >> device=05:00.0 domain=0x000c address=0xffffffb6c0 flags=0x0020] >> [6318399.915222] AMD-Vi: Event logged [IO_PAGE_FAULT >> device=05:00.0 domain=0x000c address=0xffffffa0c0 flags=0x0020] >> [6318399.925931] AMD-Vi: Event logged [IO_PAGE_FAULT >> device=05:00.0 domain=0x000c address=0xffffffbdc0 flags=0x0020] >> [6318399.936691] AMD-Vi: Event logged [IO_PAGE_FAULT >> device=05:00.0 domain=0x000c address=0xffffffa4c0 flags=0x0020] >> [6318399.947479] AMD-Vi: Event logged [IO_PAGE_FAULT >> device=05:00.0 domain=0x000c address=0xffffff90c0 flags=0x0020] >> [6318399.958270] AMD-Vi: Event logged [IO_PAGE_FAULT >> device=05:00.0 domain=0x000c address=0xffffffabc0 flags=0x0020] >> >> As this is not reproducible, how would debugging go? (The system was >> rebooted in the meantime.) What options should be enabled, that next >> time the required information is logged, or what commands should I >> execute when the system is still in that state, so the bug (driver, >> userspace, …) can be pinpointed and fixed? >> >> >> Kind regards, >> >> Paul >> >> >> [1]: https://gitlab.freedesktop.org/drm/amd/-/issues/1762 >> "Oland [Radeon HD 8570 / R7 240/340 OEM]: GPU hang" > > _______________________________________________ > iommu mailing list > iommu@lists.linux-foundation.org > https://lists.linuxfoundation.org/mailman/listinfo/iommu ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: I got an IOMMU IO page fault. What to do now? @ 2021-10-25 16:01 ` Robin Murphy 0 siblings, 0 replies; 18+ messages in thread From: Robin Murphy @ 2021-10-25 16:01 UTC (permalink / raw) To: Christian König, Paul Menzel, Jörg Rödel, Suravee Suthikulpanit Cc: x86, Xinhui Pan, LKML, amd-gfx, iommu, Ingo Molnar, Borislav Petkov, Alex Deucher, it+linux-iommu, Thomas Gleixner, Christian König On 2021-10-25 12:23, Christian König wrote: > Hi Paul, > > not sure how the IOMMU gives out addresses, but the printed ones look > suspicious to me. Something like we are using an invalid address like -1 > or similar. FWIW those look like believable DMA addresses to me, assuming that the DMA mapping APIs are being backed iommu_dma_ops and the device has a 40-bit DMA mask, since the IOVA allocator works top-down. Likely causes are either a race where the dma_unmap_*() call happens before the hardware has really stopped accessing the relevant addresses, or the device's DMA mask has been set larger than it should be, and thus the upper bits have been truncated in the round-trip through the hardware. Given the addresses involved, my suspicions would initially lean towards the latter case - the faults are in the very topmost pages which imply they're the first things mapped in that range. The other contributing factor being the trick that the IOVA allocator plays for PCI devices, where it tries to prefer 32-bit addresses. Thus you're only likely to see this happen once you already have ~3.5-4GB of live DMA-mapped memory to exhaust the 32-bit IOVA space (minus some reserved areas) and start allocating from the full DMA mask. You should be able to check that with a 5.13 or newer kernel by booting with "iommu.forcedac=1" and seeing if it breaks immediately (unfortunately with an older kernel you'd have to manually hack iommu_dma_alloc_iova() to the same effect). Robin. > Can you try that on an up to date kernel as well? E.g. ideally bleeding > edge amd-staging-drm-next from Alex repository. > > Regards, > Christian. > > Am 25.10.21 um 12:25 schrieb Paul Menzel: >> Dear Linux folks, >> >> >> On a Dell OptiPlex 5055, Linux 5.10.24 logged the IOMMU messages >> below. (GPU hang in amdgpu issue #1762 [1] might be related.) >> >> $ lspci -nn -s 05:00.0 >> 05:00.0 VGA compatible controller [0300]: Advanced Micro Devices, >> Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 OEM] [1002:6611] >> (rev 87) >> $ dmesg >> […] >> [6318399.745242] amdgpu 0000:05:00.0: AMD-Vi: Event logged >> [IO_PAGE_FAULT domain=0x000c address=0xfffffff0c0 flags=0x0020] >> [6318399.757283] amdgpu 0000:05:00.0: AMD-Vi: Event logged >> [IO_PAGE_FAULT domain=0x000c address=0xfffffff7c0 flags=0x0020] >> [6318399.769154] amdgpu 0000:05:00.0: AMD-Vi: Event logged >> [IO_PAGE_FAULT domain=0x000c address=0xffffffe0c0 flags=0x0020] >> [6318399.780913] amdgpu 0000:05:00.0: AMD-Vi: Event logged >> [IO_PAGE_FAULT domain=0x000c address=0xfffffffec0 flags=0x0020] >> [6318399.792734] amdgpu 0000:05:00.0: AMD-Vi: Event logged >> [IO_PAGE_FAULT domain=0x000c address=0xffffffe5c0 flags=0x0020] >> [6318399.804309] amdgpu 0000:05:00.0: AMD-Vi: Event logged >> [IO_PAGE_FAULT domain=0x000c address=0xffffffd0c0 flags=0x0020] >> [6318399.816091] amdgpu 0000:05:00.0: AMD-Vi: Event logged >> [IO_PAGE_FAULT domain=0x000c address=0xffffffecc0 flags=0x0020] >> [6318399.827407] amdgpu 0000:05:00.0: AMD-Vi: Event logged >> [IO_PAGE_FAULT domain=0x000c address=0xffffffd3c0 flags=0x0020] >> [6318399.838708] amdgpu 0000:05:00.0: AMD-Vi: Event logged >> [IO_PAGE_FAULT domain=0x000c address=0xffffffc0c0 flags=0x0020] >> [6318399.850029] amdgpu 0000:05:00.0: AMD-Vi: Event logged >> [IO_PAGE_FAULT domain=0x000c address=0xffffffdac0 flags=0x0020] >> [6318399.861311] AMD-Vi: Event logged [IO_PAGE_FAULT >> device=05:00.0 domain=0x000c address=0xffffffc1c0 flags=0x0020] >> [6318399.872044] AMD-Vi: Event logged [IO_PAGE_FAULT >> device=05:00.0 domain=0x000c address=0xffffffc8c0 flags=0x0020] >> [6318399.882797] AMD-Vi: Event logged [IO_PAGE_FAULT >> device=05:00.0 domain=0x000c address=0xffffffb0c0 flags=0x0020] >> [6318399.893655] AMD-Vi: Event logged [IO_PAGE_FAULT >> device=05:00.0 domain=0x000c address=0xffffffcfc0 flags=0x0020] >> [6318399.904445] AMD-Vi: Event logged [IO_PAGE_FAULT >> device=05:00.0 domain=0x000c address=0xffffffb6c0 flags=0x0020] >> [6318399.915222] AMD-Vi: Event logged [IO_PAGE_FAULT >> device=05:00.0 domain=0x000c address=0xffffffa0c0 flags=0x0020] >> [6318399.925931] AMD-Vi: Event logged [IO_PAGE_FAULT >> device=05:00.0 domain=0x000c address=0xffffffbdc0 flags=0x0020] >> [6318399.936691] AMD-Vi: Event logged [IO_PAGE_FAULT >> device=05:00.0 domain=0x000c address=0xffffffa4c0 flags=0x0020] >> [6318399.947479] AMD-Vi: Event logged [IO_PAGE_FAULT >> device=05:00.0 domain=0x000c address=0xffffff90c0 flags=0x0020] >> [6318399.958270] AMD-Vi: Event logged [IO_PAGE_FAULT >> device=05:00.0 domain=0x000c address=0xffffffabc0 flags=0x0020] >> >> As this is not reproducible, how would debugging go? (The system was >> rebooted in the meantime.) What options should be enabled, that next >> time the required information is logged, or what commands should I >> execute when the system is still in that state, so the bug (driver, >> userspace, …) can be pinpointed and fixed? >> >> >> Kind regards, >> >> Paul >> >> >> [1]: https://gitlab.freedesktop.org/drm/amd/-/issues/1762 >> "Oland [Radeon HD 8570 / R7 240/340 OEM]: GPU hang" > > _______________________________________________ > iommu mailing list > iommu@lists.linux-foundation.org > https://lists.linuxfoundation.org/mailman/listinfo/iommu _______________________________________________ iommu mailing list iommu@lists.linux-foundation.org https://lists.linuxfoundation.org/mailman/listinfo/iommu ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: I got an IOMMU IO page fault. What to do now? 2021-10-25 16:01 ` Robin Murphy @ 2021-10-25 16:42 ` Christian König via iommu -1 siblings, 0 replies; 18+ messages in thread From: Christian König @ 2021-10-25 16:42 UTC (permalink / raw) To: Robin Murphy, Christian König, Paul Menzel, Jörg Rödel, Suravee Suthikulpanit Cc: x86, Xinhui Pan, LKML, amd-gfx, iommu, Ingo Molnar, Borislav Petkov, Alex Deucher, it+linux-iommu, Thomas Gleixner Hi Robin, Am 25.10.21 um 18:01 schrieb Robin Murphy: > On 2021-10-25 12:23, Christian König wrote: >> Hi Paul, >> >> not sure how the IOMMU gives out addresses, but the printed ones look >> suspicious to me. Something like we are using an invalid address like >> -1 or similar. > > FWIW those look like believable DMA addresses to me, assuming that the > DMA mapping APIs are being backed iommu_dma_ops and the device has a > 40-bit DMA mask, since the IOVA allocator works top-down. Thanks for that information. In that case the addresses look valid to me. > Likely causes are either a race where the dma_unmap_*() call happens > before the hardware has really stopped accessing the relevant > addresses, or the device's DMA mask has been set larger than it should > be, and thus the upper bits have been truncated in the round-trip > through the hardware. That actually looks correct to me. The device indeed has a 40-bit DMA mask. There is a third possibility which is actually quite likely and that are stale reads in the pipeline. See for some use cases the device can queue reads into an internal pipeline, but when it later finds that the read isn't needed doesn't flush the pipeline. The next operation pushes more read requests into the pipeline and eventually the stale read requests are executed as well. Without IOMMU the result of those reads are simply discarded, so no harm done. But with IOMMU enabled it is perfectly possible that the stale read is now accessing unmapped memory -> BAM. That's one of the reasons why we almost always have GPUs in passthrough mode on x86 and for example don't use system memory for GPU page tables on APUs. Regards, Christian. > > Given the addresses involved, my suspicions would initially lean > towards the latter case - the faults are in the very topmost pages > which imply they're the first things mapped in that range. The other > contributing factor being the trick that the IOVA allocator plays for > PCI devices, where it tries to prefer 32-bit addresses. Thus you're > only likely to see this happen once you already have ~3.5-4GB of live > DMA-mapped memory to exhaust the 32-bit IOVA space (minus some > reserved areas) and start allocating from the full DMA mask. You > should be able to check that with a 5.13 or newer kernel by booting > with "iommu.forcedac=1" and seeing if it breaks immediately > (unfortunately with an older kernel you'd have to manually hack > iommu_dma_alloc_iova() to the same effect). > > Robin. > >> Can you try that on an up to date kernel as well? E.g. ideally >> bleeding edge amd-staging-drm-next from Alex repository. >> >> Regards, >> Christian. >> >> Am 25.10.21 um 12:25 schrieb Paul Menzel: >>> Dear Linux folks, >>> >>> >>> On a Dell OptiPlex 5055, Linux 5.10.24 logged the IOMMU messages >>> below. (GPU hang in amdgpu issue #1762 [1] might be related.) >>> >>> $ lspci -nn -s 05:00.0 >>> 05:00.0 VGA compatible controller [0300]: Advanced Micro >>> Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 OEM] >>> [1002:6611] (rev 87) >>> $ dmesg >>> […] >>> [6318399.745242] amdgpu 0000:05:00.0: AMD-Vi: Event logged >>> [IO_PAGE_FAULT domain=0x000c address=0xfffffff0c0 flags=0x0020] >>> [6318399.757283] amdgpu 0000:05:00.0: AMD-Vi: Event logged >>> [IO_PAGE_FAULT domain=0x000c address=0xfffffff7c0 flags=0x0020] >>> [6318399.769154] amdgpu 0000:05:00.0: AMD-Vi: Event logged >>> [IO_PAGE_FAULT domain=0x000c address=0xffffffe0c0 flags=0x0020] >>> [6318399.780913] amdgpu 0000:05:00.0: AMD-Vi: Event logged >>> [IO_PAGE_FAULT domain=0x000c address=0xfffffffec0 flags=0x0020] >>> [6318399.792734] amdgpu 0000:05:00.0: AMD-Vi: Event logged >>> [IO_PAGE_FAULT domain=0x000c address=0xffffffe5c0 flags=0x0020] >>> [6318399.804309] amdgpu 0000:05:00.0: AMD-Vi: Event logged >>> [IO_PAGE_FAULT domain=0x000c address=0xffffffd0c0 flags=0x0020] >>> [6318399.816091] amdgpu 0000:05:00.0: AMD-Vi: Event logged >>> [IO_PAGE_FAULT domain=0x000c address=0xffffffecc0 flags=0x0020] >>> [6318399.827407] amdgpu 0000:05:00.0: AMD-Vi: Event logged >>> [IO_PAGE_FAULT domain=0x000c address=0xffffffd3c0 flags=0x0020] >>> [6318399.838708] amdgpu 0000:05:00.0: AMD-Vi: Event logged >>> [IO_PAGE_FAULT domain=0x000c address=0xffffffc0c0 flags=0x0020] >>> [6318399.850029] amdgpu 0000:05:00.0: AMD-Vi: Event logged >>> [IO_PAGE_FAULT domain=0x000c address=0xffffffdac0 flags=0x0020] >>> [6318399.861311] AMD-Vi: Event logged [IO_PAGE_FAULT >>> device=05:00.0 domain=0x000c address=0xffffffc1c0 flags=0x0020] >>> [6318399.872044] AMD-Vi: Event logged [IO_PAGE_FAULT >>> device=05:00.0 domain=0x000c address=0xffffffc8c0 flags=0x0020] >>> [6318399.882797] AMD-Vi: Event logged [IO_PAGE_FAULT >>> device=05:00.0 domain=0x000c address=0xffffffb0c0 flags=0x0020] >>> [6318399.893655] AMD-Vi: Event logged [IO_PAGE_FAULT >>> device=05:00.0 domain=0x000c address=0xffffffcfc0 flags=0x0020] >>> [6318399.904445] AMD-Vi: Event logged [IO_PAGE_FAULT >>> device=05:00.0 domain=0x000c address=0xffffffb6c0 flags=0x0020] >>> [6318399.915222] AMD-Vi: Event logged [IO_PAGE_FAULT >>> device=05:00.0 domain=0x000c address=0xffffffa0c0 flags=0x0020] >>> [6318399.925931] AMD-Vi: Event logged [IO_PAGE_FAULT >>> device=05:00.0 domain=0x000c address=0xffffffbdc0 flags=0x0020] >>> [6318399.936691] AMD-Vi: Event logged [IO_PAGE_FAULT >>> device=05:00.0 domain=0x000c address=0xffffffa4c0 flags=0x0020] >>> [6318399.947479] AMD-Vi: Event logged [IO_PAGE_FAULT >>> device=05:00.0 domain=0x000c address=0xffffff90c0 flags=0x0020] >>> [6318399.958270] AMD-Vi: Event logged [IO_PAGE_FAULT >>> device=05:00.0 domain=0x000c address=0xffffffabc0 flags=0x0020] >>> >>> As this is not reproducible, how would debugging go? (The system was >>> rebooted in the meantime.) What options should be enabled, that next >>> time the required information is logged, or what commands should I >>> execute when the system is still in that state, so the bug (driver, >>> userspace, …) can be pinpointed and fixed? >>> >>> >>> Kind regards, >>> >>> Paul >>> >>> >>> [1]: >>> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.freedesktop.org%2Fdrm%2Famd%2F-%2Fissues%2F1762&data=04%7C01%7Cchristian.koenig%40amd.com%7C13ead10a4a584537d87208d997d0c693%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637707745295391463%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=jn1HS%2FhtmfLOQBD%2FI9w4ZXpspc4X7ik6G8N1W5AlqXg%3D&reserved=0 >>> "Oland [Radeon HD 8570 / R7 240/340 OEM]: GPU hang" >> >> _______________________________________________ >> iommu mailing list >> iommu@lists.linux-foundation.org >> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.linuxfoundation.org%2Fmailman%2Flistinfo%2Fiommu&data=04%7C01%7Cchristian.koenig%40amd.com%7C13ead10a4a584537d87208d997d0c693%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637707745295391463%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=WNsslcCFP2UJX%2FtuPmsFWv%2BpW1i02q3K7pIlIdaQcfE%3D&reserved=0 >> ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: I got an IOMMU IO page fault. What to do now? @ 2021-10-25 16:42 ` Christian König via iommu 0 siblings, 0 replies; 18+ messages in thread From: Christian König via iommu @ 2021-10-25 16:42 UTC (permalink / raw) To: Robin Murphy, Christian König, Paul Menzel, Jörg Rödel, Suravee Suthikulpanit Cc: x86, Xinhui Pan, LKML, amd-gfx, iommu, Ingo Molnar, Borislav Petkov, Alex Deucher, it+linux-iommu, Thomas Gleixner Hi Robin, Am 25.10.21 um 18:01 schrieb Robin Murphy: > On 2021-10-25 12:23, Christian König wrote: >> Hi Paul, >> >> not sure how the IOMMU gives out addresses, but the printed ones look >> suspicious to me. Something like we are using an invalid address like >> -1 or similar. > > FWIW those look like believable DMA addresses to me, assuming that the > DMA mapping APIs are being backed iommu_dma_ops and the device has a > 40-bit DMA mask, since the IOVA allocator works top-down. Thanks for that information. In that case the addresses look valid to me. > Likely causes are either a race where the dma_unmap_*() call happens > before the hardware has really stopped accessing the relevant > addresses, or the device's DMA mask has been set larger than it should > be, and thus the upper bits have been truncated in the round-trip > through the hardware. That actually looks correct to me. The device indeed has a 40-bit DMA mask. There is a third possibility which is actually quite likely and that are stale reads in the pipeline. See for some use cases the device can queue reads into an internal pipeline, but when it later finds that the read isn't needed doesn't flush the pipeline. The next operation pushes more read requests into the pipeline and eventually the stale read requests are executed as well. Without IOMMU the result of those reads are simply discarded, so no harm done. But with IOMMU enabled it is perfectly possible that the stale read is now accessing unmapped memory -> BAM. That's one of the reasons why we almost always have GPUs in passthrough mode on x86 and for example don't use system memory for GPU page tables on APUs. Regards, Christian. > > Given the addresses involved, my suspicions would initially lean > towards the latter case - the faults are in the very topmost pages > which imply they're the first things mapped in that range. The other > contributing factor being the trick that the IOVA allocator plays for > PCI devices, where it tries to prefer 32-bit addresses. Thus you're > only likely to see this happen once you already have ~3.5-4GB of live > DMA-mapped memory to exhaust the 32-bit IOVA space (minus some > reserved areas) and start allocating from the full DMA mask. You > should be able to check that with a 5.13 or newer kernel by booting > with "iommu.forcedac=1" and seeing if it breaks immediately > (unfortunately with an older kernel you'd have to manually hack > iommu_dma_alloc_iova() to the same effect). > > Robin. > >> Can you try that on an up to date kernel as well? E.g. ideally >> bleeding edge amd-staging-drm-next from Alex repository. >> >> Regards, >> Christian. >> >> Am 25.10.21 um 12:25 schrieb Paul Menzel: >>> Dear Linux folks, >>> >>> >>> On a Dell OptiPlex 5055, Linux 5.10.24 logged the IOMMU messages >>> below. (GPU hang in amdgpu issue #1762 [1] might be related.) >>> >>> $ lspci -nn -s 05:00.0 >>> 05:00.0 VGA compatible controller [0300]: Advanced Micro >>> Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 OEM] >>> [1002:6611] (rev 87) >>> $ dmesg >>> […] >>> [6318399.745242] amdgpu 0000:05:00.0: AMD-Vi: Event logged >>> [IO_PAGE_FAULT domain=0x000c address=0xfffffff0c0 flags=0x0020] >>> [6318399.757283] amdgpu 0000:05:00.0: AMD-Vi: Event logged >>> [IO_PAGE_FAULT domain=0x000c address=0xfffffff7c0 flags=0x0020] >>> [6318399.769154] amdgpu 0000:05:00.0: AMD-Vi: Event logged >>> [IO_PAGE_FAULT domain=0x000c address=0xffffffe0c0 flags=0x0020] >>> [6318399.780913] amdgpu 0000:05:00.0: AMD-Vi: Event logged >>> [IO_PAGE_FAULT domain=0x000c address=0xfffffffec0 flags=0x0020] >>> [6318399.792734] amdgpu 0000:05:00.0: AMD-Vi: Event logged >>> [IO_PAGE_FAULT domain=0x000c address=0xffffffe5c0 flags=0x0020] >>> [6318399.804309] amdgpu 0000:05:00.0: AMD-Vi: Event logged >>> [IO_PAGE_FAULT domain=0x000c address=0xffffffd0c0 flags=0x0020] >>> [6318399.816091] amdgpu 0000:05:00.0: AMD-Vi: Event logged >>> [IO_PAGE_FAULT domain=0x000c address=0xffffffecc0 flags=0x0020] >>> [6318399.827407] amdgpu 0000:05:00.0: AMD-Vi: Event logged >>> [IO_PAGE_FAULT domain=0x000c address=0xffffffd3c0 flags=0x0020] >>> [6318399.838708] amdgpu 0000:05:00.0: AMD-Vi: Event logged >>> [IO_PAGE_FAULT domain=0x000c address=0xffffffc0c0 flags=0x0020] >>> [6318399.850029] amdgpu 0000:05:00.0: AMD-Vi: Event logged >>> [IO_PAGE_FAULT domain=0x000c address=0xffffffdac0 flags=0x0020] >>> [6318399.861311] AMD-Vi: Event logged [IO_PAGE_FAULT >>> device=05:00.0 domain=0x000c address=0xffffffc1c0 flags=0x0020] >>> [6318399.872044] AMD-Vi: Event logged [IO_PAGE_FAULT >>> device=05:00.0 domain=0x000c address=0xffffffc8c0 flags=0x0020] >>> [6318399.882797] AMD-Vi: Event logged [IO_PAGE_FAULT >>> device=05:00.0 domain=0x000c address=0xffffffb0c0 flags=0x0020] >>> [6318399.893655] AMD-Vi: Event logged [IO_PAGE_FAULT >>> device=05:00.0 domain=0x000c address=0xffffffcfc0 flags=0x0020] >>> [6318399.904445] AMD-Vi: Event logged [IO_PAGE_FAULT >>> device=05:00.0 domain=0x000c address=0xffffffb6c0 flags=0x0020] >>> [6318399.915222] AMD-Vi: Event logged [IO_PAGE_FAULT >>> device=05:00.0 domain=0x000c address=0xffffffa0c0 flags=0x0020] >>> [6318399.925931] AMD-Vi: Event logged [IO_PAGE_FAULT >>> device=05:00.0 domain=0x000c address=0xffffffbdc0 flags=0x0020] >>> [6318399.936691] AMD-Vi: Event logged [IO_PAGE_FAULT >>> device=05:00.0 domain=0x000c address=0xffffffa4c0 flags=0x0020] >>> [6318399.947479] AMD-Vi: Event logged [IO_PAGE_FAULT >>> device=05:00.0 domain=0x000c address=0xffffff90c0 flags=0x0020] >>> [6318399.958270] AMD-Vi: Event logged [IO_PAGE_FAULT >>> device=05:00.0 domain=0x000c address=0xffffffabc0 flags=0x0020] >>> >>> As this is not reproducible, how would debugging go? (The system was >>> rebooted in the meantime.) What options should be enabled, that next >>> time the required information is logged, or what commands should I >>> execute when the system is still in that state, so the bug (driver, >>> userspace, …) can be pinpointed and fixed? >>> >>> >>> Kind regards, >>> >>> Paul >>> >>> >>> [1]: >>> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.freedesktop.org%2Fdrm%2Famd%2F-%2Fissues%2F1762&data=04%7C01%7Cchristian.koenig%40amd.com%7C13ead10a4a584537d87208d997d0c693%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637707745295391463%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=jn1HS%2FhtmfLOQBD%2FI9w4ZXpspc4X7ik6G8N1W5AlqXg%3D&reserved=0 >>> "Oland [Radeon HD 8570 / R7 240/340 OEM]: GPU hang" >> >> _______________________________________________ >> iommu mailing list >> iommu@lists.linux-foundation.org >> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.linuxfoundation.org%2Fmailman%2Flistinfo%2Fiommu&data=04%7C01%7Cchristian.koenig%40amd.com%7C13ead10a4a584537d87208d997d0c693%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637707745295391463%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=WNsslcCFP2UJX%2FtuPmsFWv%2BpW1i02q3K7pIlIdaQcfE%3D&reserved=0 >> _______________________________________________ iommu mailing list iommu@lists.linux-foundation.org https://lists.linuxfoundation.org/mailman/listinfo/iommu ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: I got an IOMMU IO page fault. What to do now? 2021-10-25 16:01 ` Robin Murphy @ 2021-10-27 16:45 ` Paul Menzel -1 siblings, 0 replies; 18+ messages in thread From: Paul Menzel @ 2021-10-27 16:45 UTC (permalink / raw) To: Robin Murphy Cc: x86, Xinhui Pan, LKML, amd-gfx, iommu, Ingo Molnar, Borislav Petkov, Alex Deucher, it+linux-iommu, Thomas Gleixner, Christian König, Christian König, Jörg Rödel, Suravee Suthikulpanit [-- Attachment #1: Type: text/plain, Size: 2019 bytes --] Dear Robin, On 25.10.21 18:01, Robin Murphy wrote: > On 2021-10-25 12:23, Christian König wrote: >> not sure how the IOMMU gives out addresses, but the printed ones look >> suspicious to me. Something like we are using an invalid address like >> -1 or similar. > > FWIW those look like believable DMA addresses to me, assuming that the > DMA mapping APIs are being backed iommu_dma_ops and the device has a > 40-bit DMA mask, since the IOVA allocator works top-down. > > Likely causes are either a race where the dma_unmap_*() call happens > before the hardware has really stopped accessing the relevant addresses, > or the device's DMA mask has been set larger than it should be, and thus > the upper bits have been truncated in the round-trip through the hardware. > > Given the addresses involved, my suspicions would initially lean towards > the latter case - the faults are in the very topmost pages which imply > they're the first things mapped in that range. The other contributing > factor being the trick that the IOVA allocator plays for PCI devices, > where it tries to prefer 32-bit addresses. Thus you're only likely to > see this happen once you already have ~3.5-4GB of live DMA-mapped memory > to exhaust the 32-bit IOVA space (minus some reserved areas) and start > allocating from the full DMA mask. You should be able to check that with > a 5.13 or newer kernel by booting with "iommu.forcedac=1" and seeing if > it breaks immediately (unfortunately with an older kernel you'd have to > manually hack iommu_dma_alloc_iova() to the same effect). I booted Linux 5.15-rc7 with `iommu.forcedac=1` and the system booted, and I could log in remotely over SSH. Please find the Linux kernel messages attached. (The system logs say lightdm failed to start, but it might be some other issue due to a change in the operating system.) >> Can you try that on an up to date kernel as well? E.g. ideally >> bleeding edge amd-staging-drm-next from Alex repository. Kind regards, Paul [-- Attachment #2: 20211027–linux-5.15-rc7–dell-optiplex-5055–iommu.forcedac.txt --] [-- Type: text/plain, Size: 65662 bytes --] [ 0.000000] Linux version 5.15.0-rc7.mx64.407 (root@theinternet.molgen.mpg.de) (gcc (GCC) 7.5.0, GNU ld (GNU Binutils) 2.37) #1 SMP Tue Oct 26 04:00:49 CEST 2021 [ 0.000000] Command line: BOOT_IMAGE=/boot/bzImage-5.15.0-rc7.mx64.407 root=LABEL=root ro crashkernel=256M console=ttyS0,115200n8 console=tty0 init=/bin/systemd audit=0 random.trust_cpu=on iommu.forcedac=1 [ 0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' [ 0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' [ 0.000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' [ 0.000000] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 [ 0.000000] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'compacted' format. [ 0.000000] signal: max sigframe size: 1776 [ 0.000000] BIOS-provided physical RAM map: [ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x0000000000087fff] usable [ 0.000000] BIOS-e820: [mem 0x0000000000088000-0x0000000000088fff] reserved [ 0.000000] BIOS-e820: [mem 0x0000000000089000-0x000000000009ffff] usable [ 0.000000] BIOS-e820: [mem 0x00000000000a0000-0x00000000000bffff] reserved [ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x0000000009cfffff] usable [ 0.000000] BIOS-e820: [mem 0x0000000009d00000-0x0000000009e6ffff] reserved [ 0.000000] BIOS-e820: [mem 0x0000000009e70000-0x00000000dadbefff] usable [ 0.000000] BIOS-e820: [mem 0x00000000dadbf000-0x00000000dafbefff] type 20 [ 0.000000] BIOS-e820: [mem 0x00000000dafbf000-0x00000000dcfbefff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000dcfbf000-0x00000000defbefff] ACPI NVS [ 0.000000] BIOS-e820: [mem 0x00000000defbf000-0x00000000deffefff] ACPI data [ 0.000000] BIOS-e820: [mem 0x00000000defff000-0x00000000deffffff] usable [ 0.000000] BIOS-e820: [mem 0x00000000df000000-0x00000000dfffffff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000fec10000-0x00000000fec10fff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000fed80000-0x00000000fed80fff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved [ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000041effffff] usable [ 0.000000] Forcing DAC for PCI devices [ 0.000000] NX (Execute Disable) protection: active [ 0.000000] efi: EFI v2.50 by EDK II [ 0.000000] efi: TPMFinalLog=0xdefa2000 SMBIOS=0xdbeb5000 SMBIOS 3.0=0xdbeb3000 ACPI 2.0=0xdeffe014 ESRT=0xdbe9f298 MEMATTR=0xd8b6f018 [ 0.000000] SMBIOS 3.0.0 present. [ 0.000000] DMI: Dell Inc. OptiPlex 5055 Ryzen CPU/0P03DX, BIOS 1.1.50 07/28/2021 [ 0.000000] tsc: Fast TSC calibration using PIT [ 0.000000] tsc: Detected 3493.349 MHz processor [ 0.001974] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved [ 0.001976] e820: remove [mem 0x000a0000-0x000fffff] usable [ 0.001981] last_pfn = 0x41f000 max_arch_pfn = 0x400000000 [ 0.002281] x86/PAT: Configuration [0-7]: WB WC UC- UC WB WP UC- WT [ 0.002561] last_pfn = 0xdf000 max_arch_pfn = 0x400000000 [ 0.006431] esrt: Reserving ESRT space from 0x00000000dbe9f298 to 0x00000000dbe9f2d0. [ 0.006441] Using GB pages for direct mapping [ 0.006889] Secure boot could not be determined [ 0.006890] RAMDISK: [mem 0x375e7000-0x37aeafff] [ 0.006893] ACPI: Early table checksum verification disabled [ 0.006896] ACPI: RSDP 0x00000000DEFFE014 000024 (v02 AMD ) [ 0.006900] ACPI: XSDT 0x00000000DEFD9188 000104 (v01 AMD MYRTLE 00000001 01000013) [ 0.006905] ACPI: FACP 0x00000000DEFF0000 00010C (v05 AMD MYRTLE 00000001 ACPI 00040000) [ 0.006910] ACPI: DSDT 0x00000000DEFE8000 0012CB (v01 AMD MYRTLE 00040000 ACPI 00040000) [ 0.006913] ACPI: FACS 0x00000000DEB73000 000040 [ 0.006916] ACPI: SSDT 0x00000000DEFF5000 008C4C (v02 AMD MYRTLE 00000002 ACPI 00040000) [ 0.006918] ACPI: UEFI 0x00000000DEFF4000 000042 (v01 AMD MYRTLE 00000002 ACPI 00040000) [ 0.006921] ACPI: SSDT 0x00000000DEFF3000 0003C6 (v02 AMD MYRTLE 00001000 ACPI 00040000) [ 0.006924] ACPI: TPM2 0x00000000DEFF2000 000034 (v03 AMD MYRTLE 00000002 ACPI 00040000) [ 0.006927] ACPI: ASF! 0x00000000DEFF1000 0000A5 (v32 AMD MYRTLE 00000001 ACPI 00040000) [ 0.006930] ACPI: HPET 0x00000000DEFEF000 000038 (v01 AMD MYRTLE 00000001 ACPI 00040000) [ 0.006933] ACPI: APIC 0x00000000DEFEE000 000138 (v03 AMD MYRTLE 00000001 ACPI 00040000) [ 0.006935] ACPI: MCFG 0x00000000DEFED000 00003C (v01 AMD MYRTLE 00000001 ACPI 00040000) [ 0.006938] ACPI: SPCR 0x00000000DEFEC000 000050 (v01 AMD MYRTLE 00000001 ACPI 00040000) [ 0.006941] ACPI: WDAT 0x00000000DEFEB000 00017C (v01 AMD MYRTLE 00000001 ACPI 00040000) [ 0.006944] ACPI: WDRT 0x00000000DEFEA000 000047 (v01 AMD MYRTLE 00000000 ACPI 00040000) [ 0.006946] ACPI: SSDT 0x00000000DEFE5000 002AC4 (v01 AMD MYRTLE 00000001 ACPI 00040000) [ 0.006949] ACPI: SSDT 0x00000000DEFE4000 0000FC (v01 AMD MYRTLE 00000001 ACPI 00040000) [ 0.006952] ACPI: SSDT 0x00000000DEFDE000 000024 (v01 AMD MYRTLE 00001000 ACPI 00040000) [ 0.006954] ACPI: SSDT 0x00000000DEFDD000 000E0C (v01 AMD MYRTLE 00000001 ACPI 00040000) [ 0.006957] ACPI: CRAT 0x00000000DEFDC000 000850 (v01 AMD MYRTLE 00000001 ACPI 00040000) [ 0.006960] ACPI: CDIT 0x00000000DEFDB000 000029 (v01 AMD MYRTLE 00000001 ACPI 00040000) [ 0.006963] ACPI: BOOT 0x00000000DEFDA000 000028 (v01 AMD MYRTLE 00000002 ACPI 00040000) [ 0.006965] ACPI: SSDT 0x00000000DEFDF000 0048E6 (v01 AMD MYRTLE 00000001 ACPI 00040000) [ 0.006968] ACPI: VFCT 0x00000000DEFC8000 010084 (v01 AMD MYRTLE 00000001 ACPI 00040000) [ 0.006971] ACPI: IVRS 0x00000000DEFC7000 0000D0 (v02 AMD MYRTLE 00000001 ACPI 00040000) [ 0.006973] ACPI: MSDM 0x00000000DEFC6000 000055 (v03 AMD MYRTLE 06222004 ACPI 00040000) [ 0.006976] ACPI: SSDT 0x00000000DEFC5000 000920 (v01 AMD MYRTLE 00001000 ACPI 00040000) [ 0.006979] ACPI: SSDT 0x00000000DEFC4000 0000F8 (v01 AMD MYRTLE 00001000 ACPI 00040000) [ 0.006981] ACPI: SSDT 0x00000000DEFC2000 001768 (v01 AMD MYRTLE 00000001 ACPI 00040000) [ 0.006984] ACPI: FPDT 0x00000000DEFC1000 000044 (v01 AMD MYRTLE 00000002 ACPI 00040000) [ 0.006987] ACPI: BGRT 0x00000000DEFC0000 000038 (v01 AMD MYRTLE 00000002 ACPI 00040000) [ 0.006989] ACPI: Reserving FACP table memory at [mem 0xdeff0000-0xdeff010b] [ 0.006991] ACPI: Reserving DSDT table memory at [mem 0xdefe8000-0xdefe92ca] [ 0.006992] ACPI: Reserving FACS table memory at [mem 0xdeb73000-0xdeb7303f] [ 0.006994] ACPI: Reserving SSDT table memory at [mem 0xdeff5000-0xdeffdc4b] [ 0.006995] ACPI: Reserving UEFI table memory at [mem 0xdeff4000-0xdeff4041] [ 0.006996] ACPI: Reserving SSDT table memory at [mem 0xdeff3000-0xdeff33c5] [ 0.006997] ACPI: Reserving TPM2 table memory at [mem 0xdeff2000-0xdeff2033] [ 0.006999] ACPI: Reserving ASF! table memory at [mem 0xdeff1000-0xdeff10a4] [ 0.007000] ACPI: Reserving HPET table memory at [mem 0xdefef000-0xdefef037] [ 0.007001] ACPI: Reserving APIC table memory at [mem 0xdefee000-0xdefee137] [ 0.007002] ACPI: Reserving MCFG table memory at [mem 0xdefed000-0xdefed03b] [ 0.007003] ACPI: Reserving SPCR table memory at [mem 0xdefec000-0xdefec04f] [ 0.007004] ACPI: Reserving WDAT table memory at [mem 0xdefeb000-0xdefeb17b] [ 0.007006] ACPI: Reserving WDRT table memory at [mem 0xdefea000-0xdefea046] [ 0.007007] ACPI: Reserving SSDT table memory at [mem 0xdefe5000-0xdefe7ac3] [ 0.007008] ACPI: Reserving SSDT table memory at [mem 0xdefe4000-0xdefe40fb] [ 0.007009] ACPI: Reserving SSDT table memory at [mem 0xdefde000-0xdefde023] [ 0.007010] ACPI: Reserving SSDT table memory at [mem 0xdefdd000-0xdefdde0b] [ 0.007012] ACPI: Reserving CRAT table memory at [mem 0xdefdc000-0xdefdc84f] [ 0.007013] ACPI: Reserving CDIT table memory at [mem 0xdefdb000-0xdefdb028] [ 0.007014] ACPI: Reserving BOOT table memory at [mem 0xdefda000-0xdefda027] [ 0.007015] ACPI: Reserving SSDT table memory at [mem 0xdefdf000-0xdefe38e5] [ 0.007016] ACPI: Reserving VFCT table memory at [mem 0xdefc8000-0xdefd8083] [ 0.007017] ACPI: Reserving IVRS table memory at [mem 0xdefc7000-0xdefc70cf] [ 0.007019] ACPI: Reserving MSDM table memory at [mem 0xdefc6000-0xdefc6054] [ 0.007020] ACPI: Reserving SSDT table memory at [mem 0xdefc5000-0xdefc591f] [ 0.007021] ACPI: Reserving SSDT table memory at [mem 0xdefc4000-0xdefc40f7] [ 0.007022] ACPI: Reserving SSDT table memory at [mem 0xdefc2000-0xdefc3767] [ 0.007023] ACPI: Reserving FPDT table memory at [mem 0xdefc1000-0xdefc1043] [ 0.007025] ACPI: Reserving BGRT table memory at [mem 0xdefc0000-0xdefc0037] [ 0.007033] system APIC only can use physical flat [ 0.007034] Setting APIC routing to physical flat. [ 0.007155] No NUMA configuration found [ 0.007156] Faking a node at [mem 0x0000000000000000-0x000000041effffff] [ 0.007160] NODE_DATA(0) allocated [mem 0x41effa000-0x41effefff] [ 0.007167] Reserving 256MB of memory at 3136MB for crashkernel (System RAM: 16283MB) [ 0.007184] Zone ranges: [ 0.007185] DMA [mem 0x0000000000001000-0x0000000000ffffff] [ 0.007187] DMA32 [mem 0x0000000001000000-0x00000000ffffffff] [ 0.007189] Normal [mem 0x0000000100000000-0x000000041effffff] [ 0.007190] Device empty [ 0.007191] Movable zone start for each node [ 0.007192] Early memory node ranges [ 0.007193] node 0: [mem 0x0000000000001000-0x0000000000087fff] [ 0.007194] node 0: [mem 0x0000000000089000-0x000000000009ffff] [ 0.007195] node 0: [mem 0x0000000000100000-0x0000000009cfffff] [ 0.007196] node 0: [mem 0x0000000009e70000-0x00000000dadbefff] [ 0.007198] node 0: [mem 0x00000000defff000-0x00000000deffffff] [ 0.007199] node 0: [mem 0x0000000100000000-0x000000041effffff] [ 0.007201] Initmem setup node 0 [mem 0x0000000000001000-0x000000041effffff] [ 0.007205] On node 0, zone DMA: 1 pages in unavailable ranges [ 0.007206] On node 0, zone DMA: 1 pages in unavailable ranges [ 0.007225] On node 0, zone DMA: 96 pages in unavailable ranges [ 0.013935] On node 0, zone DMA32: 368 pages in unavailable ranges [ 0.014099] On node 0, zone DMA32: 16960 pages in unavailable ranges [ 0.041239] On node 0, zone Normal: 4096 pages in unavailable ranges [ 0.041283] On node 0, zone Normal: 4096 pages in unavailable ranges [ 0.041628] ACPI: PM-Timer IO Port: 0x408 [ 0.041630] system APIC only can use physical flat [ 0.041635] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) [ 0.041636] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) [ 0.041638] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1]) [ 0.041639] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1]) [ 0.041640] ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1]) [ 0.041641] ACPI: LAPIC_NMI (acpi_id[0x05] high edge lint[0x1]) [ 0.041642] ACPI: LAPIC_NMI (acpi_id[0x06] high edge lint[0x1]) [ 0.041643] ACPI: LAPIC_NMI (acpi_id[0x07] high edge lint[0x1]) [ 0.041644] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1]) [ 0.041644] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1]) [ 0.041645] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1]) [ 0.041646] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1]) [ 0.041647] ACPI: LAPIC_NMI (acpi_id[0x0c] high edge lint[0x1]) [ 0.041648] ACPI: LAPIC_NMI (acpi_id[0x0d] high edge lint[0x1]) [ 0.041649] ACPI: LAPIC_NMI (acpi_id[0x0e] high edge lint[0x1]) [ 0.041650] ACPI: LAPIC_NMI (acpi_id[0x0f] high edge lint[0x1]) [ 0.041676] IOAPIC[0]: apic_id 32, version 33, address 0xfec00000, GSI 0-23 [ 0.041681] IOAPIC[1]: apic_id 33, version 33, address 0xfec01000, GSI 24-55 [ 0.041683] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [ 0.041685] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level) [ 0.041688] ACPI: Using ACPI (MADT) for SMP configuration information [ 0.041689] ACPI: HPET id: 0x10228210 base: 0xfed00000 [ 0.041693] ACPI: SPCR: SPCR table version 1 [ 0.041695] ACPI: SPCR: console: uart,io,0x3f8,115200 [ 0.041697] smpboot: Allowing 16 CPUs, 8 hotplug CPUs [ 0.041717] [mem 0xe0000000-0xf7ffffff] available for PCI devices [ 0.041721] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1910969940391419 ns [ 0.045936] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:1 [ 0.046588] percpu: Embedded 49 pages/cpu s163160 r8192 d29352 u262144 [ 0.046595] pcpu-alloc: s163160 r8192 d29352 u262144 alloc=1*2097152 [ 0.046597] pcpu-alloc: [0] 00 01 02 03 04 05 06 07 [0] 08 09 10 11 12 13 14 15 [ 0.046621] Built 1 zonelists, mobility grouping on. Total pages: 4103390 [ 0.046623] Policy zone: Normal [ 0.046624] Kernel command line: BOOT_IMAGE=/boot/bzImage-5.15.0-rc7.mx64.407 root=LABEL=root ro crashkernel=256M console=ttyS0,115200n8 console=tty0 init=/bin/systemd audit=0 random.trust_cpu=on iommu.forcedac=1 [ 0.046701] audit: disabled (until reboot) [ 0.046731] Unknown command line parameters: BOOT_IMAGE=/boot/bzImage-5.15.0-rc7.mx64.407 crashkernel=256M [ 0.048224] Dentry cache hash table entries: 2097152 (order: 12, 16777216 bytes, linear) [ 0.048985] Inode-cache hash table entries: 1048576 (order: 11, 8388608 bytes, linear) [ 0.049025] mem auto-init: stack:off, heap alloc:off, heap free:off [ 0.094071] Memory: 15939164K/16674744K available (14349K kernel code, 3523K rwdata, 3884K rodata, 1700K init, 2608K bss, 735324K reserved, 0K cma-reserved) [ 0.094153] ftrace: allocating 45454 entries in 178 pages [ 0.106225] ftrace: allocated 178 pages with 4 groups [ 0.106304] rcu: Hierarchical RCU implementation. [ 0.106305] rcu: RCU event tracing is enabled. [ 0.106306] rcu: RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16. [ 0.106307] Rude variant of Tasks RCU enabled. [ 0.106308] Tracing variant of Tasks RCU enabled. [ 0.106308] rcu: RCU calculated value of scheduler-enlistment delay is 100 jiffies. [ 0.106310] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=16 [ 0.109576] NR_IRQS: 16640, nr_irqs: 1096, preallocated irqs: 16 [ 0.109862] random: crng done (trusting CPU's manufacturer) [ 0.110077] Console: colour dummy device 80x25 [ 0.110270] printk: console [tty0] enabled [ 1.366681] printk: console [ttyS0] enabled [ 1.370896] ACPI: Core revision 20210730 [ 1.375021] clocksource: hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 133484873504 ns [ 1.384189] APIC: Switch to symmetric I/O mode setup [ 1.392739] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1 [ 1.403189] clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x325ac60cf80, max_idle_ns: 440795363783 ns [ 1.413725] Calibrating delay loop (skipped), value calculated using timer frequency.. 6986.69 BogoMIPS (lpj=3493349) [ 1.414725] pid_max: default: 32768 minimum: 301 [ 1.417758] LSM: Security Framework initializing [ 1.418770] Mount-cache hash table entries: 32768 (order: 6, 262144 bytes, linear) [ 1.419751] Mountpoint-cache hash table entries: 32768 (order: 6, 262144 bytes, linear) [ 1.420950] LVT offset 1 assigned for vector 0xf9 [ 1.421803] LVT offset 2 assigned for vector 0xf4 [ 1.422739] Last level iTLB entries: 4KB 1024, 2MB 1024, 4MB 512 [ 1.423725] Last level dTLB entries: 4KB 1536, 2MB 1536, 4MB 768, 1GB 0 [ 1.424725] Spectre V1 : Mitigation: usercopy/swapgs barriers and __user pointer sanitization [ 1.425726] Spectre V2 : Mitigation: Full AMD retpoline [ 1.426725] Spectre V2 : Spectre v2 / SpectreRSB mitigation: Filling RSB on context switch [ 1.427725] Spectre V2 : mitigation: Enabling conditional Indirect Branch Prediction Barrier [ 1.428725] Speculative Store Bypass: Mitigation: Speculative Store Bypass disabled via prctl and seccomp [ 1.431875] Freeing SMP alternatives memory: 44K [ 1.535795] smpboot: CPU0: AMD Ryzen 5 PRO 1500 Quad-Core Processor (family: 0x17, model: 0x1, stepping: 0x1) [ 1.537774] Performance Events: Fam17h+ core perfctr, AMD PMU driver. [ 1.538725] ... version: 0 [ 1.539725] ... bit width: 48 [ 1.540725] ... generic registers: 6 [ 1.541725] ... value mask: 0000ffffffffffff [ 1.542725] ... max period: 00007fffffffffff [ 1.543725] ... fixed-purpose events: 0 [ 1.544725] ... event mask: 000000000000003f [ 1.545772] rcu: Hierarchical SRCU implementation. [ 1.547053] smp: Bringing up secondary CPUs ... [ 1.547801] x86: Booting SMP configuration: [ 1.548727] .... node #0, CPUs: #1 #2 #3 #4 #5 #6 #7 [ 1.557739] smp: Brought up 1 node, 8 CPUs [ 1.559725] smpboot: Max logical packages: 2 [ 1.560725] smpboot: Total of 8 processors activated (55893.58 BogoMIPS) [ 1.563241] devtmpfs: initialized [ 1.563763] x86/mm: Memory block size: 128MB [ 1.565931] ACPI: PM: Registering ACPI NVS region [mem 0xdcfbf000-0xdefbefff] (33554432 bytes) [ 1.568040] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1911260446275000 ns [ 1.568727] futex hash table entries: 4096 (order: 6, 262144 bytes, linear) [ 1.569891] NET: Registered PF_NETLINK/PF_ROUTE protocol family [ 1.570872] thermal_sys: Registered thermal governor 'step_wise' [ 1.570873] thermal_sys: Registered thermal governor 'user_space' [ 1.571736] cpuidle: using governor menu [ 1.573783] Simple Boot Flag at 0x44 set to 0x80 [ 1.574737] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it [ 1.575725] ACPI: bus type PCI registered [ 1.576756] PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf8000000-0xfbffffff] (base 0xf8000000) [ 1.577727] PCI: MMCONFIG at [mem 0xf8000000-0xfbffffff] reserved in E820 [ 1.578736] PCI: Using configuration type 1 for base access [ 1.581546] Kprobes globally optimized [ 1.581745] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages [ 1.582727] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages [ 1.600725] raid6: avx2x4 gen() 24543 MB/s [ 1.618725] raid6: avx2x4 xor() 8458 MB/s [ 1.636725] raid6: avx2x2 gen() 26948 MB/s [ 1.654725] raid6: avx2x2 xor() 16452 MB/s [ 1.672725] raid6: avx2x1 gen() 24404 MB/s [ 1.690725] raid6: avx2x1 xor() 15328 MB/s [ 1.708725] raid6: sse2x4 gen() 16141 MB/s [ 1.726725] raid6: sse2x4 xor() 8198 MB/s [ 1.744725] raid6: sse2x2 gen() 18234 MB/s [ 1.762725] raid6: sse2x2 xor() 10455 MB/s [ 1.780725] raid6: sse2x1 gen() 13770 MB/s [ 1.798725] raid6: sse2x1 xor() 7739 MB/s [ 1.799725] raid6: using algorithm avx2x2 gen() 26948 MB/s [ 1.800725] raid6: .... xor() 16452 MB/s, rmw enabled [ 1.801725] raid6: using avx2x2 recovery algorithm [ 1.802750] ACPI: Added _OSI(Module Device) [ 1.803727] ACPI: Added _OSI(Processor Device) [ 1.804725] ACPI: Added _OSI(3.0 _SCP Extensions) [ 1.805725] ACPI: Added _OSI(Processor Aggregator Device) [ 1.806725] ACPI: Added _OSI(Linux-Dell-Video) [ 1.807725] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio) [ 1.808725] ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics) [ 1.815760] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored [ 1.818092] ACPI: 11 ACPI AML tables successfully acquired and loaded [ 1.822666] ACPI: Interpreter enabled [ 1.822734] ACPI: PM: (supports S0 S3 S5) [ 1.823725] ACPI: Using IOAPIC for interrupt routing [ 1.824908] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug [ 1.826858] ACPI: Enabled 2 GPEs in block 00 to 1F [ 1.833403] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff]) [ 1.833729] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI HPX-Type3] [ 1.835757] acpi PNP0A08:00: _OSC: platform does not support [LTR] [ 1.836812] acpi PNP0A08:00: _OSC: OS now controls [PME PCIeCapability] [ 1.837725] acpi PNP0A08:00: FADT indicates ASPM is unsupported, using BIOS configuration [ 1.838730] acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain 0000 [bus 00-3f] only partially covers this bridge [ 1.839875] PCI host bridge to bus 0000:00 [ 1.840726] pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7 window] [ 1.841725] pci_bus 0000:00: root bus resource [io 0x0d00-0xffff window] [ 1.842725] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window] [ 1.843725] pci_bus 0000:00: root bus resource [mem 0x000c0000-0x000c3fff window] [ 1.844725] pci_bus 0000:00: root bus resource [mem 0x000c4000-0x000c7fff window] [ 1.845726] pci_bus 0000:00: root bus resource [mem 0x000c8000-0x000cbfff window] [ 1.846725] pci_bus 0000:00: root bus resource [mem 0x000cc000-0x000cffff window] [ 1.847725] pci_bus 0000:00: root bus resource [mem 0x000d0000-0x000d3fff window] [ 1.848725] pci_bus 0000:00: root bus resource [mem 0x000d4000-0x000d7fff window] [ 1.849725] pci_bus 0000:00: root bus resource [mem 0x000d8000-0x000dbfff window] [ 1.850725] pci_bus 0000:00: root bus resource [mem 0x000dc000-0x000dffff window] [ 1.851725] pci_bus 0000:00: root bus resource [mem 0x000e0000-0x000e3fff window] [ 1.852725] pci_bus 0000:00: root bus resource [mem 0x000e4000-0x000e7fff window] [ 1.853725] pci_bus 0000:00: root bus resource [mem 0x000e8000-0x000ebfff window] [ 1.854725] pci_bus 0000:00: root bus resource [mem 0x000ec000-0x000effff window] [ 1.855725] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xf7ffffff window] [ 1.856725] pci_bus 0000:00: root bus resource [mem 0xfc000000-0xfeafffff window] [ 1.857725] pci_bus 0000:00: root bus resource [bus 00-ff] [ 1.858751] pci 0000:00:00.0: [1022:1450] type 00 class 0x060000 [ 1.859805] pci 0000:00:00.2: [1022:1451] type 00 class 0x080600 [ 1.860818] pci 0000:00:01.0: [1022:1452] type 00 class 0x060000 [ 1.861814] pci 0000:00:01.3: [1022:1453] type 01 class 0x060400 [ 1.862773] pci 0000:00:01.3: PME# supported from D0 D3hot D3cold [ 1.863812] pci 0000:00:02.0: [1022:1452] type 00 class 0x060000 [ 1.865744] pci 0000:00:03.0: [1022:1452] type 00 class 0x060000 [ 1.866808] pci 0000:00:03.1: [1022:1453] type 01 class 0x060400 [ 1.867770] pci 0000:00:03.1: PME# supported from D0 D3hot D3cold [ 1.868861] pci 0000:00:04.0: [1022:1452] type 00 class 0x060000 [ 1.869812] pci 0000:00:07.0: [1022:1452] type 00 class 0x060000 [ 1.870808] pci 0000:00:07.1: [1022:1454] type 01 class 0x060400 [ 1.871742] pci 0000:00:07.1: enabling Extended Tags [ 1.872747] pci 0000:00:07.1: PME# supported from D0 D3hot D3cold [ 1.873806] pci 0000:00:08.0: [1022:1452] type 00 class 0x060000 [ 1.874809] pci 0000:00:08.1: [1022:1454] type 01 class 0x060400 [ 1.875745] pci 0000:00:08.1: enabling Extended Tags [ 1.876749] pci 0000:00:08.1: PME# supported from D0 D3hot D3cold [ 1.877853] pci 0000:00:14.0: [1022:790b] type 00 class 0x0c0500 [ 1.878918] pci 0000:00:14.3: [1022:790e] type 00 class 0x060100 [ 1.879945] pci 0000:00:18.0: [1022:1460] type 00 class 0x060000 [ 1.880781] pci 0000:00:18.1: [1022:1461] type 00 class 0x060000 [ 1.881783] pci 0000:00:18.2: [1022:1462] type 00 class 0x060000 [ 1.882781] pci 0000:00:18.3: [1022:1463] type 00 class 0x060000 [ 1.883781] pci 0000:00:18.4: [1022:1464] type 00 class 0x060000 [ 1.884781] pci 0000:00:18.5: [1022:1465] type 00 class 0x060000 [ 1.886763] pci 0000:00:18.6: [1022:1466] type 00 class 0x060000 [ 1.887781] pci 0000:00:18.7: [1022:1467] type 00 class 0x060000 [ 1.888816] pci 0000:01:00.0: [1022:43bb] type 00 class 0x0c0330 [ 1.889739] pci 0000:01:00.0: reg 0x10: [mem 0xf0620000-0xf0627fff 64bit] [ 1.890802] pci 0000:01:00.0: PME# supported from D3hot D3cold [ 1.892763] pci 0000:01:00.1: [1022:43b7] type 00 class 0x010601 [ 1.893765] pci 0000:01:00.1: reg 0x24: [mem 0xf0600000-0xf061ffff] [ 1.894731] pci 0000:01:00.1: reg 0x30: [mem 0xfff80000-0xffffffff pref] [ 1.895763] pci 0000:01:00.1: PME# supported from D3hot D3cold [ 1.896771] pci 0000:01:00.2: [1022:43b2] type 01 class 0x060400 [ 1.897799] pci 0000:01:00.2: PME# supported from D3hot D3cold [ 1.898779] pci 0000:00:01.3: PCI bridge to [bus 01-04] [ 1.899728] pci 0000:00:01.3: bridge window [mem 0xf0600000-0xf06fffff] [ 1.900727] pci 0000:00:01.3: bridge window [mem 0xf0000000-0xf00fffff 64bit pref] [ 1.901766] pci 0000:02:00.0: [1022:43b4] type 01 class 0x060400 [ 1.902814] pci 0000:02:00.0: PME# supported from D3hot D3cold [ 1.903783] pci 0000:02:01.0: [1022:43b4] type 01 class 0x060400 [ 1.904813] pci 0000:02:01.0: PME# supported from D3hot D3cold [ 1.905791] pci 0000:01:00.2: PCI bridge to [bus 02-04] [ 1.906734] pci 0000:01:00.2: bridge window [mem 0xf0000000-0xf00fffff 64bit pref] [ 1.907788] pci 0000:03:00.0: [14e4:1687] type 00 class 0x020000 [ 1.908756] pci 0000:03:00.0: reg 0x10: [mem 0xf0020000-0xf002ffff 64bit pref] [ 1.909743] pci 0000:03:00.0: reg 0x18: [mem 0xf0010000-0xf001ffff 64bit pref] [ 1.910743] pci 0000:03:00.0: reg 0x20: [mem 0xf0000000-0xf000ffff 64bit pref] [ 1.911867] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold [ 1.915743] pci 0000:02:00.0: PCI bridge to [bus 03] [ 1.916734] pci 0000:02:00.0: bridge window [mem 0xf0000000-0xf00fffff 64bit pref] [ 1.918755] pci 0000:02:01.0: PCI bridge to [bus 04] [ 1.919778] pci 0000:05:00.0: [1002:6611] type 00 class 0x030000 [ 1.920735] pci 0000:05:00.0: reg 0x10: [mem 0xe0000000-0xefffffff 64bit pref] [ 1.921731] pci 0000:05:00.0: reg 0x18: [mem 0xf0500000-0xf053ffff 64bit] [ 1.922729] pci 0000:05:00.0: reg 0x20: [io 0x2000-0x20ff] [ 1.923733] pci 0000:05:00.0: reg 0x30: [mem 0xfffe0000-0xffffffff pref] [ 1.924736] pci 0000:05:00.0: BAR 0: assigned to efifb [ 1.925754] pci 0000:05:00.0: supports D1 D2 [ 1.926725] pci 0000:05:00.0: PME# supported from D1 D2 D3hot [ 1.927779] pci 0000:05:00.1: [1002:aab0] type 00 class 0x040300 [ 1.928734] pci 0000:05:00.1: reg 0x10: [mem 0xf0540000-0xf0543fff 64bit] [ 1.929772] pci 0000:05:00.1: supports D1 D2 [ 1.930766] pci 0000:00:03.1: PCI bridge to [bus 05] [ 1.931727] pci 0000:00:03.1: bridge window [io 0x2000-0x2fff] [ 1.932726] pci 0000:00:03.1: bridge window [mem 0xf0500000-0xf05fffff] [ 1.933727] pci 0000:00:03.1: bridge window [mem 0xe0000000-0xefffffff 64bit pref] [ 1.934755] pci 0000:06:00.0: [1022:145a] type 00 class 0x130000 [ 1.935745] pci 0000:06:00.0: enabling Extended Tags [ 1.936784] pci 0000:06:00.2: [1022:1456] type 00 class 0x108000 [ 1.937735] pci 0000:06:00.2: reg 0x18: [mem 0xf0300000-0xf03fffff] [ 1.938732] pci 0000:06:00.2: reg 0x24: [mem 0xf0400000-0xf0401fff] [ 1.939730] pci 0000:06:00.2: enabling Extended Tags [ 1.940783] pci 0000:06:00.3: [1022:145c] type 00 class 0x0c0330 [ 1.941733] pci 0000:06:00.3: reg 0x10: [mem 0xf0200000-0xf02fffff 64bit] [ 1.942743] pci 0000:06:00.3: enabling Extended Tags [ 1.943747] pci 0000:06:00.3: PME# supported from D0 D3hot D3cold [ 1.944781] pci 0000:00:07.1: PCI bridge to [bus 06] [ 1.945728] pci 0000:00:07.1: bridge window [mem 0xf0200000-0xf04fffff] [ 1.946757] pci 0000:07:00.0: [1022:1455] type 00 class 0x130000 [ 1.947747] pci 0000:07:00.0: enabling Extended Tags [ 1.948789] pci 0000:07:00.2: [1022:7901] type 00 class 0x010601 [ 1.949748] pci 0000:07:00.2: reg 0x24: [mem 0xf0108000-0xf0108fff] [ 1.950731] pci 0000:07:00.2: enabling Extended Tags [ 1.951750] pci 0000:07:00.2: PME# supported from D3hot D3cold [ 1.953732] pci 0000:07:00.3: [1022:1457] type 00 class 0x040300 [ 1.954731] pci 0000:07:00.3: reg 0x10: [mem 0xf0100000-0xf0107fff] [ 1.955742] pci 0000:07:00.3: enabling Extended Tags [ 1.956748] pci 0000:07:00.3: PME# supported from D0 D3hot D3cold [ 1.957780] pci 0000:00:08.1: PCI bridge to [bus 07] [ 1.958728] pci 0000:00:08.1: bridge window [mem 0xf0100000-0xf01fffff] [ 1.959983] ACPI: PCI: Interrupt link LNKA configured for IRQ 0 [ 1.960725] ACPI: PCI: Interrupt link LNKA disabled [ 1.961779] ACPI: PCI: Interrupt link LNKB configured for IRQ 0 [ 1.962725] ACPI: PCI: Interrupt link LNKB disabled [ 1.963769] ACPI: PCI: Interrupt link LNKC configured for IRQ 0 [ 1.964725] ACPI: PCI: Interrupt link LNKC disabled [ 1.965782] ACPI: PCI: Interrupt link LNKD configured for IRQ 0 [ 1.966725] ACPI: PCI: Interrupt link LNKD disabled [ 1.967778] ACPI: PCI: Interrupt link LNKE configured for IRQ 0 [ 1.968725] ACPI: PCI: Interrupt link LNKE disabled [ 1.969766] ACPI: PCI: Interrupt link LNKF configured for IRQ 0 [ 1.970725] ACPI: PCI: Interrupt link LNKF disabled [ 1.971767] ACPI: PCI: Interrupt link LNKG configured for IRQ 0 [ 1.972725] ACPI: PCI: Interrupt link LNKG disabled [ 1.973767] ACPI: PCI: Interrupt link LNKH configured for IRQ 0 [ 1.974725] ACPI: PCI: Interrupt link LNKH disabled [ 1.975968] iommu: Default domain type: Translated [ 1.976726] iommu: DMA domain TLB invalidation policy: lazy mode [ 1.977739] pci 0000:05:00.0: vgaarb: VGA device added: decodes=io+mem,owns=none,locks=none [ 1.978726] pci 0000:05:00.0: vgaarb: bridge control possible [ 1.979725] pci 0000:05:00.0: vgaarb: setting as boot device [ 1.980725] vgaarb: loaded [ 1.981783] SCSI subsystem initialized [ 1.982738] libata version 3.00 loaded. [ 1.982749] ACPI: bus type USB registered [ 1.984729] usbcore: registered new interface driver usbfs [ 1.985731] usbcore: registered new interface driver hub [ 1.986730] usbcore: registered new device driver usb [ 1.987735] mc: Linux media interface: v0.10 [ 1.988728] videodev: Linux video capture interface: v2.00 [ 1.989728] pps_core: LinuxPPS API ver. 1 registered [ 1.990725] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it> [ 1.991727] PTP clock support registered [ 1.992749] Registered efivars operations [ 1.993847] PCI: Using ACPI for IRQ routing [ 1.999279] PCI: pci_cache_line_size set to 64 bytes [ 1.999327] e820: reserve RAM buffer [mem 0x00088000-0x0008ffff] [ 1.999329] e820: reserve RAM buffer [mem 0x09d00000-0x0bffffff] [ 1.999330] e820: reserve RAM buffer [mem 0xdadbf000-0xdbffffff] [ 1.999331] e820: reserve RAM buffer [mem 0xdf000000-0xdfffffff] [ 1.999332] e820: reserve RAM buffer [mem 0x41f000000-0x41fffffff] [ 1.999336] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0 [ 1.999725] hpet0: 3 comparators, 32-bit 14.318180 MHz counter [ 2.002758] clocksource: Switched to clocksource tsc-early [ 2.015069] VFS: Disk quotas dquot_6.6.0 [ 2.019021] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes) [ 2.025939] FS-Cache: Loaded [ 2.028871] CacheFiles: Loaded [ 2.031956] pnp: PnP ACPI init [ 2.035171] system 00:00: [mem 0xfec00000-0xfec01fff] could not be reserved [ 2.042141] system 00:00: [mem 0xfee00000-0xfee00fff] has been reserved [ 2.048762] system 00:00: [mem 0xfdf00000-0xfdffffff] has been reserved [ 2.055484] system 00:02: [io 0x0400-0x04cf] has been reserved [ 2.061415] system 00:02: [io 0x04d0-0x04d1] has been reserved [ 2.067344] system 00:02: [io 0x04d6] has been reserved [ 2.072664] system 00:02: [io 0x0c00-0x0c01] has been reserved [ 2.078592] system 00:02: [io 0x0c14] has been reserved [ 2.083913] system 00:02: [io 0x0c50-0x0c52] has been reserved [ 2.089844] system 00:02: [io 0x0c6c] has been reserved [ 2.095168] system 00:02: [io 0x0c6f] has been reserved [ 2.100491] system 00:02: [io 0x0cd0-0x0cdb] has been reserved [ 2.106462] system 00:03: [mem 0x000e0000-0x000fffff] could not be reserved [ 2.113434] system 00:03: [mem 0xff000000-0xffffffff] has been reserved [ 2.120518] pnp: PnP ACPI: found 5 devices [ 2.130237] clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns [ 2.139157] NET: Registered PF_INET protocol family [ 2.144276] IP idents hash table entries: 262144 (order: 9, 2097152 bytes, linear) [ 2.153342] tcp_listen_portaddr_hash hash table entries: 8192 (order: 5, 131072 bytes, linear) [ 2.161983] TCP established hash table entries: 131072 (order: 8, 1048576 bytes, linear) [ 2.170222] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes, linear) [ 2.177739] TCP: Hash tables configured (established 131072 bind 65536) [ 2.184392] UDP hash table entries: 8192 (order: 6, 262144 bytes, linear) [ 2.191223] UDP-Lite hash table entries: 8192 (order: 6, 262144 bytes, linear) [ 2.198534] pci 0000:01:00.1: can't claim BAR 6 [mem 0xfff80000-0xffffffff pref]: no compatible bridge window [ 2.208453] pci 0000:05:00.0: can't claim BAR 6 [mem 0xfffe0000-0xffffffff pref]: no compatible bridge window [ 2.218380] pci 0000:01:00.1: BAR 6: assigned [mem 0xf0680000-0xf06fffff pref] [ 2.225611] pci 0000:02:00.0: PCI bridge to [bus 03] [ 2.230590] pci 0000:02:00.0: bridge window [mem 0xf0000000-0xf00fffff 64bit pref] [ 2.238347] pci 0000:02:01.0: PCI bridge to [bus 04] [ 2.243333] pci 0000:01:00.2: PCI bridge to [bus 02-04] [ 2.248568] pci 0000:01:00.2: bridge window [mem 0xf0000000-0xf00fffff 64bit pref] [ 2.256326] pci 0000:00:01.3: PCI bridge to [bus 01-04] [ 2.261555] pci 0000:00:01.3: bridge window [mem 0xf0600000-0xf06fffff] [ 2.268351] pci 0000:00:01.3: bridge window [mem 0xf0000000-0xf00fffff 64bit pref] [ 2.276099] pci 0000:05:00.0: BAR 6: assigned [mem 0xf0560000-0xf057ffff pref] [ 2.283327] pci 0000:00:03.1: PCI bridge to [bus 05] [ 2.288298] pci 0000:00:03.1: bridge window [io 0x2000-0x2fff] [ 2.294398] pci 0000:00:03.1: bridge window [mem 0xf0500000-0xf05fffff] [ 2.301196] pci 0000:00:03.1: bridge window [mem 0xe0000000-0xefffffff 64bit pref] [ 2.308943] pci 0000:00:07.1: PCI bridge to [bus 06] [ 2.313914] pci 0000:00:07.1: bridge window [mem 0xf0200000-0xf04fffff] [ 2.320712] pci 0000:00:08.1: PCI bridge to [bus 07] [ 2.325682] pci 0000:00:08.1: bridge window [mem 0xf0100000-0xf01fffff] [ 2.332476] pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7 window] [ 2.338660] pci_bus 0000:00: resource 5 [io 0x0d00-0xffff window] [ 2.344847] pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff window] [ 2.351727] pci_bus 0000:00: resource 7 [mem 0x000c0000-0x000c3fff window] [ 2.358609] pci_bus 0000:00: resource 8 [mem 0x000c4000-0x000c7fff window] [ 2.365489] pci_bus 0000:00: resource 9 [mem 0x000c8000-0x000cbfff window] [ 2.372368] pci_bus 0000:00: resource 10 [mem 0x000cc000-0x000cffff window] [ 2.379337] pci_bus 0000:00: resource 11 [mem 0x000d0000-0x000d3fff window] [ 2.386303] pci_bus 0000:00: resource 12 [mem 0x000d4000-0x000d7fff window] [ 2.393271] pci_bus 0000:00: resource 13 [mem 0x000d8000-0x000dbfff window] [ 2.400239] pci_bus 0000:00: resource 14 [mem 0x000dc000-0x000dffff window] [ 2.407207] pci_bus 0000:00: resource 15 [mem 0x000e0000-0x000e3fff window] [ 2.414178] pci_bus 0000:00: resource 16 [mem 0x000e4000-0x000e7fff window] [ 2.421143] pci_bus 0000:00: resource 17 [mem 0x000e8000-0x000ebfff window] [ 2.428116] pci_bus 0000:00: resource 18 [mem 0x000ec000-0x000effff window] [ 2.435084] pci_bus 0000:00: resource 19 [mem 0xe0000000-0xf7ffffff window] [ 2.442055] pci_bus 0000:00: resource 20 [mem 0xfc000000-0xfeafffff window] [ 2.449025] pci_bus 0000:01: resource 1 [mem 0xf0600000-0xf06fffff] [ 2.455300] pci_bus 0000:01: resource 2 [mem 0xf0000000-0xf00fffff 64bit pref] [ 2.462529] pci_bus 0000:02: resource 2 [mem 0xf0000000-0xf00fffff 64bit pref] [ 2.469757] pci_bus 0000:03: resource 2 [mem 0xf0000000-0xf00fffff 64bit pref] [ 2.476988] pci_bus 0000:05: resource 0 [io 0x2000-0x2fff] [ 2.482568] pci_bus 0000:05: resource 1 [mem 0xf0500000-0xf05fffff] [ 2.488844] pci_bus 0000:05: resource 2 [mem 0xe0000000-0xefffffff 64bit pref] [ 2.496077] pci_bus 0000:06: resource 1 [mem 0xf0200000-0xf04fffff] [ 2.502351] pci_bus 0000:07: resource 1 [mem 0xf0100000-0xf01fffff] [ 2.508799] pci 0000:05:00.1: D0 power state depends on 0000:05:00.0 [ 2.515298] PCI: CLS 0 bytes, default 64 [ 2.519240] AMD-Vi: [Firmware Warn]: EFR mismatch. Use IVHD EFR (0xf77ef22294ada : 0x400f77ef22294ada). [ 2.519270] Trying to unpack rootfs image as initramfs... [ 2.528645] pci 0000:00:00.2: AMD-Vi: IOMMU performance counters supported [ 2.540984] pci 0000:00:00.2: can't derive routing for PCI INT A [ 2.547002] pci 0000:00:00.2: PCI INT A: not connected [ 2.552171] pci 0000:00:01.0: Adding to iommu group 0 [ 2.557240] pci 0000:00:01.3: Adding to iommu group 1 [ 2.562311] pci 0000:00:02.0: Adding to iommu group 2 [ 2.567408] pci 0000:00:03.0: Adding to iommu group 3 [ 2.572484] pci 0000:00:03.1: Adding to iommu group 4 [ 2.577556] pci 0000:00:04.0: Adding to iommu group 5 [ 2.582631] pci 0000:00:07.0: Adding to iommu group 6 [ 2.587703] pci 0000:00:07.1: Adding to iommu group 6 [ 2.592775] pci 0000:00:08.0: Adding to iommu group 7 [ 2.597847] pci 0000:00:08.1: Adding to iommu group 7 [ 2.598418] Freeing initrd memory: 5136K [ 2.602918] pci 0000:00:14.0: Adding to iommu group 8 [ 2.611901] pci 0000:00:14.3: Adding to iommu group 8 [ 2.616992] pci 0000:00:18.0: Adding to iommu group 9 [ 2.622064] pci 0000:00:18.1: Adding to iommu group 9 [ 2.627131] pci 0000:00:18.2: Adding to iommu group 9 [ 2.632199] pci 0000:00:18.3: Adding to iommu group 9 [ 2.637265] pci 0000:00:18.4: Adding to iommu group 9 [ 2.642334] pci 0000:00:18.5: Adding to iommu group 9 [ 2.647404] pci 0000:00:18.6: Adding to iommu group 9 [ 2.652471] pci 0000:00:18.7: Adding to iommu group 9 [ 2.657549] pci 0000:01:00.0: Adding to iommu group 10 [ 2.662703] pci 0000:01:00.1: Adding to iommu group 10 [ 2.667859] pci 0000:01:00.2: Adding to iommu group 10 [ 2.673009] pci 0000:02:00.0: Adding to iommu group 10 [ 2.678155] pci 0000:02:01.0: Adding to iommu group 10 [ 2.683299] pci 0000:03:00.0: Adding to iommu group 10 [ 2.688457] pci 0000:05:00.0: Adding to iommu group 11 [ 2.693617] pci 0000:05:00.1: Adding to iommu group 11 [ 2.698765] pci 0000:06:00.0: Adding to iommu group 6 [ 2.703824] pci 0000:06:00.2: Adding to iommu group 6 [ 2.708886] pci 0000:06:00.3: Adding to iommu group 6 [ 2.713953] pci 0000:07:00.0: Adding to iommu group 7 [ 2.719011] pci 0000:07:00.2: Adding to iommu group 7 [ 2.724072] pci 0000:07:00.3: Adding to iommu group 7 [ 2.730322] pci 0000:00:00.2: AMD-Vi: Found IOMMU cap 0x40 [ 2.735819] AMD-Vi: Extended features (0x400f77ef22294ada): PPR NX GT IA GA PC GA_vAPIC [ 2.743837] AMD-Vi: Interrupt remapping enabled [ 2.748376] AMD-Vi: Virtual APIC enabled [ 2.752387] software IO TLB: tearing down default memory pool [ 2.758895] RAPL PMU: API unit is 2^-32 Joules, 1 fixed counters, 163840 ms ovfl timer [ 2.766819] RAPL PMU: hw unit of domain package 2^-16 Joules [ 2.772490] amd_uncore: 4 amd_df counters detected [ 2.777374] amd_uncore: 6 amd_l3 counters detected [ 2.782356] perf/amd_iommu: Detected AMD IOMMU #0 (2 banks, 4 counters/bank). [ 2.789801] Initialise system trusted keyrings [ 2.794289] workingset: timestamp_bits=40 max_order=22 bucket_order=0 [ 2.800788] zbud: loaded [ 2.803371] SGI XFS with ACLs, security attributes, realtime, quota, no debug enabled [ 2.811365] xor: automatically using best checksumming function avx [ 2.818423] Key type asymmetric registered [ 2.822524] Asymmetric key parser 'x509' registered [ 2.827422] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 247) [ 2.834848] io scheduler mq-deadline registered [ 2.839389] io scheduler kyber registered [ 2.843529] pcieport 0000:00:01.3: PME: Signaling with IRQ 26 [ 2.849382] pcieport 0000:00:03.1: PME: Signaling with IRQ 27 [ 2.855230] pcieport 0000:00:07.1: PME: Signaling with IRQ 28 [ 2.861123] pcieport 0000:00:08.1: PME: Signaling with IRQ 30 [ 2.867222] IPMI message handler: version 39.2 [ 2.871722] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0 [ 2.880094] ACPI: button: Power Button [PWRB] [ 2.884505] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1 [ 2.891932] ACPI: button: Power Button [PWRF] [ 2.896858] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled [ 2.903347] 00:04: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A [ 2.911359] lp: driver loaded but no devices found [ 2.916289] Linux agpgart interface v0.103 [ 2.923437] brd: module loaded [ 2.927688] loop: module loaded [ 2.932239] drbd: initialized. Version: 8.4.11 (api:1/proto:86-101) [ 2.938574] drbd: built-in [ 2.941342] drbd: registered as block device major 147 [ 2.946645] megaraid cmm: 2.20.2.7 (Release Date: Sun Jul 16 00:01:03 EST 2006) [ 2.954059] megaraid: 2.20.5.1 (Release Date: Thu Nov 16 15:32:35 EST 2006) [ 2.961096] megasas: 07.717.02.00-rc1 [ 2.964835] mpt3sas version 39.100.00.00 loaded [ 2.969692] ahci 0000:01:00.1: version 3.0 [ 2.970061] ahci 0000:01:00.1: SSS flag set, parallel bus scan disabled [ 2.977056] ahci 0000:01:00.1: AHCI 0001.0301 32 slots 8 ports 6 Gbps 0x33 impl SATA mode [ 2.985295] ahci 0000:01:00.1: flags: 64bit ncq sntf stag pm led clo only pmp pio slum part sxs deso sadm sds apst [ 2.996496] scsi host0: ahci [ 2.999642] scsi host1: ahci [ 3.002706] scsi host2: ahci [ 3.005797] scsi host3: ahci [ 3.008871] scsi host4: ahci [ 3.011970] scsi host5: ahci [ 3.015098] scsi host6: ahci [ 3.018236] scsi host7: ahci [ 3.021215] ata1: SATA max UDMA/133 abar m131072@0xf0600000 port 0xf0600100 irq 36 [ 3.028852] ata2: SATA max UDMA/133 abar m131072@0xf0600000 port 0xf0600180 irq 36 [ 3.036492] ata3: DUMMY [ 3.039010] ata4: DUMMY [ 3.041524] ata5: SATA max UDMA/133 abar m131072@0xf0600000 port 0xf0600300 irq 36 [ 3.049159] ata6: SATA max UDMA/133 abar m131072@0xf0600000 port 0xf0600380 irq 36 [ 3.056799] ata7: DUMMY [ 3.059304] ata8: DUMMY [ 3.062220] ahci 0000:07:00.2: AHCI 0001.0301 32 slots 1 ports 6 Gbps 0x1 impl SATA mode [ 3.070367] ahci 0000:07:00.2: flags: 64bit ncq sntf ilck pm led clo only pmp fbs pio slum part [ 3.079523] scsi host8: ahci [ 3.082490] ata9: SATA max UDMA/133 abar m4096@0xf0108000 port 0xf0108100 irq 38 [ 3.090177] libphy: Fixed MDIO Bus: probed [ 3.094346] tun: Universal TUN/TAP device driver, 1.6 [ 3.112235] tg3 0000:03:00.0 eth0: Tigon3 [partno(BCM95762) rev 5762100] (PCI Express) MAC address d8:9e:f3:2a:ef:e4 [ 3.122834] tg3 0000:03:00.0 eth0: attached PHY is 5762C (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[1]) [ 3.132729] tg3 0000:03:00.0 eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] TSOcap[1] [ 3.140618] tg3 0000:03:00.0 eth0: dma_rwctrl[00000001] dma_mask[64-bit] [ 3.147996] e100: Intel(R) PRO/100 Network Driver [ 3.152757] e100: Copyright(c) 1999-2006 Intel Corporation [ 3.158309] e1000: Intel(R) PRO/1000 Network Driver [ 3.163243] e1000: Copyright (c) 1999-2006 Intel Corporation. [ 3.169060] e1000e: Intel(R) PRO/1000 Network Driver [ 3.174095] e1000e: Copyright(c) 1999 - 2015 Intel Corporation. [ 3.180086] igb: Intel(R) Gigabit Ethernet Network Driver [ 3.185542] igb: Copyright (c) 2007-2014 Intel Corporation. [ 3.191182] igbvf: Intel(R) Gigabit Virtual Function Network Driver [ 3.197512] igbvf: Copyright (c) 2009 - 2012 Intel Corporation. [ 3.203506] sky2: driver version 1.30 [ 3.207311] Fusion MPT base driver 3.04.20 [ 3.211461] Copyright (c) 1999-2008 LSI Corporation [ 3.216411] Fusion MPT SPI Host driver 3.04.20 [ 3.220931] Fusion MPT FC Host driver 3.04.20 [ 3.225366] Fusion MPT SAS Host driver 3.04.20 [ 3.229885] Fusion MPT misc device (ioctl) driver 3.04.20 [ 3.235406] mptctl: Registered with Fusion MPT base driver [ 3.240950] mptctl: /dev/mptctl @ (major,minor=10,220) [ 3.246151] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 3.252746] ehci-pci: EHCI PCI platform driver [ 3.257252] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [ 3.263496] ohci-pci: OHCI PCI platform driver [ 3.268002] uhci_hcd: USB Universal Host Controller Interface driver [ 3.274469] xhci_hcd 0000:01:00.0: xHCI Host Controller [ 3.279745] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 1 [ 3.342980] xhci_hcd 0000:01:00.0: hcc params 0x0200ef81 hci version 0x110 quirks 0x0000010048000410 [ 3.352872] xhci_hcd 0000:01:00.0: xHCI Host Controller [ 3.358162] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 2 [ 3.365613] xhci_hcd 0000:01:00.0: Host supports USB 3.1 Enhanced SuperSpeed [ 3.372874] hub 1-0:1.0: USB hub found [ 3.376777] hub 1-0:1.0: 10 ports detected [ 3.381614] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM. [ 3.389873] hub 2-0:1.0: USB hub found [ 3.393723] hub 2-0:1.0: 4 ports detected [ 3.397927] usb: port power management may be unreliable [ 3.404074] xhci_hcd 0000:06:00.3: xHCI Host Controller [ 3.405503] ata9: SATA link down (SStatus 0 SControl 300) [ 3.409367] xhci_hcd 0000:06:00.3: new USB bus registered, assigned bus number 3 [ 3.418774] tsc: Refined TSC clocksource calibration: 3493.378 MHz [ 3.422770] xhci_hcd 0000:06:00.3: hcc params 0x0270f665 hci version 0x100 quirks 0x0000000040000410 [ 3.428506] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x325ae149e20, max_idle_ns: 440795289459 ns [ 3.438818] xhci_hcd 0000:06:00.3: xHCI Host Controller [ 3.453027] clocksource: Switched to clocksource tsc [ 3.453028] xhci_hcd 0000:06:00.3: new USB bus registered, assigned bus number 4 [ 3.465430] xhci_hcd 0000:06:00.3: Host supports USB 3.0 SuperSpeed [ 3.471979] hub 3-0:1.0: USB hub found [ 3.475829] hub 3-0:1.0: 4 ports detected [ 3.480179] usb usb4: We don't know the algorithms for LPM for this host, disabling LPM. [ 3.488415] hub 4-0:1.0: USB hub found [ 3.492268] hub 4-0:1.0: 4 ports detected [ 3.496586] usbcore: registered new interface driver usb-storage [ 3.502783] i8042: PNP: No PS/2 controller found. [ 3.507542] i8042: Probing ports directly. [ 3.513182] serio: i8042 KBD port at 0x60,0x64 irq 1 [ 3.518211] serio: i8042 AUX port at 0x60,0x64 irq 12 [ 3.522885] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 3.523579] rtc_cmos 00:01: RTC can wake from S4 [ 3.535396] rtc_cmos 00:01: registered as rtc0 [ 3.540222] rtc_cmos 00:01: setting system clock to 2021-10-27T15:52:32 UTC (1635349952) [ 3.548392] rtc_cmos 00:01: alarms up to one month, y3k, 114 bytes nvram, hpet irqs [ 3.556205] efifb: probing for efifb [ 3.559287] ata1.00: ATA-8: ST500LM021-1KJ152, 0005SDM1, max UDMA/133 [ 3.559851] efifb: framebuffer at 0xe0000000, using 5632k, total 5632k [ 3.566344] ata1.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 32) [ 3.572934] efifb: mode is 1600x900x32, linelength=6400, pages=1 [ 3.585615] efifb: scrolling: redraw [ 3.589259] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0 [ 3.596926] Console: switching to colour frame buffer device 200x56 [ 3.605173] fb0: EFI VGA frame buffer device [ 3.609522] EFI Variables Facility v0.08 2004-May-17 [ 3.655335] hid: raw HID events driver (C) Jiri Kosina [ 3.660656] usbcore: registered new interface driver usbhid [ 3.666307] usbhid: USB HID core driver [ 3.670296] Key type dns_resolver registered [ 3.674682] ata1.00: configured for UDMA/133 [ 3.679386] scsi 0:0:0:0: Direct-Access ATA ST500LM021-1KJ15 SDM1 PQ: 0 ANSI: 5 [ 3.679443] microcode: CPU0: patch_level=0x08001137 [ 3.687651] scsi 0:0:0:0: Attached scsi generic sg0 type 0 [ 3.692497] microcode: CPU1: patch_level=0x08001137 [ 3.692538] sd 0:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/466 GiB) [ 3.692540] sd 0:0:0:0: [sda] 4096-byte physical blocks [ 3.692545] sd 0:0:0:0: [sda] Write Protect is off [ 3.692546] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [ 3.692553] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 3.726730] usb 3-2: new low-speed USB device number 2 using xhci_hcd [ 3.729699] microcode: CPU2: patch_level=0x08001137 [ 3.741125] microcode: CPU3: patch_level=0x08001137 [ 3.746077] microcode: CPU4: patch_level=0x08001137 [ 3.751041] microcode: CPU5: patch_level=0x08001137 [ 3.755988] microcode: CPU6: patch_level=0x08001137 [ 3.760973] microcode: CPU7: patch_level=0x08001137 [ 3.765909] microcode: Microcode Update Driver: v2.2. [ 3.765912] IPI shorthand broadcast: enabled [ 3.773638] sda: sda1 sda2 sda3 [ 3.775400] sched_clock: Marking stable (2482438658, 1292935769)->(4910510775, -1135136348) [ 3.778798] sd 0:0:0:0: [sda] Attached SCSI disk [ 3.787319] registered taskstats version 1 [ 3.795947] Loading compiled-in X.509 certificates [ 3.801586] Loaded X.509 cert 'Build time autogenerated kernel key: 7a4fdf53e64e4e4b389e2ee43c5487ca6284f7c3' [ 3.811664] zswap: loaded using pool lzo/zbud [ 3.934112] input: Fujitsu Fujitsu Keyboard as /devices/pci0000:00/0000:00:07.1/0000:06:00.3/usb3/3-2/3-2:1.0/0003:0BF8:101E.0001/input/input6 [ 3.998800] hid-generic 0003:0BF8:101E.0001: input,hidraw0: USB HID v1.10 Keyboard [Fujitsu Fujitsu Keyboard] on usb-0000:06:00.3-2/input0 [ 4.013329] ata2: SATA link down (SStatus 0 SControl 300) [ 4.035118] input: Fujitsu Fujitsu Keyboard System Control as /devices/pci0000:00/0000:00:07.1/0000:06:00.3/usb3/3-2/3-2:1.1/0003:0BF8:101E.0002/input/input7 [ 4.101779] input: Fujitsu Fujitsu Keyboard Consumer Control as /devices/pci0000:00/0000:00:07.1/0000:06:00.3/usb3/3-2/3-2:1.1/0003:0BF8:101E.0002/input/input8 [ 4.116781] hid-generic 0003:0BF8:101E.0002: input,hidraw1: USB HID v1.10 Device [Fujitsu Fujitsu Keyboard] on usb-0000:06:00.3-2/input1 [ 4.243738] usb 3-3: new low-speed USB device number 3 using xhci_hcd [ 4.328300] ata5: SATA link down (SStatus 0 SControl 300) [ 4.435056] input: Logitech USB Optical Mouse as /devices/pci0000:00/0000:00:07.1/0000:06:00.3/usb3/3-3/3-3:1.0/0003:046D:C077.0003/input/input9 [ 4.448833] hid-generic 0003:046D:C077.0003: input,hidraw2: USB HID v1.11 Mouse [Logitech USB Optical Mouse] on usb-0000:06:00.3-3/input0 [ 4.640260] ata6: SATA link down (SStatus 0 SControl 300) [ 4.647636] Freeing unused kernel image (initmem) memory: 1700K [ 4.654335] Write protecting the kernel read-only data: 20480k [ 4.661448] Freeing unused kernel image (text/rodata gap) memory: 2032K [ 4.669004] Freeing unused kernel image (rodata/data gap) memory: 212K [ 4.676297] Run /init as init process [ 4.680714] with arguments: [ 4.680715] /init [ 4.680716] with environment: [ 4.680717] HOME=/ [ 4.680717] TERM=linux [ 4.680718] BOOT_IMAGE=/boot/bzImage-5.15.0-rc7.mx64.407 [ 4.680718] crashkernel=256M [ 4.971888] XFS (sda1): Mounting V5 Filesystem [ 5.151691] XFS (sda1): Ending clean mount [ 6.501731] systemd[1]: Inserted module 'autofs4' [ 6.804283] NET: Registered PF_INET6 protocol family [ 6.810363] Segment Routing with IPv6 [ 6.814813] In-situ OAM (IOAM) with IPv6 [ 6.854111] NET: Registered PF_UNIX/PF_LOCAL protocol family [ 6.860611] systemd[1]: Inserted module 'unix' [ 7.366835] systemd[1]: systemd 242 running in system mode. (+PAM -AUDIT -SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP -LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 -SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid) [ 7.401781] systemd[1]: Detected architecture x86-64. [ 7.446037] systemd[1]: Set hostname to <serotimor.molgen.mpg.de>. [ 9.590505] systemd[1]: Listening on Journal Socket (/dev/log). [ 9.599619] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point. [ 9.613202] systemd[1]: Listening on initctl Compatibility Named Pipe. [ 9.623236] systemd[1]: Started Dispatch Password Requests to Console Directory Watch. [ 9.635036] systemd[1]: Started Forward Password Requests to Wall Directory Watch. [ 9.646818] systemd[1]: Created slice system-serial\x2dlog.slice. [ 9.656407] systemd[1]: Reached target Swap. [ 10.394340] RPC: Registered named UNIX socket transport module. [ 10.401857] RPC: Registered udp transport module. [ 10.408023] RPC: Registered tcp transport module. [ 10.414173] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 11.475939] Installing knfsd (copyright (C) 1996 okir@monad.swb.de). [ 11.738900] systemd-journald[181]: Received request to flush runtime journal from PID 1 [ 12.529108] piix4_smbus 0000:00:14.0: SMBus Host Controller at 0xb00, revision 0 [ 12.538752] piix4_smbus 0000:00:14.0: Using register 0x02 for SMBus port selection [ 12.547509] piix4_smbus 0000:00:14.0: Auxiliary SMBus Host Controller at 0xb20 [ 12.608079] acpi_cpufreq: overriding BIOS provided _PSD data [ 12.621155] wmi_bus wmi_bus-PNP0C14:00: WQBC data block query control method not found [ 12.630666] acpi PNP0C14:01: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00) [ 13.077533] pstore: Using crash dump compression: deflate [ 13.085240] pstore: Registered efi as persistent store backend [ 13.668722] snd_hda_intel 0000:05:00.1: enabling device (0000 -> 0002) [ 13.677870] snd_hda_intel 0000:05:00.1: Force to non-snoop mode [ 13.686860] snd_hda_intel 0000:07:00.3: enabling device (0000 -> 0002) [ 13.927872] input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:03.1/0000:05:00.1/sound/card0/input10 [ 13.940585] input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:03.1/0000:05:00.1/sound/card0/input11 [ 14.116032] snd_hda_codec_realtek hdaudioC1D0: autoconfig for ALC3234: line_outs=1 (0x1b/0x0/0x0/0x0/0x0) type:line [ 14.128006] snd_hda_codec_realtek hdaudioC1D0: speaker_outs=1 (0x14/0x0/0x0/0x0/0x0) [ 14.137518] snd_hda_codec_realtek hdaudioC1D0: hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [ 14.147718] snd_hda_codec_realtek hdaudioC1D0: mono: mono_out=0x0 [ 14.156333] snd_hda_codec_realtek hdaudioC1D0: inputs: [ 14.163264] snd_hda_codec_realtek hdaudioC1D0: Headset Mic=0x19 [ 14.171801] snd_hda_codec_realtek hdaudioC1D0: Headphone Mic=0x1a [ 14.266631] kvm: Nested Virtualization enabled [ 14.273744] SVM: kvm: Nested Paging enabled [ 14.280183] SVM: Virtual VMLOAD VMSAVE supported [ 14.280793] input: HD-Audio Generic Headphone Mic as /devices/pci0000:00/0000:00:08.1/0000:07:00.3/sound/card1/input12 [ 14.286821] SVM: Virtual GIF supported [ 14.299982] input: HD-Audio Generic Line Out as /devices/pci0000:00/0000:00:08.1/0000:07:00.3/sound/card1/input13 [ 21.862639] [drm] amdgpu kernel modesetting enabled. [ 21.869174] checking generic (e0000000 580000) vs hw (e0000000 10000000) [ 21.869176] fb0: switching to amdgpu from EFI VGA [ 21.875414] Console: switching to colour dummy device 80x25 [ 21.881973] amdgpu 0000:05:00.0: vgaarb: deactivate vga console [ 21.889204] amdgpu 0000:05:00.0: enabling device (0006 -> 0007) [ 21.896301] [drm] initializing kernel modesetting (OLAND 0x1002:0x6611 0x1028:0x1002 0x87). [ 21.906152] amdgpu 0000:05:00.0: amdgpu: Trusted Memory Zone (TMZ) feature not supported [ 21.915624] [drm] register mmio base: 0xF0500000 [ 21.921003] [drm] register mmio size: 262144 [ 21.926053] [drm] add ip block number 0 <si_common> [ 21.931750] [drm] add ip block number 1 <gmc_v6_0> [ 21.937386] [drm] add ip block number 2 <si_ih> [ 21.942680] [drm] add ip block number 3 <gfx_v6_0> [ 21.948315] [drm] add ip block number 4 <si_dma> [ 21.953720] [drm] add ip block number 5 <si_dpm> [ 21.959153] [drm] add ip block number 6 <dce_v6_0> [ 21.964787] [drm] add ip block number 7 <uvd_v3_1> [ 21.970427] amdgpu 0000:05:00.0: amdgpu: Fetched VBIOS from VFCT [ 21.977447] amdgpu: ATOM BIOS: 113-C8690301-102 [ 21.982896] [drm] vm size is 64 GB, 2 levels, block size is 10-bit, fragment size is 9-bit [ 22.044359] amdgpu 0000:05:00.0: amdgpu: VRAM: 2048M 0x000000F400000000 - 0x000000F47FFFFFFF (2048M used) [ 22.056487] amdgpu 0000:05:00.0: amdgpu: GART: 1024M 0x000000FF00000000 - 0x000000FF3FFFFFFF [ 22.066767] [drm] Detected VRAM RAM=2048M, BAR=256M [ 22.072499] [drm] RAM width 64bits GDDR5 [ 22.080208] [drm] amdgpu: 2048M of VRAM memory ready [ 22.086015] [drm] amdgpu: 3072M of GTT memory ready. [ 22.092095] [drm] GART: num cpu pages 262144, num gpu pages 262144 [ 22.100997] amdgpu 0000:05:00.0: amdgpu: PCIE GART of 1024M enabled (table at 0x000000F40057F000). [ 22.289396] [drm] Internal thermal controller with fan control [ 22.296859] [drm] amdgpu: dpm initialized [ 22.302026] [drm] AMDGPU Display Connectors [ 22.306997] [drm] Connector 0: [ 22.310611] [drm] DP-1 [ 22.313595] [drm] HPD1 [ 22.316829] [drm] DDC: 0x1950 0x1950 0x1951 0x1951 0x1952 0x1952 0x1953 0x1953 [ 22.325470] [drm] Encoders: [ 22.328987] [drm] DFP1: INTERNAL_UNIPHY [ 22.334118] [drm] Connector 1: [ 22.337731] [drm] DVI-I-1 [ 22.341224] [drm] HPD2 [ 22.344266] [drm] DDC: 0x194c 0x194c 0x194d 0x194d 0x194e 0x194e 0x194f 0x194f [ 22.352935] [drm] Encoders: [ 22.356403] [drm] DFP2: INTERNAL_UNIPHY [ 22.361303] [drm] CRT1: INTERNAL_KLDSCP_DAC1 [ 22.415670] [drm] Found UVD firmware Version: 64.0 Family ID: 13 [ 22.425018] [drm] PCIE gen 3 link speeds already enabled [ 22.432034] amdgpu 0000:05:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000c address=0xfffffe0000 flags=0x0020] [ 22.444890] amdgpu 0000:05:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000c address=0xffffffc000 flags=0x0020] [ 22.809410] amdgpu 0000:05:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000c address=0xfffffde000 flags=0x0000] [ 22.821262] amdgpu 0000:05:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000c address=0xfffffde100 flags=0x0000] [ 22.833199] amdgpu 0000:05:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000c address=0xfffffde200 flags=0x0000] [ 22.845105] amdgpu 0000:05:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000c address=0xfffffde300 flags=0x0000] [ 22.856634] amdgpu 0000:05:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000c address=0xffffffc040 flags=0x0020] [ 22.868630] amdgpu 0000:05:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000c address=0xfffffde400 flags=0x0000] [ 22.880516] amdgpu 0000:05:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000c address=0xfffffde500 flags=0x0000] [ 22.892546] amdgpu 0000:05:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000c address=0xfffffde600 flags=0x0000] [ 23.179596] amdgpu 0000:05:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring gfx test failed (-110) [ 23.190562] [drm:amdgpu_device_init [amdgpu]] *ERROR* hw_init of IP block <gfx_v6_0> failed -110 [ 23.200405] amdgpu 0000:05:00.0: amdgpu: amdgpu_device_ip_init failed [ 23.207524] amdgpu 0000:05:00.0: amdgpu: Fatal error during GPU init [ 23.214632] amdgpu 0000:05:00.0: amdgpu: amdgpu: finishing device. [ 23.222739] amdgpu: probe of 0000:05:00.0 failed with error -110 [ 23.229552] BUG: unable to handle page fault for address: 0000000000005e00 [ 23.237233] #PF: supervisor write access in kernel mode [ 23.243081] #PF: error_code(0x0002) - not-present page [ 23.248858] PGD 103731067 P4D 103731067 PUD 103732067 PMD 0 [ 23.255217] Oops: 0002 [#1] SMP NOPTI [ 23.259350] CPU: 4 PID: 214 Comm: systemd-udevd Not tainted 5.15.0-rc7.mx64.407 #1 [ 23.267824] Hardware name: Dell Inc. OptiPlex 5055 Ryzen CPU/0P03DX, BIOS 1.1.50 07/28/2021 [ 23.277214] RIP: 0010:amdgpu_device_wreg.part.26+0x5d/0xe0 [amdgpu] [ 23.284441] Code: 8e e1 8b 05 4d c3 5e 00 85 c0 7f 2c 5b 5d 41 5c 41 5d 41 5e c3 83 e1 02 75 09 f6 87 60 69 01 00 10 75 4d 48 03 ab 60 09 00 00 <44> 89 6d 00 8b 05 21 c3 5e 00 85 c0 7e d4 48 8b 43 08 0f b7 70 3e [ 23.305471] RSP: 0018:ffffc90000ceba68 EFLAGS: 00010006 [ 23.311432] RAX: 0000000000000246 RBX: ffff88812f300000 RCX: 0000000000000000 [ 23.319490] RDX: 0000000000000154 RSI: 0000000000001780 RDI: ffff88812f300000 [ 23.327501] RBP: 0000000000005e00 R08: ffffffffa0586860 R09: ffff88841effab00 [ 23.335512] R10: 0000000000000000 R11: 000ffffffffff000 R12: 0000000000001780 [ 23.343473] R13: 0000000000000154 R14: 0000000000000246 R15: ffff88812f300a30 [ 23.351461] FS: 00007f6ece88b800(0000) GS:ffff88840eb00000(0000) knlGS:0000000000000000 [ 23.360556] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 23.367102] CR2: 0000000000005e00 CR3: 0000000107f2e000 CR4: 00000000003506e0 [ 23.375103] Call Trace: [ 23.377828] dce_v6_0_audio_endpt_wreg+0x42/0x70 [amdgpu] [ 23.384104] dce_v6_0_sw_fini+0x7f/0xe0 [amdgpu] [ 23.389484] amdgpu_device_fini_sw+0xb1/0x290 [amdgpu] [ 23.395367] amdgpu_driver_release_kms+0x12/0x30 [amdgpu] [ 23.401600] drm_dev_release+0x23/0x40 [drm] [ 23.406439] release_nodes+0x44/0xa0 [ 23.410527] devres_release_all+0x92/0xc0 [ 23.415028] really_probe+0x106/0x470 [ 23.419188] __driver_probe_device+0x81/0x170 [ 23.424080] driver_probe_device+0x1f/0xa0 [ 23.428710] __driver_attach+0xbd/0x170 [ 23.433027] ? __device_attach_driver+0xf0/0xf0 [ 23.438136] bus_for_each_dev+0x76/0xc0 [ 23.442450] bus_add_driver+0x189/0x230 [ 23.446789] ? 0xffffffffa0b7d000 [ 23.450513] driver_register+0x5b/0xf0 [ 23.454753] ? 0xffffffffa0b7d000 [ 23.458459] do_one_initcall+0x4d/0x1e0 [ 23.462826] ? __vunmap+0x1bb/0x210 [ 23.466704] do_init_module+0x5b/0x212 [ 23.470992] load_module+0x2823/0x2c40 [ 23.475150] ? __do_sys_finit_module+0xb1/0x110 [ 23.480272] __do_sys_finit_module+0xb1/0x110 [ 23.485128] do_syscall_64+0x42/0x90 [ 23.489220] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 23.494842] RIP: 0033:0x7f6ecf1f2519 [ 23.498959] Code: 0c 00 b8 ca 00 00 00 0f 05 eb a5 66 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 1f 89 0c 00 f7 d8 64 89 01 48 [ 23.520055] RSP: 002b:00007ffe66832648 EFLAGS: 00000246 ORIG_RAX: 0000000000000139 [ 23.528621] RAX: ffffffffffffffda RBX: 0000000000681470 RCX: 00007f6ecf1f2519 [ 23.536652] RDX: 0000000000000000 RSI: 00007f6ecf35254b RDI: 0000000000000016 [ 23.544680] RBP: 00007f6ecf35254b R08: 0000000000000000 R09: 0000000000020000 [ 23.552728] R10: 0000000000000016 R11: 0000000000000246 R12: 0000000000000000 [ 23.560746] R13: 0000000000675720 R14: 0000000000020000 R15: 0000000000679b90 [ 23.568800] Modules linked in: amdgpu(+) gpu_sched drm_ttm_helper ttm drm_kms_helper kvm_amd snd_ctl_led snd_hda_codec_realtek kvm drm snd_hda_codec_hdmi snd_hda_codec_generic ledtrig_audio snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_hda_core snd_pcm snd_timer fb_sys_fops deflate input_leds syscopyarea led_class sysfillrect sysimgblt snd k10temp efi_pstore wmi_bmof irqbypass wmi acpi_cpufreq soundcore crc32c_intel i2c_piix4 pstore nfsd auth_rpcgss nfs_acl lockd grace sunrpc efivarfs ip_tables x_tables unix ipv6 autofs4 [ 23.620743] CR2: 0000000000005e00 [ 23.624537] ---[ end trace a7c9f1dd6c99f43f ]--- [ 23.880537] RIP: 0010:amdgpu_device_wreg.part.26+0x5d/0xe0 [amdgpu] [ 23.887736] Code: 8e e1 8b 05 4d c3 5e 00 85 c0 7f 2c 5b 5d 41 5c 41 5d 41 5e c3 83 e1 02 75 09 f6 87 60 69 01 00 10 75 4d 48 03 ab 60 09 00 00 <44> 89 6d 00 8b 05 21 c3 5e 00 85 c0 7e d4 48 8b 43 08 0f b7 70 3e [ 23.908898] RSP: 0018:ffffc90000ceba68 EFLAGS: 00010006 [ 23.914812] RAX: 0000000000000246 RBX: ffff88812f300000 RCX: 0000000000000000 [ 23.922872] RDX: 0000000000000154 RSI: 0000000000001780 RDI: ffff88812f300000 [ 23.930895] RBP: 0000000000005e00 R08: ffffffffa0586860 R09: ffff88841effab00 [ 23.938921] R10: 0000000000000000 R11: 000ffffffffff000 R12: 0000000000001780 [ 23.946957] R13: 0000000000000154 R14: 0000000000000246 R15: ffff88812f300a30 [ 23.954998] FS: 00007f6ece88b800(0000) GS:ffff88840eb00000(0000) knlGS:0000000000000000 [ 23.964147] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 23.970638] CR2: 0000000000005e00 CR3: 0000000107f2e000 CR4: 00000000003506e0 [ 27.942588] tg3 0000:03:00.0 net00: renamed from eth0 [ 28.892353] 8021q: 802.1Q VLAN Support v1.8 [ 30.380630] XFS (sda2): Mounting V5 Filesystem [ 30.582163] XFS (sda2): Ending clean mount [ 31.089143] NFSD: Using UMH upcall client tracking operations. [ 31.096579] NFSD: starting 90-second grace period (net f0000098) [ 31.859010] tg3 0000:03:00.0 net00: Link is up at 1000 Mbps, full duplex [ 31.866891] tg3 0000:03:00.0 net00: Flow control is off for TX and off for RX [ 31.874807] tg3 0000:03:00.0 net00: EEE is disabled [ 91.654886] FS-Cache: Netfs 'nfs' registered for caching [ 92.064603] NFS: Registering the id_resolver key type [ 92.070632] Key type id_resolver registered [ 92.075574] Key type id_legacy registered ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: I got an IOMMU IO page fault. What to do now? @ 2021-10-27 16:45 ` Paul Menzel 0 siblings, 0 replies; 18+ messages in thread From: Paul Menzel @ 2021-10-27 16:45 UTC (permalink / raw) To: Robin Murphy Cc: x86, Christian König, Xinhui Pan, LKML, amd-gfx, iommu, Ingo Molnar, Borislav Petkov, Alex Deucher, it+linux-iommu, Thomas Gleixner, Christian König [-- Attachment #1: Type: text/plain, Size: 2019 bytes --] Dear Robin, On 25.10.21 18:01, Robin Murphy wrote: > On 2021-10-25 12:23, Christian König wrote: >> not sure how the IOMMU gives out addresses, but the printed ones look >> suspicious to me. Something like we are using an invalid address like >> -1 or similar. > > FWIW those look like believable DMA addresses to me, assuming that the > DMA mapping APIs are being backed iommu_dma_ops and the device has a > 40-bit DMA mask, since the IOVA allocator works top-down. > > Likely causes are either a race where the dma_unmap_*() call happens > before the hardware has really stopped accessing the relevant addresses, > or the device's DMA mask has been set larger than it should be, and thus > the upper bits have been truncated in the round-trip through the hardware. > > Given the addresses involved, my suspicions would initially lean towards > the latter case - the faults are in the very topmost pages which imply > they're the first things mapped in that range. The other contributing > factor being the trick that the IOVA allocator plays for PCI devices, > where it tries to prefer 32-bit addresses. Thus you're only likely to > see this happen once you already have ~3.5-4GB of live DMA-mapped memory > to exhaust the 32-bit IOVA space (minus some reserved areas) and start > allocating from the full DMA mask. You should be able to check that with > a 5.13 or newer kernel by booting with "iommu.forcedac=1" and seeing if > it breaks immediately (unfortunately with an older kernel you'd have to > manually hack iommu_dma_alloc_iova() to the same effect). I booted Linux 5.15-rc7 with `iommu.forcedac=1` and the system booted, and I could log in remotely over SSH. Please find the Linux kernel messages attached. (The system logs say lightdm failed to start, but it might be some other issue due to a change in the operating system.) >> Can you try that on an up to date kernel as well? E.g. ideally >> bleeding edge amd-staging-drm-next from Alex repository. Kind regards, Paul [-- Attachment #2: 20211027–linux-5.15-rc7–dell-optiplex-5055–iommu.forcedac.txt --] [-- Type: text/plain, Size: 65662 bytes --] [ 0.000000] Linux version 5.15.0-rc7.mx64.407 (root@theinternet.molgen.mpg.de) (gcc (GCC) 7.5.0, GNU ld (GNU Binutils) 2.37) #1 SMP Tue Oct 26 04:00:49 CEST 2021 [ 0.000000] Command line: BOOT_IMAGE=/boot/bzImage-5.15.0-rc7.mx64.407 root=LABEL=root ro crashkernel=256M console=ttyS0,115200n8 console=tty0 init=/bin/systemd audit=0 random.trust_cpu=on iommu.forcedac=1 [ 0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' [ 0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' [ 0.000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' [ 0.000000] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 [ 0.000000] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'compacted' format. [ 0.000000] signal: max sigframe size: 1776 [ 0.000000] BIOS-provided physical RAM map: [ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x0000000000087fff] usable [ 0.000000] BIOS-e820: [mem 0x0000000000088000-0x0000000000088fff] reserved [ 0.000000] BIOS-e820: [mem 0x0000000000089000-0x000000000009ffff] usable [ 0.000000] BIOS-e820: [mem 0x00000000000a0000-0x00000000000bffff] reserved [ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x0000000009cfffff] usable [ 0.000000] BIOS-e820: [mem 0x0000000009d00000-0x0000000009e6ffff] reserved [ 0.000000] BIOS-e820: [mem 0x0000000009e70000-0x00000000dadbefff] usable [ 0.000000] BIOS-e820: [mem 0x00000000dadbf000-0x00000000dafbefff] type 20 [ 0.000000] BIOS-e820: [mem 0x00000000dafbf000-0x00000000dcfbefff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000dcfbf000-0x00000000defbefff] ACPI NVS [ 0.000000] BIOS-e820: [mem 0x00000000defbf000-0x00000000deffefff] ACPI data [ 0.000000] BIOS-e820: [mem 0x00000000defff000-0x00000000deffffff] usable [ 0.000000] BIOS-e820: [mem 0x00000000df000000-0x00000000dfffffff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000fec10000-0x00000000fec10fff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000fed80000-0x00000000fed80fff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved [ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000041effffff] usable [ 0.000000] Forcing DAC for PCI devices [ 0.000000] NX (Execute Disable) protection: active [ 0.000000] efi: EFI v2.50 by EDK II [ 0.000000] efi: TPMFinalLog=0xdefa2000 SMBIOS=0xdbeb5000 SMBIOS 3.0=0xdbeb3000 ACPI 2.0=0xdeffe014 ESRT=0xdbe9f298 MEMATTR=0xd8b6f018 [ 0.000000] SMBIOS 3.0.0 present. [ 0.000000] DMI: Dell Inc. OptiPlex 5055 Ryzen CPU/0P03DX, BIOS 1.1.50 07/28/2021 [ 0.000000] tsc: Fast TSC calibration using PIT [ 0.000000] tsc: Detected 3493.349 MHz processor [ 0.001974] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved [ 0.001976] e820: remove [mem 0x000a0000-0x000fffff] usable [ 0.001981] last_pfn = 0x41f000 max_arch_pfn = 0x400000000 [ 0.002281] x86/PAT: Configuration [0-7]: WB WC UC- UC WB WP UC- WT [ 0.002561] last_pfn = 0xdf000 max_arch_pfn = 0x400000000 [ 0.006431] esrt: Reserving ESRT space from 0x00000000dbe9f298 to 0x00000000dbe9f2d0. [ 0.006441] Using GB pages for direct mapping [ 0.006889] Secure boot could not be determined [ 0.006890] RAMDISK: [mem 0x375e7000-0x37aeafff] [ 0.006893] ACPI: Early table checksum verification disabled [ 0.006896] ACPI: RSDP 0x00000000DEFFE014 000024 (v02 AMD ) [ 0.006900] ACPI: XSDT 0x00000000DEFD9188 000104 (v01 AMD MYRTLE 00000001 01000013) [ 0.006905] ACPI: FACP 0x00000000DEFF0000 00010C (v05 AMD MYRTLE 00000001 ACPI 00040000) [ 0.006910] ACPI: DSDT 0x00000000DEFE8000 0012CB (v01 AMD MYRTLE 00040000 ACPI 00040000) [ 0.006913] ACPI: FACS 0x00000000DEB73000 000040 [ 0.006916] ACPI: SSDT 0x00000000DEFF5000 008C4C (v02 AMD MYRTLE 00000002 ACPI 00040000) [ 0.006918] ACPI: UEFI 0x00000000DEFF4000 000042 (v01 AMD MYRTLE 00000002 ACPI 00040000) [ 0.006921] ACPI: SSDT 0x00000000DEFF3000 0003C6 (v02 AMD MYRTLE 00001000 ACPI 00040000) [ 0.006924] ACPI: TPM2 0x00000000DEFF2000 000034 (v03 AMD MYRTLE 00000002 ACPI 00040000) [ 0.006927] ACPI: ASF! 0x00000000DEFF1000 0000A5 (v32 AMD MYRTLE 00000001 ACPI 00040000) [ 0.006930] ACPI: HPET 0x00000000DEFEF000 000038 (v01 AMD MYRTLE 00000001 ACPI 00040000) [ 0.006933] ACPI: APIC 0x00000000DEFEE000 000138 (v03 AMD MYRTLE 00000001 ACPI 00040000) [ 0.006935] ACPI: MCFG 0x00000000DEFED000 00003C (v01 AMD MYRTLE 00000001 ACPI 00040000) [ 0.006938] ACPI: SPCR 0x00000000DEFEC000 000050 (v01 AMD MYRTLE 00000001 ACPI 00040000) [ 0.006941] ACPI: WDAT 0x00000000DEFEB000 00017C (v01 AMD MYRTLE 00000001 ACPI 00040000) [ 0.006944] ACPI: WDRT 0x00000000DEFEA000 000047 (v01 AMD MYRTLE 00000000 ACPI 00040000) [ 0.006946] ACPI: SSDT 0x00000000DEFE5000 002AC4 (v01 AMD MYRTLE 00000001 ACPI 00040000) [ 0.006949] ACPI: SSDT 0x00000000DEFE4000 0000FC (v01 AMD MYRTLE 00000001 ACPI 00040000) [ 0.006952] ACPI: SSDT 0x00000000DEFDE000 000024 (v01 AMD MYRTLE 00001000 ACPI 00040000) [ 0.006954] ACPI: SSDT 0x00000000DEFDD000 000E0C (v01 AMD MYRTLE 00000001 ACPI 00040000) [ 0.006957] ACPI: CRAT 0x00000000DEFDC000 000850 (v01 AMD MYRTLE 00000001 ACPI 00040000) [ 0.006960] ACPI: CDIT 0x00000000DEFDB000 000029 (v01 AMD MYRTLE 00000001 ACPI 00040000) [ 0.006963] ACPI: BOOT 0x00000000DEFDA000 000028 (v01 AMD MYRTLE 00000002 ACPI 00040000) [ 0.006965] ACPI: SSDT 0x00000000DEFDF000 0048E6 (v01 AMD MYRTLE 00000001 ACPI 00040000) [ 0.006968] ACPI: VFCT 0x00000000DEFC8000 010084 (v01 AMD MYRTLE 00000001 ACPI 00040000) [ 0.006971] ACPI: IVRS 0x00000000DEFC7000 0000D0 (v02 AMD MYRTLE 00000001 ACPI 00040000) [ 0.006973] ACPI: MSDM 0x00000000DEFC6000 000055 (v03 AMD MYRTLE 06222004 ACPI 00040000) [ 0.006976] ACPI: SSDT 0x00000000DEFC5000 000920 (v01 AMD MYRTLE 00001000 ACPI 00040000) [ 0.006979] ACPI: SSDT 0x00000000DEFC4000 0000F8 (v01 AMD MYRTLE 00001000 ACPI 00040000) [ 0.006981] ACPI: SSDT 0x00000000DEFC2000 001768 (v01 AMD MYRTLE 00000001 ACPI 00040000) [ 0.006984] ACPI: FPDT 0x00000000DEFC1000 000044 (v01 AMD MYRTLE 00000002 ACPI 00040000) [ 0.006987] ACPI: BGRT 0x00000000DEFC0000 000038 (v01 AMD MYRTLE 00000002 ACPI 00040000) [ 0.006989] ACPI: Reserving FACP table memory at [mem 0xdeff0000-0xdeff010b] [ 0.006991] ACPI: Reserving DSDT table memory at [mem 0xdefe8000-0xdefe92ca] [ 0.006992] ACPI: Reserving FACS table memory at [mem 0xdeb73000-0xdeb7303f] [ 0.006994] ACPI: Reserving SSDT table memory at [mem 0xdeff5000-0xdeffdc4b] [ 0.006995] ACPI: Reserving UEFI table memory at [mem 0xdeff4000-0xdeff4041] [ 0.006996] ACPI: Reserving SSDT table memory at [mem 0xdeff3000-0xdeff33c5] [ 0.006997] ACPI: Reserving TPM2 table memory at [mem 0xdeff2000-0xdeff2033] [ 0.006999] ACPI: Reserving ASF! table memory at [mem 0xdeff1000-0xdeff10a4] [ 0.007000] ACPI: Reserving HPET table memory at [mem 0xdefef000-0xdefef037] [ 0.007001] ACPI: Reserving APIC table memory at [mem 0xdefee000-0xdefee137] [ 0.007002] ACPI: Reserving MCFG table memory at [mem 0xdefed000-0xdefed03b] [ 0.007003] ACPI: Reserving SPCR table memory at [mem 0xdefec000-0xdefec04f] [ 0.007004] ACPI: Reserving WDAT table memory at [mem 0xdefeb000-0xdefeb17b] [ 0.007006] ACPI: Reserving WDRT table memory at [mem 0xdefea000-0xdefea046] [ 0.007007] ACPI: Reserving SSDT table memory at [mem 0xdefe5000-0xdefe7ac3] [ 0.007008] ACPI: Reserving SSDT table memory at [mem 0xdefe4000-0xdefe40fb] [ 0.007009] ACPI: Reserving SSDT table memory at [mem 0xdefde000-0xdefde023] [ 0.007010] ACPI: Reserving SSDT table memory at [mem 0xdefdd000-0xdefdde0b] [ 0.007012] ACPI: Reserving CRAT table memory at [mem 0xdefdc000-0xdefdc84f] [ 0.007013] ACPI: Reserving CDIT table memory at [mem 0xdefdb000-0xdefdb028] [ 0.007014] ACPI: Reserving BOOT table memory at [mem 0xdefda000-0xdefda027] [ 0.007015] ACPI: Reserving SSDT table memory at [mem 0xdefdf000-0xdefe38e5] [ 0.007016] ACPI: Reserving VFCT table memory at [mem 0xdefc8000-0xdefd8083] [ 0.007017] ACPI: Reserving IVRS table memory at [mem 0xdefc7000-0xdefc70cf] [ 0.007019] ACPI: Reserving MSDM table memory at [mem 0xdefc6000-0xdefc6054] [ 0.007020] ACPI: Reserving SSDT table memory at [mem 0xdefc5000-0xdefc591f] [ 0.007021] ACPI: Reserving SSDT table memory at [mem 0xdefc4000-0xdefc40f7] [ 0.007022] ACPI: Reserving SSDT table memory at [mem 0xdefc2000-0xdefc3767] [ 0.007023] ACPI: Reserving FPDT table memory at [mem 0xdefc1000-0xdefc1043] [ 0.007025] ACPI: Reserving BGRT table memory at [mem 0xdefc0000-0xdefc0037] [ 0.007033] system APIC only can use physical flat [ 0.007034] Setting APIC routing to physical flat. [ 0.007155] No NUMA configuration found [ 0.007156] Faking a node at [mem 0x0000000000000000-0x000000041effffff] [ 0.007160] NODE_DATA(0) allocated [mem 0x41effa000-0x41effefff] [ 0.007167] Reserving 256MB of memory at 3136MB for crashkernel (System RAM: 16283MB) [ 0.007184] Zone ranges: [ 0.007185] DMA [mem 0x0000000000001000-0x0000000000ffffff] [ 0.007187] DMA32 [mem 0x0000000001000000-0x00000000ffffffff] [ 0.007189] Normal [mem 0x0000000100000000-0x000000041effffff] [ 0.007190] Device empty [ 0.007191] Movable zone start for each node [ 0.007192] Early memory node ranges [ 0.007193] node 0: [mem 0x0000000000001000-0x0000000000087fff] [ 0.007194] node 0: [mem 0x0000000000089000-0x000000000009ffff] [ 0.007195] node 0: [mem 0x0000000000100000-0x0000000009cfffff] [ 0.007196] node 0: [mem 0x0000000009e70000-0x00000000dadbefff] [ 0.007198] node 0: [mem 0x00000000defff000-0x00000000deffffff] [ 0.007199] node 0: [mem 0x0000000100000000-0x000000041effffff] [ 0.007201] Initmem setup node 0 [mem 0x0000000000001000-0x000000041effffff] [ 0.007205] On node 0, zone DMA: 1 pages in unavailable ranges [ 0.007206] On node 0, zone DMA: 1 pages in unavailable ranges [ 0.007225] On node 0, zone DMA: 96 pages in unavailable ranges [ 0.013935] On node 0, zone DMA32: 368 pages in unavailable ranges [ 0.014099] On node 0, zone DMA32: 16960 pages in unavailable ranges [ 0.041239] On node 0, zone Normal: 4096 pages in unavailable ranges [ 0.041283] On node 0, zone Normal: 4096 pages in unavailable ranges [ 0.041628] ACPI: PM-Timer IO Port: 0x408 [ 0.041630] system APIC only can use physical flat [ 0.041635] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) [ 0.041636] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) [ 0.041638] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1]) [ 0.041639] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1]) [ 0.041640] ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1]) [ 0.041641] ACPI: LAPIC_NMI (acpi_id[0x05] high edge lint[0x1]) [ 0.041642] ACPI: LAPIC_NMI (acpi_id[0x06] high edge lint[0x1]) [ 0.041643] ACPI: LAPIC_NMI (acpi_id[0x07] high edge lint[0x1]) [ 0.041644] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1]) [ 0.041644] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1]) [ 0.041645] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1]) [ 0.041646] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1]) [ 0.041647] ACPI: LAPIC_NMI (acpi_id[0x0c] high edge lint[0x1]) [ 0.041648] ACPI: LAPIC_NMI (acpi_id[0x0d] high edge lint[0x1]) [ 0.041649] ACPI: LAPIC_NMI (acpi_id[0x0e] high edge lint[0x1]) [ 0.041650] ACPI: LAPIC_NMI (acpi_id[0x0f] high edge lint[0x1]) [ 0.041676] IOAPIC[0]: apic_id 32, version 33, address 0xfec00000, GSI 0-23 [ 0.041681] IOAPIC[1]: apic_id 33, version 33, address 0xfec01000, GSI 24-55 [ 0.041683] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [ 0.041685] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level) [ 0.041688] ACPI: Using ACPI (MADT) for SMP configuration information [ 0.041689] ACPI: HPET id: 0x10228210 base: 0xfed00000 [ 0.041693] ACPI: SPCR: SPCR table version 1 [ 0.041695] ACPI: SPCR: console: uart,io,0x3f8,115200 [ 0.041697] smpboot: Allowing 16 CPUs, 8 hotplug CPUs [ 0.041717] [mem 0xe0000000-0xf7ffffff] available for PCI devices [ 0.041721] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1910969940391419 ns [ 0.045936] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:1 [ 0.046588] percpu: Embedded 49 pages/cpu s163160 r8192 d29352 u262144 [ 0.046595] pcpu-alloc: s163160 r8192 d29352 u262144 alloc=1*2097152 [ 0.046597] pcpu-alloc: [0] 00 01 02 03 04 05 06 07 [0] 08 09 10 11 12 13 14 15 [ 0.046621] Built 1 zonelists, mobility grouping on. Total pages: 4103390 [ 0.046623] Policy zone: Normal [ 0.046624] Kernel command line: BOOT_IMAGE=/boot/bzImage-5.15.0-rc7.mx64.407 root=LABEL=root ro crashkernel=256M console=ttyS0,115200n8 console=tty0 init=/bin/systemd audit=0 random.trust_cpu=on iommu.forcedac=1 [ 0.046701] audit: disabled (until reboot) [ 0.046731] Unknown command line parameters: BOOT_IMAGE=/boot/bzImage-5.15.0-rc7.mx64.407 crashkernel=256M [ 0.048224] Dentry cache hash table entries: 2097152 (order: 12, 16777216 bytes, linear) [ 0.048985] Inode-cache hash table entries: 1048576 (order: 11, 8388608 bytes, linear) [ 0.049025] mem auto-init: stack:off, heap alloc:off, heap free:off [ 0.094071] Memory: 15939164K/16674744K available (14349K kernel code, 3523K rwdata, 3884K rodata, 1700K init, 2608K bss, 735324K reserved, 0K cma-reserved) [ 0.094153] ftrace: allocating 45454 entries in 178 pages [ 0.106225] ftrace: allocated 178 pages with 4 groups [ 0.106304] rcu: Hierarchical RCU implementation. [ 0.106305] rcu: RCU event tracing is enabled. [ 0.106306] rcu: RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16. [ 0.106307] Rude variant of Tasks RCU enabled. [ 0.106308] Tracing variant of Tasks RCU enabled. [ 0.106308] rcu: RCU calculated value of scheduler-enlistment delay is 100 jiffies. [ 0.106310] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=16 [ 0.109576] NR_IRQS: 16640, nr_irqs: 1096, preallocated irqs: 16 [ 0.109862] random: crng done (trusting CPU's manufacturer) [ 0.110077] Console: colour dummy device 80x25 [ 0.110270] printk: console [tty0] enabled [ 1.366681] printk: console [ttyS0] enabled [ 1.370896] ACPI: Core revision 20210730 [ 1.375021] clocksource: hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 133484873504 ns [ 1.384189] APIC: Switch to symmetric I/O mode setup [ 1.392739] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1 [ 1.403189] clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x325ac60cf80, max_idle_ns: 440795363783 ns [ 1.413725] Calibrating delay loop (skipped), value calculated using timer frequency.. 6986.69 BogoMIPS (lpj=3493349) [ 1.414725] pid_max: default: 32768 minimum: 301 [ 1.417758] LSM: Security Framework initializing [ 1.418770] Mount-cache hash table entries: 32768 (order: 6, 262144 bytes, linear) [ 1.419751] Mountpoint-cache hash table entries: 32768 (order: 6, 262144 bytes, linear) [ 1.420950] LVT offset 1 assigned for vector 0xf9 [ 1.421803] LVT offset 2 assigned for vector 0xf4 [ 1.422739] Last level iTLB entries: 4KB 1024, 2MB 1024, 4MB 512 [ 1.423725] Last level dTLB entries: 4KB 1536, 2MB 1536, 4MB 768, 1GB 0 [ 1.424725] Spectre V1 : Mitigation: usercopy/swapgs barriers and __user pointer sanitization [ 1.425726] Spectre V2 : Mitigation: Full AMD retpoline [ 1.426725] Spectre V2 : Spectre v2 / SpectreRSB mitigation: Filling RSB on context switch [ 1.427725] Spectre V2 : mitigation: Enabling conditional Indirect Branch Prediction Barrier [ 1.428725] Speculative Store Bypass: Mitigation: Speculative Store Bypass disabled via prctl and seccomp [ 1.431875] Freeing SMP alternatives memory: 44K [ 1.535795] smpboot: CPU0: AMD Ryzen 5 PRO 1500 Quad-Core Processor (family: 0x17, model: 0x1, stepping: 0x1) [ 1.537774] Performance Events: Fam17h+ core perfctr, AMD PMU driver. [ 1.538725] ... version: 0 [ 1.539725] ... bit width: 48 [ 1.540725] ... generic registers: 6 [ 1.541725] ... value mask: 0000ffffffffffff [ 1.542725] ... max period: 00007fffffffffff [ 1.543725] ... fixed-purpose events: 0 [ 1.544725] ... event mask: 000000000000003f [ 1.545772] rcu: Hierarchical SRCU implementation. [ 1.547053] smp: Bringing up secondary CPUs ... [ 1.547801] x86: Booting SMP configuration: [ 1.548727] .... node #0, CPUs: #1 #2 #3 #4 #5 #6 #7 [ 1.557739] smp: Brought up 1 node, 8 CPUs [ 1.559725] smpboot: Max logical packages: 2 [ 1.560725] smpboot: Total of 8 processors activated (55893.58 BogoMIPS) [ 1.563241] devtmpfs: initialized [ 1.563763] x86/mm: Memory block size: 128MB [ 1.565931] ACPI: PM: Registering ACPI NVS region [mem 0xdcfbf000-0xdefbefff] (33554432 bytes) [ 1.568040] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1911260446275000 ns [ 1.568727] futex hash table entries: 4096 (order: 6, 262144 bytes, linear) [ 1.569891] NET: Registered PF_NETLINK/PF_ROUTE protocol family [ 1.570872] thermal_sys: Registered thermal governor 'step_wise' [ 1.570873] thermal_sys: Registered thermal governor 'user_space' [ 1.571736] cpuidle: using governor menu [ 1.573783] Simple Boot Flag at 0x44 set to 0x80 [ 1.574737] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it [ 1.575725] ACPI: bus type PCI registered [ 1.576756] PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf8000000-0xfbffffff] (base 0xf8000000) [ 1.577727] PCI: MMCONFIG at [mem 0xf8000000-0xfbffffff] reserved in E820 [ 1.578736] PCI: Using configuration type 1 for base access [ 1.581546] Kprobes globally optimized [ 1.581745] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages [ 1.582727] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages [ 1.600725] raid6: avx2x4 gen() 24543 MB/s [ 1.618725] raid6: avx2x4 xor() 8458 MB/s [ 1.636725] raid6: avx2x2 gen() 26948 MB/s [ 1.654725] raid6: avx2x2 xor() 16452 MB/s [ 1.672725] raid6: avx2x1 gen() 24404 MB/s [ 1.690725] raid6: avx2x1 xor() 15328 MB/s [ 1.708725] raid6: sse2x4 gen() 16141 MB/s [ 1.726725] raid6: sse2x4 xor() 8198 MB/s [ 1.744725] raid6: sse2x2 gen() 18234 MB/s [ 1.762725] raid6: sse2x2 xor() 10455 MB/s [ 1.780725] raid6: sse2x1 gen() 13770 MB/s [ 1.798725] raid6: sse2x1 xor() 7739 MB/s [ 1.799725] raid6: using algorithm avx2x2 gen() 26948 MB/s [ 1.800725] raid6: .... xor() 16452 MB/s, rmw enabled [ 1.801725] raid6: using avx2x2 recovery algorithm [ 1.802750] ACPI: Added _OSI(Module Device) [ 1.803727] ACPI: Added _OSI(Processor Device) [ 1.804725] ACPI: Added _OSI(3.0 _SCP Extensions) [ 1.805725] ACPI: Added _OSI(Processor Aggregator Device) [ 1.806725] ACPI: Added _OSI(Linux-Dell-Video) [ 1.807725] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio) [ 1.808725] ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics) [ 1.815760] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored [ 1.818092] ACPI: 11 ACPI AML tables successfully acquired and loaded [ 1.822666] ACPI: Interpreter enabled [ 1.822734] ACPI: PM: (supports S0 S3 S5) [ 1.823725] ACPI: Using IOAPIC for interrupt routing [ 1.824908] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug [ 1.826858] ACPI: Enabled 2 GPEs in block 00 to 1F [ 1.833403] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff]) [ 1.833729] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI HPX-Type3] [ 1.835757] acpi PNP0A08:00: _OSC: platform does not support [LTR] [ 1.836812] acpi PNP0A08:00: _OSC: OS now controls [PME PCIeCapability] [ 1.837725] acpi PNP0A08:00: FADT indicates ASPM is unsupported, using BIOS configuration [ 1.838730] acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain 0000 [bus 00-3f] only partially covers this bridge [ 1.839875] PCI host bridge to bus 0000:00 [ 1.840726] pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7 window] [ 1.841725] pci_bus 0000:00: root bus resource [io 0x0d00-0xffff window] [ 1.842725] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window] [ 1.843725] pci_bus 0000:00: root bus resource [mem 0x000c0000-0x000c3fff window] [ 1.844725] pci_bus 0000:00: root bus resource [mem 0x000c4000-0x000c7fff window] [ 1.845726] pci_bus 0000:00: root bus resource [mem 0x000c8000-0x000cbfff window] [ 1.846725] pci_bus 0000:00: root bus resource [mem 0x000cc000-0x000cffff window] [ 1.847725] pci_bus 0000:00: root bus resource [mem 0x000d0000-0x000d3fff window] [ 1.848725] pci_bus 0000:00: root bus resource [mem 0x000d4000-0x000d7fff window] [ 1.849725] pci_bus 0000:00: root bus resource [mem 0x000d8000-0x000dbfff window] [ 1.850725] pci_bus 0000:00: root bus resource [mem 0x000dc000-0x000dffff window] [ 1.851725] pci_bus 0000:00: root bus resource [mem 0x000e0000-0x000e3fff window] [ 1.852725] pci_bus 0000:00: root bus resource [mem 0x000e4000-0x000e7fff window] [ 1.853725] pci_bus 0000:00: root bus resource [mem 0x000e8000-0x000ebfff window] [ 1.854725] pci_bus 0000:00: root bus resource [mem 0x000ec000-0x000effff window] [ 1.855725] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xf7ffffff window] [ 1.856725] pci_bus 0000:00: root bus resource [mem 0xfc000000-0xfeafffff window] [ 1.857725] pci_bus 0000:00: root bus resource [bus 00-ff] [ 1.858751] pci 0000:00:00.0: [1022:1450] type 00 class 0x060000 [ 1.859805] pci 0000:00:00.2: [1022:1451] type 00 class 0x080600 [ 1.860818] pci 0000:00:01.0: [1022:1452] type 00 class 0x060000 [ 1.861814] pci 0000:00:01.3: [1022:1453] type 01 class 0x060400 [ 1.862773] pci 0000:00:01.3: PME# supported from D0 D3hot D3cold [ 1.863812] pci 0000:00:02.0: [1022:1452] type 00 class 0x060000 [ 1.865744] pci 0000:00:03.0: [1022:1452] type 00 class 0x060000 [ 1.866808] pci 0000:00:03.1: [1022:1453] type 01 class 0x060400 [ 1.867770] pci 0000:00:03.1: PME# supported from D0 D3hot D3cold [ 1.868861] pci 0000:00:04.0: [1022:1452] type 00 class 0x060000 [ 1.869812] pci 0000:00:07.0: [1022:1452] type 00 class 0x060000 [ 1.870808] pci 0000:00:07.1: [1022:1454] type 01 class 0x060400 [ 1.871742] pci 0000:00:07.1: enabling Extended Tags [ 1.872747] pci 0000:00:07.1: PME# supported from D0 D3hot D3cold [ 1.873806] pci 0000:00:08.0: [1022:1452] type 00 class 0x060000 [ 1.874809] pci 0000:00:08.1: [1022:1454] type 01 class 0x060400 [ 1.875745] pci 0000:00:08.1: enabling Extended Tags [ 1.876749] pci 0000:00:08.1: PME# supported from D0 D3hot D3cold [ 1.877853] pci 0000:00:14.0: [1022:790b] type 00 class 0x0c0500 [ 1.878918] pci 0000:00:14.3: [1022:790e] type 00 class 0x060100 [ 1.879945] pci 0000:00:18.0: [1022:1460] type 00 class 0x060000 [ 1.880781] pci 0000:00:18.1: [1022:1461] type 00 class 0x060000 [ 1.881783] pci 0000:00:18.2: [1022:1462] type 00 class 0x060000 [ 1.882781] pci 0000:00:18.3: [1022:1463] type 00 class 0x060000 [ 1.883781] pci 0000:00:18.4: [1022:1464] type 00 class 0x060000 [ 1.884781] pci 0000:00:18.5: [1022:1465] type 00 class 0x060000 [ 1.886763] pci 0000:00:18.6: [1022:1466] type 00 class 0x060000 [ 1.887781] pci 0000:00:18.7: [1022:1467] type 00 class 0x060000 [ 1.888816] pci 0000:01:00.0: [1022:43bb] type 00 class 0x0c0330 [ 1.889739] pci 0000:01:00.0: reg 0x10: [mem 0xf0620000-0xf0627fff 64bit] [ 1.890802] pci 0000:01:00.0: PME# supported from D3hot D3cold [ 1.892763] pci 0000:01:00.1: [1022:43b7] type 00 class 0x010601 [ 1.893765] pci 0000:01:00.1: reg 0x24: [mem 0xf0600000-0xf061ffff] [ 1.894731] pci 0000:01:00.1: reg 0x30: [mem 0xfff80000-0xffffffff pref] [ 1.895763] pci 0000:01:00.1: PME# supported from D3hot D3cold [ 1.896771] pci 0000:01:00.2: [1022:43b2] type 01 class 0x060400 [ 1.897799] pci 0000:01:00.2: PME# supported from D3hot D3cold [ 1.898779] pci 0000:00:01.3: PCI bridge to [bus 01-04] [ 1.899728] pci 0000:00:01.3: bridge window [mem 0xf0600000-0xf06fffff] [ 1.900727] pci 0000:00:01.3: bridge window [mem 0xf0000000-0xf00fffff 64bit pref] [ 1.901766] pci 0000:02:00.0: [1022:43b4] type 01 class 0x060400 [ 1.902814] pci 0000:02:00.0: PME# supported from D3hot D3cold [ 1.903783] pci 0000:02:01.0: [1022:43b4] type 01 class 0x060400 [ 1.904813] pci 0000:02:01.0: PME# supported from D3hot D3cold [ 1.905791] pci 0000:01:00.2: PCI bridge to [bus 02-04] [ 1.906734] pci 0000:01:00.2: bridge window [mem 0xf0000000-0xf00fffff 64bit pref] [ 1.907788] pci 0000:03:00.0: [14e4:1687] type 00 class 0x020000 [ 1.908756] pci 0000:03:00.0: reg 0x10: [mem 0xf0020000-0xf002ffff 64bit pref] [ 1.909743] pci 0000:03:00.0: reg 0x18: [mem 0xf0010000-0xf001ffff 64bit pref] [ 1.910743] pci 0000:03:00.0: reg 0x20: [mem 0xf0000000-0xf000ffff 64bit pref] [ 1.911867] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold [ 1.915743] pci 0000:02:00.0: PCI bridge to [bus 03] [ 1.916734] pci 0000:02:00.0: bridge window [mem 0xf0000000-0xf00fffff 64bit pref] [ 1.918755] pci 0000:02:01.0: PCI bridge to [bus 04] [ 1.919778] pci 0000:05:00.0: [1002:6611] type 00 class 0x030000 [ 1.920735] pci 0000:05:00.0: reg 0x10: [mem 0xe0000000-0xefffffff 64bit pref] [ 1.921731] pci 0000:05:00.0: reg 0x18: [mem 0xf0500000-0xf053ffff 64bit] [ 1.922729] pci 0000:05:00.0: reg 0x20: [io 0x2000-0x20ff] [ 1.923733] pci 0000:05:00.0: reg 0x30: [mem 0xfffe0000-0xffffffff pref] [ 1.924736] pci 0000:05:00.0: BAR 0: assigned to efifb [ 1.925754] pci 0000:05:00.0: supports D1 D2 [ 1.926725] pci 0000:05:00.0: PME# supported from D1 D2 D3hot [ 1.927779] pci 0000:05:00.1: [1002:aab0] type 00 class 0x040300 [ 1.928734] pci 0000:05:00.1: reg 0x10: [mem 0xf0540000-0xf0543fff 64bit] [ 1.929772] pci 0000:05:00.1: supports D1 D2 [ 1.930766] pci 0000:00:03.1: PCI bridge to [bus 05] [ 1.931727] pci 0000:00:03.1: bridge window [io 0x2000-0x2fff] [ 1.932726] pci 0000:00:03.1: bridge window [mem 0xf0500000-0xf05fffff] [ 1.933727] pci 0000:00:03.1: bridge window [mem 0xe0000000-0xefffffff 64bit pref] [ 1.934755] pci 0000:06:00.0: [1022:145a] type 00 class 0x130000 [ 1.935745] pci 0000:06:00.0: enabling Extended Tags [ 1.936784] pci 0000:06:00.2: [1022:1456] type 00 class 0x108000 [ 1.937735] pci 0000:06:00.2: reg 0x18: [mem 0xf0300000-0xf03fffff] [ 1.938732] pci 0000:06:00.2: reg 0x24: [mem 0xf0400000-0xf0401fff] [ 1.939730] pci 0000:06:00.2: enabling Extended Tags [ 1.940783] pci 0000:06:00.3: [1022:145c] type 00 class 0x0c0330 [ 1.941733] pci 0000:06:00.3: reg 0x10: [mem 0xf0200000-0xf02fffff 64bit] [ 1.942743] pci 0000:06:00.3: enabling Extended Tags [ 1.943747] pci 0000:06:00.3: PME# supported from D0 D3hot D3cold [ 1.944781] pci 0000:00:07.1: PCI bridge to [bus 06] [ 1.945728] pci 0000:00:07.1: bridge window [mem 0xf0200000-0xf04fffff] [ 1.946757] pci 0000:07:00.0: [1022:1455] type 00 class 0x130000 [ 1.947747] pci 0000:07:00.0: enabling Extended Tags [ 1.948789] pci 0000:07:00.2: [1022:7901] type 00 class 0x010601 [ 1.949748] pci 0000:07:00.2: reg 0x24: [mem 0xf0108000-0xf0108fff] [ 1.950731] pci 0000:07:00.2: enabling Extended Tags [ 1.951750] pci 0000:07:00.2: PME# supported from D3hot D3cold [ 1.953732] pci 0000:07:00.3: [1022:1457] type 00 class 0x040300 [ 1.954731] pci 0000:07:00.3: reg 0x10: [mem 0xf0100000-0xf0107fff] [ 1.955742] pci 0000:07:00.3: enabling Extended Tags [ 1.956748] pci 0000:07:00.3: PME# supported from D0 D3hot D3cold [ 1.957780] pci 0000:00:08.1: PCI bridge to [bus 07] [ 1.958728] pci 0000:00:08.1: bridge window [mem 0xf0100000-0xf01fffff] [ 1.959983] ACPI: PCI: Interrupt link LNKA configured for IRQ 0 [ 1.960725] ACPI: PCI: Interrupt link LNKA disabled [ 1.961779] ACPI: PCI: Interrupt link LNKB configured for IRQ 0 [ 1.962725] ACPI: PCI: Interrupt link LNKB disabled [ 1.963769] ACPI: PCI: Interrupt link LNKC configured for IRQ 0 [ 1.964725] ACPI: PCI: Interrupt link LNKC disabled [ 1.965782] ACPI: PCI: Interrupt link LNKD configured for IRQ 0 [ 1.966725] ACPI: PCI: Interrupt link LNKD disabled [ 1.967778] ACPI: PCI: Interrupt link LNKE configured for IRQ 0 [ 1.968725] ACPI: PCI: Interrupt link LNKE disabled [ 1.969766] ACPI: PCI: Interrupt link LNKF configured for IRQ 0 [ 1.970725] ACPI: PCI: Interrupt link LNKF disabled [ 1.971767] ACPI: PCI: Interrupt link LNKG configured for IRQ 0 [ 1.972725] ACPI: PCI: Interrupt link LNKG disabled [ 1.973767] ACPI: PCI: Interrupt link LNKH configured for IRQ 0 [ 1.974725] ACPI: PCI: Interrupt link LNKH disabled [ 1.975968] iommu: Default domain type: Translated [ 1.976726] iommu: DMA domain TLB invalidation policy: lazy mode [ 1.977739] pci 0000:05:00.0: vgaarb: VGA device added: decodes=io+mem,owns=none,locks=none [ 1.978726] pci 0000:05:00.0: vgaarb: bridge control possible [ 1.979725] pci 0000:05:00.0: vgaarb: setting as boot device [ 1.980725] vgaarb: loaded [ 1.981783] SCSI subsystem initialized [ 1.982738] libata version 3.00 loaded. [ 1.982749] ACPI: bus type USB registered [ 1.984729] usbcore: registered new interface driver usbfs [ 1.985731] usbcore: registered new interface driver hub [ 1.986730] usbcore: registered new device driver usb [ 1.987735] mc: Linux media interface: v0.10 [ 1.988728] videodev: Linux video capture interface: v2.00 [ 1.989728] pps_core: LinuxPPS API ver. 1 registered [ 1.990725] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it> [ 1.991727] PTP clock support registered [ 1.992749] Registered efivars operations [ 1.993847] PCI: Using ACPI for IRQ routing [ 1.999279] PCI: pci_cache_line_size set to 64 bytes [ 1.999327] e820: reserve RAM buffer [mem 0x00088000-0x0008ffff] [ 1.999329] e820: reserve RAM buffer [mem 0x09d00000-0x0bffffff] [ 1.999330] e820: reserve RAM buffer [mem 0xdadbf000-0xdbffffff] [ 1.999331] e820: reserve RAM buffer [mem 0xdf000000-0xdfffffff] [ 1.999332] e820: reserve RAM buffer [mem 0x41f000000-0x41fffffff] [ 1.999336] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0 [ 1.999725] hpet0: 3 comparators, 32-bit 14.318180 MHz counter [ 2.002758] clocksource: Switched to clocksource tsc-early [ 2.015069] VFS: Disk quotas dquot_6.6.0 [ 2.019021] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes) [ 2.025939] FS-Cache: Loaded [ 2.028871] CacheFiles: Loaded [ 2.031956] pnp: PnP ACPI init [ 2.035171] system 00:00: [mem 0xfec00000-0xfec01fff] could not be reserved [ 2.042141] system 00:00: [mem 0xfee00000-0xfee00fff] has been reserved [ 2.048762] system 00:00: [mem 0xfdf00000-0xfdffffff] has been reserved [ 2.055484] system 00:02: [io 0x0400-0x04cf] has been reserved [ 2.061415] system 00:02: [io 0x04d0-0x04d1] has been reserved [ 2.067344] system 00:02: [io 0x04d6] has been reserved [ 2.072664] system 00:02: [io 0x0c00-0x0c01] has been reserved [ 2.078592] system 00:02: [io 0x0c14] has been reserved [ 2.083913] system 00:02: [io 0x0c50-0x0c52] has been reserved [ 2.089844] system 00:02: [io 0x0c6c] has been reserved [ 2.095168] system 00:02: [io 0x0c6f] has been reserved [ 2.100491] system 00:02: [io 0x0cd0-0x0cdb] has been reserved [ 2.106462] system 00:03: [mem 0x000e0000-0x000fffff] could not be reserved [ 2.113434] system 00:03: [mem 0xff000000-0xffffffff] has been reserved [ 2.120518] pnp: PnP ACPI: found 5 devices [ 2.130237] clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns [ 2.139157] NET: Registered PF_INET protocol family [ 2.144276] IP idents hash table entries: 262144 (order: 9, 2097152 bytes, linear) [ 2.153342] tcp_listen_portaddr_hash hash table entries: 8192 (order: 5, 131072 bytes, linear) [ 2.161983] TCP established hash table entries: 131072 (order: 8, 1048576 bytes, linear) [ 2.170222] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes, linear) [ 2.177739] TCP: Hash tables configured (established 131072 bind 65536) [ 2.184392] UDP hash table entries: 8192 (order: 6, 262144 bytes, linear) [ 2.191223] UDP-Lite hash table entries: 8192 (order: 6, 262144 bytes, linear) [ 2.198534] pci 0000:01:00.1: can't claim BAR 6 [mem 0xfff80000-0xffffffff pref]: no compatible bridge window [ 2.208453] pci 0000:05:00.0: can't claim BAR 6 [mem 0xfffe0000-0xffffffff pref]: no compatible bridge window [ 2.218380] pci 0000:01:00.1: BAR 6: assigned [mem 0xf0680000-0xf06fffff pref] [ 2.225611] pci 0000:02:00.0: PCI bridge to [bus 03] [ 2.230590] pci 0000:02:00.0: bridge window [mem 0xf0000000-0xf00fffff 64bit pref] [ 2.238347] pci 0000:02:01.0: PCI bridge to [bus 04] [ 2.243333] pci 0000:01:00.2: PCI bridge to [bus 02-04] [ 2.248568] pci 0000:01:00.2: bridge window [mem 0xf0000000-0xf00fffff 64bit pref] [ 2.256326] pci 0000:00:01.3: PCI bridge to [bus 01-04] [ 2.261555] pci 0000:00:01.3: bridge window [mem 0xf0600000-0xf06fffff] [ 2.268351] pci 0000:00:01.3: bridge window [mem 0xf0000000-0xf00fffff 64bit pref] [ 2.276099] pci 0000:05:00.0: BAR 6: assigned [mem 0xf0560000-0xf057ffff pref] [ 2.283327] pci 0000:00:03.1: PCI bridge to [bus 05] [ 2.288298] pci 0000:00:03.1: bridge window [io 0x2000-0x2fff] [ 2.294398] pci 0000:00:03.1: bridge window [mem 0xf0500000-0xf05fffff] [ 2.301196] pci 0000:00:03.1: bridge window [mem 0xe0000000-0xefffffff 64bit pref] [ 2.308943] pci 0000:00:07.1: PCI bridge to [bus 06] [ 2.313914] pci 0000:00:07.1: bridge window [mem 0xf0200000-0xf04fffff] [ 2.320712] pci 0000:00:08.1: PCI bridge to [bus 07] [ 2.325682] pci 0000:00:08.1: bridge window [mem 0xf0100000-0xf01fffff] [ 2.332476] pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7 window] [ 2.338660] pci_bus 0000:00: resource 5 [io 0x0d00-0xffff window] [ 2.344847] pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff window] [ 2.351727] pci_bus 0000:00: resource 7 [mem 0x000c0000-0x000c3fff window] [ 2.358609] pci_bus 0000:00: resource 8 [mem 0x000c4000-0x000c7fff window] [ 2.365489] pci_bus 0000:00: resource 9 [mem 0x000c8000-0x000cbfff window] [ 2.372368] pci_bus 0000:00: resource 10 [mem 0x000cc000-0x000cffff window] [ 2.379337] pci_bus 0000:00: resource 11 [mem 0x000d0000-0x000d3fff window] [ 2.386303] pci_bus 0000:00: resource 12 [mem 0x000d4000-0x000d7fff window] [ 2.393271] pci_bus 0000:00: resource 13 [mem 0x000d8000-0x000dbfff window] [ 2.400239] pci_bus 0000:00: resource 14 [mem 0x000dc000-0x000dffff window] [ 2.407207] pci_bus 0000:00: resource 15 [mem 0x000e0000-0x000e3fff window] [ 2.414178] pci_bus 0000:00: resource 16 [mem 0x000e4000-0x000e7fff window] [ 2.421143] pci_bus 0000:00: resource 17 [mem 0x000e8000-0x000ebfff window] [ 2.428116] pci_bus 0000:00: resource 18 [mem 0x000ec000-0x000effff window] [ 2.435084] pci_bus 0000:00: resource 19 [mem 0xe0000000-0xf7ffffff window] [ 2.442055] pci_bus 0000:00: resource 20 [mem 0xfc000000-0xfeafffff window] [ 2.449025] pci_bus 0000:01: resource 1 [mem 0xf0600000-0xf06fffff] [ 2.455300] pci_bus 0000:01: resource 2 [mem 0xf0000000-0xf00fffff 64bit pref] [ 2.462529] pci_bus 0000:02: resource 2 [mem 0xf0000000-0xf00fffff 64bit pref] [ 2.469757] pci_bus 0000:03: resource 2 [mem 0xf0000000-0xf00fffff 64bit pref] [ 2.476988] pci_bus 0000:05: resource 0 [io 0x2000-0x2fff] [ 2.482568] pci_bus 0000:05: resource 1 [mem 0xf0500000-0xf05fffff] [ 2.488844] pci_bus 0000:05: resource 2 [mem 0xe0000000-0xefffffff 64bit pref] [ 2.496077] pci_bus 0000:06: resource 1 [mem 0xf0200000-0xf04fffff] [ 2.502351] pci_bus 0000:07: resource 1 [mem 0xf0100000-0xf01fffff] [ 2.508799] pci 0000:05:00.1: D0 power state depends on 0000:05:00.0 [ 2.515298] PCI: CLS 0 bytes, default 64 [ 2.519240] AMD-Vi: [Firmware Warn]: EFR mismatch. Use IVHD EFR (0xf77ef22294ada : 0x400f77ef22294ada). [ 2.519270] Trying to unpack rootfs image as initramfs... [ 2.528645] pci 0000:00:00.2: AMD-Vi: IOMMU performance counters supported [ 2.540984] pci 0000:00:00.2: can't derive routing for PCI INT A [ 2.547002] pci 0000:00:00.2: PCI INT A: not connected [ 2.552171] pci 0000:00:01.0: Adding to iommu group 0 [ 2.557240] pci 0000:00:01.3: Adding to iommu group 1 [ 2.562311] pci 0000:00:02.0: Adding to iommu group 2 [ 2.567408] pci 0000:00:03.0: Adding to iommu group 3 [ 2.572484] pci 0000:00:03.1: Adding to iommu group 4 [ 2.577556] pci 0000:00:04.0: Adding to iommu group 5 [ 2.582631] pci 0000:00:07.0: Adding to iommu group 6 [ 2.587703] pci 0000:00:07.1: Adding to iommu group 6 [ 2.592775] pci 0000:00:08.0: Adding to iommu group 7 [ 2.597847] pci 0000:00:08.1: Adding to iommu group 7 [ 2.598418] Freeing initrd memory: 5136K [ 2.602918] pci 0000:00:14.0: Adding to iommu group 8 [ 2.611901] pci 0000:00:14.3: Adding to iommu group 8 [ 2.616992] pci 0000:00:18.0: Adding to iommu group 9 [ 2.622064] pci 0000:00:18.1: Adding to iommu group 9 [ 2.627131] pci 0000:00:18.2: Adding to iommu group 9 [ 2.632199] pci 0000:00:18.3: Adding to iommu group 9 [ 2.637265] pci 0000:00:18.4: Adding to iommu group 9 [ 2.642334] pci 0000:00:18.5: Adding to iommu group 9 [ 2.647404] pci 0000:00:18.6: Adding to iommu group 9 [ 2.652471] pci 0000:00:18.7: Adding to iommu group 9 [ 2.657549] pci 0000:01:00.0: Adding to iommu group 10 [ 2.662703] pci 0000:01:00.1: Adding to iommu group 10 [ 2.667859] pci 0000:01:00.2: Adding to iommu group 10 [ 2.673009] pci 0000:02:00.0: Adding to iommu group 10 [ 2.678155] pci 0000:02:01.0: Adding to iommu group 10 [ 2.683299] pci 0000:03:00.0: Adding to iommu group 10 [ 2.688457] pci 0000:05:00.0: Adding to iommu group 11 [ 2.693617] pci 0000:05:00.1: Adding to iommu group 11 [ 2.698765] pci 0000:06:00.0: Adding to iommu group 6 [ 2.703824] pci 0000:06:00.2: Adding to iommu group 6 [ 2.708886] pci 0000:06:00.3: Adding to iommu group 6 [ 2.713953] pci 0000:07:00.0: Adding to iommu group 7 [ 2.719011] pci 0000:07:00.2: Adding to iommu group 7 [ 2.724072] pci 0000:07:00.3: Adding to iommu group 7 [ 2.730322] pci 0000:00:00.2: AMD-Vi: Found IOMMU cap 0x40 [ 2.735819] AMD-Vi: Extended features (0x400f77ef22294ada): PPR NX GT IA GA PC GA_vAPIC [ 2.743837] AMD-Vi: Interrupt remapping enabled [ 2.748376] AMD-Vi: Virtual APIC enabled [ 2.752387] software IO TLB: tearing down default memory pool [ 2.758895] RAPL PMU: API unit is 2^-32 Joules, 1 fixed counters, 163840 ms ovfl timer [ 2.766819] RAPL PMU: hw unit of domain package 2^-16 Joules [ 2.772490] amd_uncore: 4 amd_df counters detected [ 2.777374] amd_uncore: 6 amd_l3 counters detected [ 2.782356] perf/amd_iommu: Detected AMD IOMMU #0 (2 banks, 4 counters/bank). [ 2.789801] Initialise system trusted keyrings [ 2.794289] workingset: timestamp_bits=40 max_order=22 bucket_order=0 [ 2.800788] zbud: loaded [ 2.803371] SGI XFS with ACLs, security attributes, realtime, quota, no debug enabled [ 2.811365] xor: automatically using best checksumming function avx [ 2.818423] Key type asymmetric registered [ 2.822524] Asymmetric key parser 'x509' registered [ 2.827422] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 247) [ 2.834848] io scheduler mq-deadline registered [ 2.839389] io scheduler kyber registered [ 2.843529] pcieport 0000:00:01.3: PME: Signaling with IRQ 26 [ 2.849382] pcieport 0000:00:03.1: PME: Signaling with IRQ 27 [ 2.855230] pcieport 0000:00:07.1: PME: Signaling with IRQ 28 [ 2.861123] pcieport 0000:00:08.1: PME: Signaling with IRQ 30 [ 2.867222] IPMI message handler: version 39.2 [ 2.871722] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0 [ 2.880094] ACPI: button: Power Button [PWRB] [ 2.884505] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1 [ 2.891932] ACPI: button: Power Button [PWRF] [ 2.896858] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled [ 2.903347] 00:04: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A [ 2.911359] lp: driver loaded but no devices found [ 2.916289] Linux agpgart interface v0.103 [ 2.923437] brd: module loaded [ 2.927688] loop: module loaded [ 2.932239] drbd: initialized. Version: 8.4.11 (api:1/proto:86-101) [ 2.938574] drbd: built-in [ 2.941342] drbd: registered as block device major 147 [ 2.946645] megaraid cmm: 2.20.2.7 (Release Date: Sun Jul 16 00:01:03 EST 2006) [ 2.954059] megaraid: 2.20.5.1 (Release Date: Thu Nov 16 15:32:35 EST 2006) [ 2.961096] megasas: 07.717.02.00-rc1 [ 2.964835] mpt3sas version 39.100.00.00 loaded [ 2.969692] ahci 0000:01:00.1: version 3.0 [ 2.970061] ahci 0000:01:00.1: SSS flag set, parallel bus scan disabled [ 2.977056] ahci 0000:01:00.1: AHCI 0001.0301 32 slots 8 ports 6 Gbps 0x33 impl SATA mode [ 2.985295] ahci 0000:01:00.1: flags: 64bit ncq sntf stag pm led clo only pmp pio slum part sxs deso sadm sds apst [ 2.996496] scsi host0: ahci [ 2.999642] scsi host1: ahci [ 3.002706] scsi host2: ahci [ 3.005797] scsi host3: ahci [ 3.008871] scsi host4: ahci [ 3.011970] scsi host5: ahci [ 3.015098] scsi host6: ahci [ 3.018236] scsi host7: ahci [ 3.021215] ata1: SATA max UDMA/133 abar m131072@0xf0600000 port 0xf0600100 irq 36 [ 3.028852] ata2: SATA max UDMA/133 abar m131072@0xf0600000 port 0xf0600180 irq 36 [ 3.036492] ata3: DUMMY [ 3.039010] ata4: DUMMY [ 3.041524] ata5: SATA max UDMA/133 abar m131072@0xf0600000 port 0xf0600300 irq 36 [ 3.049159] ata6: SATA max UDMA/133 abar m131072@0xf0600000 port 0xf0600380 irq 36 [ 3.056799] ata7: DUMMY [ 3.059304] ata8: DUMMY [ 3.062220] ahci 0000:07:00.2: AHCI 0001.0301 32 slots 1 ports 6 Gbps 0x1 impl SATA mode [ 3.070367] ahci 0000:07:00.2: flags: 64bit ncq sntf ilck pm led clo only pmp fbs pio slum part [ 3.079523] scsi host8: ahci [ 3.082490] ata9: SATA max UDMA/133 abar m4096@0xf0108000 port 0xf0108100 irq 38 [ 3.090177] libphy: Fixed MDIO Bus: probed [ 3.094346] tun: Universal TUN/TAP device driver, 1.6 [ 3.112235] tg3 0000:03:00.0 eth0: Tigon3 [partno(BCM95762) rev 5762100] (PCI Express) MAC address d8:9e:f3:2a:ef:e4 [ 3.122834] tg3 0000:03:00.0 eth0: attached PHY is 5762C (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[1]) [ 3.132729] tg3 0000:03:00.0 eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] TSOcap[1] [ 3.140618] tg3 0000:03:00.0 eth0: dma_rwctrl[00000001] dma_mask[64-bit] [ 3.147996] e100: Intel(R) PRO/100 Network Driver [ 3.152757] e100: Copyright(c) 1999-2006 Intel Corporation [ 3.158309] e1000: Intel(R) PRO/1000 Network Driver [ 3.163243] e1000: Copyright (c) 1999-2006 Intel Corporation. [ 3.169060] e1000e: Intel(R) PRO/1000 Network Driver [ 3.174095] e1000e: Copyright(c) 1999 - 2015 Intel Corporation. [ 3.180086] igb: Intel(R) Gigabit Ethernet Network Driver [ 3.185542] igb: Copyright (c) 2007-2014 Intel Corporation. [ 3.191182] igbvf: Intel(R) Gigabit Virtual Function Network Driver [ 3.197512] igbvf: Copyright (c) 2009 - 2012 Intel Corporation. [ 3.203506] sky2: driver version 1.30 [ 3.207311] Fusion MPT base driver 3.04.20 [ 3.211461] Copyright (c) 1999-2008 LSI Corporation [ 3.216411] Fusion MPT SPI Host driver 3.04.20 [ 3.220931] Fusion MPT FC Host driver 3.04.20 [ 3.225366] Fusion MPT SAS Host driver 3.04.20 [ 3.229885] Fusion MPT misc device (ioctl) driver 3.04.20 [ 3.235406] mptctl: Registered with Fusion MPT base driver [ 3.240950] mptctl: /dev/mptctl @ (major,minor=10,220) [ 3.246151] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 3.252746] ehci-pci: EHCI PCI platform driver [ 3.257252] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [ 3.263496] ohci-pci: OHCI PCI platform driver [ 3.268002] uhci_hcd: USB Universal Host Controller Interface driver [ 3.274469] xhci_hcd 0000:01:00.0: xHCI Host Controller [ 3.279745] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 1 [ 3.342980] xhci_hcd 0000:01:00.0: hcc params 0x0200ef81 hci version 0x110 quirks 0x0000010048000410 [ 3.352872] xhci_hcd 0000:01:00.0: xHCI Host Controller [ 3.358162] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 2 [ 3.365613] xhci_hcd 0000:01:00.0: Host supports USB 3.1 Enhanced SuperSpeed [ 3.372874] hub 1-0:1.0: USB hub found [ 3.376777] hub 1-0:1.0: 10 ports detected [ 3.381614] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM. [ 3.389873] hub 2-0:1.0: USB hub found [ 3.393723] hub 2-0:1.0: 4 ports detected [ 3.397927] usb: port power management may be unreliable [ 3.404074] xhci_hcd 0000:06:00.3: xHCI Host Controller [ 3.405503] ata9: SATA link down (SStatus 0 SControl 300) [ 3.409367] xhci_hcd 0000:06:00.3: new USB bus registered, assigned bus number 3 [ 3.418774] tsc: Refined TSC clocksource calibration: 3493.378 MHz [ 3.422770] xhci_hcd 0000:06:00.3: hcc params 0x0270f665 hci version 0x100 quirks 0x0000000040000410 [ 3.428506] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x325ae149e20, max_idle_ns: 440795289459 ns [ 3.438818] xhci_hcd 0000:06:00.3: xHCI Host Controller [ 3.453027] clocksource: Switched to clocksource tsc [ 3.453028] xhci_hcd 0000:06:00.3: new USB bus registered, assigned bus number 4 [ 3.465430] xhci_hcd 0000:06:00.3: Host supports USB 3.0 SuperSpeed [ 3.471979] hub 3-0:1.0: USB hub found [ 3.475829] hub 3-0:1.0: 4 ports detected [ 3.480179] usb usb4: We don't know the algorithms for LPM for this host, disabling LPM. [ 3.488415] hub 4-0:1.0: USB hub found [ 3.492268] hub 4-0:1.0: 4 ports detected [ 3.496586] usbcore: registered new interface driver usb-storage [ 3.502783] i8042: PNP: No PS/2 controller found. [ 3.507542] i8042: Probing ports directly. [ 3.513182] serio: i8042 KBD port at 0x60,0x64 irq 1 [ 3.518211] serio: i8042 AUX port at 0x60,0x64 irq 12 [ 3.522885] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 3.523579] rtc_cmos 00:01: RTC can wake from S4 [ 3.535396] rtc_cmos 00:01: registered as rtc0 [ 3.540222] rtc_cmos 00:01: setting system clock to 2021-10-27T15:52:32 UTC (1635349952) [ 3.548392] rtc_cmos 00:01: alarms up to one month, y3k, 114 bytes nvram, hpet irqs [ 3.556205] efifb: probing for efifb [ 3.559287] ata1.00: ATA-8: ST500LM021-1KJ152, 0005SDM1, max UDMA/133 [ 3.559851] efifb: framebuffer at 0xe0000000, using 5632k, total 5632k [ 3.566344] ata1.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 32) [ 3.572934] efifb: mode is 1600x900x32, linelength=6400, pages=1 [ 3.585615] efifb: scrolling: redraw [ 3.589259] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0 [ 3.596926] Console: switching to colour frame buffer device 200x56 [ 3.605173] fb0: EFI VGA frame buffer device [ 3.609522] EFI Variables Facility v0.08 2004-May-17 [ 3.655335] hid: raw HID events driver (C) Jiri Kosina [ 3.660656] usbcore: registered new interface driver usbhid [ 3.666307] usbhid: USB HID core driver [ 3.670296] Key type dns_resolver registered [ 3.674682] ata1.00: configured for UDMA/133 [ 3.679386] scsi 0:0:0:0: Direct-Access ATA ST500LM021-1KJ15 SDM1 PQ: 0 ANSI: 5 [ 3.679443] microcode: CPU0: patch_level=0x08001137 [ 3.687651] scsi 0:0:0:0: Attached scsi generic sg0 type 0 [ 3.692497] microcode: CPU1: patch_level=0x08001137 [ 3.692538] sd 0:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/466 GiB) [ 3.692540] sd 0:0:0:0: [sda] 4096-byte physical blocks [ 3.692545] sd 0:0:0:0: [sda] Write Protect is off [ 3.692546] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [ 3.692553] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 3.726730] usb 3-2: new low-speed USB device number 2 using xhci_hcd [ 3.729699] microcode: CPU2: patch_level=0x08001137 [ 3.741125] microcode: CPU3: patch_level=0x08001137 [ 3.746077] microcode: CPU4: patch_level=0x08001137 [ 3.751041] microcode: CPU5: patch_level=0x08001137 [ 3.755988] microcode: CPU6: patch_level=0x08001137 [ 3.760973] microcode: CPU7: patch_level=0x08001137 [ 3.765909] microcode: Microcode Update Driver: v2.2. [ 3.765912] IPI shorthand broadcast: enabled [ 3.773638] sda: sda1 sda2 sda3 [ 3.775400] sched_clock: Marking stable (2482438658, 1292935769)->(4910510775, -1135136348) [ 3.778798] sd 0:0:0:0: [sda] Attached SCSI disk [ 3.787319] registered taskstats version 1 [ 3.795947] Loading compiled-in X.509 certificates [ 3.801586] Loaded X.509 cert 'Build time autogenerated kernel key: 7a4fdf53e64e4e4b389e2ee43c5487ca6284f7c3' [ 3.811664] zswap: loaded using pool lzo/zbud [ 3.934112] input: Fujitsu Fujitsu Keyboard as /devices/pci0000:00/0000:00:07.1/0000:06:00.3/usb3/3-2/3-2:1.0/0003:0BF8:101E.0001/input/input6 [ 3.998800] hid-generic 0003:0BF8:101E.0001: input,hidraw0: USB HID v1.10 Keyboard [Fujitsu Fujitsu Keyboard] on usb-0000:06:00.3-2/input0 [ 4.013329] ata2: SATA link down (SStatus 0 SControl 300) [ 4.035118] input: Fujitsu Fujitsu Keyboard System Control as /devices/pci0000:00/0000:00:07.1/0000:06:00.3/usb3/3-2/3-2:1.1/0003:0BF8:101E.0002/input/input7 [ 4.101779] input: Fujitsu Fujitsu Keyboard Consumer Control as /devices/pci0000:00/0000:00:07.1/0000:06:00.3/usb3/3-2/3-2:1.1/0003:0BF8:101E.0002/input/input8 [ 4.116781] hid-generic 0003:0BF8:101E.0002: input,hidraw1: USB HID v1.10 Device [Fujitsu Fujitsu Keyboard] on usb-0000:06:00.3-2/input1 [ 4.243738] usb 3-3: new low-speed USB device number 3 using xhci_hcd [ 4.328300] ata5: SATA link down (SStatus 0 SControl 300) [ 4.435056] input: Logitech USB Optical Mouse as /devices/pci0000:00/0000:00:07.1/0000:06:00.3/usb3/3-3/3-3:1.0/0003:046D:C077.0003/input/input9 [ 4.448833] hid-generic 0003:046D:C077.0003: input,hidraw2: USB HID v1.11 Mouse [Logitech USB Optical Mouse] on usb-0000:06:00.3-3/input0 [ 4.640260] ata6: SATA link down (SStatus 0 SControl 300) [ 4.647636] Freeing unused kernel image (initmem) memory: 1700K [ 4.654335] Write protecting the kernel read-only data: 20480k [ 4.661448] Freeing unused kernel image (text/rodata gap) memory: 2032K [ 4.669004] Freeing unused kernel image (rodata/data gap) memory: 212K [ 4.676297] Run /init as init process [ 4.680714] with arguments: [ 4.680715] /init [ 4.680716] with environment: [ 4.680717] HOME=/ [ 4.680717] TERM=linux [ 4.680718] BOOT_IMAGE=/boot/bzImage-5.15.0-rc7.mx64.407 [ 4.680718] crashkernel=256M [ 4.971888] XFS (sda1): Mounting V5 Filesystem [ 5.151691] XFS (sda1): Ending clean mount [ 6.501731] systemd[1]: Inserted module 'autofs4' [ 6.804283] NET: Registered PF_INET6 protocol family [ 6.810363] Segment Routing with IPv6 [ 6.814813] In-situ OAM (IOAM) with IPv6 [ 6.854111] NET: Registered PF_UNIX/PF_LOCAL protocol family [ 6.860611] systemd[1]: Inserted module 'unix' [ 7.366835] systemd[1]: systemd 242 running in system mode. (+PAM -AUDIT -SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP -LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 -SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid) [ 7.401781] systemd[1]: Detected architecture x86-64. [ 7.446037] systemd[1]: Set hostname to <serotimor.molgen.mpg.de>. [ 9.590505] systemd[1]: Listening on Journal Socket (/dev/log). [ 9.599619] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point. [ 9.613202] systemd[1]: Listening on initctl Compatibility Named Pipe. [ 9.623236] systemd[1]: Started Dispatch Password Requests to Console Directory Watch. [ 9.635036] systemd[1]: Started Forward Password Requests to Wall Directory Watch. [ 9.646818] systemd[1]: Created slice system-serial\x2dlog.slice. [ 9.656407] systemd[1]: Reached target Swap. [ 10.394340] RPC: Registered named UNIX socket transport module. [ 10.401857] RPC: Registered udp transport module. [ 10.408023] RPC: Registered tcp transport module. [ 10.414173] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 11.475939] Installing knfsd (copyright (C) 1996 okir@monad.swb.de). [ 11.738900] systemd-journald[181]: Received request to flush runtime journal from PID 1 [ 12.529108] piix4_smbus 0000:00:14.0: SMBus Host Controller at 0xb00, revision 0 [ 12.538752] piix4_smbus 0000:00:14.0: Using register 0x02 for SMBus port selection [ 12.547509] piix4_smbus 0000:00:14.0: Auxiliary SMBus Host Controller at 0xb20 [ 12.608079] acpi_cpufreq: overriding BIOS provided _PSD data [ 12.621155] wmi_bus wmi_bus-PNP0C14:00: WQBC data block query control method not found [ 12.630666] acpi PNP0C14:01: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00) [ 13.077533] pstore: Using crash dump compression: deflate [ 13.085240] pstore: Registered efi as persistent store backend [ 13.668722] snd_hda_intel 0000:05:00.1: enabling device (0000 -> 0002) [ 13.677870] snd_hda_intel 0000:05:00.1: Force to non-snoop mode [ 13.686860] snd_hda_intel 0000:07:00.3: enabling device (0000 -> 0002) [ 13.927872] input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:03.1/0000:05:00.1/sound/card0/input10 [ 13.940585] input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:03.1/0000:05:00.1/sound/card0/input11 [ 14.116032] snd_hda_codec_realtek hdaudioC1D0: autoconfig for ALC3234: line_outs=1 (0x1b/0x0/0x0/0x0/0x0) type:line [ 14.128006] snd_hda_codec_realtek hdaudioC1D0: speaker_outs=1 (0x14/0x0/0x0/0x0/0x0) [ 14.137518] snd_hda_codec_realtek hdaudioC1D0: hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [ 14.147718] snd_hda_codec_realtek hdaudioC1D0: mono: mono_out=0x0 [ 14.156333] snd_hda_codec_realtek hdaudioC1D0: inputs: [ 14.163264] snd_hda_codec_realtek hdaudioC1D0: Headset Mic=0x19 [ 14.171801] snd_hda_codec_realtek hdaudioC1D0: Headphone Mic=0x1a [ 14.266631] kvm: Nested Virtualization enabled [ 14.273744] SVM: kvm: Nested Paging enabled [ 14.280183] SVM: Virtual VMLOAD VMSAVE supported [ 14.280793] input: HD-Audio Generic Headphone Mic as /devices/pci0000:00/0000:00:08.1/0000:07:00.3/sound/card1/input12 [ 14.286821] SVM: Virtual GIF supported [ 14.299982] input: HD-Audio Generic Line Out as /devices/pci0000:00/0000:00:08.1/0000:07:00.3/sound/card1/input13 [ 21.862639] [drm] amdgpu kernel modesetting enabled. [ 21.869174] checking generic (e0000000 580000) vs hw (e0000000 10000000) [ 21.869176] fb0: switching to amdgpu from EFI VGA [ 21.875414] Console: switching to colour dummy device 80x25 [ 21.881973] amdgpu 0000:05:00.0: vgaarb: deactivate vga console [ 21.889204] amdgpu 0000:05:00.0: enabling device (0006 -> 0007) [ 21.896301] [drm] initializing kernel modesetting (OLAND 0x1002:0x6611 0x1028:0x1002 0x87). [ 21.906152] amdgpu 0000:05:00.0: amdgpu: Trusted Memory Zone (TMZ) feature not supported [ 21.915624] [drm] register mmio base: 0xF0500000 [ 21.921003] [drm] register mmio size: 262144 [ 21.926053] [drm] add ip block number 0 <si_common> [ 21.931750] [drm] add ip block number 1 <gmc_v6_0> [ 21.937386] [drm] add ip block number 2 <si_ih> [ 21.942680] [drm] add ip block number 3 <gfx_v6_0> [ 21.948315] [drm] add ip block number 4 <si_dma> [ 21.953720] [drm] add ip block number 5 <si_dpm> [ 21.959153] [drm] add ip block number 6 <dce_v6_0> [ 21.964787] [drm] add ip block number 7 <uvd_v3_1> [ 21.970427] amdgpu 0000:05:00.0: amdgpu: Fetched VBIOS from VFCT [ 21.977447] amdgpu: ATOM BIOS: 113-C8690301-102 [ 21.982896] [drm] vm size is 64 GB, 2 levels, block size is 10-bit, fragment size is 9-bit [ 22.044359] amdgpu 0000:05:00.0: amdgpu: VRAM: 2048M 0x000000F400000000 - 0x000000F47FFFFFFF (2048M used) [ 22.056487] amdgpu 0000:05:00.0: amdgpu: GART: 1024M 0x000000FF00000000 - 0x000000FF3FFFFFFF [ 22.066767] [drm] Detected VRAM RAM=2048M, BAR=256M [ 22.072499] [drm] RAM width 64bits GDDR5 [ 22.080208] [drm] amdgpu: 2048M of VRAM memory ready [ 22.086015] [drm] amdgpu: 3072M of GTT memory ready. [ 22.092095] [drm] GART: num cpu pages 262144, num gpu pages 262144 [ 22.100997] amdgpu 0000:05:00.0: amdgpu: PCIE GART of 1024M enabled (table at 0x000000F40057F000). [ 22.289396] [drm] Internal thermal controller with fan control [ 22.296859] [drm] amdgpu: dpm initialized [ 22.302026] [drm] AMDGPU Display Connectors [ 22.306997] [drm] Connector 0: [ 22.310611] [drm] DP-1 [ 22.313595] [drm] HPD1 [ 22.316829] [drm] DDC: 0x1950 0x1950 0x1951 0x1951 0x1952 0x1952 0x1953 0x1953 [ 22.325470] [drm] Encoders: [ 22.328987] [drm] DFP1: INTERNAL_UNIPHY [ 22.334118] [drm] Connector 1: [ 22.337731] [drm] DVI-I-1 [ 22.341224] [drm] HPD2 [ 22.344266] [drm] DDC: 0x194c 0x194c 0x194d 0x194d 0x194e 0x194e 0x194f 0x194f [ 22.352935] [drm] Encoders: [ 22.356403] [drm] DFP2: INTERNAL_UNIPHY [ 22.361303] [drm] CRT1: INTERNAL_KLDSCP_DAC1 [ 22.415670] [drm] Found UVD firmware Version: 64.0 Family ID: 13 [ 22.425018] [drm] PCIE gen 3 link speeds already enabled [ 22.432034] amdgpu 0000:05:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000c address=0xfffffe0000 flags=0x0020] [ 22.444890] amdgpu 0000:05:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000c address=0xffffffc000 flags=0x0020] [ 22.809410] amdgpu 0000:05:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000c address=0xfffffde000 flags=0x0000] [ 22.821262] amdgpu 0000:05:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000c address=0xfffffde100 flags=0x0000] [ 22.833199] amdgpu 0000:05:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000c address=0xfffffde200 flags=0x0000] [ 22.845105] amdgpu 0000:05:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000c address=0xfffffde300 flags=0x0000] [ 22.856634] amdgpu 0000:05:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000c address=0xffffffc040 flags=0x0020] [ 22.868630] amdgpu 0000:05:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000c address=0xfffffde400 flags=0x0000] [ 22.880516] amdgpu 0000:05:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000c address=0xfffffde500 flags=0x0000] [ 22.892546] amdgpu 0000:05:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000c address=0xfffffde600 flags=0x0000] [ 23.179596] amdgpu 0000:05:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring gfx test failed (-110) [ 23.190562] [drm:amdgpu_device_init [amdgpu]] *ERROR* hw_init of IP block <gfx_v6_0> failed -110 [ 23.200405] amdgpu 0000:05:00.0: amdgpu: amdgpu_device_ip_init failed [ 23.207524] amdgpu 0000:05:00.0: amdgpu: Fatal error during GPU init [ 23.214632] amdgpu 0000:05:00.0: amdgpu: amdgpu: finishing device. [ 23.222739] amdgpu: probe of 0000:05:00.0 failed with error -110 [ 23.229552] BUG: unable to handle page fault for address: 0000000000005e00 [ 23.237233] #PF: supervisor write access in kernel mode [ 23.243081] #PF: error_code(0x0002) - not-present page [ 23.248858] PGD 103731067 P4D 103731067 PUD 103732067 PMD 0 [ 23.255217] Oops: 0002 [#1] SMP NOPTI [ 23.259350] CPU: 4 PID: 214 Comm: systemd-udevd Not tainted 5.15.0-rc7.mx64.407 #1 [ 23.267824] Hardware name: Dell Inc. OptiPlex 5055 Ryzen CPU/0P03DX, BIOS 1.1.50 07/28/2021 [ 23.277214] RIP: 0010:amdgpu_device_wreg.part.26+0x5d/0xe0 [amdgpu] [ 23.284441] Code: 8e e1 8b 05 4d c3 5e 00 85 c0 7f 2c 5b 5d 41 5c 41 5d 41 5e c3 83 e1 02 75 09 f6 87 60 69 01 00 10 75 4d 48 03 ab 60 09 00 00 <44> 89 6d 00 8b 05 21 c3 5e 00 85 c0 7e d4 48 8b 43 08 0f b7 70 3e [ 23.305471] RSP: 0018:ffffc90000ceba68 EFLAGS: 00010006 [ 23.311432] RAX: 0000000000000246 RBX: ffff88812f300000 RCX: 0000000000000000 [ 23.319490] RDX: 0000000000000154 RSI: 0000000000001780 RDI: ffff88812f300000 [ 23.327501] RBP: 0000000000005e00 R08: ffffffffa0586860 R09: ffff88841effab00 [ 23.335512] R10: 0000000000000000 R11: 000ffffffffff000 R12: 0000000000001780 [ 23.343473] R13: 0000000000000154 R14: 0000000000000246 R15: ffff88812f300a30 [ 23.351461] FS: 00007f6ece88b800(0000) GS:ffff88840eb00000(0000) knlGS:0000000000000000 [ 23.360556] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 23.367102] CR2: 0000000000005e00 CR3: 0000000107f2e000 CR4: 00000000003506e0 [ 23.375103] Call Trace: [ 23.377828] dce_v6_0_audio_endpt_wreg+0x42/0x70 [amdgpu] [ 23.384104] dce_v6_0_sw_fini+0x7f/0xe0 [amdgpu] [ 23.389484] amdgpu_device_fini_sw+0xb1/0x290 [amdgpu] [ 23.395367] amdgpu_driver_release_kms+0x12/0x30 [amdgpu] [ 23.401600] drm_dev_release+0x23/0x40 [drm] [ 23.406439] release_nodes+0x44/0xa0 [ 23.410527] devres_release_all+0x92/0xc0 [ 23.415028] really_probe+0x106/0x470 [ 23.419188] __driver_probe_device+0x81/0x170 [ 23.424080] driver_probe_device+0x1f/0xa0 [ 23.428710] __driver_attach+0xbd/0x170 [ 23.433027] ? __device_attach_driver+0xf0/0xf0 [ 23.438136] bus_for_each_dev+0x76/0xc0 [ 23.442450] bus_add_driver+0x189/0x230 [ 23.446789] ? 0xffffffffa0b7d000 [ 23.450513] driver_register+0x5b/0xf0 [ 23.454753] ? 0xffffffffa0b7d000 [ 23.458459] do_one_initcall+0x4d/0x1e0 [ 23.462826] ? __vunmap+0x1bb/0x210 [ 23.466704] do_init_module+0x5b/0x212 [ 23.470992] load_module+0x2823/0x2c40 [ 23.475150] ? __do_sys_finit_module+0xb1/0x110 [ 23.480272] __do_sys_finit_module+0xb1/0x110 [ 23.485128] do_syscall_64+0x42/0x90 [ 23.489220] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 23.494842] RIP: 0033:0x7f6ecf1f2519 [ 23.498959] Code: 0c 00 b8 ca 00 00 00 0f 05 eb a5 66 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 1f 89 0c 00 f7 d8 64 89 01 48 [ 23.520055] RSP: 002b:00007ffe66832648 EFLAGS: 00000246 ORIG_RAX: 0000000000000139 [ 23.528621] RAX: ffffffffffffffda RBX: 0000000000681470 RCX: 00007f6ecf1f2519 [ 23.536652] RDX: 0000000000000000 RSI: 00007f6ecf35254b RDI: 0000000000000016 [ 23.544680] RBP: 00007f6ecf35254b R08: 0000000000000000 R09: 0000000000020000 [ 23.552728] R10: 0000000000000016 R11: 0000000000000246 R12: 0000000000000000 [ 23.560746] R13: 0000000000675720 R14: 0000000000020000 R15: 0000000000679b90 [ 23.568800] Modules linked in: amdgpu(+) gpu_sched drm_ttm_helper ttm drm_kms_helper kvm_amd snd_ctl_led snd_hda_codec_realtek kvm drm snd_hda_codec_hdmi snd_hda_codec_generic ledtrig_audio snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_hda_core snd_pcm snd_timer fb_sys_fops deflate input_leds syscopyarea led_class sysfillrect sysimgblt snd k10temp efi_pstore wmi_bmof irqbypass wmi acpi_cpufreq soundcore crc32c_intel i2c_piix4 pstore nfsd auth_rpcgss nfs_acl lockd grace sunrpc efivarfs ip_tables x_tables unix ipv6 autofs4 [ 23.620743] CR2: 0000000000005e00 [ 23.624537] ---[ end trace a7c9f1dd6c99f43f ]--- [ 23.880537] RIP: 0010:amdgpu_device_wreg.part.26+0x5d/0xe0 [amdgpu] [ 23.887736] Code: 8e e1 8b 05 4d c3 5e 00 85 c0 7f 2c 5b 5d 41 5c 41 5d 41 5e c3 83 e1 02 75 09 f6 87 60 69 01 00 10 75 4d 48 03 ab 60 09 00 00 <44> 89 6d 00 8b 05 21 c3 5e 00 85 c0 7e d4 48 8b 43 08 0f b7 70 3e [ 23.908898] RSP: 0018:ffffc90000ceba68 EFLAGS: 00010006 [ 23.914812] RAX: 0000000000000246 RBX: ffff88812f300000 RCX: 0000000000000000 [ 23.922872] RDX: 0000000000000154 RSI: 0000000000001780 RDI: ffff88812f300000 [ 23.930895] RBP: 0000000000005e00 R08: ffffffffa0586860 R09: ffff88841effab00 [ 23.938921] R10: 0000000000000000 R11: 000ffffffffff000 R12: 0000000000001780 [ 23.946957] R13: 0000000000000154 R14: 0000000000000246 R15: ffff88812f300a30 [ 23.954998] FS: 00007f6ece88b800(0000) GS:ffff88840eb00000(0000) knlGS:0000000000000000 [ 23.964147] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 23.970638] CR2: 0000000000005e00 CR3: 0000000107f2e000 CR4: 00000000003506e0 [ 27.942588] tg3 0000:03:00.0 net00: renamed from eth0 [ 28.892353] 8021q: 802.1Q VLAN Support v1.8 [ 30.380630] XFS (sda2): Mounting V5 Filesystem [ 30.582163] XFS (sda2): Ending clean mount [ 31.089143] NFSD: Using UMH upcall client tracking operations. [ 31.096579] NFSD: starting 90-second grace period (net f0000098) [ 31.859010] tg3 0000:03:00.0 net00: Link is up at 1000 Mbps, full duplex [ 31.866891] tg3 0000:03:00.0 net00: Flow control is off for TX and off for RX [ 31.874807] tg3 0000:03:00.0 net00: EEE is disabled [ 91.654886] FS-Cache: Netfs 'nfs' registered for caching [ 92.064603] NFS: Registering the id_resolver key type [ 92.070632] Key type id_resolver registered [ 92.075574] Key type id_legacy registered [-- Attachment #3: Type: text/plain, Size: 156 bytes --] _______________________________________________ iommu mailing list iommu@lists.linux-foundation.org https://lists.linuxfoundation.org/mailman/listinfo/iommu ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: I got an IOMMU IO page fault. What to do now? 2021-10-27 16:45 ` Paul Menzel @ 2021-10-27 17:18 ` Robin Murphy -1 siblings, 0 replies; 18+ messages in thread From: Robin Murphy @ 2021-10-27 17:18 UTC (permalink / raw) To: Paul Menzel Cc: x86, Xinhui Pan, LKML, amd-gfx, iommu, Ingo Molnar, Borislav Petkov, Alex Deucher, it+linux-iommu, Thomas Gleixner, Christian König, Christian König, Jörg Rödel, Suravee Suthikulpanit On 27/10/2021 5:45 pm, Paul Menzel wrote: > Dear Robin, > > > On 25.10.21 18:01, Robin Murphy wrote: >> On 2021-10-25 12:23, Christian König wrote: > >>> not sure how the IOMMU gives out addresses, but the printed ones look >>> suspicious to me. Something like we are using an invalid address like >>> -1 or similar. >> >> FWIW those look like believable DMA addresses to me, assuming that the >> DMA mapping APIs are being backed iommu_dma_ops and the device has a >> 40-bit DMA mask, since the IOVA allocator works top-down. >> >> Likely causes are either a race where the dma_unmap_*() call happens >> before the hardware has really stopped accessing the relevant >> addresses, or the device's DMA mask has been set larger than it should >> be, and thus the upper bits have been truncated in the round-trip >> through the hardware. >> >> Given the addresses involved, my suspicions would initially lean >> towards the latter case - the faults are in the very topmost pages >> which imply they're the first things mapped in that range. The other >> contributing factor being the trick that the IOVA allocator plays for >> PCI devices, where it tries to prefer 32-bit addresses. Thus you're >> only likely to see this happen once you already have ~3.5-4GB of live >> DMA-mapped memory to exhaust the 32-bit IOVA space (minus some >> reserved areas) and start allocating from the full DMA mask. You >> should be able to check that with a 5.13 or newer kernel by booting >> with "iommu.forcedac=1" and seeing if it breaks immediately >> (unfortunately with an older kernel you'd have to manually hack >> iommu_dma_alloc_iova() to the same effect). > > I booted Linux 5.15-rc7 with `iommu.forcedac=1` and the system booted, > and I could log in remotely over SSH. Please find the Linux kernel > messages attached. (The system logs say lightdm failed to start, but it > might be some other issue due to a change in the operating system.) OK, that looks like it's made the GPU blow up straight away, which is what I was hoping for (and also appears to reveal another bug where it's not handling probe failure very well - possibly trying to remove a non-existent audio device?). Lightdm presumably fails to start because it doesn't find any display devices, since amdgpu failed to probe. If you can boot the same kernel without "iommu.forcedac" and get a successful probe and working display, that will imply that it is managing to work OK with 32-bit DMA addresses, at which point I'd have to leave it to Christian and Alex to figure out exactly where DMA addresses are getting mangled. The only thing that stands out to me is the reference to "gfx_v6_0", which makes me wonder whether it's related to gmc_v6_0_sw_init() where a 44-bit DMA mask gets set. If so, that would suggest that either this particular model of GPU is more limited than expected, or that SoC only has 40 bits of address wired up between the PCI host bridge and the IOMMU. Cheers, Robin. ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: I got an IOMMU IO page fault. What to do now? @ 2021-10-27 17:18 ` Robin Murphy 0 siblings, 0 replies; 18+ messages in thread From: Robin Murphy @ 2021-10-27 17:18 UTC (permalink / raw) To: Paul Menzel Cc: x86, Christian König, Xinhui Pan, LKML, amd-gfx, iommu, Ingo Molnar, Borislav Petkov, Alex Deucher, it+linux-iommu, Thomas Gleixner, Christian König On 27/10/2021 5:45 pm, Paul Menzel wrote: > Dear Robin, > > > On 25.10.21 18:01, Robin Murphy wrote: >> On 2021-10-25 12:23, Christian König wrote: > >>> not sure how the IOMMU gives out addresses, but the printed ones look >>> suspicious to me. Something like we are using an invalid address like >>> -1 or similar. >> >> FWIW those look like believable DMA addresses to me, assuming that the >> DMA mapping APIs are being backed iommu_dma_ops and the device has a >> 40-bit DMA mask, since the IOVA allocator works top-down. >> >> Likely causes are either a race where the dma_unmap_*() call happens >> before the hardware has really stopped accessing the relevant >> addresses, or the device's DMA mask has been set larger than it should >> be, and thus the upper bits have been truncated in the round-trip >> through the hardware. >> >> Given the addresses involved, my suspicions would initially lean >> towards the latter case - the faults are in the very topmost pages >> which imply they're the first things mapped in that range. The other >> contributing factor being the trick that the IOVA allocator plays for >> PCI devices, where it tries to prefer 32-bit addresses. Thus you're >> only likely to see this happen once you already have ~3.5-4GB of live >> DMA-mapped memory to exhaust the 32-bit IOVA space (minus some >> reserved areas) and start allocating from the full DMA mask. You >> should be able to check that with a 5.13 or newer kernel by booting >> with "iommu.forcedac=1" and seeing if it breaks immediately >> (unfortunately with an older kernel you'd have to manually hack >> iommu_dma_alloc_iova() to the same effect). > > I booted Linux 5.15-rc7 with `iommu.forcedac=1` and the system booted, > and I could log in remotely over SSH. Please find the Linux kernel > messages attached. (The system logs say lightdm failed to start, but it > might be some other issue due to a change in the operating system.) OK, that looks like it's made the GPU blow up straight away, which is what I was hoping for (and also appears to reveal another bug where it's not handling probe failure very well - possibly trying to remove a non-existent audio device?). Lightdm presumably fails to start because it doesn't find any display devices, since amdgpu failed to probe. If you can boot the same kernel without "iommu.forcedac" and get a successful probe and working display, that will imply that it is managing to work OK with 32-bit DMA addresses, at which point I'd have to leave it to Christian and Alex to figure out exactly where DMA addresses are getting mangled. The only thing that stands out to me is the reference to "gfx_v6_0", which makes me wonder whether it's related to gmc_v6_0_sw_init() where a 44-bit DMA mask gets set. If so, that would suggest that either this particular model of GPU is more limited than expected, or that SoC only has 40 bits of address wired up between the PCI host bridge and the IOMMU. Cheers, Robin. _______________________________________________ iommu mailing list iommu@lists.linux-foundation.org https://lists.linuxfoundation.org/mailman/listinfo/iommu ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: I got an IOMMU IO page fault. What to do now? 2021-10-27 17:18 ` Robin Murphy @ 2021-10-27 17:24 ` Alex Deucher -1 siblings, 0 replies; 18+ messages in thread From: Alex Deucher @ 2021-10-27 17:24 UTC (permalink / raw) To: Robin Murphy Cc: Paul Menzel, X86 ML, Xinhui Pan, LKML, amd-gfx list, list@263.net:IOMMU DRIVERS <iommu@lists.linux-foundation.org>, Joerg Roedel <joro@8bytes.org>, , Ingo Molnar, Borislav Petkov, Alex Deucher, it+linux-iommu, Thomas Gleixner, Christian König, Christian König, Jörg Rödel, Suravee Suthikulpanit On Wed, Oct 27, 2021 at 1:20 PM Robin Murphy <robin.murphy@arm.com> wrote: > > On 27/10/2021 5:45 pm, Paul Menzel wrote: > > Dear Robin, > > > > > > On 25.10.21 18:01, Robin Murphy wrote: > >> On 2021-10-25 12:23, Christian König wrote: > > > >>> not sure how the IOMMU gives out addresses, but the printed ones look > >>> suspicious to me. Something like we are using an invalid address like > >>> -1 or similar. > >> > >> FWIW those look like believable DMA addresses to me, assuming that the > >> DMA mapping APIs are being backed iommu_dma_ops and the device has a > >> 40-bit DMA mask, since the IOVA allocator works top-down. > >> > >> Likely causes are either a race where the dma_unmap_*() call happens > >> before the hardware has really stopped accessing the relevant > >> addresses, or the device's DMA mask has been set larger than it should > >> be, and thus the upper bits have been truncated in the round-trip > >> through the hardware. > >> > >> Given the addresses involved, my suspicions would initially lean > >> towards the latter case - the faults are in the very topmost pages > >> which imply they're the first things mapped in that range. The other > >> contributing factor being the trick that the IOVA allocator plays for > >> PCI devices, where it tries to prefer 32-bit addresses. Thus you're > >> only likely to see this happen once you already have ~3.5-4GB of live > >> DMA-mapped memory to exhaust the 32-bit IOVA space (minus some > >> reserved areas) and start allocating from the full DMA mask. You > >> should be able to check that with a 5.13 or newer kernel by booting > >> with "iommu.forcedac=1" and seeing if it breaks immediately > >> (unfortunately with an older kernel you'd have to manually hack > >> iommu_dma_alloc_iova() to the same effect). > > > > I booted Linux 5.15-rc7 with `iommu.forcedac=1` and the system booted, > > and I could log in remotely over SSH. Please find the Linux kernel > > messages attached. (The system logs say lightdm failed to start, but it > > might be some other issue due to a change in the operating system.) > > OK, that looks like it's made the GPU blow up straight away, which is > what I was hoping for (and also appears to reveal another bug where it's > not handling probe failure very well - possibly trying to remove a > non-existent audio device?). Lightdm presumably fails to start because > it doesn't find any display devices, since amdgpu failed to probe. > > If you can boot the same kernel without "iommu.forcedac" and get a > successful probe and working display, that will imply that it is > managing to work OK with 32-bit DMA addresses, at which point I'd have > to leave it to Christian and Alex to figure out exactly where DMA > addresses are getting mangled. The only thing that stands out to me is > the reference to "gfx_v6_0", which makes me wonder whether it's related > to gmc_v6_0_sw_init() where a 44-bit DMA mask gets set. If so, that > would suggest that either this particular model of GPU is more limited > than expected, or that SoC only has 40 bits of address wired up between > the PCI host bridge and the IOMMU. That device only has a 40 bit DMA mask. It looks like the code is wrong there. Alex > > Cheers, > Robin. ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: I got an IOMMU IO page fault. What to do now? @ 2021-10-27 17:24 ` Alex Deucher 0 siblings, 0 replies; 18+ messages in thread From: Alex Deucher @ 2021-10-27 17:24 UTC (permalink / raw) To: Robin Murphy Cc: Paul Menzel, Xinhui Pan, Christian König, X86 ML, LKML, amd-gfx list, list@263.net:IOMMU DRIVERS <iommu@lists.linux-foundation.org>, Joerg Roedel <joro@8bytes.org>, , Ingo Molnar, Borislav Petkov, Alex Deucher, it+linux-iommu, Thomas Gleixner, Christian König On Wed, Oct 27, 2021 at 1:20 PM Robin Murphy <robin.murphy@arm.com> wrote: > > On 27/10/2021 5:45 pm, Paul Menzel wrote: > > Dear Robin, > > > > > > On 25.10.21 18:01, Robin Murphy wrote: > >> On 2021-10-25 12:23, Christian König wrote: > > > >>> not sure how the IOMMU gives out addresses, but the printed ones look > >>> suspicious to me. Something like we are using an invalid address like > >>> -1 or similar. > >> > >> FWIW those look like believable DMA addresses to me, assuming that the > >> DMA mapping APIs are being backed iommu_dma_ops and the device has a > >> 40-bit DMA mask, since the IOVA allocator works top-down. > >> > >> Likely causes are either a race where the dma_unmap_*() call happens > >> before the hardware has really stopped accessing the relevant > >> addresses, or the device's DMA mask has been set larger than it should > >> be, and thus the upper bits have been truncated in the round-trip > >> through the hardware. > >> > >> Given the addresses involved, my suspicions would initially lean > >> towards the latter case - the faults are in the very topmost pages > >> which imply they're the first things mapped in that range. The other > >> contributing factor being the trick that the IOVA allocator plays for > >> PCI devices, where it tries to prefer 32-bit addresses. Thus you're > >> only likely to see this happen once you already have ~3.5-4GB of live > >> DMA-mapped memory to exhaust the 32-bit IOVA space (minus some > >> reserved areas) and start allocating from the full DMA mask. You > >> should be able to check that with a 5.13 or newer kernel by booting > >> with "iommu.forcedac=1" and seeing if it breaks immediately > >> (unfortunately with an older kernel you'd have to manually hack > >> iommu_dma_alloc_iova() to the same effect). > > > > I booted Linux 5.15-rc7 with `iommu.forcedac=1` and the system booted, > > and I could log in remotely over SSH. Please find the Linux kernel > > messages attached. (The system logs say lightdm failed to start, but it > > might be some other issue due to a change in the operating system.) > > OK, that looks like it's made the GPU blow up straight away, which is > what I was hoping for (and also appears to reveal another bug where it's > not handling probe failure very well - possibly trying to remove a > non-existent audio device?). Lightdm presumably fails to start because > it doesn't find any display devices, since amdgpu failed to probe. > > If you can boot the same kernel without "iommu.forcedac" and get a > successful probe and working display, that will imply that it is > managing to work OK with 32-bit DMA addresses, at which point I'd have > to leave it to Christian and Alex to figure out exactly where DMA > addresses are getting mangled. The only thing that stands out to me is > the reference to "gfx_v6_0", which makes me wonder whether it's related > to gmc_v6_0_sw_init() where a 44-bit DMA mask gets set. If so, that > would suggest that either this particular model of GPU is more limited > than expected, or that SoC only has 40 bits of address wired up between > the PCI host bridge and the IOMMU. That device only has a 40 bit DMA mask. It looks like the code is wrong there. Alex > > Cheers, > Robin. _______________________________________________ iommu mailing list iommu@lists.linux-foundation.org https://lists.linuxfoundation.org/mailman/listinfo/iommu ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: I got an IOMMU IO page fault. What to do now? 2021-10-27 17:24 ` Alex Deucher @ 2021-10-27 17:28 ` Alex Deucher -1 siblings, 0 replies; 18+ messages in thread From: Alex Deucher @ 2021-10-27 17:28 UTC (permalink / raw) To: Robin Murphy Cc: Paul Menzel, X86 ML, Xinhui Pan, LKML, amd-gfx list, list@263.net:IOMMU DRIVERS <iommu@lists.linux-foundation.org>, Joerg Roedel <joro@8bytes.org>, , Ingo Molnar, Borislav Petkov, Alex Deucher, it+linux-iommu, Thomas Gleixner, Christian König, Christian König, Jörg Rödel, Suravee Suthikulpanit [-- Attachment #1: Type: text/plain, Size: 3511 bytes --] On Wed, Oct 27, 2021 at 1:24 PM Alex Deucher <alexdeucher@gmail.com> wrote: > > On Wed, Oct 27, 2021 at 1:20 PM Robin Murphy <robin.murphy@arm.com> wrote: > > > > On 27/10/2021 5:45 pm, Paul Menzel wrote: > > > Dear Robin, > > > > > > > > > On 25.10.21 18:01, Robin Murphy wrote: > > >> On 2021-10-25 12:23, Christian König wrote: > > > > > >>> not sure how the IOMMU gives out addresses, but the printed ones look > > >>> suspicious to me. Something like we are using an invalid address like > > >>> -1 or similar. > > >> > > >> FWIW those look like believable DMA addresses to me, assuming that the > > >> DMA mapping APIs are being backed iommu_dma_ops and the device has a > > >> 40-bit DMA mask, since the IOVA allocator works top-down. > > >> > > >> Likely causes are either a race where the dma_unmap_*() call happens > > >> before the hardware has really stopped accessing the relevant > > >> addresses, or the device's DMA mask has been set larger than it should > > >> be, and thus the upper bits have been truncated in the round-trip > > >> through the hardware. > > >> > > >> Given the addresses involved, my suspicions would initially lean > > >> towards the latter case - the faults are in the very topmost pages > > >> which imply they're the first things mapped in that range. The other > > >> contributing factor being the trick that the IOVA allocator plays for > > >> PCI devices, where it tries to prefer 32-bit addresses. Thus you're > > >> only likely to see this happen once you already have ~3.5-4GB of live > > >> DMA-mapped memory to exhaust the 32-bit IOVA space (minus some > > >> reserved areas) and start allocating from the full DMA mask. You > > >> should be able to check that with a 5.13 or newer kernel by booting > > >> with "iommu.forcedac=1" and seeing if it breaks immediately > > >> (unfortunately with an older kernel you'd have to manually hack > > >> iommu_dma_alloc_iova() to the same effect). > > > > > > I booted Linux 5.15-rc7 with `iommu.forcedac=1` and the system booted, > > > and I could log in remotely over SSH. Please find the Linux kernel > > > messages attached. (The system logs say lightdm failed to start, but it > > > might be some other issue due to a change in the operating system.) > > > > OK, that looks like it's made the GPU blow up straight away, which is > > what I was hoping for (and also appears to reveal another bug where it's > > not handling probe failure very well - possibly trying to remove a > > non-existent audio device?). Lightdm presumably fails to start because > > it doesn't find any display devices, since amdgpu failed to probe. > > > > If you can boot the same kernel without "iommu.forcedac" and get a > > successful probe and working display, that will imply that it is > > managing to work OK with 32-bit DMA addresses, at which point I'd have > > to leave it to Christian and Alex to figure out exactly where DMA > > addresses are getting mangled. The only thing that stands out to me is > > the reference to "gfx_v6_0", which makes me wonder whether it's related > > to gmc_v6_0_sw_init() where a 44-bit DMA mask gets set. If so, that > > would suggest that either this particular model of GPU is more limited > > than expected, or that SoC only has 40 bits of address wired up between > > the PCI host bridge and the IOMMU. > > That device only has a 40 bit DMA mask. It looks like the code is wrong there. The attached patch should fix it. Alex [-- Attachment #2: 0001-drm-amdgpu-gmc6-fix-DMA-mask.patch --] [-- Type: text/x-patch, Size: 974 bytes --] From 39735f761234fa480d393b1477dd9d4006783f34 Mon Sep 17 00:00:00 2001 From: Alex Deucher <alexander.deucher@amd.com> Date: Wed, 27 Oct 2021 13:26:19 -0400 Subject: [PATCH] drm/amdgpu/gmc6: fix DMA mask The DMA mask on SI parts is 40 bits not 44. Looks like a copy paste typo. Signed-off-by: Alex Deucher <alexander.deucher@amd.com> --- drivers/gpu/drm/amd/amdgpu/gmc_v6_0.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/amd/amdgpu/gmc_v6_0.c b/drivers/gpu/drm/amd/amdgpu/gmc_v6_0.c index 0e81e03e9b49..a9354cb2d639 100644 --- a/drivers/gpu/drm/amd/amdgpu/gmc_v6_0.c +++ b/drivers/gpu/drm/amd/amdgpu/gmc_v6_0.c @@ -841,7 +841,7 @@ static int gmc_v6_0_sw_init(void *handle) adev->gmc.mc_mask = 0xffffffffffULL; - r = dma_set_mask_and_coherent(adev->dev, DMA_BIT_MASK(44)); + r = dma_set_mask_and_coherent(adev->dev, DMA_BIT_MASK(40)); if (r) { dev_warn(adev->dev, "No suitable DMA available.\n"); return r; -- 2.31.1 ^ permalink raw reply related [flat|nested] 18+ messages in thread
* Re: I got an IOMMU IO page fault. What to do now? @ 2021-10-27 17:28 ` Alex Deucher 0 siblings, 0 replies; 18+ messages in thread From: Alex Deucher @ 2021-10-27 17:28 UTC (permalink / raw) To: Robin Murphy Cc: Paul Menzel, Xinhui Pan, Christian König, X86 ML, LKML, amd-gfx list, list@263.net:IOMMU DRIVERS <iommu@lists.linux-foundation.org>, Joerg Roedel <joro@8bytes.org>, , Ingo Molnar, Borislav Petkov, Alex Deucher, it+linux-iommu, Thomas Gleixner, Christian König [-- Attachment #1: Type: text/plain, Size: 3511 bytes --] On Wed, Oct 27, 2021 at 1:24 PM Alex Deucher <alexdeucher@gmail.com> wrote: > > On Wed, Oct 27, 2021 at 1:20 PM Robin Murphy <robin.murphy@arm.com> wrote: > > > > On 27/10/2021 5:45 pm, Paul Menzel wrote: > > > Dear Robin, > > > > > > > > > On 25.10.21 18:01, Robin Murphy wrote: > > >> On 2021-10-25 12:23, Christian König wrote: > > > > > >>> not sure how the IOMMU gives out addresses, but the printed ones look > > >>> suspicious to me. Something like we are using an invalid address like > > >>> -1 or similar. > > >> > > >> FWIW those look like believable DMA addresses to me, assuming that the > > >> DMA mapping APIs are being backed iommu_dma_ops and the device has a > > >> 40-bit DMA mask, since the IOVA allocator works top-down. > > >> > > >> Likely causes are either a race where the dma_unmap_*() call happens > > >> before the hardware has really stopped accessing the relevant > > >> addresses, or the device's DMA mask has been set larger than it should > > >> be, and thus the upper bits have been truncated in the round-trip > > >> through the hardware. > > >> > > >> Given the addresses involved, my suspicions would initially lean > > >> towards the latter case - the faults are in the very topmost pages > > >> which imply they're the first things mapped in that range. The other > > >> contributing factor being the trick that the IOVA allocator plays for > > >> PCI devices, where it tries to prefer 32-bit addresses. Thus you're > > >> only likely to see this happen once you already have ~3.5-4GB of live > > >> DMA-mapped memory to exhaust the 32-bit IOVA space (minus some > > >> reserved areas) and start allocating from the full DMA mask. You > > >> should be able to check that with a 5.13 or newer kernel by booting > > >> with "iommu.forcedac=1" and seeing if it breaks immediately > > >> (unfortunately with an older kernel you'd have to manually hack > > >> iommu_dma_alloc_iova() to the same effect). > > > > > > I booted Linux 5.15-rc7 with `iommu.forcedac=1` and the system booted, > > > and I could log in remotely over SSH. Please find the Linux kernel > > > messages attached. (The system logs say lightdm failed to start, but it > > > might be some other issue due to a change in the operating system.) > > > > OK, that looks like it's made the GPU blow up straight away, which is > > what I was hoping for (and also appears to reveal another bug where it's > > not handling probe failure very well - possibly trying to remove a > > non-existent audio device?). Lightdm presumably fails to start because > > it doesn't find any display devices, since amdgpu failed to probe. > > > > If you can boot the same kernel without "iommu.forcedac" and get a > > successful probe and working display, that will imply that it is > > managing to work OK with 32-bit DMA addresses, at which point I'd have > > to leave it to Christian and Alex to figure out exactly where DMA > > addresses are getting mangled. The only thing that stands out to me is > > the reference to "gfx_v6_0", which makes me wonder whether it's related > > to gmc_v6_0_sw_init() where a 44-bit DMA mask gets set. If so, that > > would suggest that either this particular model of GPU is more limited > > than expected, or that SoC only has 40 bits of address wired up between > > the PCI host bridge and the IOMMU. > > That device only has a 40 bit DMA mask. It looks like the code is wrong there. The attached patch should fix it. Alex [-- Attachment #2: 0001-drm-amdgpu-gmc6-fix-DMA-mask.patch --] [-- Type: text/x-patch, Size: 974 bytes --] From 39735f761234fa480d393b1477dd9d4006783f34 Mon Sep 17 00:00:00 2001 From: Alex Deucher <alexander.deucher@amd.com> Date: Wed, 27 Oct 2021 13:26:19 -0400 Subject: [PATCH] drm/amdgpu/gmc6: fix DMA mask The DMA mask on SI parts is 40 bits not 44. Looks like a copy paste typo. Signed-off-by: Alex Deucher <alexander.deucher@amd.com> --- drivers/gpu/drm/amd/amdgpu/gmc_v6_0.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/amd/amdgpu/gmc_v6_0.c b/drivers/gpu/drm/amd/amdgpu/gmc_v6_0.c index 0e81e03e9b49..a9354cb2d639 100644 --- a/drivers/gpu/drm/amd/amdgpu/gmc_v6_0.c +++ b/drivers/gpu/drm/amd/amdgpu/gmc_v6_0.c @@ -841,7 +841,7 @@ static int gmc_v6_0_sw_init(void *handle) adev->gmc.mc_mask = 0xffffffffffULL; - r = dma_set_mask_and_coherent(adev->dev, DMA_BIT_MASK(44)); + r = dma_set_mask_and_coherent(adev->dev, DMA_BIT_MASK(40)); if (r) { dev_warn(adev->dev, "No suitable DMA available.\n"); return r; -- 2.31.1 [-- Attachment #3: Type: text/plain, Size: 156 bytes --] _______________________________________________ iommu mailing list iommu@lists.linux-foundation.org https://lists.linuxfoundation.org/mailman/listinfo/iommu ^ permalink raw reply related [flat|nested] 18+ messages in thread
end of thread, other threads:[~2021-10-27 17:28 UTC | newest] Thread overview: 18+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2021-10-25 10:25 I got an IOMMU IO page fault. What to do now? Paul Menzel 2021-10-25 10:25 ` Paul Menzel 2021-10-25 11:23 ` Christian König 2021-10-25 11:23 ` Christian König 2021-10-25 11:38 ` Paul Menzel 2021-10-25 11:38 ` Paul Menzel 2021-10-25 16:01 ` Robin Murphy 2021-10-25 16:01 ` Robin Murphy 2021-10-25 16:42 ` Christian König 2021-10-25 16:42 ` Christian König via iommu 2021-10-27 16:45 ` Paul Menzel 2021-10-27 16:45 ` Paul Menzel 2021-10-27 17:18 ` Robin Murphy 2021-10-27 17:18 ` Robin Murphy 2021-10-27 17:24 ` Alex Deucher 2021-10-27 17:24 ` Alex Deucher 2021-10-27 17:28 ` Alex Deucher 2021-10-27 17:28 ` Alex Deucher
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.