From: Jeff Garzik <jgarzik@pobox.com>
To: Sven-Haegar Koch <haegar@sdinet.de>
Cc: netdev@oss.sgi.com, "David S. Miller" <davem@redhat.com>,
Andrew Morton <akpm@digeo.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH] Re: ifconfig up/down problem
Date: Mon, 08 Sep 2003 18:15:26 -0400 [thread overview]
Message-ID: <3F5CFF7E.1090005@pobox.com> (raw)
In-Reply-To: <Pine.LNX.4.56.0309090004100.24700@space.comunit.de>
[-- Attachment #1: Type: text/plain, Size: 1035 bytes --]
Sven-Haegar Koch wrote:
> hi...
>
> Short: ifconfig ethX down locks
>
> Kernel: 2.4.22-bk12 (same problem with 2.4.23-pre3)
> eth0: eepro100
> eth1: orinoco_cs (orinoco mini-pci)
> System: Toshiba Satellite Pro 4600 Laptop, P3 700Mhz
>
> Just after booting, no X startet yet, interface not yet initialized:
>
> aurora:~# ifconfig eth1 down
> aurora:~# ifconfig eth1 up
> aurora:~# ifconfig eth1 down
> aurora:~# ifconfig eth1 up
> aurora:~# ifconfig eth1 down
> <--lock here, shell does not return, even ctrl-c does not help
>
> haegar@aurora:~$ ps axl|grep ifconfig
> 4 0 1041 1035 9 0 1448 404 dev_cl S pts/0 0:00 ifconfig eth1
>
> top shows ifconfig consuming 100% cpu, 100% system
>
> The same happens with eth0, there it takes only two up/down cycles,
> perhaps because it is already configured with ipv4+ipv6 addresses, and the
> same happens using '/sbin/ip link set eth0 up/down' too.
>
> Kernel 2.4.20-pre2-ac3 is ok (my last kernel, running for month')
Does the attached patch fix it?
Jeff
[-- Attachment #2: patch --]
[-- Type: text/plain, Size: 510 bytes --]
diff -Nru a/net/core/dev.c b/net/core/dev.c
--- a/net/core/dev.c Mon Sep 8 18:14:36 2003
+++ b/net/core/dev.c Mon Sep 8 18:14:36 2003
@@ -851,7 +851,11 @@
* engine, but this requires more changes in devices. */
smp_mb__after_clear_bit(); /* Commit netif_running(). */
- netif_poll_disable(dev);
+ while (test_bit(__LINK_STATE_RX_SCHED, &dev->state)) {
+ /* No hurry. */
+ current->state = TASK_INTERRUPTIBLE;
+ schedule_timeout(1);
+ }
/*
* Call the device specific close. This cannot fail.
next prev parent reply other threads:[~2003-09-08 22:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-08 22:08 ifconfig up/down problem Sven-Haegar Koch
2003-09-08 22:15 ` Jeff Garzik [this message]
2003-09-08 22:40 ` [PATCH] " Sven-Haegar Koch
2003-09-09 23:35 ` Fedor Karpelevitch
2003-09-10 6:08 ` Fedor Karpelevitch
2003-09-10 14:52 ` Fedor Karpelevitch
2003-09-10 16:00 ` Fedor Karpelevitch
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=3F5CFF7E.1090005@pobox.com \
--to=jgarzik@pobox.com \
--cc=akpm@digeo.com \
--cc=davem@redhat.com \
--cc=haegar@sdinet.de \
--cc=linux-kernel@vger.kernel.org \
--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).