netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Dumazet <dada1@cosmosbay.com>
To: Eric Dumazet <dada1@cosmosbay.com>
Cc: Linux Netdev List <netdev@vger.kernel.org>,
	Jarek Poplawski <jarkao2@gmail.com>
Subject: Re: [BUG] linux-2.6.26.7 : loading of sch_cbq is stuck
Date: Tue, 04 Nov 2008 15:31:38 +0100	[thread overview]
Message-ID: <49105CCA.1040903@cosmosbay.com> (raw)
In-Reply-To: <491027B9.2090403@cosmosbay.com>

Eric Dumazet a écrit :
> Hi all
> 
> Just found this problem on linux-2.6.26.7 when trying to add cbq on eth0
> 
> /proc/modules hangs too
> 
> root     12117  0.0  0.0   1560   360 pts/1    D+   11:07   0:00 lsmod
> root     10361  0.0  0.0   1996   696 pts/0    D+   11:05   0:00 tc 
> qdisc add dev eth0 root handle 1: cbq avpkt 1000 rate 100Mbit bandwidth 
> 100Mbit
> root     10362  0.0  0.0      0     0 ?        S<   11:05   0:00 [khelper]
> root     10363  0.0  0.0   1592   588 ?        R    11:05   0:00 
> /sbin/modprobe -q -- sch_cbq
> root     10364  0.0  0.0      0     0 ?        S<   11:05   0:00 
> [kstopmachine]
> root     10365  0.0  0.0      0     0 ?        Z<   11:05   0:00 
> [kstopmachine] <defunct>
> root     10366  0.0  0.0      0     0 ?        Z<   11:05   0:00 
> [kstopmachine] <defunct>
> root     10367  0.0  0.0      0     0 ?        Z<   11:05   0:00 
> [kstopmachine] <defunct>
> 

Well, the answer is : I had a realtime user process that was looping.

Killing it one hour later solved the problem and unlocked all blocked
tasks.

Dont let users run realtime, better let them access hard-reset button...



      reply	other threads:[~2008-11-04 14:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-04 10:45 [BUG] linux-2.6.26.7 : loading of sch_cbq is stuck Eric Dumazet
2008-11-04 14:31 ` Eric Dumazet [this message]

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=49105CCA.1040903@cosmosbay.com \
    --to=dada1@cosmosbay.com \
    --cc=jarkao2@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;
as well as URLs for NNTP newsgroup(s).