Bug 10027 - Slower boot times in Mageia 3 compared to version 1 and 2
Summary: Slower boot times in Mageia 3 compared to version 1 and 2
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-08 19:32 CEST by Philippe Leblanc
Modified: 2013-05-10 22:40 CEST (History)
0 users

See Also:
Source RPM: systemd-195-22.mga3.src.rpm,dkms-2.0.19-30.mga3.src.rpm
CVE:
Status comment:

Attachments
Bootchart for dm1z on MGA3RC (903.64 KB, image/png)
2013-05-08 19:33 CEST, Philippe Leblanc 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Philippe Leblanc 2013-05-08 19:32:45 CEST 
Description of problem:
The move to systemd was supposed to improve boot times with it's more modern design. However, I'm seeing slow boot times on my system with one boot clocked at 79 seconds from the time I press enter in GRUB to gdm being loaded. That number looks high to me. I installed bootchart and have a chart showing data for one boot. I'm not sure how to read this correctly, but looks like dkms is taking a very long time to run. My system is a bit modest (running an AMD E2-1800 apu) but I'd expect boot times to be closer to 45 seconds or so on such a system.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.


Reproducible: 

Steps to Reproduce:
Comment 1 Philippe Leblanc 2013-05-08 19:33:54 CEST 
Created attachment 3902 [details]
Bootchart for dm1z on MGA3RC
Comment 2 Philippe Leblanc 2013-05-10 22:40:29 CEST 
Well I figured out how to improve my boot times. I had about 12 kernels installed which I assume was the cause of dkms spening a lot of time at boot. I unstalled all but the most recent kernels and shaved my boot time to a reasonable 52 seconds. It's not speedy, but it's closer to what I expect this system should be doing. Closing.

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.