| Summary: | Kernel trace dump on bootup | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | greg.hellings | ||||||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | high | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 17 | CC: | gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, sgruszka | ||||||||
| 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-04-04 11:10:08 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: |
|
||||||||||
|
Description
greg.hellings
2012-03-19 21:51:48 UTC
we need the whole trace. Any suggestions how to accomplish that short of copying from one screen to the other by hand as the above partial output gives? Would that be logged to /var/log somewhere? take a photo of the trace with a camera ? the kernel kdump feature *should* work in f17, but requires some setup, we're working towards making that easier. Created attachment 572482 [details]
First portion of kernel dump
Created attachment 572483 [details]
Second portion of kernel dump
Created attachment 572484 [details]
Final portion, post dump
I have attached pictures of the dump starting from where the Bug is first detected and continuing down through the point where bootup is stalled. This is after updating to the Beta RC dated March 23. *** This bug has been marked as a duplicate of bug 808603 *** |