From: Shawn Starr <shawn.starr-bJEeYj9oJeDQT0dZR+AlfA@public.gmane.org>
To: amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: Latest testing with drm-next-4.9-wip and latest LLVM/mesa stack - Regression in PowerPlay/DPM on CIK?
Date: Mon, 10 Oct 2016 19:36:28 -0400 [thread overview]
Message-ID: <8025413.75ZrRe18t5@segfault> (raw)
In-Reply-To: <5955047.4M9YlcR7bW@segfault>
On Monday, October 10, 2016 4:55:24 PM EDT Shawn Starr wrote:
> Hello,
>
> It turns out its not kernel, bisecting mesa/LLVM now to see where this issue
> is happening from.
Correction, it is kernel, 4.8-rc8 is good from commit
c2cbc38b9715bd8318062e600668fc30e5a3fbfa
Bisecting this now.
Thanks,
Shawn
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next prev parent reply other threads:[~2016-10-10 23:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-10 19:43 Latest testing with drm-next-4.9-wip and latest LLVM/mesa stack - Regression in PowerPlay/DPM on CIK? Shawn Starr
2016-10-10 20:55 ` Shawn Starr
2016-10-10 23:36 ` Shawn Starr [this message]
2016-10-13 18:28 ` mm: fix cache mode tracking in vm_insert_mixed() breaks AMDGPU [was: Re: Latest testing with drm-next-4.9-wip and latest LLVM/mesa stack - Regression in PowerPlay/DPM on CIK?] Shawn Starr
2016-10-14 1:33 ` Michel Dänzer
[not found] ` <10a1e298-df32-52a5-7694-b205794ca009-otUistvHUpPR7s880joybQ@public.gmane.org>
2016-10-16 18:41 ` Marek Olšák
2016-10-16 20:53 ` Dave Airlie
2016-10-17 21:25 ` Dan Williams
2016-10-17 22:01 ` Dave Airlie
2016-10-18 3:48 ` Dave Airlie
2016-10-18 13:53 ` Dan Williams
2016-10-19 6:42 ` Dave Airlie
2016-10-19 10:33 ` Marek Olšák
2016-10-20 1:11 ` Michel Dänzer
[not found] ` <2ebd438d-21e6-cee8-3062-0ef84ab6c347-otUistvHUpPR7s880joybQ@public.gmane.org>
2016-10-20 9:06 ` Marek Olšák
2016-10-18 7:39 ` Daniel Vetter
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=8025413.75ZrRe18t5@segfault \
--to=shawn.starr-bjeeyj9ojedqt0dzr+alfa@public.gmane.org \
--cc=amd-gfx-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 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.