Random desktop environment crash #197
Comments
|
+1 |
|
Have same problem on Gentoo while having connected two displaylink devices. Happens especially under having loads (e.g. looking HD videos or compiling in parallel): As there is so much i915 and some kernel bug trackers mention heavy issues with Kernel 5.4.x and i915 @UnoSD : may you able to check if you have also kernel traces in your kernel log? As stated above, can check in terminal with |
|
|
Are these helpful? |
|
Would love to help if I can get an idea of the best place to start? :-) |
@monofox I just tried, but unfortunately it has been purged from the logs, it happened last time on the 23rd and then I decided to roll back to 5.4. |
|
All given stack traces here have to do with DRM so likeley evdi has some incompatibilities with kernel? Although don't get any traces with kernel 5.5.13, but had a smaller interval until next crash of display manager. So switched back to kernel 5.2.3-ck to see if the crashes appears there as well for me. @grant-traynor : does the issues appear for you on earlier kernel releases? You're right now using 5.5.11. |
|
Hi @monofox, I'm happy to give it a crack. I've been using arch for about 5 years now and have not had a need to build a kernel since using it. So I'm pretty well out of practice in general, and have never done it on arch at all. Do you have a recommendation for the best method to do that? https://wiki.archlinux.org/index.php/Kernel/Arch_Build_System ? |
|
Hi @grant-traynor, I tested during the day my old kernel 5.2.3-ck which worked without any crash with same xorg, same evdi version. There was couple of minutes ago only one issue, that displaylink docking station freezed (no ethernet anymore, no usb, images were frozen). So this actually does not have to do with evdi. |
|
OK. I'm running 5.2.3 now. I'll let you know how it goes. |
|
So I've been running in the 5.2.3 kernel all day and it seems "rock solid". No issues. Good in fact. I'll stick on this version and report back if it fails, but I think you're onto something @monofox |
|
@monofox @UnoSD @grant-traynor Are you all on Intel iGPUs? |
|
@abucodonosor , yes: |
|
@monofox Same here: Intel Corporation UHD Graphics 620 (Whiskey Lake) |
|
@abucodonosor |
|
No crashes today also. |
|
Those bugs look to me like Intel drm bugs, especially after they did the eb_* rework. Is someone willing to test a vanilla 5.6 kernel? |
|
Same here at X-Session (xfce4 and lxqt) crashed randomly - I suppose especially in Browser activity (heavily load) and brought back to lightdm login screen. HW is thinkpad x260 with following lspci-output:
user.log If I could do something more, pls let me know. |
|
@abucodonosor : sure, i'm willing to test. |
|
@monofox I noticed @displaylink-dkurek already added a fix for 5.6 kernels in git. This commit 34d92e8. It is similar to my fix just with <= logic :-) |
|
@abucodonosor : Kernel is configured, compiled, installed: |
|
Was a short test. Desktop environment crashed after round about 30 minutes. |
|
nothing interesting in the logs. Can you maybe use journalctl or similar to get a full dmesg? |
|
@abucodonosor Full log is here: https://gist.github.com/monofox/9199cb2a5a844c9c706c621b60f6c91b I didn't worked last two hours (so in last two hours nothing happened). But i'll stick a while for 5.6 and check how its going. |
|
Putting this here for future reference ==> dkms install evdi/1.6.2 -k 5.6.0-arch1-1-gkt-5-6 |
|
Ok. I'm using this version today. Did not get time with it yesterday due to work commitments. I'll let you know how it goes. |
|
@abucodonosor : Package was up-to-date. Just my initramfs not. I've updated it. And made two tests: one with GUC enable and one with GUC disabled. In both cases, crash happens: https://gist.github.com/monofox/5a15cd0672dc6eacc4e0c1a987aceeb0 |
|
OK. Might be a bit premature, but I've been using this version for the whole morning with no issues, doing the sorts of things that would normally cause the crash (Videoconferencing, flowcharting and graphical stuff, Moving windows between the laptop and the two attached screens). It seems a little slower though? For reference:
|
|
Update: I just updated, had one system freeze and now video playback is insanely slow. I will have to downgrade once again. Will try evdi-git first, but I have no hope this will be fixed. I'm getting really close to toss the docking station out of the window. |
|
Same issue with evdi-git. |
|
ffs! now I downgraded and videos are still slow! |
|
I wonder if it's helped by some of the other tweaking I've been playing with over time. Note that I'm also using X11 not Wayland. I also tried stuff on this thread at some point and thought it helped: https://displaylink.org/forum/showthread.php?t=65650 I'm upgrading arch at the moment, I'll let you know if I see a problem on the latest versions. |
|
thank you @grant-traynor , I will give your settings a go. I am also using X11, I actually wanted to try Wayland as I saw some posts around issues with X11, but I'm on XFCE and LightDM, and I understand that it's not well supported/not doable at all. I was on kernel I updated to I decided then to re-downgrade evdi, displaylink and use the LTS kernel I am trying now to rebuild the old kernel to see if that helps, but I'm getting all sort of incompatibility issues with the new gcc... I basically wasted a weekend on this. any help would be really appreciated as I'm desperate and this is becoming more and more frustrating. If I didn't have all the cables stapled and only one HDMI, I would have already thrown away the docking station. |
|
Hi @UnoSD So I'm running this at the moment, and it's been stable and performant since yesterday when I said I'd do the upgrade. I think I patched my own display link driver, but that was just a versioning / download URL change from what I remember. The machine is a Lenovo E15 with an external USB-C hub. I've got this file: And I'm setting my monitors up with a shell script depending upon if I'm home or in the office. Mostly at home at the moment. Most of this I've pieced together using the information from this wiki article: https://wiki.archlinux.org/index.php/DisplayLink The only other file I have I think is this one: Note that I had problems with spectrwm for a while, and using GNOME seemed stable. Maybe there's still something going on that XFCE has a problem with. Have you tried an alternative WM / DE for a while to see if that helps? |
|
@grant-traynor Thank you very much, I really appreciate you sharing your configuration. I managed to downgrade back to a working kernel/evdi combination. I had to get the old kernel from the archives, downgrade gcc, compile evdi, re-upgrade gcc and finally I got it to the same state as before (no constant disconnects/reconnects and working audio). I will need to get this sorted at some point, when I have some time, I'll back all this up and try with your configuration and I will give some feedback. Thanks again. |
|
@UnoSD .... I did notice today that if I routed audio out through the HDMI connections in the dock then the video slowed down .... routing it to a USB connected headset on the same dock was fine. |
|
@grant-traynor that may be related to the same issue I was experiencing, that was apparently fixed in the new kernel, but I haven't tried it: |
|
Throwing my hat in the ring. Getting similar error as #197 (comment) and tempted to throw it out the window as well :) So far I haven't been able to find a good combo on 18.04 and the 5.7+ kernels aren't available yet. Linux distribution and its version: Ubuntu 18.04 |
|
I got fed up with this issues and I decided to plug my monitors buying some adaptors directly in the laptop so I can't really comment on this issue anymore. But I'll gladly try again later if it seems resolved for the others. |
|
@UnoSD I don't have that option that I know of. If this doesn't work I think my only option is to move to a USB-C laptop + dock setup. Not exactly clear if the evdi is still needed. |
|
To add to the frustration I thought I was safe by going back to Gnome and it just crashed on me. :( |
|
Starting to get to the same point. This clearly looks like something that displaylink really aren't interested in continuing ... need to find another answer. |
|
Looks like a good Samaritan in arch has raised a ticket on xorg. Apparently it's on known regression. There is hope: https://aur.archlinux.org/packages/displaylink/ |
|
I've been struggling thinking it was my Ubuntu install and heavy usage of apps. I'm testing out a non-DisplayLink setup, I'm also going to try upgrading to Ubuntu 20.10 with kernel 5.8 and see if that makes any difference. |
|
@timnolte Same, I'm moving some of my workloads that aren't compatible with Ubuntu 20.10 in a KVM as a last ditch effort to see if 5.8 works which sounds like success on this issue thread. |
|
+1 First, thank you @displaylink-dkurek, for the amazing work. I was hoping #225 (kernel > 5.8) would finally solve the present issue as well as #126. This is reported in several ways here and in the DisplayLink forum. Here it is mentioned to report these problems to the DisplayLink forum instead. But some of the (perhaps) related issues are still open. I would be happy to test or report log files if needed. |
|
Hi, i have a laptop with nvidia video card, the dock work perfectly with other note, but with my notebook crash randomly, freezing the bluethoot and usb ports (my keyboard and mouse). I tested 1 million of things, but dosent work anything. |
|
Hi all, same/similar problem here. Randomly dropping out of the X session to login screen. Sometimes this happens immediately after login, i.e. I get the desktop for a brief moment or even only a "blink". Feels like on 2nd login it then always works... until it drops out later after n or nn minutes. Nothing regular as far as I see. Appears to happen more or less only when browsing the web ("normal" sites, not even videos). Where to start? Logs don't really give me a hint, see below, but first some data on the setup maybe. The Dock is a "lenovo hybrid USB-C with USB-A dock", connected via a HDMI-DVI adaptor cable to a HP ZR24w. Running without problems on two different lenovo thinkpads with W10. So, no hardware issues. running 5.5.4 as others freeze my machine randomly; not related to displaylink Added the "PageFlip" "false" but didn't help. From what I read it appears necessary in cases where the displaylink connected screens aren't usable at all. Not my case. Now for the little information I can find from the logs. Apologies for not knowing better where to get what from, maybe throw me some hints what I should gather.
From For the above crash, I found this in Once (!) I got this: Another time I had these two lines But again, not much in front (several seconds silence), and only messages thereafter resulting from the "log out". Where to start looking further? How to make the crashes "dump" useful information? |
|
replying to my own post: took the "easy" way (well...):
|
|
I have been experiencing the same issue, random crashes sometimes several times per day, with a ThinkPad Hybrid USB-C running Xubuntu 20.04 and DisplayLink 5.3.1. However I have not had a single crash after upgrading DisplayLink to 5.4.0 about two weeks ago. |
|
@tbjornli 5.8.x Kernel? |
|
Sorry, I forgot to include the kernel. I'm running on 5.4.0-73-generic. |
|
Got a crash today with fairy recent kernel and displaylink driver: I believe it happened when I checked gitlab job output which updated the screen very often. Kernel version: 5.10.79 Kernel crash log: |
|
Bumping this issue back as I believe I might be having the same issue as poeple were having here. I was able to at least have the monitors displaying properly with a 4K display and another vertical monitor. But as stated early in the issue, heavy workloads just seem to crash either the Wayland/Xorg (tried both). I've also used this fork which has a script to installing all the required dependencies for the DisplayLink driver to work properly. Here is my system info: These are the output right before crashing DisplayLink (or I believe it must be DisplayLink), btw this happens on Wayland. Xorg has the vertical monitor simply unusable as it hardly catches up on rendering: |
|
I'm noticing a lot more screen tearing and artifacts. I am using the latest beta of the DisplayLink driver which includes everything to support the newer kernels. My monitor is usable but not as good as it used to be. |
|
I have a portable monitor which is unusable when set to vertical with xorg. Using the latest kernel (5.15..) and displaylink beta. I'll add details later. |
|
Still getting the same kernel BUG with recent drivers and kernel: Kernel version: 5.17.12 Kernel crash log: |
and others
Initially please make sure the problem hasn't been already addressed:
(https://www.displaylink.com/downloads/ubuntu)
(https://github.com/DisplayLink/evdi/releases)
on DisplayLink's website?
(https://support.displaylink.com/knowledgebase/topics/103927-troubleshooting-ubuntu)
(if it is rather connected to DisplayLinkManager please take a look at support
https://support.displaylink.com or forum https://www.displaylink.org/forum/)
Some information for baseline would help a lot:
Arch Linux
5.5.10-arch1-1
1.20.7
XFCE 4.14
Please provide good title for the issue and description.
I refrained from updating to kernel 5.5 for a while for the well know issue (package in Arch Linux AUR still does not have the patch: https://aur.archlinux.org/packages/evdi/)
Since it was taking a while, I decided to try and update the kernel to 5.5 and used the git version of the Arch package (https://aur.archlinux.org/packages/evdi-git/).
After updating, everything seemed to work, but, more than once during the same hour of usage, the desktop crashed killing the whole session and going back to the lightdm login screen. This never happened with the old evdi package and kernel 5.4; Unplugged from the docking station with evdi and dispalylink process running, this does not happen.
If you can give us logs they will be welcome but please don't paste long listings
as they will make it hard to read the thread, instead you can use other services
for sharing raw text like pastebin or gist.
can you please suggest what logs to share? Xorg.log? dmesg?
Thank you
The text was updated successfully, but these errors were encountered: