From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 80201] New: general protection fault: 0000 [#1] SMP (while using HTB)
Date: Mon, 14 Jul 2014 08:47:33 -0700 [thread overview]
Message-ID: <20140714084733.0b4aeeef@haswell> (raw)
Begin forwarded message:
Date: Mon, 14 Jul 2014 04:12:45 -0700
From: "bugzilla-daemon@bugzilla.kernel.org" <bugzilla-daemon@bugzilla.kernel.org>
To: "stephen@networkplumber.org" <stephen@networkplumber.org>
Subject: [Bug 80201] New: general protection fault: 0000 [#1] SMP (while using HTB)
https://bugzilla.kernel.org/show_bug.cgi?id=80201
Bug ID: 80201
Summary: general protection fault: 0000 [#1] SMP (while using
HTB)
Product: Networking
Version: 2.5
Kernel Version: Linux 3.10.41-1.el6.elrepo.x86_64
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Other
Assignee: shemminger@linux-foundation.org
Reporter: cenek.zach@gmail.com
Regression: No
Created attachment 142971
--> https://bugzilla.kernel.org/attachment.cgi?id=142971&action=edit
Kernel GPF stack trace
Encountered GPF under normal circumstances - no heavy load (CPU, IO, net).
HTB configuration is very simple: 1 HTB class with SFQ qdisc and filter on
source port 80:
tc qdisc add dev eth0 root handle 1: htb default 30
tc class add dev eth0 parent 1: classid 1:1 htb rate $LIMIT burst 1500k cburst
1500k
tc qdisc add dev eth0 parent 1:1 handle 10: sfq perturb 10
tc filter add dev eth0 protocol ip parent 1:0 prio 1 u32 match ip sport 80
0xffff flowid 1:1
Relevant part of vmcore-dmesg.txt attached.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2014-07-14 15:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-14 15:47 Stephen Hemminger [this message]
2014-08-05 10:59 ` Fw: [Bug 80201] New: general protection fault: 0000 [#1] SMP (while using HTB) Eric Dumazet
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=20140714084733.0b4aeeef@haswell \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.