netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Roland Franke <fli4l@franke-prem.de>, netdev@vger.kernel.org
Subject: Re: BUG: iproute2 4.14.1 tc class add come to kernel-panic
Date: Mon, 29 Jan 2018 07:02:28 -0800	[thread overview]
Message-ID: <1517238148.3715.88.camel@gmail.com> (raw)
In-Reply-To: <9AD3E60C0FF644D9B0EB7D279E3FE8CC@ROLANDAMD64>

On Mon, 2018-01-29 at 15:51 +0100, Roland Franke wrote:
> Starting with Kernel 4.14.1 (x86_64) I found the following problem:
> When I made the following commands:
> 
> 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
> 
> The identical message come, when i try the kernel till 4.14.15.
> 
> When i have tested the same with one of the kernels from the 4.13 series,
> i had no problem.Will this be solved in the kernel-series 4.14 or will this 
> only with the
> coming series 4.15 be made?
> 
> Kernel 4.15 is not be tested till now.
> 
> Best regards,
> Roland Franke 
> 

Hi Roland

Would you have a stack trace to share with us ?

Thanks !

  reply	other threads:[~2018-01-29 15:02 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 [this message]
2018-01-29 15:18   ` Roland Franke
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=1517238148.3715.88.camel@gmail.com \
    --to=eric.dumazet@gmail.com \
    --cc=fli4l@franke-prem.de \
    --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).