linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Lutomirski <luto@amacapital.net>
To: Harry Wentland <harry.wentland@amd.com>
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.freedeskop.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: Fri, 5 Jan 2018 13:28:39 -0800	[thread overview]
Message-ID: <62B74215-776F-4DB0-A316-FCE56E1328F0@amacapital.net> (raw)
In-Reply-To: <e57b5775-d7f2-a89c-f007-41b4db704251@amd.com>


> On Jan 5, 2018, at 1:00 PM, Harry Wentland <harry.wentland@amd.com> wrote:
> 
> Since rebasing our dev trees on v4.15-rc2 a bunch of our systems are failing to resume from S3. I've bisected it to the following commit
> 
> commit ca37e57bbe0cf1455ea3e84eb89ed04a132d59e1 (refs/bisect/bad)
> Author: Andy Lutomirski <luto@kernel.org>
> Date:   Wed Nov 22 20:39:16 2017 -0800
> 
>    x86/entry/64: Add missing irqflags tracing to native_load_gs_index()
> 
> When reverting this on the tip of our tree (https://cgit.freedesktop.org/~agd5f/linux/log/?h=amd-staging-drm-next) we still observe the issue, though, so there must be more going on.
> 
> I only observe this issue when CONFIG_TRACE_IRQFLAGS is on, but in order to disable it I'll also have to disable things like CONFIG_LOCKDEP and CONFIG_DEBUG_WW_MUTEX_SLOWPATH, which is less than ideal.
> 
> Attached are my .config, dmesg.log (up until suspend) and a system configuration log with lshw, lspci, lsmod, and distro info.
> 
> I could find a ton of info online when searching for this. The only two things I found were a mention by Intel IGT guys of the same or similar issue and a revert from Greg K-H for the 4.14 stable tree.
> * https://bugs.freedesktop.org/show_bug.cgi?id=103936
> * https://patchwork.kernel.org/patch/10090797/
> 
> Has anyone else seen this?
> 
> Please let me know if there's anything else I can do to help find the root cause and fix for this.

It's a known issue, and it should be fixed in newer -rc kernels.

  reply	other threads:[~2018-01-05 21:28 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 [this message]
2018-01-05 21:51   ` Harry Wentland
2018-01-05 23:07     ` Andy Lutomirski
2018-01-06 14:55       ` Harry Wentland
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=62B74215-776F-4DB0-A316-FCE56E1328F0@amacapital.net \
    --to=luto@amacapital.net \
    --cc=Alexander.Deucher@amd.com \
    --cc=amd-gfx@lists.freedeskop.org \
    --cc=bp@suse.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=harry.wentland@amd.com \
    --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@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).