public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 215888] New: raw socket test with stress-ng trigger soft lockup
Date: Tue, 26 Apr 2022 07:54:48 -0700	[thread overview]
Message-ID: <20220426075448.037015eb@hermes.local> (raw)



Begin forwarded message:

Date: Tue, 26 Apr 2022 09:31:50 +0000
From: bugzilla-daemon@kernel.org
To: stephen@networkplumber.org
Subject: [Bug 215888] New: raw socket test with stress-ng trigger soft lockup


https://bugzilla.kernel.org/show_bug.cgi?id=215888

            Bug ID: 215888
           Summary: raw socket test with stress-ng trigger soft lockup
           Product: Networking
           Version: 2.5
    Kernel Version: 5.17
          Hardware: Intel
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: blocking
          Priority: P1
         Component: IPV4
          Assignee: stephen@networkplumber.org
          Reporter: colin.king@canonical.com
        Regression: No

Running stress-ng [1] with the following raw socket stressor triggers a
softlockup on a SMP NUMA x86-64 system:

sudo stress-ng --rawsock 20 -t 60

kernel:watchdog: BUG: soft lockup - CPU#4 stuck for 22s! [stress-ng:49781]

Tested this on 5.17. User has also reported this against the stress-ng project:

https://github.com/ColinIanKing/stress-ng/issues/187

[1] Stress-ng:
https://github.com/ColinIanKing/stress-ng
git clone https://github.com/ColinIanKing/stress-ng
cd stress-ng
make
sudo ./stress-ng --rawsock 0 -t 60

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.

                 reply	other threads:[~2022-04-26 14:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20220426075448.037015eb@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=netdev@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