2017-12-12 10:11 UTC

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0012598CentOS-7kernelpublic2017-06-15 13:00
Reportererik.wramner 
PriorityhighSeveritycrashReproducibilityalways
StatusnewResolutionopen 
Platformx86_64OSCentOS 7OS Version3.10.0-514.2.2
Product Version7.3.1611 
Target VersionFixed in Version 
Summary0012598: Kernel panic not syncing with 3.10.0-514 at boot, works with 327
DescriptionAfter upgrading to 3.10.0-514.2.2 the system consistently hangs when rebooted just after the login prompt has been displayed. It crashes in different services, but with the same message:

Comm: (some process) Not tainted 3.10.0-514.2.2.el7.x_86_64 #1.
...
Kernel panic - not syncing: Fatal exception

I'll upload two screenshots with more data. Reverting to the previous kernel (327) works. This is reproducible, it happens every time with the new kernel and never with the old kernel.

I have plenty of free space in /boot (70% free) and I have uninstalled and reinstalled the kernel several times.
Steps To ReproduceOn my system:
1) Upgrade from kernel 327 to 514 with yum.
2) Reboot, wait for login prompt.
3) Kernel panic.
Additional InformationUsing encrypted disks with an mdadm mirror for /root and /boot.
This is a production system, so I can't afford too much downtime for diagnostics. I have not been able to reproduce the issue elsewhere, but then I have no other system with the same hardware and configuration.
Tags"ONBOOT"
abrt_hash
URL
Attached Files

-Relationships
+Relationships

-Notes

~0028447

petrilak.m (reporter)

I have same issue on ProLiant DL380 G7. I don't use encrypted disks. Only MBR+LVM+xfs.
kernel 3.10.0-514.2.2 and 3.10.0-514.6.1 cause kernel panic too.

~0028502

ray.zuniga@mosaic451.com (reporter)

Similar issues here centos 7.2 Kernel 3.10.0-514.6.1 causes kernel panic and will not boot but the previous kernel does works which is 3.10.0-327. Although my kernel panic states unable to mount FS issue

~0028522

gerwim (reporter)

Same issue here. Fixed it by running "yum reinstall kernel-3.10.0-514*".

~0029494

v_bobik (reporter)

Similar issues here
Lenovo System x3250 M5
Centos 7.1 Kernel 3.10.0-229.el7.x86_64
Driver ServeRAID C100 for RHEL 7.1 (ok) (there is no newer driver for RHEL 7.2 or 7.3)
Install & boot (ok)
yum update -> (ok)

and stuck at boot Kernel 3.10.0-514.21.1.el7.x86_64
and showed this: "A start job is running for dev-mapper-centos7\x2droot.device"

After that:
reset
choose the Kernel 3.10.0-229.el7.x86_64 and boot (ok)
changed grub2 default boot to Kernel 3.10.0-229.el7.x86_64
+Notes

-Issue History
Date Modified Username Field Change
2017-01-08 07:57 erik.wramner New Issue
2017-01-08 07:57 erik.wramner File Added: kernel-panic-1.jpg
2017-01-08 07:57 erik.wramner Tag Attached: "ONBOOT"
2017-01-08 07:58 erik.wramner File Added: kernel-panic-2.jpg
2017-01-22 16:11 petrilak.m Note Added: 0028447
2017-01-28 14:55 ray.zuniga@mosaic451.com Note Added: 0028502
2017-02-02 14:20 gerwim Note Added: 0028522
2017-06-15 13:00 v_bobik File Added: centos 7 dracut-initqueue.jpg
2017-06-15 13:00 v_bobik Note Added: 0029494
+Issue History