You are not logged in.

#26 2016-11-16 04:18:11

pntruongan
Member
Registered: 2011-01-31
Posts: 63

Re: [Solved] Displaylink SegFault

mesa and mesa-libgl have an update today. Anyone test it out yet ?

PS: OK I tested them out and immediately downgrade, mesa-13.0.1-1 does not work with displaylink. If you need display link keep mesa in Ignore package for now.

Last edited by pntruongan (2016-11-16 04:48:51)

Offline

#27 2016-11-23 16:07:18

TrevorBramble
Member
From: Seattle, WA, USA
Registered: 2009-11-12
Posts: 21
Website

Re: [Solved] Displaylink SegFault

Everything appears to be working well on my system now. Latest kernel, Mesa, and DisplayLink.

riomus? How about you? If it's working, could you please mark the thread solved?

Offline

#28 2016-11-24 18:20:28

pntruongan
Member
Registered: 2011-01-31
Posts: 63

Re: [Solved] Displaylink SegFault

Working fine for me too. Those kernel update seem to have somehow fixed it.

Offline

#29 2016-11-29 15:15:20

bfritz
Member
Registered: 2016-11-29
Posts: 2

Re: [Solved] Displaylink SegFault

@TrevorBramble or @pntruongan Which kernel update fixed the issue for you?  I'm seeing the same segfault on resume running:

Linux t440p 4.8.10-1-ARCH #1 SMP PREEMPT Mon Nov 21 11:55:43 CET 2016 x86_64 GNU/Linux

Looks like 4.8.11 is out now, but 4.8.10 was probably latest when you posted.

My backtrace, when resuming with two DL monitors connected to docked T440p:

