Go Back   DisplayLink Forum > DisplayLink Graphics Technology > Linux and Open Source

Reply
 
Thread Tools Search this Thread Display Modes
Old 11-02-2016, 01:24 PM   #1
Sparxy
Junior Member
 
Join Date: Jun 2016
Posts: 12
Default Kernel hangs for a minute when plugging in display

The kernel keeps freezing every few seconds for the first minute after plugging in a DisplayLink display (or even changing display settings while DisplayLinkManager is running) while spamming the syslog with the following messages:

Ubuntu 16.10, Linux 4.8.0-26-generic, displaylink 1.2.65.

kernel: [ 66.255209] usb 4-6: new SuperSpeed USB device number 2 using xhci_hcd
kernel: [ 66.275893] usb 4-6: New USB device found, idVendor=17e9, idProduct=ff0b
kernel: [ 66.275896] usb 4-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
kernel: [ 66.275898] usb 4-6: Product: ASUSTEK MB169B+
kernel: [ 66.275899] usb 4-6: Manufacturer: DisplayLink
kernel: [ 66.275901] usb 4-6: SerialNumber: <removed>
mtp-probe: checking bus 4, device 2: "/sys/devices/pci0000:00/0000:00:14.0/usb4/4-6"
mtp-probe: bus: 4, device: 2 was not an MTP device
colord-sane: io/hpmud/pp.c 627: unable to read device-id ret=-1
systemd[1]: Starting DisplayLink Manager Service...
kernel: [ 67.328937] evdi: loading out-of-tree module taints kernel.
kernel: [ 67.328989] evdi: module verification failed: signature and/or required key missing - tainting kernel
kernel: [ 67.330128] evdi: [I] Initialising logging on level 5
systemd[1]: Started DisplayLink Manager Service.
kernel: [ 67.876334] [drm] probing gen 2 caps for device 8086:c01 = 261ad03/e
kernel: [ 67.876337] [drm] PCIE gen 3 link speeds already enabled
kernel: [ 67.880506] [drm] PCIE GART of 2048M enabled (table at 0x00000000001D6000).
kernel: [ 67.880609] radeon 0000:01:00.0: WB enabled
kernel: [ 67.880611] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0xffff8b5a7cd3fc00
kernel: [ 67.880612] radeon 0000:01:00.0: fence driver on ring 1 use gpu addr 0x0000000040000c04 and cpu addr 0xffff8b5a7cd3fc04
kernel: [ 67.880613] radeon 0000:01:00.0: fence driver on ring 2 use gpu addr 0x0000000040000c08 and cpu addr 0xffff8b5a7cd3fc08
kernel: [ 67.880614] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0xffff8b5a7cd3fc0c
kernel: [ 67.880615] radeon 0000:01:00.0: fence driver on ring 4 use gpu addr 0x0000000040000c10 and cpu addr 0xffff8b5a7cd3fc10
kernel: [ 67.880825] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000075a18 and cpu addr 0xffffaa58c1a35a18
kernel: [ 67.981038] radeon 0000:01:00.0: failed VCE resume (-110).
kernel: [ 68.155617] [drm] ring test on 0 succeeded in 1 usecs
kernel: [ 68.155621] [drm] ring test on 1 succeeded in 1 usecs
kernel: [ 68.155625] [drm] ring test on 2 succeeded in 1 usecs
kernel: [ 68.155632] [drm] ring test on 3 succeeded in 4 usecs
kernel: [ 68.155637] [drm] ring test on 4 succeeded in 3 usecs
kernel: [ 68.331312] [drm] ring test on 5 succeeded in 2 usecs
kernel: [ 68.331317] [drm] UVD initialized successfully.
kernel: [ 68.331348] [drm] ib test on ring 0 succeeded in 0 usecs
kernel: [ 68.331374] [drm] ib test on ring 1 succeeded in 0 usecs
kernel: [ 68.331399] [drm] ib test on ring 2 succeeded in 0 usecs
kernel: [ 68.331432] [drm] ib test on ring 3 succeeded in 0 usecs
kernel: [ 68.331456] [drm] ib test on ring 4 succeeded in 0 usecs
kernel: [ 68.998865] [drm] ib test on ring 5 succeeded
kernel: [ 69.365870] evdi: [D] add_store:195 Increasing device count to 1
kernel: [ 69.366079] evdi: [D] evdi_crtc_init:312 drm_crtc_init: 0
kernel: [ 69.366678] evdi: [W] evdi_painter_crtc_state_notify:377 Painter does not exist!
kernel: [ 69.366679] evdi: [D] evdi_detect:72 Painter is disconnected
kernel: [ 69.366682] evdi evdi.0: No connectors reported connected with modes
kernel: [ 69.366684] [drm] Cannot find any crtc or sizes - going 1024x768
kernel: [ 69.367654] evdi evdi.0: fb2: evdidrmfb frame buffer device
kernel: [ 69.367656] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
kernel: [ 69.367657] [drm] No driver support for vblank timestamp query.
kernel: [ 69.367657] [drm] evdi: evdi_stats_init
kernel: [ 69.367661] [drm] Initialized evdi 1.2.64 20161003 on minor 2
kernel: [ 70.822646] evdi: [W] evdi_painter_disconnect:478 (dev=0) An unknown connection to ffff8b59cfa58e00 tries to close us
kernel: [ 70.822647] evdi: [W] evdi_painter_disconnect:479 - ignoring
kernel: [ 70.822835] evdi: [W] evdi_painter_disconnect:478 (dev=0) An unknown connection to ffff8b59cfa58e00 tries to close us
kernel: [ 70.822835] evdi: [W] evdi_painter_disconnect:479 - ignoring
kernel: [ 70.824983] evdi: [D] evdi_detect:72 Painter is disconnected
kernel: [ 70.825012] evdi: [D] evdi_detect:72 Painter is disconnected
kernel: [ 70.825226] evdi: [D] evdi_painter_crtc_state_notify:374 (dev=0) Notifying crtc state: 3
kernel: [ 70.825227] evdi: [W] evdi_painter_send_crtc_state:266 Painter is not connected!
kernel: [ 70.825230] evdi: [D] evdi_painter_crtc_state_notify:374 (dev=0) Notifying crtc state: 3
kernel: [ 70.825230] evdi: [W] evdi_painter_send_crtc_state:266 Painter is not connected!
kernel: [ 70.862357] evdi: [W] evdi_painter_disconnect:478 (dev=0) An unknown connection to ffff8b5a7fd2cc00 tries to close us<4>[ 70.862358] evdi: [W] evdi_painter_disconnect:479 - ignoring
kernel: [ 70.869937] evdi: [D] evdi_painter_connect:448 (dev=0) Connected with (null)
kernel: [ 70.869938] evdi: [D] evdi_detect:69 (dev=2) Painter is connected
kernel: [ 70.869969] evdi: [D] evdi_painter_crtc_state_notify:374 (dev=2) Notifying crtc state: 3
kernel: [ 72.521056] evdi: [D] evdi_detect:69 (dev=2) Painter is connected
kernel: [ 72.521059] evdi: [D] evdi_painter_get_edid_copy:192 (dev=2) 00 ff ff
kernel: [ 78.738759] evdi: [D] evdi_painter_mode_changed_notify:391 (dev=2) Notifying mode changed: 1920x1080@60; bpp 32;
kernel: [ 78.738760] evdi: [D] evdi_painter_mode_changed_notify:392 pixel format 875713112
kernel: [ 78.738766] evdi: [D] evdi_painter_crtc_state_notify:374 (dev=2) Notifying crtc state: 0
kernel: [ 79.442143] evdi: [D] evdi_detect:69 (dev=2) Painter is connected
kernel: [ 79.442147] evdi: [D] evdi_painter_get_edid_copy:192 (dev=2) 00 ff ff
kernel: [ 81.717924] evdi: [D] evdi_detect:69 (dev=2) Painter is connected
kernel: [ 81.717927] evdi: [D] evdi_painter_get_edid_copy:192 (dev=2) 00 ff ff

