Description of problem: from the change of kernels (4.1.15-(server,desktop)-1.mga5 to 4.4.13-(server, desktop)-1.mga5), the boot process runs much more slowly my stuff (old): mobo gigabyte X58A cpu: corei7-960 ram: 24 Go DDR 3 gskill graphic card: nvidia gtx 9800+ the os mageia5-x86_64 is installed on lvm2 which lies on mdadm raid level5 (/dev/sd[a-d]5) Version-Release number of selected component (if applicable): kernel-server,desktop-4.4.13-1.mga5-1-1.mga5 How reproducible:make last mageia update Steps to Reproduce: 1. 2. 3.
I suspect you're using the proprietary driver and I think that on the first boot with the new kernel, the driver is compiled for this new kernel
CC: (none) => thierry.vignaud, tmb
(In reply to Thierry Vignaud from comment #1) > I suspect you're using the proprietary driver and I think that on the first > boot with the new kernel, the driver is compiled for this new kernel Sorry, it's not the case: 1) I don't use any proprietary driver, only those provided by the mageia rpm repositories 2) it happens at EVERY boot, not only the first
(In reply to peter lawford from comment #2) > 1) I don't use any proprietary driver, only those provided by the mageia rpm > repositories Mageia provides proprietary drivers in the Nonfree repository. Check if `rpm -qa | grep nvidia` returns the nvidia-current package. > 2) it happens at EVERY boot, not only the first Then it's likely another issue than what Thierry mentioned.
Summary: boot slow => Slow boot since upgrade from kernel 4.1.15 to kernel 4.4.13
Can you _attach_ (not paste) the output of the "systemd-analyze blame" command?
Keywords: (none) => NEEDINFO
Created attachment 8003 [details] systemd-analyze blame command's return file
(In reply to Rémi Verschelde from comment #3) > (In reply to peter lawford from comment #2) > > 1) I don't use any proprietary driver, only those provided by the mageia rpm > > repositories > > Mageia provides proprietary drivers in the Nonfree repository. Check if `rpm > -qa | grep nvidia` returns the nvidia-current package. > > > 2) it happens at EVERY boot, not only the first > > Then it's likely another issue than what Thierry mentioned. see by yourself: [petelaw@mageia4_64 ~]$ rpm -qa | grep nvidia nvidia-current-doc-html-352.79-3.mga5.nonfree nvidia-current-kernel-4.1.15-server-2.mga5-346.96-5.mga5.nonfree x11-driver-video-nvidia-current-352.79-3.mga5.nonfree nvidia-current-kernel-desktop-latest-352.79-10.mga5.nonfree nvidia-current-kernel-server-latest-352.79-10.mga5.nonfree dkms-nvidia-current-352.79-3.mga5.nonfree nvidia-current-kernel-4.1.15-desktop-2.mga5-346.96-5.mga5.nonfree nvidia-cuda-toolkit-6.5.14-6.1.mga5.nonfree
Can you attach the blame log for the original kernel too? What's the version reported by "rpm -q dkms-minimal" ?
(In reply to Thierry Vignaud from comment #7) > Can you attach the blame log for the original kernel too? > What's the version reported by "rpm -q dkms-minimal" ? dkms-minimal-2.0.19-34.mga5 furthermore, I don't know how to obtain the blame log; sorry
Just boot on the older kernel and run the "systemd-analyze blame" command...
(In reply to Thierry Vignaud from comment #9) > Just boot on the older kernel and run the "systemd-analyze blame" command... OK, but for that I have to reboot on a second mageia5_64 system on the same machine, I have not yet updated to the new kernel, and which is quite similar to the first one. I can't make it immediateley, since I am very busy. please, wait one hour or two thank you for your patience sincerly
You already removed the old kernel? Else you can choose another kernel from the boot menu.
Created attachment 8004 [details] systemd_analyze_blame_4.1.15-server-2.mga5.txt
(In reply to Thierry Vignaud from comment #11) > You already removed the old kernel? > Else you can choose another kernel from the boot menu. OK here is attached the file systemd_analyze_blame_4.1.15-server-2.mga5.txt since I have rebooted on the old kernel: [petelaw@mageia4_64 ~]$ uname -a Linux mageia4_64 4.1.15-server-2.mga5 #1 SMP Wed Jan 20 17:37:41 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
This is not from the same system: in the last logs, there's no trace of the sendmail service that was slow in the first logs
(In reply to Thierry Vignaud from comment #14) > This is not from the same system: in the last logs, there's no trace of the > sendmail service that was slow in the first logs It's EXACTLY the same system, it's why I don't understand too what happens between the two kernels
(In reply to peter lawford from comment #15) > (In reply to Thierry Vignaud from comment #14) > > This is not from the same system: in the last logs, there's no trace of the > > sendmail service that was slow in the first logs > > It's EXACTLY the same system, it's why I don't understand too what happens > between the two kernels my two systems are, for historical reasons, called mga4-64 and mga5-64; both are mageia5-x86_64, and are quite similar; but the logs I have posted to you are both from mga4-64 system
Created attachment 8013 [details] kernel 4.1.15 for mga5-64
Created attachment 8014 [details] kernel 4.4.13 for mga5-64
here attached file containing reports of the command "systemd-analyze blame" for respectively kernels 4.1.15 and 4.4.13 on my second system mga5-64
(In reply to Thierry Vignaud from comment #14) > This is not from the same system: in the last logs, there's no trace of the > sendmail service that was slow in the first logs please see comments #17, 18 & 19 sincerely
Could you attach (for both kernels) the journalctl logs? Just run "journalctl -b>/tmp/journal-$(uname -r).txt" as root
Created attachment 8017 [details] journal-4.1.15
Created attachment 8018 [details] journal-4.4.13
(In reply to Thierry Vignaud from comment #21) > Could you attach (for both kernels) the journalctl logs? > Just run "journalctl -b>/tmp/journal-$(uname -r).txt" as root here the attached files
Keywords: NEEDINFO => (none)CC: (none) => marja11Assignee: bugsquad => tmbSource RPM: kernel-server-4.4.13-1.mga5-1-1.mga5, kernel-desktop-4.4.13-1.mga5-1-1.mga5 => kernel-4.4.13-1.mga5-1-1.mga5
Mass-reassigning all bugs with "kernel" in the Source RPM field that are assigned to tmb, to the kernel packagers group, because tmb is currently MIA.
Assignee: tmb => kernel
Hi Peter, Thank you for having taken the needed time to report this issue, and even more thanks for all the effort you've taken to supply good information and logs! Did this bug get fixed? If so, please change its status to RESOLVED - FIXED If it didn't, then we regret that we weren't able to fix it in Mageia 5. Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/ It only continued to get important security updates since then, because we are waiting for a big Plasma5 update in Mageia 6, that'll fix many of the Mageia 5 => 6 upgrade issues. If you haven't seen that this bug got fixed, then please check whether this bug still exists in Mageia 6. If it does, then please change the Version (near the top, at the left) to "6". If you know it exists in Cauldron, then change Version to Cauldron. If you see it in both Cauldron and Mageia 6, then please set Version to Cauldron and add MGA6TOO on the Whiteboard. Thanks, Marja
(In reply to Marja Van Waes from comment #26) > Hi Peter, > > Thank you for having taken the needed time to report this issue, and even > more thanks for all the effort you've taken to supply good information and > logs! > > Did this bug get fixed? If so, please change its status to RESOLVED - FIXED > > If it didn't, then we regret that we weren't able to fix it in Mageia 5. > Mageia 5 has officially reached its End of Life on December 31st, 2017 > https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/ > It only continued to get important security updates since then, because we > are waiting for a big Plasma5 update in Mageia 6, that'll fix many of the > Mageia 5 => 6 upgrade issues. > > If you haven't seen that this bug got fixed, then please check whether this > bug still exists in Mageia 6. If it does, then please change the Version > (near the top, at the left) to "6". If you know it exists in Cauldron, then > change Version to Cauldron. If you see it in both Cauldron and Mageia 6, > then please set Version to Cauldron and add MGA6TOO on the Whiteboard. > > Thanks, > Marja bug fixed for mageia5 & 6
(In reply to peter lawford from comment #27) > > bug fixed for mageia5 & 6 Thanks for telling us :-)
Status: NEW => RESOLVEDResolution: (none) => FIXED