Comment 20 for bug 2026790

Sure,I get it.

The work around of using Xorg does not resolve the issue on this setup, Wayland and Xorg both suffer different problems. Just wanted to call that out!

Simple open questions:

1. The NVIDIA DRM component here appears to be a culprit. Can I disable it ? Is there an open source driver that performs better than NVIDIA's proprietary driver here in this configuration you have run across ?

2. Exercising the NVIDIA GPU by using a VM (VirtualBox) was used as a method to troubleshoot and use it in a real world scenario. It may have run afoul of other bugs. Is there a better way to exercise the NVIDIA GPU and/or the Intel GPU and stay within the context of this ticket ?

3. gdm failing(?) to start when the NVIDIA GPU is set as PRIME, preventing GUI login seems like a bug. Would you like an Xorg(?) bug ticket for this ?

4. Please be advised, selecting Xorg as a server from the gdm login screen was never an option for me. Should I be concerned that a version or code difference here is leading us to different results ?

5. split_lock detection has knock-on effects due to the delay introduced, this was only highlighted by kernel logs using the the VirtualBox implementation when I began to exercise the GPU. Can we safely rule out split_lock's for this ticket ? Or is it worth troubleshooting further in the event I am experiencing the effects, but they're simply not getting reliably *detected* by the Tiger Lake or split_lock kernel logic ?

Thanks.