[ 39973.251] (II) intel(0): Enabled output DP2-1
[ 39973.251] (II) intel(0): Enabled output DP2-2
[ 39973.251] (II) intel(0): Enabled output DP2-3
[ 39973.280] (EE) 
[ 39973.280] (EE) Backtrace:
[ 39973.350] (EE) 0: /usr/lib/xorg-server/Xorg (OsLookupColor+0x139) [0x59cd49]
[ 39973.406] (EE) 1: /usr/lib/libc.so.6 (__restore_rt+0x0) [0x7ff3e5b680af]
[ 39973.407] (EE) 2: /usr/lib/libc.so.6 (readdir+0x29) [0x7ff3e5be87e9]
[ 39973.433] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so (_init+0x63998) [0x7ff3e11de738]
[ 39973.437] (EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so (_init+0x662ab) [0x7ff3e11e410b]
[ 39973.438] (EE) 5: /usr/lib/xorg/modules/drivers/intel_drv.so (_init+0x6d985) [0x7ff3e11f2fc5]
[ 39973.438] (EE) 6: /usr/lib/xorg-server/Xorg (xf86Wakeup+0x197) [0x479697]
[ 39973.438] (EE) 7: /usr/lib/xorg-server/Xorg (WakeupHandler+0x6d) [0x43b2dd]
[ 39973.438] (EE) 8: /usr/lib/xorg-server/Xorg (WaitForSomething+0x1e9) [0x5954f9]
[ 39973.438] (EE) 9: /usr/lib/xorg-server/Xorg (SendErrorToClient+0x10e) [0x4365ee]
[ 39973.438] (EE) 10: /usr/lib/xorg-server/Xorg (remove_fs_handlers+0x463) [0x43a7f3]
[ 39973.439] (EE) 11: /usr/lib/libc.so.6 (__libc_start_main+0xf1) [0x7ff3e5b55291]
[ 39973.439] (EE) 12: /usr/lib/xorg-server/Xorg (_start+0x29) [0x4246e9]
[ 39973.439] (EE) 13: ? (?+0x29) [0x29]
[ 39973.439] (EE) 
[ 39973.439] (EE) Segmentation fault at address 0x4
[ 39973.439] (EE) 
Fatal server error:
[ 39973.440] (EE) Caught signal 11 (Segmentation fault). Server aborting
[ 39973.440] (EE) 
[ 39973.440] (EE) 

Offline

#30 2016-11-29 19:38:06

TrevorBramble
Member
From: Seattle, WA, USA
Registered: 2009-11-12
Posts: 21
Website

Re: [Solved] Displaylink SegFault

@bfritz, Maybe 4.8.10? But also make sure you've updated mesa. I'd continued applying other updates and held back mesa until updates beyond the bugged version were available.

Offline

#31 2016-12-07 17:20:37

markjanes
Member
Registered: 2016-12-07
Posts: 1

Re: [Solved] Displaylink SegFault

There are two separate bugs in the Intel driver stack which can trigger this crash.  Both are described here:

https://bugs.freedesktop.org/show_bug.cgi?id=98563

To fix the issue, you should update libdrm to 2.4.72 and stop using xf86-video-intel.

If you don't want to switch to modesetting, make sure xf86-video-intel is newer than a1b39eb6dd1717501a0546275d07df8321fe4905.

Offline

#32 2016-12-08 16:35:20

bfritz
Member
Registered: 2016-11-29
Posts: 2

Re: [Solved] Displaylink SegFault

Thank you, Mark!  Removed xf86-video-intel to switch to modesetting and all is well again when docking.

Offline

#33 2017-01-12 11:52:31

riomus
Member
Registered: 2016-11-01
Posts: 6

Re: [Solved] Displaylink SegFault

TrevorBramble wrote:

Everything appears to be working well on my system now. Latest kernel, Mesa, and DisplayLink.

riomus? How about you? If it's working, could you please mark the thread solved?

Sorry for not replying but it was quite busy time for me. Currently, there is no SegFault and everything related to that issue seems to be working.

Offline

#34 2017-01-25 09:51:50

fethio
Member
Registered: 2013-05-13
Posts: 12

Re: [Solved] Displaylink SegFault

I was using the displaylink AUR package to work with my second screen attached to the USB3 port of a Lenovo T430s running arch linux and xfce4. (with the previous lib32-mesa-lib, etc package versions 12.0.X instead of 13.0.X)

An update about a week ago broke my displaylink. Now when I attach the USB from the monitor, and use the 'xrandr --setprovideroutputsource' command all I get is a blank screen, where I can see my mouse hovering over, but no windows.

I am using kernel 4.8.13-1, libdrm 2.4.74-1, evdi 1.2.64-1, displaylink 1.2.65-1, xfce4 4.12.3-2, xorg-server 1.19.1-1

In the dmesg this is what I see after the USB attachment::

[fethi@c_corax ~]$ dmesg
...
[   21.422846] usbcore: registered new interface driver udl
[   38.703638] evdi: [I] Initialising logging on level 5
[   58.361178] fuse init (API version 7.25)
[   88.716301] cinnamon-screen[1181]: segfault at 18 ip 00007f4caacec9b0 sp 00007ffc807010d8 error 4 in libxklavier.so.16.4.0[7f4caace5000+1a000]
[   91.954653] usb 4-1: new SuperSpeed USB device number 2 using xhci_hcd
[   96.529558] evdi: [D] add_store:195 Increasing device count to 1
[   96.529815] evdi: [D] evdi_crtc_init:312 drm_crtc_init: 0
[   96.530382] evdi: [W] evdi_painter_crtc_state_notify:377 Painter does not exist!
[   96.530387] evdi: [D] evdi_detect:72 Painter is disconnected
[   96.530392] evdi evdi.0: No connectors reported connected with modes
[   96.530395] [drm] Cannot find any crtc or sizes - going 1024x768
[   96.531799] evdi evdi.0: fb1: evdidrmfb frame buffer device
[   96.531803] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[   96.531804] [drm] No driver support for vblank timestamp query.
[   96.531806] [drm] evdi: evdi_stats_init
[   96.531815] [drm] Initialized evdi 1.2.64 20161003 on minor 1
[   97.241984] evdi: [D] evdi_detect:72 Painter is disconnected
 

What does 'Painter does not exist!' mean, and how can I correct this issue? Any clues will be greatly appreciated.

Offline

#35 2017-01-25 17:46:22

TrevorBramble
Member
From: Seattle, WA, USA
Registered: 2009-11-12
Posts: 21
Website

Re: [Solved] Displaylink SegFault

Please don't re-use threads for different problems. The topic for this thread has been resolved. Start a new thread for your specific trouble.

fethio wrote:

I was using the displaylink AUR package to work with my second screen attached to the USB3 port of a Lenovo T430s running arch linux and xfce4. (with the previous lib32-mesa-lib, etc package versions 12.0.X instead of 13.0.X)

An update about a week ago broke my displaylink. Now when I attach the USB from the monitor, and use the 'xrandr --setprovideroutputsource' command all I get is a blank screen, where I can see my mouse hovering over, but no windows.
[snip]

Offline

Board footer

Powered by FluxBB