@Aaron: Thanks for the explanation... we can dig back knowing what to look for now.
@demonx and others: Were the lspci results attached to your reports captured from a session where this bug was triggered? If not, can you boot those PCs into a configuration that triggers the bug and, if you have a console or SSH shell, re-run
sudo sh -c 'lspci -nnvvvxxxx -q -d10de:* > /tmp/nvidia-lspci.log'
and attach the results to a new comment that makes clear the log was captured whilst the bug was active.
@Aaron: Thanks for the explanation... we can dig back knowing what to look for now.
@demonx and others: Were the lspci results attached to your reports captured from a session where this bug was triggered? If not, can you boot those PCs into a configuration that triggers the bug and, if you have a console or SSH shell, re-run
sudo sh -c 'lspci -nnvvvxxxx -q -d10de:* > /tmp/nvidia- lspci.log'
and attach the results to a new comment that makes clear the log was captured whilst the bug was active.