From: Fedor Karpelevitch <fedor@karpelevitch.net>
To: Jeff Garzik <jgarzik@pobox.com>, 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: Re: [PATCH] Re: ifconfig up/down problem
Date: Tue, 9 Sep 2003 16:35:58 -0700 [thread overview]
Message-ID: <200309091635.58748.fedor@karpelevitch.net> (raw)
In-Reply-To: <3F5CFF7E.1090005@pobox.com>
Jeff Garzik wrote:
> 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
does not help me (assuming I have the same problem). I have a total
lockup a few seconds after setting up the interface (not
immidiately).
Fedor.
next prev parent reply other threads:[~2003-09-10 5:51 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 ` [PATCH] " Jeff Garzik
2003-09-08 22:40 ` Sven-Haegar Koch
2003-09-09 23:35 ` Fedor Karpelevitch [this message]
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=200309091635.58748.fedor@karpelevitch.net \
--to=fedor@karpelevitch.net \
--cc=akpm@digeo.com \
--cc=davem@redhat.com \
--cc=haegar@sdinet.de \
--cc=jgarzik@pobox.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.