| 2024-03-08 13:01:08 |
Simon Fels |
description |
We see sporadically the NVIDIA GPU reporting errors from within the firmware like
Mar 08 02:50:28 ip-172-31-85-157 kernel: NVRM: Xid (PCI:0000:00:1f): 32, pid=109337, name=vkr-ring-1, Channel ID 0000006f intr0 00040000
Mar 08 02:50:28 ip-172-31-85-157 kernel: NVRM: Xid (PCI:0000:00:1f): 32, pid=109337, name=vkr-ring-1, Channel ID 0000006f intr0 00040000
when using VirGL and the NVIDIA Vulkan driver.
It is unclear at this point what exactly is triggering the error but it causes the Vulkan execution in the particular process to hang and mesa reporting
03-08 02:55:41.970 128 147 D MESA-VIRTIO: stuck in client wait with iter at 4096
until Android triggers an ANR report. |
We see sporadically the NVIDIA GPU reporting errors from within the firmware like
Mar 08 02:50:28 ip-172-31-85-157 kernel: NVRM: Xid (PCI:0000:00:1f): 32, pid=109337, name=vkr-ring-1, Channel ID 0000006f intr0 00040000
Mar 08 02:50:28 ip-172-31-85-157 kernel: NVRM: Xid (PCI:0000:00:1f): 32, pid=109337, name=vkr-ring-1, Channel ID 0000006f intr0 00040000
when using VirGL and the NVIDIA Vulkan driver.
It is unclear at this point what exactly is triggering the error but it causes the Vulkan execution in the particular process to hang and mesa reporting
03-08 02:55:41.970 128 147 D MESA-VIRTIO: stuck in client wait with iter at 4096
until Android triggers an ANR report.
The same issue has been seen on both arm64 and amd64. |
|
