[lkml]   [2018]   [Jul]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Kernel 4.17.4 lockup
On Fri, Jul 20, 2018 at 2:35 PM, Andy Lutomirski <> wrote:
>> On Jul 16, 2018, at 6:05 AM, H.J. Lu <> wrote:
>>> On Fri, Jul 13, 2018 at 7:08 PM, Andy Lutomirski <> 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:
>> 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:


 \ /
  Last update: 2018-07-23 16:52    [W:0.075 / U:0.876 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site