Date: Fri, 09 Dec 2022 16:37:43 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 268276] Regression: Black screen on resume caused by commit 9e007a88d65b Message-ID: <bug-268276-227-JNBvW0klzV@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-268276-227@https.bugs.freebsd.org/bugzilla/> References: <bug-268276-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D268276 --- Comment #2 from Austin Shafer <ashafer@badland.io> --- I don't think it's directly affecting the GPU per se, but instead is causing something wacky to happen with the PCI bus. Then the GPU can't be found on = the bus, so the nvidia driver bails and the screen stays black. The GPU fans fu= lly spin up, so it's not like the GPU doesn't have power. Thanks, saving CPU makes sense, polling on resume is an interesting idea. I wonder if not polling makes us do something different that causes us to mis= s an interrupt or something. It's hard to know without having more info, but I'm= not sure what I should do to get better data? --- Also I feel like I should mention this (probably unrelated) issue: https://github.com/amshafer/nvidia-driver/issues/1 This predates commit 9e007a88d65b and therefore has a different root cause,= but I'm linking it because the symptoms are the same. In that case it looked li= ke ACPI/buggy firmware, but I find it interesting as a second data point. Maybe the atkbd polling causes us or the firmware to hit a situation like this for some reason. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-268276-227-JNBvW0klzV>