| Summary: | 4.4 kernel does not discover LVDS when docked | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Michael K Johnson <mcdanlj> |
| Component: | xorg-x11-drv-intel | Assignee: | Adam Jackson <ajax> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 23 | CC: | ajax, ali+rhbugzilla, asmundo, cben, gansalmon, itamar, jan.public, jonathan, kernel-maint, labbott, leho, madhu.chinakonda, marcel, martin.bozic, mchehab, mrhodes, ncross, redhat, sdodson, xgl-maint |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-12-20 19:38:09 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: | |
|
Description
Michael K Johnson
2016-03-25 09:55:38 UTC
I don't know whether it matters whether I boot docked. Every time this happened, the system has been in the dock when I booted. I don't yet know what happens if I boot undocked and then dock. If that is important to diagnosing the problem, I can experiment. I just experienced a similar symptom with 4.3.3-303.fc23.x86_64 after many successful undock/dock cycles: [388642.070874] thinkpad_acpi: docked into hotplug port replicator [388642.158475] [drm:intel_uncore_check_errors [i915]] *ERROR* Unclaimed register before interrupt [388642.158502] [drm:intel_uncore_check_errors [i915]] *ERROR* Unclaimed register before interrupt [388642.160052] [drm:intel_uncore_check_errors [i915]] *ERROR* Unclaimed register before interrupt [388642.844876] [drm:intel_dp_start_link_train [i915]] *ERROR* too many voltage retries, give up With 4.4 kernels, it seems never to work; with 4.3, I've seen one instance of failure now, though once it fails it seems to be a permanent case. A sleep/wakeup cycle does not sufficiently reset it to work again. I am currently running 4.4.8-300.fc23.x86_64 and it is not exhibiting the problem. I booted docked and have since had several cycles of docking and undocking, as well as software-initiated and lid-close-initiated suspend: $ dmesg | grep 'ThinkPad Dock' [ 1.717658] usb 4-5: Product: Lenovo ThinkPad Dock [ 1.919875] usb 3-9: Product: Lenovo ThinkPad Dock [ 2.407340] usb 3-9.4: Product: Lenovo ThinkPad Dock [ 3049.452626] usb 3-9: Product: Lenovo ThinkPad Dock [ 3049.822189] usb 3-9.4: Product: Lenovo ThinkPad Dock [ 7298.907517] usb 4-5: Product: Lenovo ThinkPad Dock [52911.311570] usb 4-5: Product: Lenovo ThinkPad Dock [52911.605273] usb 3-9: Product: Lenovo ThinkPad Dock [52911.976259] usb 3-9.4: Product: Lenovo ThinkPad Dock Since 4.3 has since failed occasionally with this pattern and now a newer 4.4 is at least in one case not reproduced the problem, I can't call it reliably reproducible any more. I also updated the entire system since the problem started, so the improvement with the new kernel could be due to other updates. However, it hasn't been fixed either, since it just recurred after one more suspend-resume cycle from that same instance of 4.4.8-300.fc23.x86_64 I'll reboot it undocked now. 4.4.8-300.fc23.x86_64 reproduced the problem after quite a few cycles over eight days of uptime, initially booted undocked, and six docking events. This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 '23'. 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 23 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 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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. |