Bug 579495 - iwlist reports "Network is down" after resume
Summary: iwlist reports "Network is down" after resume
Keywords:
Status: CLOSED DUPLICATE of bug 578141
Alias: None
Product: Fedora
Classification: Fedora
Component: wireless-tools
Version: rawhide
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-05 15:17 UTC by Evgeny F
Modified: 2010-04-09 21:30 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-04-09 21:30:03 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
/var/log/messages info after resume (13.06 KB, application/octet-stream)
2010-04-07 15:42 UTC, Miroslav Vadkerti
no flags Details
/var/log/messages after resume (1.32 MB, application/octet-stream)
2010-04-09 21:03 UTC, Aron Parsons
no flags Details

Description Evgeny F 2010-04-05 15:17:26 UTC
Description of problem:

I cannot see the list of wireless networks after resume and the "iwlist scan" reports that "Network is down".

After I disable the wireless and re-enable it in NetworkManager applet everything goes back to normal.

Version-Release number of selected component (if applicable):
Linux 2.6.33.1-19.fc13.x86_64
Wireless-Tools version 29
NetworkManager Applet 0.8

How reproducible:
Every time


Steps to Reproduce:
1. Suspend
2. Resume
3. Click on network manager applet to see the list of networks
4. Run "iwlist scan" as root. (optionally)
  
Actual results:
No networks are listed. "iwlist scan" reports the network is down.

Expected results:
Listing of available wireless networks.


Additional info:
Driver: ath5k

Comment 1 Miroslav Vadkerti 2010-04-07 15:41:49 UTC
I'm having similar issues. After suspend (wlan connection active) my wlan connection doesn't resume. 

kernel:
kernel-2.6.33.1-19.fc13.x86_64

In /var/log messages I have:
Apr  7 17:34:35 freedom NetworkManager: <info>  (wlan0): now managed
Apr  7 17:34:35 freedom NetworkManager: <info>  (wlan0): device state change: 1 -> 2 (reason 2)
Apr  7 17:34:35 freedom NetworkManager: <info>  (wlan0): bringing up device.
Apr  7 17:34:35 freedom NetworkManager: <info>  (wlan0): deactivating device (reason: 2).

Wireless:
03:00.0 Network controller: Intel Corporation PRO/Wireless 5100 AGN [Shiloh] Network Connection

Also attaching /var/log/messages part after resume.

Comment 2 Miroslav Vadkerti 2010-04-07 15:42:23 UTC
Created attachment 405005 [details]
/var/log/messages info after resume

Comment 3 Aron Parsons 2010-04-09 21:03:03 UTC
I'm having the same issue.  Toggling the kill switch brings the connection back immediately.

# uname -r
2.6.33.1-24.fc13.x86_64

# lspci | grep -i wireless
03:00.0 Network controller: Intel Corporation PRO/Wireless 5100 AGN [Shiloh] Network Connection

Comment 4 Aron Parsons 2010-04-09 21:03:36 UTC
Created attachment 405643 [details]
/var/log/messages after resume

Comment 5 Dan Williams 2010-04-09 21:30:03 UTC
I think this is a dupe of bug 578141; please try the builds referenced there and see if they fix your problem.  Thanks!

*** This bug has been marked as a duplicate of bug 578141 ***


Note You need to log in before you can comment on or make changes to this bug.