From: "孙世龙 sunshilong" <sunshilong369@gmail.com>
To: Cong Wang <xiyou.wangcong@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
kernelnewbies <Kernelnewbies@kernelnewbies.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?
Date: Fri, 3 Jul 2020 14:09:43 +0800 [thread overview]
Message-ID: <CAAvDm6aCU0+1iL28t7mf-bc=CM3e8ybAYCtJ6AfYTeLNUCmyVg@mail.gmail.com> (raw)
In-Reply-To: <CAM_iQpWcK1ou9st5QWvdQ7MNfdV09WqjfPB1ASwpoJaBKzJrjQ@mail.gmail.com>
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@gmail.com> 于2020年7月1日周三 下午2:07写道:
>
> On Tue, Jun 30, 2020 at 7:49 PM 孙世龙 sunshilong <sunshilong369@gmail.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.
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
prev parent reply other threads:[~2020-07-03 6:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-01 2:46 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? 孙世龙 sunshilong
2020-07-01 6:06 ` Cong Wang
2020-07-03 6:09 ` 孙世龙 sunshilong [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='CAAvDm6aCU0+1iL28t7mf-bc=CM3e8ybAYCtJ6AfYTeLNUCmyVg@mail.gmail.com' \
--to=sunshilong369@gmail.com \
--cc=Kernelnewbies@kernelnewbies.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xiyou.wangcong@gmail.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).