Bug 274411 - NetworkManager causes resume from suspend fail on ACER TM2490
NetworkManager causes resume from suspend fail on ACER TM2490
Product: Fedora
Classification: Fedora
Component: NetworkManager (Show other bugs)
i686 Linux
medium Severity high
: ---
: ---
Assigned To: Dan Williams
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2007-09-02 05:23 EDT by Martin Sourada
Modified: 2008-01-05 17:30 EST (History)
1 user (show)

See Also:
Fixed In Version: NetworkManager-0.7.0-0.6.6.svn3109.fc8
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-01-05 17:30:47 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Martin Sourada 2007-09-02 05:23:17 EDT
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):

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
Comment 1 Martin Sourada 2008-01-05 17:30:47 EST
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.

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