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 89664] Nouveau fails to enter KMS with the Gigabyte G1 Gaming GTX970
Date: Fri, 28 Apr 2017 19:25:52 +0000	[thread overview]
Message-ID: <bug-89664-8800-f5IE2GzoUe@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-89664-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


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

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

--- Comment #20 from Omar <omarpakker+freedesktop-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> ---
I suspect these are not the same problem tbh.
Anyway, I've tried to run nouveau once again. I've tried the default kernel,
the nouveau.config arguments on the default kernel, and using the linux-4.12
branch of github/skeggsb/linux.git.


Default kernel (Linux Omar-PC 4.10.13-1-ARCH #1 SMP PREEMPT Thu Apr 27 12:15:09
CEST 2017 x86_64 GNU/Linux):
- Main GPU blinks with boot information on the first monitor. It then loses
signal and the second monitor turns on showing the top and bottom of the boot
information that was on screen, everything else is distorted and it shows the
coloured stripes along the top (it does so in a higher resolution than the
monitor on the second GPU).
- Turning the first monitor off and back on makes the second monitor lose
signal and the contents displayed are now shown on the first monitor.
Turning the second off and on after that flips things around again. It seems
the last monitor to be turned on gets to display the (distorted) output.
- The monitor attached to the second GPU shows the coloured stripes. Turning it
off and back on again and it only shows black (it does have a signal).

Default kernel with module arguments gr+sec/secboot:
- Both monitors on the primary GPU lose signal. Turning them off and on changes
nothing.
- Monitor on the secondary GPU is black (does get a signal). Turning off and
back on again and it loses signal.

linux-4.12 branch of github/skeggsb/linux.git:
- Same as above with the module arguments, except the monitor on the second GPU
does not lose signal after turning it off and on again.
I am assuming this is still the full kernel with the latest nouveau kernel
module as stated on the wiki? Otherwise I guess this test was pretty
meaningless.


If you want certain logs of any/all of the runs, please drop a message with
what you need and I'll do another run to get the requested information. I'm
also occasionally on the IRC so you can also reach me there :)
I did see some errors regarding "link training failed" (these have always been
there for me every time iirc) and "DRM EVO timeout" (I believe these are new to
me. They do not ring a bell).
If I have some time this weekend I'll give things a shot when unplugging the
second GPU to see if this changes any behaviour with the 4.10 kernel or not.

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

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

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

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

  parent reply	other threads:[~2017-04-28 19:25 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-18 19:17 [Bug 89664] New: Nouveau fails to enter KMS with the Gigabyte G1 Gaming GTX970 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-89664-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2015-03-18 19:20   ` [Bug 89664] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-03-18 19:29   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-03-18 19:51   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-22  7:05   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-22 11:24   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-22 16:11   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-22 21:42   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-22 21:42   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-22 21:44   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-22 21:47   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-22 21:48   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-22 22:09   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-22 22:09   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-06-15 14:46   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-12-09 20:26   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-12-09 20:27   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-12-09 20:28   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-04-10 17:53   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-04-10 18:10   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-04-28 19:25   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2017-04-30 20:34   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-05-20 16:46   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-05-20 16:55   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-05-22 18:47   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-05-22 22:18   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-05-25  9:46   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-05-25  9:51   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-05-26  2:51   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-05-26 15:14   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-05-26 15:19   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-05-27  1:34   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-05-27 14:26   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-01-29 14:10   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-01-29 17:34   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04  8:57   ` 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-89664-8800-f5IE2GzoUe@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.