| Summary: | pm-suspend sometimes does not work | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Jerome Quelin <jquelin> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | thierry.vignaud, tmb |
| Version: | Cauldron | Keywords: | NEEDINFO |
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | kernel | CVE: | |
| Status comment: | |||
| Attachments: | dmesg output when non-working. | ||
|
Description
Jerome Quelin
2011-03-30 09:37:04 CEST
Ahmad Samir
2011-03-30 17:58:02 CEST
CC:
(none) =>
tmb Please attach dmesg output in both working and not working cases Keywords:
(none) =>
NEEDINFO it's much less frequent nowadays, maybe due to new kernel? previously, at report time (2.6.38.2-desktop-1.mga), i could have 1 suspend ok and the later ones were not working, need reboot. now (2.6.38.4-desktop-1.mga), i had no problem suspending. i propose to leave the bug open just in case. 2.6.38.6-desktop-1.mga and 2.6.38.7-desktop-1.mga trigger the problem. Created attachment 500 [details]
dmesg output when non-working.
hmm, in fact it seemed to be related to a network script that took too much time. keeping open just in case. it was definitely the case, closing bug. Status:
NEW =>
RESOLVED |