dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 201867] New: Nouveau + discrete GPU (GP104M = GTX 1070 M) Driver Crashes, System freezes, dual screen not working
Date: Tue, 04 Dec 2018 00:29:24 +0000	[thread overview]
Message-ID: <bug-201867-2300@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=201867

            Bug ID: 201867
           Summary: Nouveau + discrete GPU (GP104M = GTX 1070 M) Driver
                    Crashes, System freezes, dual screen not working
           Product: Drivers
           Version: 2.5
    Kernel Version: 4.19.4-arch1-1-ARCH #1 SMP PREEMPT
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: high
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: david.kremer.dk@gmail.com
        Regression: No

Created attachment 279831
  --> https://bugzilla.kernel.org/attachment.cgi?id=279831&action=edit
Driver Traceback

The problem is proteiform. It is actually well described in
https://bugzilla.kernel.org/show_bug.cgi?id=156341 so this could be a
duplicate, however, since the driver supposed to actually drive the nvidia GPU
is nouveau, I feel obliged to fill a new bug report to address the issue.

So basically, there is two issues:

1. when loading the nouveau driver in a tty, you can't launch Xorg afterward,
the xinit program waits for a server to be available but that never come.
2. When loading the nouveau driver after the X session has started, the fan
finally switches off, but there is first a traceback in dmesg and everything
that is reported in bug_id=156341 happens: subsequent calls to lspci/lshw/...
are freezing the system definetely without possibility to recover except by
doing a hard reboot.

So there's definitely something messy about this familiy of Nvidia GPU
integrated as a discrete GC on this new laptop generation.

Can't give much more info

See attachment for the traceback.

lspci output:

00:00.0 Host bridge: Intel Corporation 8th Gen Core Processor Host Bridge/DRAM
Registers (rev 07)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core
Processor PCIe Controller (x16) (rev 07)
00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 630 (Mobile)
01:00.0 VGA compatible controller: NVIDIA Corporation GP104M [GeForce GTX 1070
Mobile] (rev ff)

CPU=Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2018-12-04  0:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-04  0:29 bugzilla-daemon [this message]
2018-12-04 10:43 ` [Bug 201867] Nouveau + discrete GPU (GP104M = GTX 1070 M) Driver Crashes, System freezes, dual screen not working bugzilla-daemon
2018-12-04 15:46 ` bugzilla-daemon
2019-01-08 10:19 ` bugzilla-daemon

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-201867-2300@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox