Bug 274411

Summary: NetworkManager causes resume from suspend fail on ACER TM2490
Product: [Fedora] Fedora Reporter: Martin Sourada <martin.sourada>
Component: NetworkManagerAssignee: Dan Williams <dcbw>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: medium    
Version: rawhideCC: dcbw
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: NetworkManager-0.7.0-0.6.6.svn3109.fc8 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-01-05 22:30:47 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 Martin Sourada 2007-09-02 09:23:17 UTC 
Description of problem:
If I want to successfuly resume from suspend on ACER TM2490 I need to stop the
Network manager service before suspend. Otherwise the computer freeze during the
resume process.

Version-Release number of selected component (if applicable):
NetworkManager-0.6.5-9.fc8
kernel-2.6.23-0.149.rc4.fc8


How reproducible:
Everytime NetworkMananger is running.

Steps to Reproduce:
1. if not running turn NetworkManager service on (service NetoworkManager start)
2. suspend (pm-suspend --quirk-s3-bios --quirk-vbe-post --quirk-vbestate-restore)
3. try to resume
  
Actual results:
Resume fails, screen is either black (i.e. not turned on) or forzen on console
(depending on used quirks), nothing reacts.

Expected results:
Computer resumes.

Additional info:
The quirks listed in the steps-to-reproduce section, work even by themselves,
but must be present (TM2490 is not in halinfo yet), the --quirk-s3-bios works
slightly different from the other two. Also need to handle b44 kmod to suspend
successfuly.
Comment 1 Martin Sourada 2008-01-05 22:30:47 UTC 
My notebook recently suspended by itself (as it was set to suspend when laptop
lid is closed without power supply, and the power supply was unexpectedly cut
of) and to my joy it successfully resumed, though I could not get pulseaudio to
work again... but that's another issue. So closing this bug.