Linux RAID subsystem development
 help / color / mirror / Atom feed
From: "John Stoffel" <john@stoffel.org>
To: Roger Heflin <rogerheflin@gmail.com>
Cc: Wol <antlists@youngman.org.uk>, linux-raid <linux-raid@vger.kernel.org>
Subject: Re: Debugging system hangs
Date: Thu, 16 Dec 2021 16:43:43 -0500	[thread overview]
Message-ID: <25019.45839.872620.235430@quad.stoffel.home> (raw)
In-Reply-To: <CAAMCDeemZO2u_4WW8pHVP2qOxz0HdHQTy2Gsa=zgY-7g4ptw7w@mail.gmail.com>


Another thing that struck me is maybe it's time to boot into a small
stress testing image and see if it's more of a hardware issue.  It
might also be a power supply issue, where as the load goes up, your
power supply can't keep the voltage up and the system fails that way?

There's the 'stress-ng' package for beating on systems.  And I think
I've used 'sysrecue' in the past to boot up systems and run stress
tests.

Getting the regular OS out of the way with something lower level and
simpler to stress test the hardware is a good idea.

https://www.stresslinux.org/sl/

Might be another good option.

Good luck!
John

  reply	other threads:[~2021-12-16 21:44 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
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 [this message]
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=25019.45839.872620.235430@quad.stoffel.home \
    --to=john@stoffel.org \
    --cc=antlists@youngman.org.uk \
    --cc=linux-raid@vger.kernel.org \
    --cc=rogerheflin@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