From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 97248] [regression] [amdgpu] New regression in 4.8-rc1
Date: Mon, 08 Aug 2016 19:35:11 +0000 [thread overview]
Message-ID: <bug-97248-502-xjukpxF7ZR@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-97248-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 785 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=97248
--- Comment #7 from Alex Deucher <alexdeucher@gmail.com> ---
(In reply to Mike Lothian from comment #2)
> I'll revert that on the 4.9-next-wip branch and see if it makes a difference
>
> I'm bisecting on linus's tree at the moment to see where the regression
> crept in
It's probably due to the d3cold support that when upstream in 4.8.
>
> I've also been runnig with these local patches to use Dave's D3cold work (I
> reverted those before reporting) I'll attach them to the bug though
You shouldn't need those (or the workaround from my tree referenced in comment
1) now that the d3cold support has gone upstream via the pci tree.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1680 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:[~2016-08-08 19:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-08 19:17 [Bug 97248] [regression] [amdgpu] New regression in 4.8-rc1 bugzilla-daemon
2016-08-08 19:24 ` bugzilla-daemon
2016-08-08 19:29 ` bugzilla-daemon
2016-08-08 19:30 ` bugzilla-daemon
2016-08-08 19:30 ` bugzilla-daemon
2016-08-08 19:31 ` bugzilla-daemon
2016-08-08 19:33 ` bugzilla-daemon
2016-08-08 19:35 ` bugzilla-daemon [this message]
2016-11-03 13:14 ` 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-97248-502-xjukpxF7ZR@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).