All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 91705] New: [NVE7] GPU crash (read fault) on boot w/ DMI+HDMI outputs
Date: Thu, 20 Aug 2015 18:35:08 +0000	[thread overview]
Message-ID: <bug-91705-8800@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2315 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=91705

            Bug ID: 91705
           Summary: [NVE7] GPU crash (read fault) on boot w/ DMI+HDMI
                    outputs
           Product: xorg
           Version: unspecified
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Driver/nouveau
          Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
          Reporter: zackw-VmQCmMdMyN0AvxtiuMwx3w@public.gmane.org
        QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org

I have a brand new computer with an NVE7-based card (GT740); the card has three
physical outputs, 1 each DVI, HDMI, and VGA.  I have two monitors.  If I
connect one to the DVI and one to the VGA port, or if I just connect one
monitor to the DVI port, it boots successfully.  But if I connect one monitor
to the DVI port and the other to the HDMI port (using an HDMI-to-DVI adapter
cable), the GPU and/or the kernel component of the nouveau driver crash
immediately upon switching the console to nouveaufb.  (This happens before the
X server starts.) Both monitors go into power save, the keyboard is
unresponsive, and there is a flood of nouveau-related errors in the kernel log.
 Later, X *thinks* it has started successfully -- there's nothing that looks
like an error to me in xorg.0.log -- but the monitors do not wake up and the
keyboard remains unresponsive.  I can, however, ssh into the computer.

(It now occurs to me to try connecting just one monitor to HDMI.  I will do
that after submitting this bug report.)

I will attach dmesg and xorg logs from both successful and unsuccessful boots. 
Please let me know if any additional information is required.

I'm using distribution packages of everything involved, from Debian unstable as
of, er, today.  The Nvidia proprietary drivers have never been installed. 
Version information gleaned from xorg.log:

Current Operating System: Linux kenaz 4.1.0-2-amd64 #1 SMP Debian 4.1.5-1
(2015-08-15) x86_64
xorg-server 2:1.17.2-1.1
Current version of pixman: 0.32.6
NOUVEAU driver Date:   Thu Aug 28 03:57:48 2014 +0200
[drm] nouveau interface version: 1.2.2

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

[-- Attachment #1.2: Type: text/html, Size: 3518 bytes --]

[-- Attachment #2: Type: text/plain, Size: 153 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau

             reply	other threads:[~2015-08-20 18:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-20 18:35 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-91705-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2015-08-20 18:35   ` [Bug 91705] [NVE7] GPU crash (read fault) on boot w/ DMI+HDMI outputs bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-08-20 18:35   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-08-20 18:36   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-08-20 18:36   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-08-20 18:39   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-08-20 18:47   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-08-20 18:53   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-08-20 19:17   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-08-20 19:21   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04  9:03   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-91705-8800@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.