Bug 466166

Summary: Suspending causes there to be no route on the ipw2200 after resuming
Product: Red Hat Enterprise Linux 5 Reporter: Suzanne Hillman <shillman>
Component: NetworkManagerAssignee: Dan Williams <dcbw>
Status: CLOSED ERRATA QA Contact: desktop-bugs <desktop-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.3CC: riek, syeghiay
Target Milestone: rcFlags: riek: needinfo-
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-01-20 21:28:55 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Suzanne Hillman 2008-10-08 20:07:33 UTC
Description of problem:
Suspending causes there to be no route on the wireless (ipw2200) (IBM T42) after resuming.

Version-Release number of selected component (if applicable):
NM-0.7.0-0.11.svn4133.el5
(20081006.0 build)

How reproducible:
Always

Steps to Reproduce:
1. Have a wireless connection.
2. Suspend, resume.
  
Actual results:
Connection, but no route.

Expected results:
Connection and route

Additional info:
I've only tested with both wired and wireless connections, but I doubt it matters. It requires a reboot to make it happy again.

Unclear if this is a regression, as I did not test this card in 5.2. I suspect that it is. Also not yet sure if it happens on other cards/system.

Comment 1 Suzanne Hillman 2008-10-08 20:20:02 UTC
I can't regularly reproduce this, although the developer just dropped by to say that he thinks they may have tracked this down anyway.

Comment 2 Dan Williams 2008-10-08 20:41:02 UTC
believe this is fixed upstream in svn4157 and later

Comment 4 Dan Williams 2008-10-14 14:48:57 UTC
acked, will be respinning on Wednesday.

Comment 7 Dan Williams 2008-10-16 20:01:03 UTC
NetworkManager-0.7.0-0.11.svn4185.el5

Comment 11 errata-xmlrpc 2009-01-20 21:28:55 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHEA-2009-0161.html