From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 108615] [NVE7] changing resolution causes blank screen
Date: Sat, 21 Sep 2019 20:49:48 +0000 [thread overview]
Message-ID: <bug-108615-8800-ABLjuP5FeA@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-108615-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
[-- Attachment #1.1: Type: text/plain, Size: 867 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=108615
--- Comment #7 from jbytecoder-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org ---
I have tested the issue against linux-5.3 and it stil persists. I also
attempted to narrow down the commit that did introduce the problem.
Using kernel sources at https://github.com/torvalds/linux.git i detected that
between tags v4.9 and v4.10 The kernel breaks @ 9439b3710df6 - this is a big
change commit that intorduces drm changes planned for linux-4.10.
I guess the issue has to do with "atomic modesseting" it would appear that for
nv50 the atomic modesseting works only for default resolution, but not for any
other
Can someone suggest any way to further narrow down the culprit ?
logging has no effect ( no errors appear in log )
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1662 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau
next prev parent reply other threads:[~2019-09-21 20:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-31 20:28 [Bug 108615] New: [NVE7] changing resolution causes blank screen bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-108615-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2018-10-31 20:29 ` [Bug 108615] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-10-31 20:30 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-11-21 19:08 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-11-21 19:10 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-11-21 19:13 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-11-21 19:15 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-09-21 20:49 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2019-09-21 20:51 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-09-21 20:52 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-09-26 18:44 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04 9:46 ` 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-108615-8800-ABLjuP5FeA@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox