Date: Mon, 04 Dec 2017 22:22:15 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 224069] (Fix included) Use of uninitalized register value in vesa.ko, causing X, text console and suspend/resume to fail Message-ID: <bug-224069-8-jTJiD5CPL5@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-224069-8@https.bugs.freebsd.org/bugzilla/> References: <bug-224069-8@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224069 --- Comment #9 from Jung-uk Kim <jkim@FreeBSD.org> --- (In reply to Stefan B. from comment #8) > Btw, are you still interested in improving suspend/resume from STR to STD? No, not really. > In the FreeBSD forums, there are constant complaints regarding Nvidia cards. ... > So I have the strong feeling that there is a serious problem with the vesa > module. But that is just my (possibly misleading) intuition. Ah, NVIDIA... It is a well known problem for many years. The root cause is NVIDIA does not really support VESA BIOS re-POST and save/restore state calls. It just checks few bits and returns immediately if they are set/clear. I have a feeling that they intentionally did it to make reverse engineering harder. On top of that, they don't provide any information to improve the situation. Long time ago, I even bought couple of cheap NVIDIA controllers to fix the problem but soon I gave up because I realized it was too complicated and I wasn't desperate. So, no, VESA module have no "serious" problem. Just NVIDIA doesn't want us to mess around with their hardware although we own it. We can add few knobs in the driver to work around these issues and turn them on by default if NVIDIA controller is found. -- You are receiving this mail because: You are the assignee for the bug.help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-224069-8-jTJiD5CPL5>