Comment 12 for bug 2023647

Revision history for this message
Daniel van Vugt (vanvugt) wrote : Re: Screens go into flicker cycle after going blank with external monitor(s)

There's a hardware connection problem which seems to come first in some cases:

cze 23 15:35:36 jarek-Inspiron kernel: [drm] perform_link_training_with_retries: Link(2) training attempt 1 of 4 failed @ rate(10) x lane(2) : fail reason:(1)
...
cze 23 15:35:36 jarek-Inspiron kernel: [drm] perform_link_training_with_retries: Link(2) training attempt 2 of 4 failed @ rate(10) x lane(2) : fail reason:(1)
cze 23 15:35:37 jarek-Inspiron kernel: [drm] perform_link_training_with_retries: Link(2) training attempt 3 of 4 failed @ rate(10) x lane(2) : fail reason:(1)
...
cze 23 15:35:37 jarek-Inspiron kernel: [drm] enabling link 2 failed: 15
cze 23 15:35:38 jarek-Inspiron gnome-shell[3512]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->logical_monitors)' failed
cze 23 15:35:38 jarek-Inspiron gnome-shell[3512]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed
cze 23 15:35:38 jarek-Inspiron gnome-shell[3512]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->logical_monitors)' failed
cze 23 15:35:38 jarek-Inspiron gnome-shell[3512]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed
cze 23 15:35:38 jarek-Inspiron gnome-shell[3512]: meta_display_get_monitor_in_fullscreen: assertion 'monitor >= 0 && monitor < n_logical_monitors' failed
cze 23 15:35:39 jarek-Inspiron gnome-shell[3512]: 0x3800080: Frame has assigned frame counter but no frame drawn time
cze 23 15:35:39 jarek-Inspiron gnome-shell[3512]: 0x3800080: Frame has assigned frame counter but no frame drawn time
cze 23 15:35:39 jarek-Inspiron gnome-shell[3512]: 0x3800080: Frame has assigned frame counter but no frame drawn time