From: Nuno Silva <nuno.silva@vgertech.com>
To: "David S. Miller" <davem@redhat.com>
Cc: linux-kernel@vger.kernel.org, master@sectorb.msk.ru, netdev@oss.sgi.com
Subject: Re: 2.6.8-rc4-bk1 problem: unregister_netdevice: waiting for ppp0 to become free. Usage count = 1
Date: Sun, 22 Aug 2004 09:02:02 +0100 [thread overview]
Message-ID: <412852FA.70801@vgertech.com> (raw)
In-Reply-To: <20040821222503.51268490.davem@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2000 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
David S. Miller wrote:
| On Sun, 22 Aug 2004 03:13:55 +0100
| Nuno Silva <nuno.silva@vgertech.com> wrote:
|
|
|>This problem was introduced between 2.6.8-rc2-bk11 and 2.6.8-rc4-bk1 and
|>always happens. Right now I'm testing with 2.6.8.1 with a patch from Mr.
|>Miller -- "cacheline-align qdisc data in qdisc_create()" (attached).
|
|
| Does that patch fix the problem?
|
Hi!
No, but that patch is necessary for me to use QoS at all, or the kernel
oopses.
I was refering to that patch for you to know that's not the same
problem. Sorry for not being 100% clear.
If you want to freeze your networking :-) you can do this:
remove pppd (or adjust the ppp0 interface name later)
# killall pppd
# sleep 10
make a fony connection to 1.1.1.2 using /dev/null
#pppd /dev/null connect /bin/true persist demand 1.1.1.1:1.1.1.2
# sleep 1
add a CBQ root to ppp0 (or ppp1, if you didn't killall and have another
running)
# tc qdisc add dev ppp0 root handle 1: cbq avpkt 1000 bandwidth 10mbit
ping the fony remote:
# ping 1.1.1.2
kill pppd
#killall pppd
Now check dmesg, you should get "unregister_netdevice: waiting for ppp0
to become free. Usage count = 1"
Another remark: In single user mode pppd died and system load is 0. In
initlevel 3, pppd eats all my CPU... Don't know why.
Right now I'm testing 2.6.8.1-ck3 (because of that can't-burn-cdrom
thing and other stuff) so the attached /proc/config.gz is somewhat
non-vanilla, but this happens with 2.6.8-rc4-bk1[*] and above.
[*] this version is "bad" and 2.6.8-rc2-bk11 is "good". Didn't test with
rc3...
As you can see in the .config I'm using the OLD POLICER.
As always, please request more info if you need it! :-)
Regards,
Nuno Silva
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBKFL5OPig54MP17wRAsHeAJ4nZFSW7nat0/aahUokzriHIueO5wCgqPCM
EogRAFF/jofq4kN609j6dFc=
=1HPc
-----END PGP SIGNATURE-----
[-- Attachment #2: config.gz --]
[-- Type: application/x-gzip, Size: 10941 bytes --]
next prev parent reply other threads:[~2004-08-22 8:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <411BC284.6080807@vgertech.com>
2004-08-13 8:03 ` 2.6.8-rc4-bk1 problem: unregister_netdevice: waiting for ppp0 to become free. Usage count = 1 Vladimir B. Savkin
2004-08-13 20:35 ` Nuno Silva
2004-08-22 2:13 ` Nuno Silva
2004-08-22 5:25 ` David S. Miller
2004-08-22 8:02 ` Nuno Silva [this message]
2004-08-22 8:14 ` Herbert Xu
2004-08-22 12:39 ` Patrick McHardy
2004-08-23 4:47 ` David S. Miller
2004-08-26 16:46 ` Jurriaan
2004-08-23 17:56 ` Nuno Silva
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=412852FA.70801@vgertech.com \
--to=nuno.silva@vgertech.com \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=master@sectorb.msk.ru \
--cc=netdev@oss.sgi.com \
/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).