From: Harry Wentland <harry.wentland-5C7GfCeVMHo@public.gmane.org>
To: Andy Lutomirski <luto-kltTT9wpgjJwATOyAt5JVQ@public.gmane.org>
Cc: Juergen Gross <jgross-IBi9RG/b67k@public.gmane.org>,
"H. Peter Anvin" <hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>,
Greg Kroah-Hartman
<gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org>,
x86-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
Ingo Molnar <mingo-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
marta.lofstedt-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
Andy Lutomirski <luto-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Josh Poimboeuf <jpoimboe-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
"Deucher,
Alexander" <Alexander.Deucher-5C7GfCeVMHo@public.gmane.org>,
Thomas Gleixner <tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>,
Borislav Petkov <bp-l3A5Bk7waGM@public.gmane.org>,
"Kirill A. Shutemov"
<kirill.shutemov-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
Subject: Re: Failing S3 resume since "Add missing irqflags tracing to native_load_gs_index()"
Date: Fri, 19 Jan 2018 12:18:47 -0500 [thread overview]
Message-ID: <859de65b-a5ac-e0e7-99cb-10d70248b6d5@amd.com> (raw)
In-Reply-To: <54e8303c-47e7-40a6-6b70-d7fd2abd3462-5C7GfCeVMHo@public.gmane.org>
On 2018-01-06 09:55 AM, Harry Wentland wrote:
> On 2018-01-05 06:07 PM, Andy Lutomirski wrote:
>>
>>
>>> On Jan 5, 2018, at 1:51 PM, Harry Wentland <harry.wentland@amd.com> wrote:
>>>
>>>> On 2018-01-05 04:28 PM, Andy Lutomirski wrote:
>>>> It's a known issue, and it should be fixed in newer -rc kernels.
>>>>
>>>
>>> I'm still seeing this on v4.15-rc6. Will I need rc7 or the latest x86 merges in linus's master?
>>>
>>
>> No, it should be fine in -rc6. I don't suppose you could try bisecting but reverting the native_load_gs_index change on each iteration?
>
> (fixing up the amd-gfx address)
>
> I'll give that a try on Monday when I'm back at work.
Apologies for the very late response. I mostly blame the flu.
Anyways, things are working now. Tested rc5, rc6, and rc8+ and all look good.
Not sure why I saw issues with rc6 before. I must've missed something.
Harry
>
> Harry
>
>>
>>> Thanks,
>>> Harry
> _______________________________________________
> amd-gfx mailing list
> amd-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/amd-gfx
>
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
prev parent reply other threads:[~2018-01-19 17:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <e57b5775-d7f2-a89c-f007-41b4db704251@amd.com>
[not found] ` <62B74215-776F-4DB0-A316-FCE56E1328F0@amacapital.net>
[not found] ` <84ec8c27-77ea-4915-aabb-657225194e3a@amd.com>
[not found] ` <0D266FAA-2C99-4944-81D1-8CBE140A5D26@amacapital.net>
[not found] ` <0D266FAA-2C99-4944-81D1-8CBE140A5D26-kltTT9wpgjJwATOyAt5JVQ@public.gmane.org>
2018-01-06 14:55 ` Failing S3 resume since "Add missing irqflags tracing to native_load_gs_index()" Harry Wentland
[not found] ` <54e8303c-47e7-40a6-6b70-d7fd2abd3462-5C7GfCeVMHo@public.gmane.org>
2018-01-19 17:18 ` Harry Wentland [this message]
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=859de65b-a5ac-e0e7-99cb-10d70248b6d5@amd.com \
--to=harry.wentland-5c7gfcevmho@public.gmane.org \
--cc=Alexander.Deucher-5C7GfCeVMHo@public.gmane.org \
--cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=bp-l3A5Bk7waGM@public.gmane.org \
--cc=gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org \
--cc=hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org \
--cc=jgross-IBi9RG/b67k@public.gmane.org \
--cc=jpoimboe-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=kirill.shutemov-VuQAYsv1563Yd54FQh9/CA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=luto-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=luto-kltTT9wpgjJwATOyAt5JVQ@public.gmane.org \
--cc=marta.lofstedt-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=mingo-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org \
--cc=x86-DgEjT+Ai2ygdnm+yROfE0A@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox