Bug 1398893
Summary: | Kernel panic: init general protection ip | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Christian Kujau <redhat> | ||||||||||
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||||||||
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
Severity: | unspecified | Docs Contact: | |||||||||||
Priority: | unspecified | ||||||||||||
Version: | 25 | CC: | cz172638, gansalmon, ichavero, itamar, jonathan, kernel-maint, labbott, madhu.chinakonda, mchehab, redhat | ||||||||||
Target Milestone: | --- | Flags: | jforbes:
needinfo?
|
||||||||||
Target Release: | --- | ||||||||||||
Hardware: | i686 | ||||||||||||
OS: | Linux | ||||||||||||
Whiteboard: | |||||||||||||
Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||||
Doc Text: | Story Points: | --- | |||||||||||
Clone Of: | Environment: | ||||||||||||
Last Closed: | 2017-04-28 17:15:42 UTC | Type: | Bug | ||||||||||
Regression: | --- | Mount Type: | --- | ||||||||||
Documentation: | --- | CRM: | |||||||||||
Verified Versions: | Category: | --- | |||||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
Embargoed: | |||||||||||||
Attachments: |
|
Description
Christian Kujau
2016-11-27 05:52:33 UTC
Created attachment 1224737 [details]
dmesg
This isn't a kernel error per se but most likely a problem with the initrd. Can you share the output of lsinitrd? Created attachment 1226621 [details]
lsinitrd initramfs-4.8.10-300.fc25.i686+PAE.img
Created attachment 1226622 [details]
lsinitrd initramfs-4.8.8-200.fc24.i686+PAE.img
I've attached two "lsinitrd" outputs to this bug, as they were too big to paste. I uninstalled the FC25 kernels and re-installed kernel-PAE-4.8.10-300.fc25.i686, so it would re-generate the initrd, but booting still fails with the same message. kernel-PAE-core-4.8.8-200.fc24.i686 still works. $ sha1sum /boot/vmlinuz-4.8.* 516cc4f4c3f0d483273ef6f5e9a163d66c15297c /boot/vmlinuz-4.8.10-300.fc25.i686+PAE fb3283200a04d21b4b9f0dde075d7b5569b37f35 /boot/vmlinuz-4.8.8-200.fc24.i686+PAE Again, this is all in a VirtualBox 5.0.30 virtual machine and since nobody else seems to complain, this may or may not be related to that fact. *********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 25 kernel bugs. Fedora 25 has now been rebased to 4.9.3-200.fc25. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 26, and are still experiencing this issue, please change the version to Fedora 26. If you experience different issues, please open a new bug report for those. Upgrading to 4.9.3-200.fc25 did not help, same error. The only bootable kernel remains 4.8.8-200 on this system. *********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 25 kernel bugs. Fedora 25 has now been rebased to 4.10.9-200.fc25. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 26, and are still experiencing this issue, please change the version to Fedora 26. If you experience different issues, please open a new bug report for those. *********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously. |