|
Bugzilla – Full Text Bug Listing |
| Summary: | KDE desktop crashes with qxl driver warning | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Distribution | Reporter: | Niblick <nixbugz> |
| Component: | X.Org | Assignee: | E-mail List <xorg-maintainer-bugs> |
| Status: | RESOLVED WONTFIX | QA Contact: | E-mail List <xorg-maintainer-bugs> |
| Severity: | Minor | ||
| Priority: | P4 - Low | CC: | nixbugz |
| Version: | 13.2 | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | openSUSE 13.2 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
Xorg.1.log.old: (EE) qxl(0): error doing QXL_ALLOC
Xorg.0.log.old: (EE) Couldn't init device "ImExPS/2 Generic Explorer Mouse" Xorg logs and systemd journal |
||
|
Description
Niblick
2016-05-06 07:39:33 UTC
Just a warning. Minor (In reply to NIk Zbugz from comment #0) > > Would it be possible to port these fixes to openSUSE? I don't see any patches mentioned in there. Just that some updated fixed issues with QXL. It is not at all clear what the cause of the KDE crash is and whether the warning is related to it. Have you tried a later version of openSUSE - ie. Leap 42.1? Also, please supply the X.org log file - /var/log/Xorg.0.log(.old). '.old' when the Xserver has restarted already after a crash occurred. I've backported a bunch of crash fixes to 13.2 now. You need to add: http://download.opensuse.org/repositories/home:/eeich:/branches:/OBS_Maintained:/xf86-video-qxl/openSUSE_13.2_Update/ As repo and update the xf86-video-qxl. (In reply to Egbert Eich from comment #1) > Just a warning. Minor It may be minor to you but I lose work when it happens. (In reply to Egbert Eich from comment #2) > (In reply to NIk Zbugz from comment #0) > > > > Would it be possible to port these fixes to openSUSE? > > I don't see any patches mentioned in there. Just that some updated fixed > issues with QXL. > I don't know how code from Red Hat is or might be included in openSUSE or if the Red Hat update is all or nothing. > It is not at all clear what the cause of the KDE crash is and whether the > warning is related to it. How can I narrow down the cause or causes? > Have you tried a later version of openSUSE - ie. Leap 42.1? No, I could set one up but don't have the time for the hours of use necessary to provoke it into falling over. Created attachment 676026 [details]
Xorg.1.log.old: (EE) qxl(0): error doing QXL_ALLOC
The crashes happen mostly when I have 2 desktops open via Switch User and mostly on the second desktop, as here.
Created attachment 676027 [details]
Xorg.0.log.old: (EE) Couldn't init device "ImExPS/2 Generic Explorer Mouse"
(In reply to Egbert Eich from comment #3) > Also, please supply the X.org log file - /var/log/Xorg.0.log(.old). '.old' > when the Xserver has restarted already after a crash occurred. See the 2 attachments. The QXL_ALLOC error is more common but I've included the other because it was there. I could look through old log files to see if there are other errors. > > I've backported a bunch of crash fixes to 13.2 now. > You need to add: > http://download.opensuse.org/repositories/home:/eeich:/branches:/ > OBS_Maintained:/xf86-video-qxl/openSUSE_13.2_Update/ > As repo and update the xf86-video-qxl. Thank you, I'll try that. (In reply to NIk Zbugz from comment #5) > No, I could set one up but don't have the time for the hours of use > necessary to provoke it into falling over. To me this is not really a strong argument. There is no such thing like a free lunch. I do this in my spare time as well. If you think since I've got a SUSE email address, this is my work and obligation then I'd have a 12 to 14 h work day ;) Regardless, (In reply to NIk Zbugz from comment #6) > Created attachment 676026 [details] > Xorg.1.log.old: (EE) qxl(0): error doing QXL_ALLOC > This looks like a memory leak issue. Several of those have been fixed in the patches I've backported now. (In reply to NIk Zbugz from comment #8) > > I've backported a bunch of crash fixes to 13.2 now. > > You need to add: > > http://download.opensuse.org/repositories/home:/eeich:/branches:/ > > OBS_Maintained:/xf86-video-qxl/openSUSE_13.2_Update/ > > As repo and update the xf86-video-qxl. > > Thank you, I'll try that. Ok, thanks! Nik, any news here? Yes Egbert there is news but not good news. I installed xf86-video-qxl 0.1.2-2.5.1 on openSUSE 13.2 but it still falls over: opensuse:~ # journalctl -b|grep qxl_ttm.c May 14 11:01:10 opensuse kernel: WARNING: CPU: 3 PID: 3474 at ../drivers/gpu/drm/qxl/qxl_ttm.c:414 qxl_sync_obj_wait+0x172/0x1f0 [qxl]() May 15 07:13:59 opensuse kernel: WARNING: CPU: 0 PID: 20212 at ../drivers/gpu/drm/qxl/qxl_ttm.c:414 qxl_sync_obj_wait+0x172/0x1f0 [qxl]() May 17 04:04:18 opensuse kernel: WARNING: CPU: 3 PID: 31395 at ../drivers/gpu/drm/qxl/qxl_ttm.c:414 qxl_sync_obj_wait+0x172/0x1f0 [qxl]() May 17 04:04:41 opensuse kernel: WARNING: CPU: 1 PID: 27309 at ../drivers/gpu/drm/qxl/qxl_ttm.c:414 qxl_sync_obj_wait+0x172/0x1f0 [qxl]() May 17 04:04:51 opensuse kernel: WARNING: CPU: 2 PID: 27524 at ../drivers/gpu/drm/qxl/qxl_ttm.c:414 qxl_sync_obj_wait+0x172/0x1f0 [qxl]() May 17 04:12:29 opensuse kernel: WARNING: CPU: 2 PID: 27847 at ../drivers/gpu/drm/qxl/qxl_ttm.c:414 qxl_sync_obj_wait+0x172/0x1f0 [qxl]() May 17 04:13:39 opensuse kernel: WARNING: CPU: 1 PID: 28431 at ../drivers/gpu/drm/qxl/qxl_ttm.c:414 qxl_sync_obj_wait+0x172/0x1f0 [qxl]() May 17 04:15:16 opensuse kernel: WARNING: CPU: 2 PID: 28770 at ../drivers/gpu/drm/qxl/qxl_ttm.c:414 qxl_sync_obj_wait+0x172/0x1f0 [qxl]() opensuse:~ # I will attach the Xorg logs and systemd journal. The last few entries are where it doesn't quite get to the desktop after logging in before reverting to the login screen. Created attachment 677142 [details]
Xorg logs and systemd journal
Ok, then I'm sorry - I can't help you. Investigating this will simply cost too much time which I'm not able to invest. Sorry again. This is an autogenerated message for OBS integration: This bug (978785) was mentioned in https://build.opensuse.org/request/show/396131 13.2 / xf86-input-vmmouse The situation is so complicated as the logs show several failures: 1. Crash in vmmouse driver 2. Vmmouse driver fails to reinitialize the device. 3. Cannot get DRM master upon VT switch. 4. Not able to allocate framebuffer. 1. and 4.seem to be a consequence of a memory leak in the kernel. I've fixed 1. now, but this doesn't solve the memory leak so it will fail with 4. 2. and 3. could be races due to switches between different user sessions. Fixing them may require a lengthy investigation. 3. could even be caused by Plymouth. So even without the memory leak, problems would still remain. Well that's disappointing but thanks for the work you have done on this. I'm not sure about no. 1: are you saying it's fixed in vmmouse but it will still fail elsewhere until 4 is fixed (and if it is fixed, where can I find the new code)? How do I get the other bugs fixed? Should I add 2, 3 and 4 as new bugs and if so, here or somewhere else? I've disabled Plymouth so I'll see how that goes. I expect no. 4 will be present in any distribution but I could try another desktop to try to avoid 2 & 3. Is there an alternative to vmmouse? I'm surprised to be the only one apparently suffering these crashes: does no-one else use more than one login session with spice or is it something else? openSUSE-RU-2016:1394-1: An update that has one recommended fix can now be installed. Category: recommended (moderate) Bug References: 978785 CVE References: Sources used: openSUSE 13.2 (src): xf86-input-vmmouse-13.0.0-11.3.1 |