From: "Roland Franke" <fli4l@franke-prem.de>
To: "Eric Dumazet" <eric.dumazet@gmail.com>, <netdev@vger.kernel.org>
Subject: Re: iproute2 4.14.1 tc class add come to kernel-panic
Date: Mon, 29 Jan 2018 16:18:07 +0100 [thread overview]
Message-ID: <1E16D55C93FB425AA8431609B1A38168@ROLANDAMD64> (raw)
In-Reply-To: <1517238148.3715.88.camel@gmail.com>
Hello,
> To: Roland Franke ; netdev@vger.kernel.org
> Subject: Re: BUG: iproute2 4.14.1 tc class add come to kernel-panic
>>
>> tc qdisc add dev eth0 root handle 20: htb default 4 r2q 1
>> tc class add dev eth0 parent 20: classid 20:7 htb rate 10000kbit
>> tc qdisc add dev eth0 parent 20:7 sfq perturb 10
>> tc class add dev eth0 parent 20:7 classid 20:1 htb rate 200kbit ceil
>> 10000kbit prio 0
>>
>> I become an Kernel-panic with the following output:
>> kern.err kernel: BUG: scheduling while atomic: tc/1036/0x00000200
>
> Would you have a stack trace to share with us ?
As i will be an absolute newby here, i will not know how to
get the stack trace out.
When i will get some information how to get this, i can try to
give you this information.
But by my last tests i made the first 3 commands on an console
and had no error. Only by typing the last line i will get the error and
here i get actally only the "kern.err kernel: BUG: ....." message.
Roland
next prev parent reply other threads:[~2018-01-29 15:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-29 14:51 BUG: iproute2 4.14.1 tc class add come to kernel-panic Roland Franke
2018-01-29 15:02 ` Eric Dumazet
2018-01-29 15:18 ` Roland Franke [this message]
2018-01-29 16:00 ` Stephen Hemminger
2018-01-29 17:03 ` Cong Wang
2018-01-29 19:07 ` Cong Wang
2018-01-30 17:46 ` Roland Franke
2018-01-31 6:27 ` Cong Wang
2018-01-31 7:46 ` Roland Franke
2018-02-02 6:42 ` Cong Wang
2018-02-03 7:07 ` Roland Franke
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=1E16D55C93FB425AA8431609B1A38168@ROLANDAMD64 \
--to=fli4l@franke-prem.de \
--cc=eric.dumazet@gmail.com \
--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