From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1751226AbdIOJfZ (ORCPT <rfc822;w@1wt.eu>);
        Fri, 15 Sep 2017 05:35:25 -0400
Received: from mail-wr0-f194.google.com ([209.85.128.194]:33090 "EHLO
        mail-wr0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1750879AbdIOJfX (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Fri, 15 Sep 2017 05:35:23 -0400
X-Google-Smtp-Source: ADKCNb5IvhxP6bw4hOVIiA4idfQsbcWztb3AprycEdC6xXZUQab9y/X4Z15f/cZXR1G+Wz4atcZiAw==
Date: Fri, 15 Sep 2017 11:35:20 +0200
From: Ingo Molnar <mingo@kernel.org>
To: Pavel Machek <pavel@ucw.cz>
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
Message-ID: <20170915093520.xzulap5wiijwfdyf@gmail.com>
References: <cover.1504752689.git.luto@kernel.org>
 <CA+55aFya1LtF9UK8+nAyVo__GHCW1Xp1H1AZn62zhC+D4HtH5Q@mail.gmail.com>
 <20170915065936.GA6580@amd>
 <20170915083901.aql6zkcabewy52kb@gmail.com>
 <20170915091642.GA11125@amd>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170915091642.GA11125@amd>
User-Agent: NeoMutt/20170113 (1.7.2)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org


* Pavel Machek <pavel@ucw.cz> wrote:

> 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.

Ok, just to reiterate: that SHA1 has all relevant and current fixes included, so 
this definitely is an open regression.

Thanks,

	Ingo