linux-kernel - Re: How do you investigate the cause of total hang? Is there some information that I should pay attention to in order to get some hint?

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] [day] [month] [year] [list]

Message-ID: <CAAvDm6aCU0+1iL28t7mf-bc=CM3e8ybAYCtJ6AfYTeLNUCmyVg@mail.gmail.com>
Date:   Fri, 3 Jul 2020 14:09:43 +0800
From:   孙世龙 sunshilong <sunshilong369@...il.com>
To:     Cong Wang <xiyou.wangcong@...il.com>
Cc:     LKML <linux-kernel@...r.kernel.org>,
        kernelnewbies <Kernelnewbies@...nelnewbies.org>
Subject: Re: How do you investigate the cause of total hang? Is there some
 information that I should pay attention to in order to get some hint?

Hi, Cong Wang

Thank you for taking the time to respond to me.
Do you think the message(i.e. "RCU detect a stall on CPU 2") indicates
there is a lockup.

Cong Wang <xiyou.wangcong@...il.com> 于2020年7月1日周三 下午2:07写道：


>
> On Tue, Jun 30, 2020 at 7:49 PM 孙世龙 sunshilong <sunshilong369@...il.com> wrote:
> >
> > Hi, list
> >
> > My x86 machine(linux4.19) sometimes hangs, suddenly not responding in
> > any way to the mouse or the keyboard.
> >
> > How can I investigate why it hung up? Is there extra information I can
> > find for a clue? Is there anything less drastic than power-off to get
> > some kind of action, if only some limited shell or just beeps,
> > but might give a clue?
> >
>
> If the hang was a crash which you didn't get a chance to capture the
> last kernel log, you can use kdump to collect them. The kernel log
> tells what kind of crash it is, a NULL pointer deref, a kernel page fault
> etc..
>
> If the hang was a hard lockup, you have to turn on lockup detector
> and also kdump to capture what the detector tells.
>
> Thanks.