From owner-freebsd-bugs@freebsd.org Mon Dec 4 22:54:20 2017 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 24EAAE6D412 for ; Mon, 4 Dec 2017 22:54:20 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 12E157D23B for ; Mon, 4 Dec 2017 22:54:20 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id vB4MsJa3030347 for ; Mon, 4 Dec 2017 22:54:19 GMT (envelope-from bugzilla-noreply@freebsd.org) 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 Date: Mon, 04 Dec 2017 22:54:19 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.1-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: sblachmann@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Dec 2017 22:54:20 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D224069 --- Comment #10 from Stefan B. --- (In reply to Jung-uk Kim from comment #9) > We can add few knobs in the driver to work around these issues=20 > and turn them on by default if NVIDIA controller is found. That would be the right thing to do then. Would save a lot of bad UX. And the supporting guys on the forums would be happy if these constantly recurring nvidia problems would be mitigated (at least to a degree). It's not nice to see people going back to Linux just because the text conso= le is unusable etc. > The root cause is NVIDIA does not really support VESA BIOS re-POST=20 > and save/restore state calls. It just checks few bits and returns=20 > immediately if they are set/clear. Aww. Didn't know that. You did obviously a lot of research. Kudos! This is a very bad thing to learn, as this could make STD with Nvidia cards virtually impossible without involving X. (Btw, do you know whether ATI cards behave better in this regard, supporting state saving/restoring?) --=20 You are receiving this mail because: You are the assignee for the bug.=