From owner-freebsd-bugs@freebsd.org Wed Sep 30 00:02:19 2015 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 65831A0BDCD for ; Wed, 30 Sep 2015 00:02:19 +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 384551084 for ; Wed, 30 Sep 2015 00:02:19 +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 t8U02J8P072456 for ; Wed, 30 Sep 2015 00:02:19 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 201461] switching back to sc(4) or vt(4) console fails with nvidia.ko Date: Wed, 30 Sep 2015 00:02:18 +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: 10.1-STABLE X-Bugzilla-Keywords: vt X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: aritger@nvidia.com X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit 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.20 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Sep 2015 00:02:19 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201461 --- Comment #11 from Andy Ritger --- Hi Tony. Restoring the text console can be fragile. This is often sensitive to: * The NVIDIA driver version. * The particular graphics board you are using. * How the monitor is connected to the graphics board (DVI, 15-pin VGA, DisplayPort, etc). Please be sure you have the latest version of the NVIDIA FreeBSD driver. I think the latest right now is 355.11: http://www.nvidia.com/Download/driverResults.aspx/90397/en-us If you can experiment with either different graphics boards or different connectors between the monitor and the graphics board to attempt to isolate which parameters repro or don't repro this bug, that would help. A few other things: * Does the monitor still have sync? Most monitors have an LED (e.g., green when active, amber when sync is lost, blank when powered off) Distinguishing between those will help to understand if restoring the text console is driving modetimings that the monitor can't handle (monitor lost sync), or if something about redrawing the console got broken (image on monitor is black, but monitor is active and did not lose sync) * The NVIDIA FreeBSD driver provides a script, nvidia-bug-report.sh, that will gather various information about your GPU and system. It would be helpful to attach that to this bug. * The NVIDIA FreeBSD driver includes a utility, nvidia-debugdump, which can capture various GPU hw state. Could you run `nvidia-debugdump -D` and attach the file it produces? Thanks. -- You are receiving this mail because: You are the assignee for the bug.