From: "H.J. Lu" <hjl.tools@gmail.com>
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>
Subject: Re: Kernel 4.17.4 lockup
Date: Mon, 23 Jul 2018 07:51:35 -0700 [thread overview]
Message-ID: <CAMe9rOqzvPARD6srX5BZym2ah1Ga4Z_QuJNQV-GG3d3tQ3RKCg@mail.gmail.com> (raw)
In-Reply-To: <88CBCB04-43F6-4353-82F7-20A67AD49B65@amacapital.net>
On Fri, Jul 20, 2018 at 2:35 PM, Andy Lutomirski <luto@amacapital.net> wrote:
>
>> 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=x86/guard_pages
>>>
>>
>> This kernel won't boot with this configure file.
>
> Bah humbug. You’ll 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 to unbreak their interaction with stacks in vmap space. It’s been broken literally forever, but I keep incorrectly imagining that it’s 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=1597559
--
H.J.
prev parent reply other threads:[~2018-07-23 14:55 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-08 21:36 Kernel 4.17.4 lockup H.J. Lu
2018-07-09 14:54 ` Dave Hansen
2018-07-09 23:02 ` H.J. Lu
2018-07-10 0:44 ` Dave Hansen
2018-07-10 2:14 ` H.J. Lu
2018-07-10 3:47 ` Dave Hansen
[not found] ` <CAMe9rOrHowBX06nihdRRmEqhV8v7cs+PwVY7JYQFpUFOnHC71A@mail.gmail.com>
2018-07-11 15:13 ` Dave Hansen
2018-07-11 15:40 ` H.J. Lu
2018-07-11 16:24 ` Dave Hansen
2018-07-11 16:29 ` H.J. Lu
2018-07-11 16:49 ` Dave Hansen
2018-07-11 16:53 ` H.J. Lu
[not found] ` <CAMe9rOpV89jWhvAZtqOJnc0eXzRYiLF5pLWRcdb7-kKLigj4rQ@mail.gmail.com>
2018-07-11 17:36 ` Andy Lutomirski
2018-07-11 17:43 ` Dave Hansen
2018-07-11 17:50 ` H.J. Lu
2018-07-11 17:50 ` Dave Hansen
2018-07-11 18:31 ` Dave Jones
2018-07-11 23:07 ` Andy Lutomirski
2018-07-11 23:14 ` Dave Hansen
2018-07-12 14:44 ` H.J. Lu
2018-07-12 23:28 ` H.J. Lu
2018-07-14 2:08 ` Andy Lutomirski
2018-07-16 16:05 ` H.J. Lu
2018-07-20 21:35 ` Andy Lutomirski
2018-07-23 14:51 ` H.J. Lu [this message]
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=CAMe9rOqzvPARD6srX5BZym2ah1Ga4Z_QuJNQV-GG3d3tQ3RKCg@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@intel.com \
--cc=davej@codemonkey.org.uk \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=luto@kernel.org \
--cc=mgorman@suse.de \
--cc=minchan@kernel.org \
--cc=riel@surriel.com \
/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).