Bug 985991
| Summary: | kernels > 3.11.0-0.rc0.git3.1.fc20.x86_64 do not boot properly | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Nicolas Mailhot <nicolas.mailhot> | ||||||
| Component: | NetworkManager | Assignee: | Dan Williams <dcbw> | ||||||
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | rawhide | CC: | collura, dcbw, gansalmon, itamar, jklimes, jonathan, kernel-maint, madhu.chinakonda, mcsontos, nicolas.mailhot, yaneti | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2013-08-18 07:37:30 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
Nicolas Mailhot
2013-07-18 17:13:28 UTC
Created attachment 775384 [details]
working and failing boot logs
Most things radeon would not work properly until linux-firmware is updated with the latest blobs from amd. I'd wait for that and retest the newer rc kernels then. And now X & console finally work, but networking is still hosed Created attachment 778986 [details]
new failing boot logs
Have seen "something-like-that" as well. I laboured a while with network to realize it is kernel related. One symptom of broken network was that IPv6 though disabled in ifcfg-eth0 (and later in sysctl too) was used for connections. Booting into older kernel and updating to 3.11.0-0.rc2.git3.1.fc20.x86_64 (with disabled IPv6) worked for me :-) Nicolas, if the problem is affected by the kernel, it is most probably the kernel issue, not NM. However, I am not able to open the logs. Could include /var/log/messsages and dmesg output if you still experience problems? sorry, I was away some time Today (after the mass rebuild and a few kernel update) things seem to work again (and the attached logs open fine in fire-roller, maybe you're missing and xz handler?) Thanks for your time |