Ubuntu
network-config package

eth0 unstable after update from Feisty to Gutsy

Bug #159019 reported by Gert van Spijker
4
Affects Status Importance Assigned to Milestone
network-config (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I just upgraded from Feisty to Gutsy using the normal procedure (Update Manager).
After boot into the 2.6.22-14-generic kernel I have network access most of the time, but after a while networking stops working.
The key problem seems to be that the eth0 interface drops packets once it fails.

ifconfig lists eth0 as follows while networking works:

eth0 Link encap:Ethernet HWaddr 00:13:8F1:74:B0
inet addr:192.168.1.35 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::213:8fff:fed1:74b0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:13 errors:0 dropped:0 overruns:0 frame:0
TX packets:25 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1176 (1.1 KB) TX bytes:3857 (3.7 KB)
Interrupt:17 Base address:0x8000

after networking failure:

eth0 Link encap:Ethernet HWaddr 00:13:8F1:74:B0
inet addr:192.168.1.35 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::213:8fff:fed1:74b0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:88 errors:0 dropped:4294967295 overruns:0 frame:0
TX packets:98 errors:0 dropped:92 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:63244 (61.7 KB) TX bytes:12725 (12.4 KB)
Interrupt:17 Base address:0x8000

Note the dropped:4294967295 and dropped:92

When I boot into the previous kernel, 2.6.22-16-generic, the problem disappears and the networking is stable.

Revision history for this message
Gert van Spijker (gert-ab-graph) wrote :

Extra information:
My network hardware is a "RTL8111/8168B PCI Express Gigabit Ethernet controller"

Revision history for this message
Gert van Spijker (gert-ab-graph) wrote :

Sorry for the confusion, but the kernel that works is 2.6.20-16-generic, not 2.6.22-16-generic as I wrote in the last line of the original post.

Revision history for this message
Przemek K. (azrael) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? (9.10) Thanks in advance.

Also please note that both Feisty and Gutsy have reached their End Of Life by now.

Changed in network-config (Ubuntu):
status: New → Incomplete
Revision history for this message
Przemek K. (azrael) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in network-config (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.