From: Borislav Petkov <bp@alien8.de>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Andy Lutomirski <luto@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Brian Gerst <brgerst@gmail.com>,
Dave Hansen <dave.hansen@intel.com>,
Denys Vlasenko <dvlasenk@redhat.com>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Michal Hocko <mhocko@suse.com>,
Peter Zijlstra <peterz@infradead.org>,
linux-arch@vger.kernel.org, linux-mm@kvack.org,
x86-ml <x86@kernel.org>
Subject: Re: Splat during resume
Date: Sat, 25 Mar 2017 22:50:12 +0100 [thread overview]
Message-ID: <20170325215012.v5vywew7pfi3qk5f@pd.tnic> (raw)
In-Reply-To: <20170325214615.eqgmkwbkyldt7wwl@pd.tnic>
On Sat, Mar 25, 2017 at 10:46:15PM +0100, Borislav Petkov wrote:
> On Sat, Mar 25, 2017 at 07:58:55PM +0100, Borislav Petkov wrote:
> > Hey Rafael,
> >
> > have you seen this already (partial splat photo attached)? Happens
> > during resume from s2d. Judging by the timestamps, this looks like the
> > resume kernel before we switch to the original, boot one but I could be
> > mistaken.
> >
> > This is -rc3+tip/master.
> >
> > I can't catch a full splat because this is a laptop and it doesn't have
> > serial. netconsole is helping me for shit so we'd need some guess work.
> >
> > So I'm open to suggestions.
> >
> > Please don't say "bisect" yet ;-)))
>
> No need, I found it. Reverting
>
> ea3b5e60ce80 ("x86/mm/ident_map: Add 5-level paging support")
>
> makes the machine suspend and resume just fine again. Lemme add people to CC.
So I see rIP pointing to ident_pmd_init() and the stack trace has
load_image_and_restore() so if I try to connect the dots, I get:
load_image_and_restore
|-> hibernation_restore
|-> resume_target_kernel
|-> swsusp_arch_resume
|-> set_up_temporary_mappings
|-> kernel_ident_mapping_init
|-> ... ident_pmd_init
I'll let you folks make sense of what's going on.
Thanks.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-03-25 21:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170325185855.4itsyevunczus7sc@pd.tnic>
2017-03-25 21:46 ` Borislav Petkov
2017-03-25 21:50 ` Borislav Petkov [this message]
2017-03-25 22:01 ` Kirill A. Shutemov
2017-03-25 22:05 ` Linus Torvalds
2017-03-25 22:39 ` Borislav Petkov
2017-03-26 8:25 ` Mike Galbraith
2017-03-26 8:41 ` Borislav Petkov
2017-03-26 10:10 ` Mike Galbraith
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=20170325215012.v5vywew7pfi3qk5f@pd.tnic \
--to=bp@alien8.de \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=brgerst@gmail.com \
--cc=dave.hansen@intel.com \
--cc=dvlasenk@redhat.com \
--cc=jpoimboe@redhat.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=mhocko@suse.com \
--cc=peterz@infradead.org \
--cc=rjw@rjwysocki.net \
--cc=torvalds@linux-foundation.org \
--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