From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 208833] New: applying HFSC causes soft lockup (probably related to pppoe)
Date: Thu, 6 Aug 2020 08:04:52 -0700 [thread overview]
Message-ID: <20200806080452.0693f8b2@hermes.lan> (raw)
Begin forwarded message:
Date: Thu, 06 Aug 2020 13:22:36 +0000
From: bugzilla-daemon@bugzilla.kernel.org
To: stephen@networkplumber.org
Subject: [Bug 208833] New: applying HFSC causes soft lockup (probably related to pppoe)
https://bugzilla.kernel.org/show_bug.cgi?id=208833
Bug ID: 208833
Summary: applying HFSC causes soft lockup (probably related to
pppoe)
Product: Networking
Version: 2.5
Kernel Version: 5.7
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Other
Assignee: stephen@networkplumber.org
Reporter: valahanovich@tut.by
Regression: No
Created attachment 290795
--> https://bugzilla.kernel.org/attachment.cgi?id=290795&action=edit
example of my regular tc script
Applying and reapplying HFSC qdisc to interface with heavy load often causes
soft lockup (in random processes, in short time after applying qdisc).
Stack trace was somewhat uninformative and hard to get. I mostly observe this
with torrent client on PPPOE client interface when run attached script several
times.
Will attach dmesg as soon as i will be able to reliably get it.
I tried to bisect bug, but stopped at some old kernel that won't even boot with
my config. So the problem could be old but unnoticed.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2020-08-06 16:59 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=20200806080452.0693f8b2@hermes.lan \
--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;
as well as URLs for NNTP newsgroup(s).