| Summary: | panic | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | GeoffLeach <geoffleach.gl> | ||||||||||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||||||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||
| Severity: | urgent | Docs Contact: | |||||||||||||
| Priority: | unspecified | ||||||||||||||
| Version: | 16 | CC: | gansalmon, geoffleach.gl, 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: | 2012-02-27 15:52:55 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: |
|
||||||||||||||
We're going to need to see the backtrace in order to do anything. Can you boot with the 'rhgb' and 'quiet' options removed from the grub entry for this kernel and see if you get more output? If you can't get it from a file or log on the machine, a digital picture is better than nothing. There was a ton of output on screen, but with the kernel panic, there was no way to capture. I'll retry with 'rhgb' and 'quiet' removed. Is there no way to push the output to a file? (In reply to comment #2) > There was a ton of output on screen, but with the kernel panic, there was no > way to capture. I'll retry with 'rhgb' and 'quiet' removed. Is there no way > to push the output to a file? It really depends on when/where the panic is. From the little information in the bug, it sounds like you can't even login after booting so I really doubt a kernel that broken is going to be able to write to a file on disk. If the machine has a serial console, you could hook that up and set it as the console on the kernel command line. Then you could capture the output on whatever machine you're using to read the console. Serial ports are becoming increasingly rare though. If the output is scrolling off the screen too rapidly to take a digital picture, you might be able to slow it down with 'pause_on_oops=30' on the kernel command line. That will pause it for 30 seconds. Did not reproduce. I'll try again after system rests overnight :-) "Keep your powder dry and the digicam handy!" Created attachment 565686 [details]
abrt oops #1
Created attachment 565687 [details]
abrt oops #2
Created attachment 565688 [details]
abrt oops #3
These abrt logs are better than the digicam -- which was a complete failure! Created attachment 565757 [details]
abrt oops #4
"Cold" start. Re-boot on warm system worked fine.
ok, abrt actually filed these for you, so I'll dupe this bug against that one, as it has all the info there. *** This bug has been marked as a duplicate of bug 797318 *** |
Created attachment 565310 [details] lshw output Description of problem:kernel panic last line: kernel panic: switching back to text mode Version-Release number of selected component (if applicable): kernel-PAE-3.2.7-1.fc16.i686 How reproducible: boot Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: no abrt info provided kernel-PAE-3.2.7-1.fc16.i686 running 3.1.0-7.fc16.i686.PAE running 32-bit fedora on 64-bit system