Bug 824148
Summary: | Install kernel panics on boot. Oops in pcie_aspm_init_link_state | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Eric Hopper <eric-bugs2> | ||||
Component: | kernel | Assignee: | John Feeney <jfeeney> | ||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 17 | CC: | dennis, 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: | 2012-07-10 19:00:06 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
Eric Hopper
2012-05-22 20:11:10 UTC
Can you attach a screenshot? (digicam/phone shot is fine, as long as the text is legible.) Created attachment 586194 [details]
A screen capture of the kernel panic
This might be a bit larger than you'd like. But the quality is definitely high enough to read. Ignore the white splotchiness, I have a really bad monitor.
Also, RC3 doesn't have this problem. I just tried it. Beta RC3 or final RC3? Well, that's a good question. I found it here: http://dl.fedoraproject.org/pub/alt/stage/17.RC3/Fedora/x86_64/iso/Fedora-17-x86_64-DVD.iso I suspect it's the final RC3. Did this wind up getting fixed in F17 final then? I didn't check. But I strongly suspect so. OTOH, I suspect it was also fixed 'by accident'. This is serious enough it would be nice to know a root cause. Though, of course, there are so many different kinds of motherboards out there that are broken in their own special ways that I don't really know how useful a root cause would actually be. While I agree knowing root cause would be nice, we just don't have time to dig into something that is fixed already. Unfortunate, but true. I'll close this bug out for now. If this is seen again, we can reopen or report a new bug. I will try to remember to double check with the release version when I get back to the computer I had this issue with. |