From owner-freebsd-bugs@freebsd.org  Wed Sep 30 18:09:22 2015
Return-Path: <owner-freebsd-bugs@freebsd.org>
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 1AC63A0CE52
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Wed, 30 Sep 2015 18:09:22 +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 06BCE160A
 for <freebsd-bugs@FreeBSD.org>; Wed, 30 Sep 2015 18:09:22 +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 t8UI9LOU045054
 for <freebsd-bugs@FreeBSD.org>; Wed, 30 Sep 2015 18:09:21 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 18:09:22 +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: tony@git-pull.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: attachments.created
Message-ID: <bug-201461-8-H70pSrugpo@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-201461-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-201461-8@https.bugs.freebsd.org/bugzilla/>
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 <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Sep 2015 18:09:22 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201461

--- Comment #14 from Tony Narlock <tony@git-pull.com> ---
Created attachment 161579
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=161579&action=edit
sudo nvidia-bug-report.sh

(In reply to Andy Ritger from comment #11)

$ sudo nvidia-bug-report.sh
Password:

nvidia-bug-report.sh will now collect information about your
system and create the file 'nvidia-bug-report.log.gz' in the current
directory.  It may take several seconds to run.  In some
cases, it may hang trying to capture data generated dynamically
by the FreeBSD kernel and/or the NVIDIA kernel module.  While
the bug report log file will be incomplete if this happens, it
may still contain enough data to diagnose your problem.

Please include the 'nvidia-bug-report.log.gz' log file when reporting
your bug to freebsd-gfx-bugs@nvidia.com.

Running nvidia-bug-report.sh... complete.

The file nvidia-bug-report.log.gz has been created; please send this
report, along with a description of your bug, to
freebsd-gfx-bugs@nvidia.com.

-- 
You are receiving this mail because:
You are the assignee for the bug.