No network after resume from suspend

Bug #213662 reported by Rob M
2
Affects Status Importance Assigned to Milestone
Ubuntu
Invalid
Undecided
Daniel Hahler

Bug Description

After resuming from being suspended, I no longer have a working Network. I need to run the following commands to bring it back up:
sudo ifdown eth0
sudi ifup eth0.

Note that the ifdown command reports the following two errors:
RTNETLINK answers: No such process
SIOCDELRT: No such process

Of course, I expected the network to work after resuming. This worked as expected with Ubuntu 7.10. I just updated yesterday to 8.04

I am using the following ubuntu version:
Description: Ubuntu hardy (development branch)
Release: 8.04

Note that I have KDE installed and am using that, not that that should matter any.

I have attached the output of dmesg below. I cleared its contents (sudo dmesg -c) just before suspending.

Output of ifconfig (after runninf ifdown and ifup) follows:
eth0 Link encap:Ethernet HWaddr 00:16:76:86:35:a7
          inet addr:192.168.1.100 Bcast:192.168.1.255 Mask:255.255.255.0
          inet6 addr: fe80::216:76ff:fe86:35a7/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:4143 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1284 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1872886 (1.7 MB) TX bytes:158876 (155.1 KB)
          Interrupt:18 Base address:0xde00

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:94 errors:0 dropped:0 overruns:0 frame:0
          TX packets:94 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:4700 (4.5 KB) TX bytes:4700 (4.5 KB)

contents of /etc/network/interfaces follows:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
#iface eth0 inet dhcp

iface eth0 inet static
address 192.168.1.100
netmask 255.255.255.0
gateway 192.168.1.1

Please let me know what other info I can provide that can help debug this. I am very computer literate, so I shoudl have no problems experimenting if you have any ideas of what to try.

Revision history for this message
Rob M (dmrlook) wrote :
Revision history for this message
Daniel Hahler (blueyed) wrote :

Thank you for your detailed bug report.
This sounds like a regression caused by bug 162654.

I'm marking it as duplicate.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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