Description of problem: with the new kernels (kernel-desktop,server-4.4.13-1.mga5-1-1.mga5) system may brutally freeze even if no application is running by contrast with bug 18751 no need that any application such firefox was running; hence and contrary to my earlier belief, it seems there is no link between this problem and firefox here attached the return of the command "journalctl --sine 2016-06-26" which shows that the system freezes at about 17:57. when I was back at home at 23:00, the totally system was unusable, and I had to reboot by pressing once again the reset button. furthermore, it provoques the resynchronizing of all mdam raid volumes (raid 5 & 6) to avoid troubles I run from now on only the previous kernel 4.1.15. a further evolution of the kernel-desktop,server-4.4.13-1.mga5-1-1.mga5 appears to me as being urgent Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3.
Created attachment 8071 [details] journalctl 2016-06-26 since 17:27:54
CC: (none) => marja11Assignee: bugsquad => tmb
Component: New RPM package request => RPM Packages
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! 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 #3) > Hi Peter, > > Thank you for having taken the needed time to report this issue! > > 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 this bug is fixed since kernels 4.4.114 (mageia5) and 4.14.30 (mageia6) regards
(In reply to peter lawford from comment #4) > > this bug is fixed since kernels 4.4.114 (mageia5) and 4.14.30 (mageia6) > regards Thanks for the feedback :-)
Status: NEW => RESOLVEDResolution: (none) => FIXED