Bug 6129

Summary:	resuming works, but load is very high afterwards
Product:	Mageia	Reporter:	AL13N <alien>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	stormi-mageia
Version:	2	Keywords:	NEEDINFO
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:

Description AL13N 2012-05-28 10:48:17 CEST

Description of problem:
after suspending (to-disk) and resuming, the following happens:

1. the screensaver (asciiquarium) comes up quite fast, but frozen
2. after 8seconds, the first fish start to move
3. after 2seconds, the next fish moves
4. after another 5 seconds, is starting moving until it's constantly moving, but hesitantly
5. i press a key to get my password dialog
6. after another 6seconds, it appears
7. i enter password
8. after a few seconds, screensaver unlocks and desktop appears
9. by this time, it's been over a half a minute, but it seems all functional.
10. i log into a konsole and do 'top'
11. i see load values 8, 8, 4
12. it seems to use 512MB in swap, but there's around 2GB ram free
13. top mentions there's 290 processes running
14. i can start working more or less ok now.
15. after a few minutes i look back into top and i see that the load is now less than 1; but also, there's only 211 processes now.

so, after a resume, it seems way too much stuff is being triggered, somehow it might use more ram than i have, causing it to swap, delaying the resume even more.

(when booting for the resume, i also note that it can't connect to fb and plymouth is not started (it said so))

Can anyone help me find out what happens, and if all these processes whatever it is, is actually required? or to somehow alleviate the problem a bit?


Steps to Reproduce:
1. install a mageia2 KDE x86_64
2. suspend-to-disk
3. resume by powering up

Comment 1 Samuel Verschelde 2013-09-05 14:49:37 CEST

Hi AL13N. Is the problem still present in Mageia 3 and/or cauldron?

I really don't know how to study this problem nor who could help, but before even trying maybe you'll tell me "forget it, it works in mga3 and I don't care anymore about mga3" :)

Keywords: (none) => NEEDINFO
CC: (none) => stormi

Comment 2 AL13N 2013-09-05 17:01:08 CEST

i haven't tested this in mga3/cauldron.

that laptop isn't migrated to mga3 yet :-S

Comment 3 Manuel Hiebel 2013-10-22 12:10:52 CEST

This message is a reminder that Mageia 2 is nearing its end of life.
Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life.  If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete.

-- 
The Mageia Bugsquad

Comment 4 Manuel Hiebel 2013-11-23 16:14:13 CET

Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no
longer maintained, which means that it will not receive any further security or
bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => OLD