From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 203325] 5.1 amdgpu on polaris11: broken text-fb multihead, works in X
Date: Mon, 15 Apr 2019 10:06:18 +0000 [thread overview]
Message-ID: <bug-203325-2300-6a95URmyol@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-203325-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=203325
--- Comment #3 from Duncan (1i5t5.duncan@cox.net) ---
(In reply to Michel Dänzer from comment #1)
> Can you bisect?
>
> Meanwhile, amdgpu.dc=0 on the kernel command line might serve as a
> workaround.
[Wow. Fast response!]
Yes, I can bisect, technically, anyway.
But I'm selling/buying and moving between houses in the next several weeks and
had hoped to avoid it. Unfortunately it might be 5.2 cycle before I get to it
(tho I tend to do upgrades and bug hunting for relaxation, so there's a good
chance I'll get to it before 5.2, but perhaps not in time to get the bug
squashed for 5.1 if you're waiting on the bisect).
That's why I didn't bisect before reporting.
--
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
next prev parent reply other threads:[~2019-04-15 10:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-15 9:50 [Bug 203325] New: 5.1 amdgpu on polaris11: broken text-fb multihead, works in X bugzilla-daemon
2019-04-15 9:54 ` [Bug 203325] " bugzilla-daemon
2019-04-15 9:56 ` bugzilla-daemon
2019-04-15 10:06 ` bugzilla-daemon [this message]
2019-04-15 14:15 ` bugzilla-daemon
2019-04-19 5:06 ` 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-203325-2300-6a95URmyol@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.