Bug 485332
Summary: | Kernel panic-not syncing: Attempted to kill init x86-64 Live CD not booting F11a Asus Gaming Series LT | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | GreeneNY <digital8doug> |
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | rawhide | CC: | dwmw2, esandeen, kernel-maint, quintela, stoffie |
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: | 2009-03-02 02:19:58 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
GreeneNY
2009-02-12 22:20:44 UTC
After successful net install on Asus eee PC 901 initial reboot failed as above. Second reboot with bootparam "selinux=0" did boot normally, however further boot attempts failed. Reinstallation from network with selinux disabled resulted in boot failure. guessing kernel as the component for now; it's not 0xFFFF at least. We'll need a bit more info than that, even a digital picture of the error might help. Hopefully there is something else interesting before "swapper used greatest stack depth 3752 bytes left" Apologies for not replying sooner. I cannot help for now. I have discovered the eLive distro (devel) which has almost perfect support for Eee PC 901, and I would dearly like to explore it a bit further before returning to the issue at hand. 11-Alpha Live boots without problems on the Eee, also on another Asus system (x86_64 AMD), but I have booted 32-bit only. Ok, I'm going to close this then, but please reopen if you get back to it or try another later kernel and still encounter problems. Without the hardware to reproduce, or some more detailed indication of what went wrong, I don't think there's a lot we can do. Thanks, -Eric |