Messages in this thread | | | From | Arkadiusz Miskiewicz <> | Subject | ip a flush problem on 2.6 kernels (fine on 2.4 kernels) | Date | Thu, 4 Mar 2004 03:08:15 +0100 |
| |
The problem is that
ip a a 192.168.0.1/24 dev eth0 ip link set eth0 down ip a flush dev eth0
Here on my vanilla 2.6.2 it locks eating CPU - it does netlink communication over and over. This ,,hang'' doesn't happen when interface is in UP state. Also doesn't happen on 2.4 kernels.
I've tried it on different 2.6 kernels (one from fedora, one from PLD) with different versions of iproute2 (usually latest). Friend tried it also with iproute2 from slackware - same result.
Same happens when using lo interface instead of ethX.
More description in RH bugzilla: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=116982
ps. doing that on Broadcom Corporation BCM4401 100Base-T ethX interface (using b44 driver) causes lock (but sysrq works) on 2.4.25 kernel. Would be nice if someone with that hardware could verify this. -- Arkadiusz Miśkiewicz CS at FoE, Wroclaw University of Technology arekm.pld-linux.org, 1024/3DB19BBD, JID: arekm.jabber.org, PLD/Linux - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |