/usr/bin/Xorg:6:_list_del:list_del:__kgem_retire_rq:__kgem_retire_requests_upto:kgem_bo_retire
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | xf86-video-intel |
Fix Released
|
Medium
|
||
| | xserver-xorg-video-intel (Ubuntu) |
Medium
|
Robert Ancell | ||
Bug Description
The Ubuntu Error Tracker has been receiving reports about a problem regarding xorg-server. This problem was most recently seen with version 2:1.17.2-1ubuntu9, the problem page at https:/
| Changed in xorg-server (Ubuntu): | |
| assignee: | nobody → Robert Ancell (robert-ancell) |
| affects: | xorg-server (Ubuntu) → xserver-xorg-video-intel (Ubuntu) |
| Robert Ancell (robert-ancell) wrote : | #1 |
| Changed in xserver-xorg-video-intel (Ubuntu): | |
| importance: | Undecided → Medium |
Created attachment 118868
Stacktrack of crash
We're getting reports in Ubuntu 15.04 [1] [2] of crashes in the Intel driver. This seems to have occurred during the switch from 2.99.917 to a git snapshot from 8th August 2015.
I'm not able to reproduce this issue locally and inspection of the code has't made it clear to me if any changes since then have fixed the issue. Raising here in case someone recognises the problem and the commit that may have fixed it.
[1] https:/
[2] https:/
|
|
#4 |
That crash was fixed before then. Code inspection shows that it should be impossible to get that stacktrace now - I am dubious about the reports.
| Robert Ancell (robert-ancell) wrote : | #2 |
Upstream states that it is already fixed. Now I re-read the errors.ubuntu.com reports it last occurred in 2:1.17.2-1ubuntu9 - so it has almost certainly been fixed in the git snapshot.
| Changed in xserver-xorg-video-intel (Ubuntu): | |
| status: | New → Fix Released |
| Changed in xserver-xorg-video-intel: | |
| importance: | Unknown → Medium |
| status: | Unknown → Fix Released |
You were correct - the crash reports are coming from users who have not updated in the last three months. Sorry for the noise.


The time of these issue suggests this occurred when we switched from 2.99.917 to 2.99.917+ git20150808