Bug 1253814
| Summary: | Latest kernel update causes kernel panic | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Diederik van Lierop <mail> | ||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 22 | CC: | gansalmon, itamar, jonathan, kernel-maint, labbott, madhu.chinakonda, mchehab | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2015-08-16 12:23:13 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: |
|
||||||
This panic indicates it can't find the root file system. Can you try the 4.1.5 update in testing in bohdi and see if that works for you? Yes, 4.1.5 works again! Thanks for looking into this. Thanks. Typically that means that the initramfs wasn't created or loaded for some reason. The new update likely didn't fix a kernel bug, but instead had the initramfs created properly. |
Created attachment 1063160 [details] Cellphone picture of call trace Description of problem: Just updated to the latest kernel version 4.1.4-200.fc22.x86_64, but this panics on boot after only 1.6 seconds. Can't find any log files using journalctl, maybe because it's too early in the boot process? Version-Release number of selected component (if applicable): 4.1.4-200.fc22.x86_64 How reproducible: Just booting my system and selecting the most recently installed kernel version causes this panic. When using the previously installed version (4.1.3-201) it works just fine Steps to Reproduce: 1. 2. 3. Additional info: Shuttle barebone, SZ77 Intel® Core™ i5-3570K CPU @ 3.40GHz × 4 Gallium 0.4 on AMD OLAND I took a picture of the screen, please see the attached file Just let me know what more information you would need. Also, where do I find the relevant logs of the panic and the call trace? "journalctl -k -l -b -1" doesn't show anything useful.