From: Pavel Machek <pavel@ucw.cz>
To: Ingo Molnar <mingo@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andy Lutomirski <luto@kernel.org>, X86 ML <x86@kernel.org>,
Borislav Petkov <bpetkov@suse.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: x60: warnings on boot and resume, arch/x86/mm/tlb.c:257 initialize_ ... was Re: [PATCH 0/2] Fix resume failure due to PCID
Date: Fri, 15 Sep 2017 11:16:42 +0200 [thread overview]
Message-ID: <20170915091642.GA11125@amd> (raw)
In-Reply-To: <20170915083901.aql6zkcabewy52kb@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1076 bytes --]
Hi!
> * Pavel Machek <pavel@ucw.cz> wrote:
>
> > On Wed 2017-09-06 20:25:10, Linus Torvalds wrote:
> > > On Wed, Sep 6, 2017 at 7:54 PM, Andy Lutomirski <luto@kernel.org> wrote:
> > > > Patch 1 is the fix. Patch 2 is a comment that would have kept me from
> > > > chasing down a false lead.
> > >
> > > Yes, this seems to fix things for me. Thanks.
> > >
> > > Of course, right now that laptop has no working wifi with tip-of-tree
> > > due to some issues with the networking tree, but that's an independent
> > > thing and I could suspend and resume with this. So applied and pushed
> > > out,
> >
> > Ok, seems this is still not completely right, I'm now getting WARN_ON
> > during boot and on every resume... but machine works.
> >
> > 4.14-rc0, 32-bit.
>
> Which SHA1, just to make sure? (Please enable CONFIG_LOCALVERSION_AUTO=y.)
46c1e79fee417f151547aa46fae04ab06cb666f4, AFAICT.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2017-09-15 9:16 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-07 2:54 [PATCH 0/2] Fix resume failure due to PCID Andy Lutomirski
2017-09-07 2:54 ` [PATCH 1/2] x86/mm: Reinitialize TLB state on hotplug and resume Andy Lutomirski
2017-09-07 7:01 ` [PATCH] mm/debug: Change BUG_ON() crashes to survivable WARN_ON() warnings Ingo Molnar
2017-09-07 20:50 ` Linus Torvalds
2017-09-07 7:31 ` [PATCH 1/2] x86/mm: Reinitialize TLB state on hotplug and resume Jiri Kosina
2017-09-07 7:48 ` Ingo Molnar
2017-09-07 19:55 ` Jiri Kosina
2017-09-08 1:23 ` Andy Lutomirski
2017-09-07 9:54 ` Borislav Petkov
2017-09-07 9:59 ` Ingo Molnar
2017-09-07 10:10 ` Borislav Petkov
2017-09-07 2:54 ` [PATCH 2/2] x86/mm: Document how CR4.PCIDE restore works Andy Lutomirski
2017-09-07 3:25 ` [PATCH 0/2] Fix resume failure due to PCID Linus Torvalds
2017-09-07 4:15 ` Andy Lutomirski
2017-09-15 6:59 ` x60: warnings on boot and resume, arch/x86/mm/tlb.c:257 initialize_ ... was " Pavel Machek
2017-09-15 8:39 ` Ingo Molnar
2017-09-15 9:16 ` Pavel Machek [this message]
2017-09-15 9:35 ` Ingo Molnar
2017-09-15 10:22 ` [4.14-rc0 regression] " Pavel Machek
2017-09-15 18:47 ` Linus Torvalds
2017-09-15 19:29 ` Andy Lutomirski
2017-09-15 21:06 ` Andy Lutomirski
2017-09-07 8:59 ` Borislav Petkov
2017-09-15 11:01 ` Pavel Machek
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=20170915091642.GA11125@amd \
--to=pavel@ucw.cz \
--cc=bpetkov@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).