From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 80201] general protection fault: 0000 [#1] SMP (while using HTB)
Date: Mon, 25 Aug 2014 14:48:46 -0700 [thread overview]
Message-ID: <20140825144846.57afc899@urahara> (raw)
Begin forwarded message:
Date: Mon, 25 Aug 2014 09:39:23 -0700
From: "bugzilla-daemon@bugzilla.kernel.org" <bugzilla-daemon@bugzilla.kernel.org>
To: "stephen@networkplumber.org" <stephen@networkplumber.org>
Subject: [Bug 80201] general protection fault: 0000 [#1] SMP (while using HTB)
https://bugzilla.kernel.org/show_bug.cgi?id=80201
--- Comment #12 from Cenek Zach <cenek.zach@gmail.com> ---
I might have a clue. We are changing the limits imposed by HTB each minute
using following command:
$TC class change dev "$BL_DEVICE" parent 1: classid 1:1 htb rate "$LIMIT" burst
"$BL_BURST" cburst "$BL_CBURST" quantum 60000
And this command was definitely running in 3/4 cases at the time of crash
(found him in 'crash> bt -a')
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2014-08-25 21:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-25 21:48 Stephen Hemminger [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-07-23 18:01 Fw: [Bug 80201] general protection fault: 0000 [#1] SMP (while using HTB) Stephen Hemminger
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=20140825144846.57afc899@urahara \
--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