| Summary: | Kernel panic on boot | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Horst H. von Brand <vonbrand> | ||||||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||||||
| Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | high | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | rawhide | CC: | gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda | ||||||||
| 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: | 2011-11-02 16:01:00 UTC | Type: | --- | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Attachments: |
|
||||||||||
Do you have a backtrace? Created attachment 530106 [details]
/var/log/messages, but for 3.1.0-0.rc9.git0.0
As the kernel crashed before the splashscreen, no trace remains.
I tried to reboot it several times, as the firmware on the motherboard is buggy and prone to hang (sorry, old machine; can't upgrade).
First I tried to reboot remotely with 3.1.0-0.rc10.git0.1, and the machine didn't come up. When I physically got to the machine, the screen was black. I reset it, and tried again with 3.1.0-0.rc10.git0.1, panic. Then I tried 3.1.0-0.rc9.git0.3, again panic. 3.1.0-0.rc9.git0.0 worked, but shows a backtrace.
Created attachment 530481 [details]
Backtrace
Took a photograph of the screen and copied it by hand, checked accuracy comparing a printout of the text with the photograps.
Now it worked (after finding out that /boot/grub2/grub2.cfg was empty, and recreating by "grub2-mkconfig -o /boot/grub2/grub.cfg", then updated to kernel-3.2.0-0.rc0.git2.0.fc17.x86_64. Flawless boot. It seems it got snagged by grub --> grub2 transition. Sorry for the noise. |
Created attachment 529941 [details] /proc/cpuinfo for the affected machine Description of problem: The system panics on boot with kernel-3.1.0-0.rc9.git0.3.fc17.x86_64 kernel-3.1.0-0.rc10.git0.1.fc17.x86_64 kernel-3.1.0-0.rc9.git0.0.fc17.x86_64 is fine. Version-Release number of selected component (if applicable): How reproducible: Tried some 3 times with 3.1.0-0.rc10 and once with 3.1.0-0.rc9.git0.3 Steps to Reproduce: 1. 2. 3. Actual results: Panic Expected results: Additional info: