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

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

--- Comment #1 from david.kremer.dk@gmail.com ---
I must add that the symptom as well as the concerned hardware starts to be
pretty well documented.

The problem arises with 

- recent nvidia mobile cards
- optimus technology built in
- intel integrated GPU (what else) ?

You can arrive to the same result using the `bbswitch` module or the
`acpi_call` module, trying to switch off the graphic card, *BUT*, since it's
really the `nouveau` driver job to do the work, and since it is already trying
to do it, I see no point in reporting bug for those modules.

See also:

- https://bugzilla.kernel.org/show_bug.cgi?id=156341
- https://github.com/Bumblebee-Project/Bumblebee/issues/1007
-
https://github.com/Bumblebee-Project/Bumblebee/issues/764#issuecomment-234494238

for consistent ways of reproducing the undesired behaviour.

The cheap hack to provide specific options for the `acpi_osi` driver should be
discouraged as it is not consistent across GPU models and Laptop models.

-- 
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

  parent reply	other threads:[~2018-12-04 15:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-04  0:29 [Bug 201867] New: Nouveau + discrete GPU (GP104M = GTX 1070 M) Driver Crashes, System freezes, dual screen not working bugzilla-daemon
2018-12-04 10:43 ` [Bug 201867] " bugzilla-daemon
2018-12-04 15:46 ` bugzilla-daemon [this message]
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-POy5wN3FNr@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 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.