lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 16 Dec 2010 17:17:13 +0100
From:	Nicolas Dichtel <nicolas.dichtel@...nd.com>
To:	Jeff Kirsher <jeffrey.t.kirsher@...el.com>,
	Jesse Brandeburg <jesse.brandeburg@...el.com>,
	Bruce Allan <bruce.w.allan@...el.com>,
	Carolyn Wyborny <carolyn.wyborny@...el.com>,
	Don Skidmore <donald.c.skidmore@...el.com>,
	Greg Rose <gregory.v.rose@...el.com>,
	PJ Waskiewicz <peter.p.waskiewicz.jr@...el.com>,
	Alex Duyck <alexander.h.duyck@...el.com>,
	John Ronciak <john.ronciak@...el.com>
CC:	netdev <netdev@...r.kernel.org>
Subject: e1000: more than two seconds to get the flag RUNNING

Hi,

maybe this problem has already been discussed, but I didn't find the thread.
When I put an interface managed by the e1000 driver up, down and up again, I 
must wait more than 2 seconds to get the flag running again.

Here is the sequence:

shelby:~# uname -a
Linux shelby 2.6.37-rc5+ #9 SMP Wed Dec 15 13:16:10 EST 2010 i686 GNU/Linux
shelby:~# lsmod | grep e1000
e1000                  76543  0
shelby:~# lspci | grep Gigabit
01:09.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet 
Controller (rev 02)
shelby:~# cat check_link_state.sh
#!/bin/bash

sleep_time=$1
ip link set eth0 up
ip link set eth0 down
ip link set eth0 up
while [ $sleep_time -gt 0 ] ; do
     date
     #ip link show eth0
     ifconfig eth0 | grep MULTICAST
     sleep 1
     echo ""
     sleep_time=`expr $sleep_time - 1`
done
shelby:~# ifconfig eth0
eth0      Link encap:Ethernet  HWaddr 00:30:1b:b4:dc:88
           inet addr:10.16.0.72  Bcast:10.16.0.255  Mask:255.255.255.0
           inet6 addr: fe80::230:1bff:feb4:dc88/64 Scope:Link
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           RX packets:22051 errors:0 dropped:0 overruns:0 frame:0
           TX packets:63 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:1000
           RX bytes:2480685 (2.3 MiB)  TX bytes:5242 (5.1 KiB)

shelby:~# ./check_link_state.sh 3
[83270.080175] ADDRCONF(NETDEV_UP): eth0: link is not ready
Thu Dec 16 12:45:56 EST 2010
           UP BROADCAST MULTICAST  MTU:1500  Metric:1

Thu Dec 16 12:45:57 EST 2010
           UP BROADCAST MULTICAST  MTU:1500  Metric:1
[83271.828371] e1000: eth0 NIC Link is Up 100 Mbps Half Duplex, Flow Control: None
[83271.835878] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

Thu Dec 16 12:45:58 EST 2010
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

shelby:~#

I get the same result with a 2.6.15, so it seems that the problem is here since 
a long time.
Has anyone an input for this problem?


Regards,
Nicolas
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