[hardy] network interfaces not restarted after resume
Bug #214523 reported by
P
This bug report is a duplicate of:
Bug #162654: ipw2200 needs to be reloaded after suspend.
Edit
Remove
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
acpi-support (Ubuntu) |
Invalid
|
Medium
|
Daniel Hahler |
Bug Description
Binary package hint: acpi-support
I have an thinkpad X40. After suspend to RAM and resume, my wired interface is not restored correctly.
I have to /etc/init.
I have also the same problem after hibernate/resume on another computer. The eth0 network interface is not operational.
Both computers use dhcp to get an address.
$ lsb_release -rd
Description: Ubuntu hardy (development branch)
Release: 8.04
$ apt-cache policy acpi-support
acpi-support:
Installé : 0.108
Candidat : 0.108
Table de version :
*** 0.108 0
500 http://
100 /var/lib/
To post a comment you must log in.
doing /etc/acpi/ suspend. d/55-down- interfaces. sh
manually works OK and I can see that the dhcpclient3 process has been killed
# /etc/acpi/ suspend. d/55-down- interfaces. sh dhclient. eth0.pid with pid 17093 www.isc. org/sw/ dhcp/
+ pccardctl eject
+ killall dhclient dhclient3
+ /sbin/ifconfig
+ awk /^[^ ]+/ {print $1}
+ INTERFACES=eth0
eth0:0
eth0:1
eth1
lo
+ ifdown eth0
There is already a pid file /var/run/
removed stale PID file
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://
Listening on LPF/eth0/ 00:0a:e4: 24:7b:a8 00:0a:e4: 24:7b:a8
Sending on LPF/eth0/
Sending on Socket/fallback
DHCPRELEASE on eth0 to 192.168.0.254 port 67
+ ifconfig eth0 down
+ ifdown eth0:0
RTNETLINK answers: No such process
+ ifconfig eth0:0 down
SIOCSIFFLAGS: Cannot assign requested address
+ ifdown eth0:1
RTNETLINK answers: No such process
+ ifconfig eth0:1 down
SIOCSIFFLAGS: Cannot assign requested address
+ ifdown eth1
ifdown: interface eth1 not configured
+ ifconfig eth1 down
+ ifdown lo
+ ifconfig lo down
BUT when I do a suspend to ram / resume
I can still see the same dhcpclient3 process ID active.
In fact it is as if /etc/acpi/ suspend. d/55-down- interfaces. sh is never called upon suspend
Also I have some trouble to understand how the variable INTERFACES is populated in the
following script resume.d script :
# cat /etc/acpi/ resume. d/62-ifup. sh
#!/bin/sh
# Bring up the interfaces (this should probably be left up to some policy
# manager, but at the moment we just bring back whatever we ifdowned)
for x in $INTERFACES; do
ifup $x &
done