| Summary: | kernel panic when booting up with error "Unable to load SKernel panic - not syncing: Attempted to kill init! " | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Gris Ge <fge> |
| Component: | selinux-policy | Assignee: | Miroslav Grepl <mgrepl> |
| Status: | CLOSED WONTFIX | QA Contact: | BaseOS QE Security Team <qe-baseos-security> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 5.7 | CC: | bdonahue, dwalsh, eparis, mmalik |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-05-16 12:23:01 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Gris Ge
2011-06-09 07:37:04 UTC
This would only happen if the /etc/selinux/targeted/policy/policy.X file on disk was corrupted.... If we don't have a way to reproduce that corruption I'm no sure what we can do to find how it happened.... Eric, Thanks for the point out, I will try more times for installation and hopefully we can find out the trigger. Barry, Did you ever got this kind of error on storageqe-05 and -06? I haven't been able to get storageqe-06 but storageqe-05 failed on first boot with snap-3. I'm still investigating that. This request was evaluated by Red Hat Product Management for inclusion in Red Hat Enterprise Linux 5.7 and Red Hat does not plan to fix this issue the currently developed update. Contact your manager or support representative in case you need to escalate this bug. I hit it problem again. https://beaker.engineering.redhat.com/jobs/100527 Any info you need for troubleshooting? Chris is the machine still available. We need to look at the policy file to see if it is corrupt. This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux release for currently deployed products. This request is not yet committed for inclusion in a release. Daniel, I have loaned storageqe-06 to you in beaker. As it said, it's rare condition, hopefully you could trigger the problem. Let me know if you need any help. Gris since I don't use beaker, what does this mean, can you send me mail to tell me how to access the box. Sorry for the late reply. Email sent out. Let me know if you need more assistance. Please use "needinfo" of Bugzilla for getting quick reply from me. Thanks for understanding. Do we have a reproducer here? I'm assuming the broken box is not still loaned in beaker? I am leaning towards moving this to wontfix... This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux release for currently deployed products. This request is not yet committed for inclusion in a release. Could you please set devel_ack/condnack for 5.10 or postpone/close this bugzilla? Erratas should be filed by May 21st, so development phase is nearing its exit. Closing as WONTFIX (the comment #15). |