Facing crash issues in Kwin-x11 5.14.5

Hi,
@danielt @ndec

I’m working with Kwin 5.14.5 and the latest Debian image. The display crashes/blanks out and logouts frequently, thus closing all the previous sessions. What may be the cause for this and how can I fix this?

This is the only log I get when the display blanks out.
[ 1544.449229] msm 900000.mdss: vblank time out, crtc=0
[ 1544.544976] msm 900000.mdss: vblank time out, crtc=0
[ 1544.600953] msm 900000.mdss: vblank time out, crtc=0
[ 1544.655789] msm 900000.mdss: vblank time out, crtc=0
[ 1544.732986] msm 900000.mdss: vblank time out, crtc=0
[ 1544.853020] msm 900000.mdss: vblank time out, crtc=0
[ 1545.060999] msm 900000.mdss: vblank time out, crtc=0
[ 1545.136983] msm 900000.mdss: vblank time out, crtc=0
[ 1545.205013] msm 900000.mdss: vblank time out, crtc=0

Thanks,
Naveena

Which image is it ? 19.01 release or a snapshot?

I think it’s related to https://bugs.96boards.org/show_bug.cgi?id=843
Would be nice to identify from which image problem started, though the problem is probably related to a mesa update.

I’m using the snapshot 384 from the following link:
https://snapshots.linaro.org/96boards/dragonboard820c/linaro/debian/384/

Previously, when I was using snapshot 228, the kwin version was 5.13.5 and I didn’t get this crash issue. With the snapshot 384, I face this issue and the kwin version here is 5.14.5.

@Loic
I am facing the same issue whileinstalling the qt-creator.
Initially the kwin version was 5.13.5, but while installing qt-creator using the command

apt-get install qtcreator

, it removed kwin package. Then I had to install the kwin again, and that brought the latest version of kwin (5.14.5) in. But then the window manager started crashing randomly.On crash the board goes to login screen and from there i will have to start the whole session again.

What is the fix for it? Is there a way to install kwin 5.13.5 after installing qt?

@Loic

Any update on this?

Could you please add your observation/input to the bug: https://bugs.96boards.org/show_bug.cgi?id=837, can you try downgrade mesa to the 228 snapshot version?

In linaro-buster-alip-dragonboard-820c-384.img, the crash log is as follows:
[ 165.515] (EE) 20: /usr/lib/xorg/Xorg (0xaaaaabeae000+0x510f0) [0xaaaaabeff0ff
0]
[ 165.515] (EE)
[ 165.515] (EE) Segmentation fault at address 0x20
[ 165.515] (EE)
Fatal server error:
[ 165.515] (EE) Caught signal 11 (Segmentation fault). Server aborting
[ 165.515] (EE)
[ 165.515] (EE)

When using snapshot linaro-buster-alip-dragonboard-820c-228.img, where the kwin version was 5.13.5. There wasn’t this issue.
Then, I upgraded kwin to 5.14.5 in the snapshot-228, and the crash issue occurs.

I have updated the observation in the buglist mentioned above.

Hey @Loic,
any update on this issue??

Hey @Loic, @ndec, @danielt,
Any update that could help resolve the issue?

Nothing from me I’m afraid.

A workaround is to upgrade mesa to 19.2.1:

echo "deb  http://ftp.uk.debian.org/debian/  unstable main contrib non-free" >> /etc/apt/sources.list
apt-get -t unstable install libgl1-mesa-dri
reboot

@Loic Thanks for the work-around. Display is fine now.

But becuase of the workaround now the HiFi audio fails to register. And i am not able to set headphones or speakers as the output device.

Only HDMI is available in the Pulse audio configuration options as shown in the screenshot. (Before i could choose HiFi or HDMI from this window.)

Any suggestions to resolve this issue?

Thanks in advance!

@Loic
Any update on this issue?

@Loic
After the libgl1-mesa-dri package installation, the Display seems to work fine without crashing.

But as @ashik.p mentioned, there is Audio issue.
Playback via Headphones and speaker doesn’t work and only HDMI output is available by default. There isn’t any option to change the playback other than HDMI in Pulse audio configuration.
Previously, the audio was working. So, what could be the possible cause of this issue?
Any pointers to help??

Thanks in advance!

I need to check on my setup… I’ll try that friday.

@Loic @Naveena
Any update on this issue?

Any update about the issue @Loic?