linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Harry Wentland <harry.wentland@amd.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	x86@kernel.org, Andy Lutomirski <luto@kernel.org>,
	Borislav Petkov <bp@suse.de>,
	linux-kernel@vger.kernel.org,
	Josh Poimboeuf <jpoimboe@redhat.com>,
	"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
	Juergen Gross <jgross@suse.com>,
	"Deucher, Alexander" <Alexander.Deucher@amd.com>,
	amd-gfx@lists.freedesktop.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	marta.lofstedt@intel.com
Subject: Re: Failing S3 resume since "Add missing irqflags tracing to native_load_gs_index()"
Date: Sat, 6 Jan 2018 09:55:53 -0500	[thread overview]
Message-ID: <54e8303c-47e7-40a6-6b70-d7fd2abd3462@amd.com> (raw)
In-Reply-To: <0D266FAA-2C99-4944-81D1-8CBE140A5D26@amacapital.net>

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.

Harry

> 
>> Thanks,
>> Harry

  reply	other threads:[~2018-01-06 14:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-05 21:00 Failing S3 resume since "Add missing irqflags tracing to native_load_gs_index()" Harry Wentland
2018-01-05 21:28 ` Andy Lutomirski
2018-01-05 21:51   ` Harry Wentland
2018-01-05 23:07     ` Andy Lutomirski
2018-01-06 14:55       ` Harry Wentland [this message]
2018-01-19 17:18         ` Harry Wentland

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=54e8303c-47e7-40a6-6b70-d7fd2abd3462@amd.com \
    --to=harry.wentland@amd.com \
    --cc=Alexander.Deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=bp@suse.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=hpa@zytor.com \
    --cc=jgross@suse.com \
    --cc=jpoimboe@redhat.com \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=luto@kernel.org \
    --cc=marta.lofstedt@intel.com \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.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).