Bug 19624 - system refuses to boot under new kernel and is slow under previou kernels
Summary: system refuses to boot under new kernel and is slow under previou kernels
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 5
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Kernel and Drivers maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-10-19 17:14 CEST by Alan Secker
Modified: 2018-05-03 07:37 CEST (History)
1 user (show)

See Also:
Source RPM: Update incorporating kernel 4.4.22
CVE:
Status comment:


Attachments

Description Alan Secker 2016-10-19 17:14:41 CEST
Yesterday I ran the latest Mageia 5 updates, rebooted into the new kernel
 4.4.22, recompiled my tv card drivers to match and was satisfied with the
 result.

 This morning (19/10/2016) it will not boot.

 I fsck'd the partitions from a live CD and found no errors.

 I then rebooted into the next earlier kernel 4.4.16 which hung for some time
 but it eventually came up.

 A check on boot.log showed up two hiccups:

 (1 of 2) A start job is running for udev Wait for Complete Device
 Initialization (12s / 3min)

 (2 of 2) A start job is running for Load legacy module configuration (13s /
 no limit)

 These repeated many times.

 I ran the same update on another Mag 5 machine and it is running perfectly.
Comment 1 Marja Van Waes 2016-10-19 22:26:43 CEST
Please check the time and try to boot with the new kernel until you're sure it fails again and then boot with the old kernel.

Then please run, as root:

  journalctl -ab > old.txt

and 

  journalctl -ab -1 > new.txt


If new.txt is indeed from the time you booted the new kernel (every line in the file will start with date + time), then please attach _both_ new.txt and old.txt.

If not, then attach only old.txt

CC: (none) => marja11
Assignee: bugsquad => kernel

Comment 2 Marja Van Waes 2018-05-03 07:37:33 CEST
1½ years later, no reply.

Closing as OLD

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


Note You need to log in before you can comment on or make changes to this bug.