Re: Failing S3 resume since "Add missing irqflags tracing to native_load_gs_index()"

[Andy Lutomirski]

> On Jan 5, 2018, at 1:00 PM, Harry Wentland <harry.wentland@xxxxxxx> 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@xxxxxxxxxx>
> 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.