lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Fri, 25 Jan 2019 11:16:30 -0500
From:   robert shteynfeld <robert.shteynfeld@...il.com>
To:     Michal Hocko <mhocko@...nel.org>
Cc:     Linus Torvalds <torvalds@...ux-foundation.org>,
        Mikhail Zaslonko <zaslonko@...ux.ibm.com>,
        Linux List Kernel Mailing <linux-kernel@...r.kernel.org>,
        Gerald Schaefer <gerald.schaefer@...ibm.com>,
        Mikhail Gavrilov <mikhail.v.gavrilov@...il.com>,
        Dave Hansen <dave.hansen@...el.com>,
        Alexander Duyck <alexander.h.duyck@...ux.intel.com>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Pavel Tatashin <pasha.tatashin@...cle.com>,
        Steven Sistare <steven.sistare@...cle.com>,
        Daniel Jordan <daniel.m.jordan@...cle.com>,
        Bob Picco <bob.picco@...cle.com>
Subject: Re: kernel panic due to https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2830bf6f05fb3e05bc4743274b806c821807a684

Attached is the dmesg from patched kernel.

I'm not an expert at debugging the kernel, obviously.  I tried setting
up a serial console before without much luck as part of this debugging
session.  I'll try again when I have some time, but I couldn't get to
the exact message before -- it scrolled by too quickly (and boot_delay
froze the output).

On Fri, Jan 25, 2019 at 10:58 AM Michal Hocko <mhocko@...nel.org> wrote:
>
> On Fri 25-01-19 10:52:06, robert shteynfeld wrote:
> > The person who pointed to mm/page_alloc.c commits likely causing the
> > issue did not have time to build a patched/reverted kernel to confirm
> > his hypothesis.  When I tried backing out the two separate commits he
> > suggested, the first commit (ie. the one in the subject) was the one
> > that when backed out fixed the boot issue.  Reverting the second one
> > had no effect.
>
> OK, so can you provide the full dmesg (with revert) along wth
> memblock=debug kernel parameter. Also would it be possible to configure
> serial or net console to get the actual panic report please?
> --
> Michal Hocko
> SUSE Labs

Download attachment "dmesg.good.boot" of type "application/octet-stream" (108657 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