(these 2 messages keep repeating for a while...)

kernel: [ 131.782537] evdi: [D] evdi_detect:69 (dev=2) Painter is connected
kernel: [ 131.782544] evdi: [D] evdi_painter_get_edid_copy:192 (dev=2) 00 ff ff
kernel: [ 134.018235] evdi: [D] evdi_detect:69 (dev=2) Painter is connected
kernel: [ 134.018240] evdi: [D] evdi_painter_get_edid_copy:192 (dev=2) 00 ff ff
kernel: [ 152.638927] evdi: [D] evdi_painter_crtc_state_notify:374 (dev=2) Notifying crtc state: 3
kernel: [ 152.639075] evdi: [W] evdi_painter_mode_changed_notify:399 (dev=2) Change mode duplicated - ignoring
kernel: [ 152.640291] evdi: [D] evdi_painter_crtc_state_notify:374 (dev=2) Notifying crtc state: 0
kernel: [ 152.640294] evdi: [D] evdi_painter_dpms_notify:361 (dev=2) Notifying dpms mode: 0
kernel: [ 153.125000] evdi: [D] evdi_detect:69 (dev=2) Painter is connected
kernel: [ 153.125004] evdi: [D] evdi_painter_get_edid_copy:192 (dev=2) 00 ff ff

Note it took 86 seconds from connecting the device until my computer became usable again in this instance. This is a little too long if you ask me.
Sparxy is offline   Reply With Quote
Old 11-03-2016, 01:40 PM   #2
mlukaszek
Senior Member
 
mlukaszek's Avatar
 
Join Date: Feb 2010
Posts: 386
Default

This could be caused by not enough current delivered to the monitor. Is the same reproducible if you connect it through a powered hub?

Regards,
Michal
mlukaszek is offline   Reply With Quote
Old 11-08-2016, 10:21 AM   #3
Sparxy
Junior Member
 
Join Date: Jun 2016
Posts: 12
Default

Hello Michal,

Thank you for your help this far.
The problem also occurs when using an externally powered hub.
The problem also occurs (but doesn't take quite as long to resolve) when I change the display settings, but only when a DisplayLink display is connected.

Edit: Problem seems to be related to the kernel, not the evdi or displaylink modules, since the issue is largely resolved in linux 4.9 rc (tested up to rc5)

Last edited by Sparxy; 11-22-2016 at 11:50 AM.
Sparxy is offline   Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT. The time now is 06:34 AM.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2024, vBulletin Solutions, Inc.