Bug 1180747
| Summary: | [abrt] WARNING: CPU: 0 PID: 1007 at drivers/gpu/drm/drm_dp_mst_topology.c:1242 process_single_tx_qlock+0x4b6/0x540 [drm_kms_helper]() | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Steve Meisner <smeisner> | ||||||
| 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: | 20 | CC: | ajax, gansalmon, itamar, jharriga, jonathan, kernel-maint, madhu.chinakonda, mchehab, redhat, xgl-maint | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Unspecified | ||||||||
| URL: | https://retrace.fedoraproject.org/faf/reports/bthash/56ba3344384b3934a8e12360392812b1c80b28df | ||||||||
| Whiteboard: | abrt_hash:40b42c1ab3773130c5efb9b535b85affdb3e6683 | ||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2015-06-29 23:59:51 UTC | Type: | --- | ||||||
| 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
Steve Meisner
2015-01-09 21:27:42 UTC
Created attachment 978388 [details]
File: dmesg
I have this happening on a Lenovo W540 as well - Fedora 21. As I understand it, the new setup w/ haswell CPUs means that all the video has to be routed through the integrated intel video card, and it's not possible to use the discrete NVidia card like on the W530 model laptop. I blacklisted nouveau, and still get the same kernel panic/oops. Connecting a displayport multistream hub to the mini displayport connector on the side of the laptop crashes X, the display becomes unresponsive. More context: May 07 00:48:07 localhost.localdomain kernel: [drm:drm_dp_send_link_address] link address reply: 3 May 07 00:48:07 localhost.localdomain kernel: [drm:drm_dp_send_link_address] port 0: input 1, pdt: 1, pn: 0, dpcd_rev: 00, mcs: 1, ddps: 1, ldps 0, sdp 0/0 May 07 00:48:07 localhost.localdomain kernel: [drm:drm_dp_send_link_address] port 1: input 0, pdt: 3, pn: 1, dpcd_rev: 11, mcs: 0, ddps: 1, ldps 0, sdp 0/0 May 07 00:48:07 localhost.localdomain kernel: [drm:drm_dp_send_link_address] port 2: input 0, pdt: 3, pn: 2, dpcd_rev: 11, mcs: 0, ddps: 1, ldps 0, sdp 0/0 May 07 00:48:07 localhost.localdomain kernel: [drm:drm_dp_dpcd_access] too many retries, giving up May 07 00:48:07 localhost.localdomain kernel: [drm:drm_dp_dpcd_access] too many retries, giving up May 07 00:48:07 localhost.localdomain kernel: [drm:intel_hpd_irq_handler] hotplug event received, stat 0x00200000, dig 0x00101011 May 07 00:48:07 localhost.localdomain kernel: [drm:intel_hpd_irq_handler] digital hpd port B - short May 07 00:48:07 localhost.localdomain kernel: [drm:drm_dp_dpcd_access] too many retries, giving up May 07 00:48:07 localhost.localdomain kernel: [drm:drm_dp_dpcd_access] too many retries, giving up May 07 00:48:07 localhost.localdomain kernel: [drm:drm_dp_dpcd_access] too many retries, giving up May 07 00:48:07 localhost.localdomain kernel: [drm:drm_dp_dpcd_access] too many retries, giving up May 07 00:48:07 localhost.localdomain kernel: [drm:intel_dp_hpd_pulse] got hpd irq on port B - short May 07 00:48:07 localhost.localdomain kernel: [drm:drm_dp_dpcd_access] too many retries, giving up May 07 00:48:07 localhost.localdomain kernel: [drm:drm_dp_dpcd_access] too many retries, giving up May 07 00:48:07 localhost.localdomain kernel: [drm:drm_dp_dpcd_access] too many retries, giving up May 07 00:48:07 localhost.localdomain kernel: [drm:drm_dp_dpcd_access] too many retries, giving up May 07 00:48:07 localhost.localdomain kernel: [drm:drm_dp_dpcd_access] too many retries, giving up May 07 00:48:07 localhost.localdomain kernel: [drm:drm_dp_send_sideband_msg] failed to dpcd write 7 -5 May 07 00:48:07 localhost.localdomain kernel: ------------[ cut here ]------------ May 07 00:48:07 localhost.localdomain kernel: WARNING: CPU: 0 PID: 4 at drivers/gpu/drm/drm_dp_mst_topology.c:1268 process_single_tx_qlock+0x623/0x690 [drm_kms_helper]() May 07 00:48:07 localhost.localdomain kernel: fail This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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. Created attachment 1032139 [details]
Fedora 22 oops from connecting a MST hub to the displayport connector
This bug still effects Fedora 22.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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. Please reopen this bug, this still effects Fedora 22. |