View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0000752 | channel: kernel/el7 | kernel-ml | public | 2017-07-04 09:25 | 2017-07-04 10:09 |
Reporter | NotoriousPyro | Assigned To | burakkucat | ||
Priority | normal | Severity | major | Reproducibility | always |
Status | resolved | Resolution | fixed | ||
Summary | 0000752: Kernel panic after update from 4.11.3-1.el7.elrepo.x86_64 to 4.11.8-1.el7.elrepo.x86_64 or higher | ||||
Description | Haven't tried any other versions other than 4.11.8-1 onwards. The last working version, then I know of is 4.11.3-1.el7.elrepo.x86_64. My machine is a QNAP TS-559 Pro+. This machine is not really standard configuration and often doesn't work with many distros without some work. Debian doesn't work by default, the only one I found does is CentOS 7 (luckily my favourite). Anyway, after update the machine no longer booted and upon inspection on boot through the VGA port revealed the system was halting on a kernel panic. This did not happen when I selected the older kernel. I tried updating fstab to use only the UUIDs of the partitions instead and this also did not boot but the older kernel worked fine. I tried the very latest, 4.12.0-1.el7.elrpo.x86_64 and this also suffers from this problem. | ||||
Tags | No tags attached. | ||||
Attached Files | |||||
|
Actually this may be because there's no initramfs for this kernel version. I'm starting to feel like an idiot. |
|
Not your fault at all. This problem occurs from time to time for no obvious reasons. Reinstalling the kernel usually solves it. |
|
To give you some idea: https://bugs.centos.org/view.php?id=6310 |
|
It was that initramfs hadn't been generated and yes, as you say there was no initrd16 line (because of the lack of the initramfs file). I fixed it like so: yum install kernel-ml-devel dracut -f initramfs-4.12.0-1.el7.elrepo.x86_64.img 4.12.0-1.el7.elrepo.x86_64 Then I ran my grub2-update.sh script (which updates grub for elrepo): #!/usr/bin/env bash grub2-set-default 0 if [ -f /etc/grub2-efi.conf ]; then grub2-mkconfig -o /etc/grub2-efi.cfg else grub2-mkconfig -o /etc/grub2.cfg fi Rebooted and all OK! :) |
|
Yes, that is a more "sophisticated" way to fix the issue. :) Now closing as 'resolved'. |
Date Modified | Username | Field | Change |
---|---|---|---|
2017-07-04 09:25 | NotoriousPyro | New Issue | |
2017-07-04 09:25 | NotoriousPyro | Status | new => assigned |
2017-07-04 09:25 | NotoriousPyro | Assigned To | => burakkucat |
2017-07-04 09:25 | NotoriousPyro | File Added: 20170704_161420.jpg | |
2017-07-04 09:30 | NotoriousPyro | Note Added: 0005301 | |
2017-07-04 09:32 | toracat | Note Added: 0005302 | |
2017-07-04 09:35 | toracat | Note Added: 0005303 | |
2017-07-04 09:57 | NotoriousPyro | Note Added: 0005304 | |
2017-07-04 10:09 | toracat | Note Added: 0005305 | |
2017-07-04 10:09 | toracat | Status | assigned => resolved |
2017-07-04 10:09 | toracat | Resolution | open => fixed |