Intel Corporation PRO/100 VE connects to the Internet only at times

[Alberto Milone]

My network card is an Intel Corporation PRO/100 VE:

07:08.0 Ethernet controller: Intel Corporation PRO/100 VE Network Connection (rev 02)
        Subsystem: Fujitsu Siemens Computer GmbH Unknown device 10ad
        Flags: bus master, medium devsel, latency 64, IRQ 20
        Memory at dc000000 (32-bit, non-prefetchable) [size=4K]
        I/O ports at 5000 [size=64]
        Capabilities: <access denied>

Sometimes when I boot Ubuntu on my laptop, with the network cable plugged in, I have no Internet connection even though Network manager says it's connected. All I have to do is unplug and plug the ethernet cable a few times (even 10 times) before I can get proper connection.

doing a sudo ifconfig eth0 down and then sudo ifconfig eth0 up doesn't solve the problem. Disabling ipv6 doesn't change anything.

NOTE: I connect to the Internet through a router (with DHCP) and I have no problem with my other computers of the same network.

Please let me know if you need further details.

[Alberto Milone (albertomilone)]

Here is the output of ifconfig when the network doesn't work:

:~$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:16:36:CA:DB:80
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:14 errors:0 dropped:0 overruns:0 frame:0
          TX packets:309 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:2856 (2.7 KB) TX bytes:36500 (35.6 KB)

eth0:avah Link encap:Ethernet HWaddr 00:16:36:CA:DB:80
          inet addr:169.254.8.205 Bcast:169.254.255.255 Mask:255.255.0.0
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:60 errors:0 dropped:0 overruns:0 frame:0
          TX packets:60 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:5550 (5.4 KB) TX bytes:5550 (5.4 KB)

Here's the output of ifconfig when the connection works:

:~$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:16:36:CA:DB:80
          inet addr:192.168.0.102 Bcast:192.168.0.255 Mask:255.255.255.0
          inet6 addr: fe80::216:36ff:feca:db80/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:338 errors:0 dropped:0 overruns:0 frame:0
          TX packets:572 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:157546 (153.8 KB) TX bytes:74519 (72.7 KB)

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:65 errors:0 dropped:0 overruns:0 frame:0
          TX packets:65 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:5990 (5.8 KB) TX bytes:5990 (5.8 KB)

Any ideas?

[MrMur (murrayie)]

I have the same issue.

If you do dmesg inbetween re replugging, it does not register the "link". After a few goes, you get.... (am using a Xen kernel in this example, but was the same in regular kernel.) This is a big issue for me.

[ 310.356159] e100: peth0: e100_watchdog: link up, 100Mbps, full-duplex
[ 310.358265] eth0: port 1(peth0) entering learning state
[ 310.360043] eth0: topology change detected, propagating
[ 310.360048] eth0: port 1(peth0) entering forwarding state

...and then the network port will work.

[Leann Ogasawara (leannogasawara)]

[This is an automated message. Apologies if it has reached you inappropriately.]

This bug was reported against the linux-meta package when it likely should have been reported against the linux package instead. We are automatically transitioning this to the linux kernel package so that the appropriate teams are notified and made aware of this issue. Thanks.

[kernel-janitor (kernel-janitor)]

Hi albertomilone,

Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/releases/ . Please then run following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux-image-`uname -r` 172295

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]