Bug 1452697
| Summary: | Xorg lockup when docking | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Robert Story <rs> | ||||||||||
| Component: | xorg-x11-drv-nouveau | Assignee: | Ben Skeggs <bskeggs> | ||||||||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||
| Priority: | unspecified | ||||||||||||
| Version: | 25 | CC: | airlied, ajax, bskeggs, lacombar, rs | ||||||||||
| Target Milestone: | --- | Keywords: | Reopened | ||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | Unspecified | ||||||||||||
| OS: | Unspecified | ||||||||||||
| Whiteboard: | |||||||||||||
| Fixed In Version: | xorg-x11-drv-nouveau-1.0.15-2.fc25 | Doc Type: | If docs needed, set a value | ||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2017-12-12 10:53:06 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
Robert Story
2017-05-19 13:31:34 UTC
Created attachment 1280428 [details]
annotated Xorg
Note: first dock works if you boot/login while undocked. It's docking after undocking (while logged in). Created attachment 1280430 [details]
dnf update that broke docking
dnf log from last update. prior to this update, on kernel 4.10.8-200.fc25.x86_64, both docking and undocking multiple times a day worked great.
xorg-x11-drv-nouveau-1.0.15-2.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2017-0031ce08bf tried 1.0.15-2, same bad behaviour. If you boot the older kernel, do things work as expected? I didn't try it with 1.0.15-2, but did after downgrading to 1.0.13. It didn't help. Something else that got upgraded must factor into it. I just haven't had time to figure out what it might be. (In reply to Robert Story from comment #7) > I didn't try it with 1.0.15-2, but did after downgrading to 1.0.13. It > didn't help. Something else that got upgraded must factor into it. I just > haven't had time to figure out what it might be. Can you try it again with 1.0.15-2? There are multiple factors at play here. I suspect your upgrade from 4.9->4.10 kernel is responsible for the errors in your kernel log at least. xorg-x11-drv-nouveau-1.0.15-2.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-0031ce08bf xorg-x11-drv-nouveau-1.0.15-2.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report. Created attachment 1284529 [details]
latest attempt
Still happening to me. An initial dock/undock works, but the next dock locks up. No stack trace in messages this time, though. Testing done after yum update this morning to all current packages.
[root@titan ~]# rpm -qa xorg-x11-drv-nouveau
xorg-x11-drv-nouveau-1.0.15-2.fc25.x86_64
[root@titan ~]# uname -a
Linux titan.int.futz.org 4.11.3-200.fc25.x86_64 #1 SMP Thu May 25 19:03:07 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. Just happened randomly on an up-to-date Fedora 27. No docking involved, just "normal" desktop use in a dual GPU setup. Mouse responsive, but everything else dead. Killing Xorg "fixed" the issue. some info... /% rpm -qa xorg-x11-drv-nouveau xorg-x11-drv-nouveau-1.0.15-3.fc27.x86_64 ~/% uname -a Linux hanoli 4.14.8-300.fc27.x86_64 #1 SMP Wed Dec 20 19:00:18 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Some relevant information in the dmesg buffer: [271587.979780] nouveau 0000:01:00.0: gr: TRAP ch 2 [007f955000 Xorg[1473]] [271587.979789] nouveau 0000:01:00.0: gr: GPC0/TPC0/TEX: 80000041 [271587.979794] nouveau 0000:01:00.0: gr: GPC0/TPC1/TEX: 80000041 [271587.979797] nouveau 0000:01:00.0: gr: GPC0/TPC2/TEX: 80000041 [271587.979801] nouveau 0000:01:00.0: gr: GPC0/TPC3/TEX: 80000041 [271587.979804] nouveau 0000:01:00.0: gr: GPC0/TPC4/TEX: 80000041 [271587.979814] nouveau 0000:01:00.0: fifo: read fault at 0001af4000 engine 00 [GR] client 07 [GPC0/T1_2] reason 02 [PTE] on channel 2 [007f955000 Xorg[1473]] [271587.979819] nouveau 0000:01:00.0: fifo: channel 2: killed [271587.979821] nouveau 0000:01:00.0: fifo: runlist 0: scheduled for recovery [271587.979824] nouveau 0000:01:00.0: fifo: engine 0: scheduled for recovery [271587.979830] nouveau 0000:01:00.0: fifo: engine 5: scheduled for recovery [271587.979859] nouveau 0000:01:00.0: Xorg[1473]: channel 2 killed! [271638.386491] asynchronous wait on fence nouveau:Xorg[1473]:284f8b timed out [271688.050038] asynchronous wait on fence nouveau:Xorg[1473]:284f90 timed out [271737.201617] asynchronous wait on fence nouveau:Xorg[1473]:284fa2 timed out [271787.377169] asynchronous wait on fence nouveau:Xorg[1473]:284fa6 timed out |