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/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D224069 --- 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 car= ds. ... > 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 cal= ls.=20 It just checks few bits and returns immediately if they are set/clear. I h= ave a feeling that they intentionally did it to make reverse engineering harder= .=20 On top of that, they don't provide any information to improve the situation= .=20 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 NVI= DIA 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 the= m on by default if NVIDIA controller is found. --=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-224069-8-jTJiD5CPL5>