55-down-interfaces.sh suspend script reads in incorrect wireless interface name.

Bug #181809 reported by Tomas Cassidy
2
Affects Status Importance Assigned to Milestone
acpi-support (Ubuntu)
New
Undecided
Unassigned

Bug Description

The ACPI script /etc/acpi/suspend.d/55-down-interfaces.sh seems to be run when the computer is going into suspend mode and shuts down all network interfaces. These network interfaces are obtained from the output of the 'ifconfig' command. On my laptop, the output of 'ifconfig' gives the wireless interface name as "wlan0_ren" when the correct interface name is actually "wlan0_rename" (given by iwconfig, and ubuntu default name). This prevents the script from shutting down the wireless network interface when going into suspend mode, and therefore prevents it from being started again when coming out of suspend (the resume script seems to use the same interface names as the suspend script). I thought about changing the interface name for the wireless interface since ifconfig might have a name-size limit, but I have no idea how I should be doing this.

output of ifconfig:
eth0 Link encap:Ethernet HWaddr 00:1D:09:BC:E9:EA
          inet addr:192.168.0.15 Bcast:255.255.255.255 Mask:255.255.255.0
          inet6 addr: fe80::21d:9ff:febc:e9ea/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:125072 errors:0 dropped:0 overruns:0 frame:0
          TX packets:98654 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:161688010 (154.1 MB) TX bytes:11561023 (11.0 MB)
          Interrupt:17

eth1 Link encap:UNSPEC HWaddr 00-1C-BF-8B-4D-01-00-00-00-00-00-00-00-00-00-00
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

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:18842 errors:0 dropped:0 overruns:0 frame:0
          TX packets:18842 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1084693 (1.0 MB) TX bytes:1084693 (1.0 MB)

wlan0_ren Link encap:Ethernet HWaddr 00:1C:BF:8B:4D:01
          UP BROADCAST MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

output of iwconfig:
lo no wireless extensions.

eth0 no wireless extensions.

eth1 no wireless extensions.

wlan0_rename IEEE 802.11g ESSID:""
          Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
          Retry min limit:7 RTS thr:off Fragment thr=2346 B
          Link Quality:0 Signal level:0 Noise level:0
          Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
          Tx excessive retries:0 Invalid misc:0 Missed beacon:0

Revision history for this message
Andres Mujica (andres.mujica) wrote :

This is a duplicate from bug #183968 please check the workaround described there. Thanks a lot for your bug report

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.