Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Roman Mamedov <rm@romanrm.net>
To: Wols Lists <antlists@youngman.org.uk>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: Debugging system hangs
Date: Tue, 14 Dec 2021 22:46:58 +0500	[thread overview]
Message-ID: <20211214224658.26cea5a0@nvm> (raw)
In-Reply-To: <d8a0d8c9-f8cc-a70a-03a0-aae2fd6c68c2@youngman.org.uk>

On Tue, 14 Dec 2021 15:54:50 +0000
Wols Lists <antlists@youngman.org.uk> wrote:

> Don't know if this is off-topic or not, seeing as my system is very much 
> reliant on raid ...
> 
> But basically I'm seeing the system just stop responding. Typically it's 
> in screensaver mode, I've got a blank screen, and it won't wake up. (I 
> used to think it was something to do with Thunderbird, it mostly 
> happened while TB was hammering the system, but no ...)
> 
> Today, I had it happen while the system was idle but not in screensaver, 
> I run xosview, and everything was clearly frozen - including xosview.
> 
> As you might know, my stack is ext4 over lvm (over raid over 
> dm-integrity for /home) over spinning rust.
> 
> And I run gentoo/systemd - currently on the latest stable kernel afaik, 
> 5.10.76-gentoo-r1 SMP x86_64.
> 
> Any advice on how to debug a hang - basically I need something that'll 
> just sit there so when it crashes (and I press the reset button to 
> recover) I'll have some sort of trace. It would be nice to prove it's 
> not the disk stack at fault ...
> 
> Obviously, "set these options in the kernel" won't faze me ...

Set up "netconsole":
https://www.kernel.org/doc/html/latest/networking/netconsole.html
https://wiki.ubuntu.com/Kernel/Netconsole

-- 
With respect,
Roman

  reply	other threads:[~2021-12-14 17:47 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-14 15:54 Debugging system hangs Wols Lists
2021-12-14 17:46 ` Roman Mamedov [this message]
2021-12-14 21:59   ` Phil Turmel
2021-12-15  1:08     ` John Stoffel
2021-12-15 21:45       ` Wol
2021-12-15 12:07 ` o1bigtenor
2021-12-15 16:45 ` Roger Heflin
2021-12-15 21:53   ` Wol
2021-12-15 22:05     ` Roger Heflin
2021-12-16 21:43       ` John Stoffel
2021-12-16 21:50         ` Roger Heflin
2021-12-16 22:08           ` John Stoffel
2021-12-16 22:30         ` Wols Lists
2021-12-17 10:07           ` Jani Partanen
2021-12-19 17:52       ` Wols Lists
     [not found]         ` <CAAMCDecF2PoAtAb1w6reU=RYocaDPb0ZVQ20S44QOrh3fVEXNw@mail.gmail.com>
2021-12-19 19:27           ` Wols Lists

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=20211214224658.26cea5a0@nvm \
    --to=rm@romanrm.net \
    --cc=antlists@youngman.org.uk \
    --cc=linux-raid@vger.kernel.org \
    /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