Bug 1466674
Summary: | System crashes after docking | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jiří Vymazal <jvymazal> |
Component: | xorg-x11-drv-intel | Assignee: | Adam Jackson <ajax> |
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 26 | CC: | airlied, ajax, bskeggs, eparis, esandeen, gallen, gansalmon, hdegoede, ichavero, itamar, jan.public, jarodwilson, jforbes, jglisse, jhonce, jonathan, josef, jpaulovi, jscarbor, jwboyer, kernel-maint, labbott, linville, madhu.chinakonda, mchehab, mjg59, nhorman, quintela, steved, xgl-maint |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-05-29 11:25:03 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: |
Description
Jiří Vymazal
2017-06-30 08:37:43 UTC
Same problem on FC26, regardless if I use Wayland or X.org: $ uname -a Linux jpaulovi.usersys.redhat.com 4.11.11-300.fc26.x86_64 #1 SMP Mon Jul 17 16:32:11 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux $ rpm -qa | grep x11-drv xorg-x11-drv-qxl-0.1.5-3.fc26.x86_64 xorg-x11-drv-intel-2.99.917-28.20160929.fc26.x86_64 xorg-x11-drv-vmware-13.2.1-2.fc26.x86_64 xorg-x11-drv-nouveau-1.0.15-1.fc26.x86_64 xorg-x11-drv-evdev-2.10.5-2.fc26.x86_64 xorg-x11-drv-fbdev-0.4.3-26.fc26.x86_64 xorg-x11-drv-ati-7.9.0-1.fc26.x86_64 xorg-x11-drv-wacom-0.34.2-1.fc26.x86_64 xorg-x11-drv-openchrome-0.5.0-3.fc26.x86_64 xorg-x11-drv-libinput-0.25.1-2.fc26.x86_64 xorg-x11-drv-vesa-2.3.2-26.fc26.x86_64 One more update - if I do a reboot even before re-docking it works normally (with multiple monitors as well). It is not good as workaround since full reboot is still required but maybe it can help with debugging/fixing this. I am not sure whether this is correctly targeted against intel driver. I have removed the xorg-x11-drv-intel package entirely, thus forcing system to use modesetting driver included in Xorg server and the result are the same errors in log, though modesetting driver seems to handle them better so it does not crash on every re-dock. Please re-evaluate targeting. Thanks Yes, that was the correct package, please see https://fedoraproject.org/wiki/KernelBugTriage#Video_Subsystem_bugs This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. 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 '26'. 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 26 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 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 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. |