All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 100726] [REGRESSION][BISECTED] Severe flickering with an R9 290
Date: Tue, 28 Nov 2017 16:13:19 +0000	[thread overview]
Message-ID: <bug-100726-502-s1RLEuFkOd@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-100726-502@http.bugs.freedesktop.org/>


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

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

--- Comment #8 from Michel Dänzer <michel@daenzer.net> ---
(In reply to hiwatari.seiji from comment #7)
> Are you sure, that b7d91c915290ab0bfbab84a0fb9c9eae57816982 is definitely
> not the cause?

At least 99% sure. Pure merge commits are almost never a correct bisection
result.


> - For me, when booting the machine (BIOS) - the screen resolution of GRUB is
> quite random. Sometimes, it's using the native screen resolution, sometimes
> it is using a very reduced resolution. Sometimes, it's only displaying on
> one of the two screens, sometimes it's displaying on both. But that wasn't a
> problem before linux-4.9.

This is before the Linux kernel is even loaded, so it can hardly be directly
related to it.

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

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

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

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2017-11-28 16:13 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-19 18:55 [Bug 100726] [REGRESSION][BISECTED] Severe flickering with an R9 290 bugzilla-daemon
2017-04-19 18:56 ` bugzilla-daemon
2017-04-20  1:42 ` bugzilla-daemon
2017-04-24 16:08 ` bugzilla-daemon
2017-04-24 17:54 ` bugzilla-daemon
2017-11-26 10:56 ` bugzilla-daemon
2017-11-26 10:57 ` bugzilla-daemon
2017-11-27 10:32 ` bugzilla-daemon
2017-11-27 10:34 ` bugzilla-daemon
2017-11-27 12:01 ` bugzilla-daemon
2017-11-28 16:13 ` bugzilla-daemon [this message]
2018-03-14  1:28 ` bugzilla-daemon
2018-03-14  1:29 ` bugzilla-daemon
2018-03-20 19:14 ` bugzilla-daemon
2018-03-24 11:15 ` bugzilla-daemon
2019-11-19  8:15 ` 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-100726-502-s1RLEuFkOd@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.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.