LKML Archive on
help / color / mirror / Atom feed
From: Ivid Suvarna <>
To: Kernel development list <>,
Subject: Softlockup and Hardlockup sample test module
Date: Sun, 15 Apr 2018 05:41:35 +0000	[thread overview]
Message-ID: <> (raw)

[-- Attachment #1.1: Type: text/plain, Size: 625 bytes --]

Hi All,

Could you please provide some sample test module for causing a Softlockup
and Hardlockup in latest kernel for SMP for only testing purposes. I assume
there are some Kconfigs to be enabled as well for this.

I had tried with the module where I put a busy loop inside spinlock but was
not able to cause any lockups. Maybe this is because of SMP which schedule
the job to other CPU. "How do I make a task to run on single CPU only?"

I only get RCU stalls sometimes instead of softlockup when I use busy loop
inside a spinlock. Is there any explanation for difference between these
stalls and softlockup.


[-- Attachment #1.2: Type: text/html, Size: 863 bytes --]

[-- Attachment #2: Type: text/plain, Size: 170 bytes --]

Kernelnewbies mailing list

             reply	other threads:[~2018-04-15  5:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-15  5:41 Ivid Suvarna [this message]
2018-04-15  7:47 Ivid Suvarna
2018-04-15 19:12 ` valdis.kletnieks
2018-04-15 22:19 ` Cong Wang

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \ \
    --subject='Re: Softlockup and Hardlockup sample test module' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).