From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 109135] R9 390 hangs at boot with DPM/DC enabled for kernels 4.19.x and above, says KMS not supported
Date: Fri, 11 Jan 2019 20:49:22 +0000 [thread overview]
Message-ID: <bug-109135-502-K71CyVaNIt@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-109135-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 870 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=109135
--- Comment #14 from Alex Deucher <alexdeucher@gmail.com> ---
On Fri, Jan 11, 2019 at 3:44 PM <bugzilla-daemon@freedesktop.org> wrote:
>
> Okay. I'm recompiling the first bisect now, there were no problems starting it
> this time after using "git stash." However I didn't issue "make clean" because
> it's unclear if it's necessary and I'm hoping I don't have to recompile
> everything for each iteration. Is it necessary or not? The instructions are
> vague and simple say you "might" have to. How would one know if they should?
> Does the compile fail if you need to, or can silent problems be introduced if
> you don't?
>
Generally it's not required to make clean every time unless you run
into a build related problem.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1896 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
next prev parent reply other threads:[~2019-01-11 20:49 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-22 19:20 [Bug 109135] R9 390 hangs at boot with DPM/DC enabled for kernels 4.19.x and above, says KMS not supported bugzilla-daemon
2018-12-22 19:21 ` bugzilla-daemon
2018-12-23 19:52 ` bugzilla-daemon
2018-12-24 21:43 ` bugzilla-daemon
2018-12-27 16:10 ` bugzilla-daemon
2018-12-27 16:10 ` bugzilla-daemon
2018-12-27 16:10 ` bugzilla-daemon
2018-12-27 16:15 ` bugzilla-daemon
2019-01-10 23:47 ` bugzilla-daemon
2019-01-11 0:54 ` bugzilla-daemon
2019-01-11 1:09 ` bugzilla-daemon
2019-01-11 1:25 ` bugzilla-daemon
2019-01-11 15:30 ` bugzilla-daemon
2019-01-11 16:29 ` bugzilla-daemon
2019-01-11 20:10 ` bugzilla-daemon
2019-01-11 20:38 ` bugzilla-daemon
2019-01-11 20:44 ` bugzilla-daemon
2019-01-11 20:49 ` Alex Deucher
2019-01-11 20:49 ` bugzilla-daemon [this message]
2019-01-12 21:46 ` bugzilla-daemon
2019-01-14 15:45 ` bugzilla-daemon
2019-01-14 17:53 ` bugzilla-daemon
2019-01-14 19:19 ` bugzilla-daemon
2019-01-14 20:04 ` bugzilla-daemon
2019-01-16 14:27 ` bugzilla-daemon
2019-01-16 16:45 ` bugzilla-daemon
2019-01-16 17:57 ` bugzilla-daemon
2019-01-16 18:58 ` bugzilla-daemon
2019-11-19 9:08 ` 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-109135-502-K71CyVaNIt@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.