intel_dp_max_link_bw+0x62/0x69() warnings non-stop |
|||
Issue descriptiondisplaylink continuous warnings - see below - intel_dp_max_link_bw+0x62/0x69() >> marcheu - any ideas on this? full feedback at https://feedback.corp.google.com/product/208/neutron?lView=rd&lRSort=1&lROrder=2&lRFilter=1&lReportSearch=user:03bc34a18fcb256d0e30902b0564c9a5_5395592300&lReport=57860109820 [ 2.681660] ------------[ cut here ]------------ [ 2.681671] WARNING: CPU: 0 PID: 184 at /mnt/host/source/src/third_party/kernel/v3.14/drivers/gpu/drm/i915/intel_dp.c:115 intel_dp_max_link_bw+0x62/0x69() [ 2.681683] invalid max DP link bw val 0, using 1.62Gbps [ 2.681688] Modules linked in: iwlmvm r8169 mii iwlwifi iwl7000_mac80211 cfg80211 [ 2.681708] CPU: 0 PID: 184 Comm: frecon Not tainted 3.14.0 #1 [ 2.681714] Hardware name: GOOGLE Guado, BIOS Google_Guado.6301.108.4 04/01/2015 [ 2.681721] 0000000000000000 000000002ca1bf0e ffff880077d65c00 ffffffffb0e15b9c [ 2.681733] ffff880077d65c48 ffff880077d65c38 ffffffffb085d79f ffffffffb0b6b960 [ 2.681745] ffff880176510300 ffff880178e44000 0000000000006257 0000000000000005 [ 2.681756] Call Trace: [ 2.681764] [<ffffffffb0e15b9c>] dump_stack+0x4d/0x6f [ 2.681774] [<ffffffffb085d79f>] warn_slowpath_common+0x7f/0x98 [ 2.681782] [<ffffffffb0b6b960>] ? intel_dp_max_link_bw+0x62/0x69 [ 2.681791] [<ffffffffb085d80f>] warn_slowpath_fmt+0x57/0x73 [ 2.681800] [<ffffffffb0b2460d>] ? drm_mode_create+0x40/0x56 [ 2.681808] [<ffffffffb0b6b960>] intel_dp_max_link_bw+0x62/0x69 [ 2.681817] [<ffffffffb0b6b9c5>] intel_dp_mode_valid+0x5e/0xd5 [ 2.681826] [<ffffffffb0b0ed3c>] drm_helper_probe_single_connector_modes+0x236/0x2df [ 2.681835] [<ffffffffb0b22149>] drm_mode_getconnector+0x112/0x32d [ 2.681844] [<ffffffffb0b14347>] drm_ioctl+0x2f2/0x421 [ 2.681852] [<ffffffffb0b22037>] ? drm_mode_getcrtc+0xc8/0xc8 [ 2.681861] [<ffffffffb0a1f617>] ? ioctl_has_perm+0xa8/0xed [ 2.681870] [<ffffffffb0956ef9>] do_vfs_ioctl+0x354/0x416 [ 2.681879] [<ffffffffb0957012>] SyS_ioctl+0x57/0x79 [ 2.681887] [<ffffffffb0e1e31c>] system_call_fastpath+0x20/0x25 [ 2.681894] ---[ end trace 5835b2bc01a4b5c8 ]--- [ 2.681899] ------------[ cut here ]------------ [ 2.681907] WARNING: CPU: 0 PID: 184 at /mnt/host/source/src/third_party/kernel/v3.14/drivers/gpu/drm/i915/intel_dp.c:115 intel_dp_max_link_bw+0x62/0x69() [ 2.681918] invalid max DP link bw val 0, using 1.62Gbps [ 2.681923] Modules linked in: iwlmvm r8169 mii iwlwifi iwl7000_mac80211 cfg80211 [ 2.681940] CPU: 0 PID: 184 Comm: frecon Tainted: G W 3.14.0 #1 [ 2.681951] Hardware name: GOOGLE Guado, BIOS Google_Guado.6301.108.4 04/01/2015 [ 2.681993] 0000000000000000 000000002ca1bf0e ffff880077d65c00 ffffffffb0e15b9c [ 2.682005] ffff880077d65c48 ffff880077d65c38 ffffffffb085d79f ffffffffb0b6b960 [ 2.682016] ffff880176510f00 ffff880178e44000 0000000000008ca0 0000000000000005 [ 2.682027] Call Trace: [ 2.682033] [<ffffffffb0e15b9c>] dump_stack+0x4d/0x6f [ 2.682041] [<ffffffffb085d79f>] warn_slowpath_common+0x7f/0x98 [ 2.682049] [<ffffffffb0b6b960>] ? intel_dp_max_link_bw+0x62/0x69 [ 2.682058] [<ffffffffb085d80f>] warn_slowpath_fmt+0x57/0x73 [ 2.682073] [<ffffffffb0b2460d>] ? drm_mode_create+0x40/0x56 [ 2.682081] [<ffffffffb0b6b960>] intel_dp_max_link_bw+0x62/0x69 [ 2.682090] [<ffffffffb0b6b9c5>] intel_dp_mode_valid+0x5e/0xd5 [ 2.682098] [<ffffffffb0b0ed3c>] drm_helper_probe_single_connector_modes+0x236/0x2df [ 2.682107] [<ffffffffb0b22149>] drm_mode_getconnector+0x112/0x32d [ 2.682116] [<ffffffffb0b14347>] drm_ioctl+0x2f2/0x421 [ 2.682124] [<ffffffffb0b22037>] ? drm_mode_getcrtc+0xc8/0xc8 [ 2.682133] [<ffffffffb0a1f617>] ? ioctl_has_perm+0xa8/0xed [ 2.682141] [<ffffffffb0956ef9>] do_vfs_ioctl+0x354/0x416 [ 2.682149] [<ffffffffb0957012>] SyS_ioctl+0x57/0x79 [ 2.682157] [<ffffffffb0e1e31c>] system_call_fastpath+0x20/0x25 [ 2.682163] ---[ end trace 5835b2bc01a4b5c9 ]---
,
Apr 18 2017
I doubt that these are causing your mimo issues; the mimo display uses a different drivers (UDL for displaylink) this is i915 for displayport. That said, we should figure out what's wrong here. Usually this is a sign of something broken in the DP chain. What sort of DP dongle/cable/monitor are you using?
,
Apr 19 2017
In my setup, I have a DP to DVI dongle and regular DVI cable to a pretty old monitor.
,
Apr 19 2017
In the original feedback, that it was connected HDMI from Chromebox to HDMI on TV.
,
Apr 19 2017
Can you give a detailed list of hw for the setup that reproduced this warning message? Type of adapter+cable+monitor should be enough. Or lend me these items while I debug :)
,
Apr 20 2017
A CFM system is now setup in the EE lab. I see this error only when I connect DP to HDMI. There is cable with DP to HDMI as if dongle is built in. In log in comment #1, I used an external DP to DVI dongle. So it is dongle related.
,
Apr 25 2017
I just looked and this was already fixed by Dominik, you just need to update your image to ToT. |
|||
►
Sign in to add a comment |
|||
Comment 1 by choonc@google.com
, Apr 17 2017