Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
In-Reply-To: <88CBCB04-43F6-4353-82F7-20A67AD49B65@amacapital.net>
References: <9548e10a-7403-425e-bf1f-b1eb9d055d99@intel.com>
 <CAMe9rOrHowBX06nihdRRmEqhV8v7cs+PwVY7JYQFpUFOnHC71A@mail.gmail.com>
 <f22ee1e2-9a35-697f-50ab-543ac1631c89@intel.com> <CAMe9rOpPwtPd-R+D9=iDYgbFtnP+=akWic-QBKwq9wKa7uadEQ@mail.gmail.com>
 <2022d212-62f2-a163-2493-abecfbafa07b@intel.com> <CAMe9rOqc0oVw+ZLXCM-nrtPb1OiPFBeHt+Lsx+6K6y=t3HSVhA@mail.gmail.com>
 <cbb38230-9c57-905b-3a11-e2717c5aa615@intel.com> <CAMe9rOqh9saaULM_+jNtzfYarbZScm+6KCEyibxxqn7GLvKwzA@mail.gmail.com>
 <CAMe9rOpV89jWhvAZtqOJnc0eXzRYiLF5pLWRcdb7-kKLigj4rQ@mail.gmail.com>
 <067e2d5d-1abf-efd4-cb50-992ba5ca6748@intel.com> <20180711183126.yo7eyqpd4ggb5kcr@codemonkey.org.uk>
 <9A6C6EEB-85D8-4F59-95ED-EB4DA5947BCA@amacapital.net> <f3e2ca08-e22d-f16c-1c2e-9fb1985771ef@intel.com>
 <CAMe9rOpBm71hnzG0wx=2qaWKHYNE30JJOT=Jt4i+Vqs3Xb4qBQ@mail.gmail.com>
 <CAMe9rOoX-x-YezXc_1EE9F0Nv3_SuzN+paXsTO11gcTykMr4Tw@mail.gmail.com>
 <CALCETrUwUdmRAfaKsP0dGXriU=EdoWs69XMwJwxDOLY_9G+1tw@mail.gmail.com>
 <CAMe9rOr_9zsAKMxQaxka8RWCXC8Jc7svdG3tKcp6Q+_EDTC=Zg@mail.gmail.com> <88CBCB04-43F6-4353-82F7-20A67AD49B65@amacapital.net>
From:   "H.J. Lu" <hjl.tools@gmail.com>
Date:   Mon, 23 Jul 2018 07:51:35 -0700
Message-ID: <CAMe9rOqzvPARD6srX5BZym2ah1Ga4Z_QuJNQV-GG3d3tQ3RKCg@mail.gmail.com>
Subject: Re: Kernel 4.17.4 lockup
To:     Andy Lutomirski <luto@amacapital.net>
Cc:     Dave Hansen <dave.hansen@intel.com>,
        Dave Jones <davej@codemonkey.org.uk>,
        "H. Peter Anvin" <hpa@zytor.com>,
        LKML <linux-kernel@vger.kernel.org>,
        Andy Lutomirski <luto@kernel.org>,
        Mel Gorman <mgorman@suse.de>,
        Andrew Morton <akpm@linux-foundation.org>,
        Rik van Riel <riel@surriel.com>,
        Minchan Kim <minchan@kernel.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Fri, Jul 20, 2018 at 2:35 PM, Andy Lutomirski <luto@amacapital.net> wrot=
e:
>
>> On Jul 16, 2018, at 6:05 AM, H.J. Lu <hjl.tools@gmail.com> wrote:
>>
>>> On Fri, Jul 13, 2018 at 7:08 PM, Andy Lutomirski <luto@amacapital.net> =
wrote:
>>> I'm not at all convinced that this is the problem, but the series here
>>> will give a better diagnostic if the issue really is an IRQ stack
>>> overflow:
>>>
>>> https://git.kernel.org/pub/scm/linux/kernel/git/luto/linux.git/log/?h=
=3Dx86/guard_pages
>>>
>>
>> This kernel won't boot with this configure file.
>
> Bah humbug. You=E2=80=99ll need to turn KASAN off (and maybe even compile=
 it out entirely) if you want to test this. I need to bug the KASAN folks t=
o unbreak their interaction with stacks in vmap space.  It=E2=80=99s been b=
roken literally forever, but I keep incorrectly imagining that it=E2=80=99s=
 been fixed already.
>

This particular kernel oops has been fixed by kernel 4.17.7.  But now
I am running into
another kernel oops:

https://bugzilla.redhat.com/show_bug.cgi?id=3D1597559

--=20
H.J.