On Fri, Jul 20, 2018 at 2:35 PM, Andy Lutomirski <l...@amacapital.net> wrote: > >> On Jul 16, 2018, at 6:05 AM, H.J. Lu <hjl.to...@gmail.com> wrote: >> >>> On Fri, Jul 13, 2018 at 7:08 PM, Andy Lutomirski <l...@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.
