Bug 1155168
| Summary: | Fedora 21 alpha halts on install. Ubuntu 14 works running the 3.11 kernel | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | dannyking20022001 | ||||||||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||||||||
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||
| Priority: | unspecified | ||||||||||||
| Version: | 21 | CC: | dannyking20022001, gansalmon, g.kaviyarasu, itamar, jonathan, kernel-maint, madhu.chinakonda, mchehab, vanmeeuwen+fedora | ||||||||||
| Target Milestone: | --- | Flags: | jforbes:
needinfo?
|
||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | Unspecified | ||||||||||||
| OS: | Unspecified | ||||||||||||
| Whiteboard: | |||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2015-02-24 16:14:16 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
dannyking20022001
2014-10-21 13:34:34 UTC
Please attach the log files from the install, available in /tmp at the time of the crash, to this bug as individual, text/plain attachments. Alternatively, you can use the "Report Bug" button from the crash dialog to create a bug with the necessary attachments. Sorry I don't have the ability to dump the logs. I can't get to a shell. I attached a screenshot for a better understanding. Created attachment 948974 [details]
error
Is booting stuck at this point? Can you get to a console by hitting Ctrl-Alt-F2? Booting is stuck. I can not get a console by hitting ctrl-alt-f2. OK. Based on the screenshot it appears to be stuck somewhere in the kernel initialization. Reassigning. Even when I try and boot live it does that same thing. (In reply to dannyking20022001 from comment #3) > Created attachment 948974 [details] > error There's no actual error shown in this attachment. Just normal boot up messages. Does this machine have a serial console? yes it does Could you edit the command line and add console=ttyS0,<baud rate> and capture the boot output at whatever baud you specify? Maybe we will see something further that way. Ya I will give it a try and report back. Created attachment 949058 [details]
error with serial connection
Created attachment 949059 [details]
log file of serial boot
I have added the log file from the serial console. Also a picture that shows where the screen stops booting with the console command being added to boot. Could you try one of the beta TC composes instead of the Alpha? That has a 3.17 based kernel on it and it would be better to debug off of what is going to be the base kernel in the final release anyway. Also, could you attach the output of dmesg after a boot that does work? Could you link me to a beta TC release ? Also I will load a dmesg log when I can get the system up. http://alt.fedoraproject.org/pub/alt/stage/21_Beta_TC4/ has the latest, though I suspect a TC5 will be coming in the next day or two. System still will not boot. I have attached a new log of me using beta tc4 Created attachment 949122 [details]
tc4 log
any updates on this ? Still waiting to hear something? *********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 21 kernel bugs. Fedora 21 has now been rebased to 3.18.3-201.fc21. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those. *********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in over 3 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously. |