Bug 1162068
| Summary: | High Xorg cpu usage during F21 beta install prevents installation | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Hedayat Vatankhah <hedayatv> | ||||
| Component: | xorg-x11 | Assignee: | X/OpenGL Maintenance List <xgl-maint> | ||||
| Status: | CLOSED ERRATA | QA Contact: | |||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 21 | CC: | anaconda-maint-list, awilliam, g.kaviyarasu, jonathan, juloml, kparal, mcsontos, mruckman, robatino, vanmeeuwen+fedora, znmeb | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2014-11-24 00:32: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: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 1043129 | ||||||
| Attachments: |
|
||||||
|
Description
Hedayat Vatankhah
2014-11-10 08:19:00 UTC
Oops, this time Anaconda crashed completely when I reached manual partitioning spoke (without applying anything). same backtrace as above produced. As I can't proceed with the installation (I've waited several minutes with no results), I'd propose it as a final blocker. Notice that I've already installed F21 Workstation Alpha, so the bug has been introduced in Beta. (In reply to Hedayat Vatankhah from comment #0) > Description of problem: > Notice: I doubt this is an Anaconda bug Then don't file it against anaconda! Discussed at today's blocker review meeting [1]. We decided to punt this bug. We'd like to have more information before deciding on this bug. Could you provide the following information so we can try to reproduce? CPU, RAM, graphics stack, baremetal or VM? Thanks. [1] http://meetbot.fedoraproject.org/fedora-blocker-review/2014-11-12/ Brief: Baremetal install on Thinkpad X61 Some details: CPU: Intel(R) Core(TM)2 Duo CPU T7100 @ 1.80GHz RAM: 4GB VGA: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller Might this got fixed via bug 1148493 ? It seems very similar. How can I confirm that? I have a working F21 alpha installation (without any updates), so I can update it and see if everything works fine. But does it mean that installation will work fine too? :P If there are any TC builds which contain that xorg package, I can try that. I have seen the same on Thinkpad T61 installing F21Beta via netinst iso. It "hung" when entering root password twice. The third attempt installing and entering root password only after everything else was completed succeeded. Also after installation I am experiencing appalling performance in Gnome (playing video is like a slideshow) which I solved by switching to LXDE which did the trick for me (though fullscreen is still not possible). Unless someone beats me and if I have a chance I will check gnome with updated Xorg and if there is a test-compose available including the package I may try install scenario too. But it is pretty likely a duplicate of the Bug1148493. Hedyat, can you please try this image? https://kojipkgs.fedoraproject.org//work/tasks/5751/8185751/Fedora-Live-Workstation-x86_64-21-20141119.iso It should have the fixed intel driver inside. Discussed in 2014-11-19 blocker review meeting. It is possible that this bug was already resolved. We will wait for more information again. Created attachment 959463 [details]
updates(WRONG).img
I planned to try install with the attached update file but the offended T61 machine is now busy.
The updated xorg-x11-drv-intel should be included in Final TC3 when it arrives. Just tried TC3 which fixed the issue on my T61. Thanks! The update went stable already, so let's close this out. Yes, I tried TC4 and the issue is fixed indeed! :) |