Description of problem: It happened shortly after getting to the "practice" part of extremetuxracer. I'm not sure how reproducible it is yet. Version-Release number of selected component: extremetuxracer-0.4-10.fc18 Additional info: backtrace_rating: 4 cmdline: etracer crash_function: drm_intel_bo_reference executable: /usr/bin/etracer kernel: 3.8.2-206.fc18.i686.PAE uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #1 drm_intel_bo_reference at intel_bufmgr.c:74 #2 intel_flush_prim at intel_tris.c:214 #4 intel_get_prim_space at intel_tris.c:174 #5 intelFastRenderClippedPoly at intel_tris.c:929 #6 clip_tri_4 at ../../../src/mesa/tnl/t_vb_cliptmp.h:259 #7 clip_elt_triangles at ../../../src/mesa/tnl/t_vb_render.c:174 #8 run_render at ../../../src/mesa/tnl/t_vb_render.c:321 #9 _tnl_run_pipeline at ../../../src/mesa/tnl/t_pipeline.c:163 #10 intelRunPipeline at intel_tris.c:1086 #11 _tnl_draw_prims at ../../../src/mesa/tnl/t_draw.c:524
Created attachment 710429 [details] File: backtrace
Created attachment 710430 [details] File: cgroup
Created attachment 710431 [details] File: core_backtrace
Created attachment 710432 [details] File: dso_list
Created attachment 710433 [details] File: environ
Created attachment 710434 [details] File: limits
Created attachment 710435 [details] File: maps
Created attachment 710436 [details] File: open_fds
Created attachment 710437 [details] File: proc_pid_status
Created attachment 710438 [details] File: var_log_messages
The crash happens deep down in Mesa, in an Intel-specific code path. Changing component.
Some additional information that may be handy: The error only happens in full-screen mode, but when I ran it in an 800x600-sized separate window, it runs OK. The error occurs on this laptop, with an Intel i945GME chipset (as reported by memtest86+), but on another Intel-based laptop, with a GM965 chipset, it works quite well. Let me know if you need additional info on these environments, or if you have further tests for me to perform.
I'm pleased to report that the error no longer happens with the recent update to kernel 3.8.3-201.fc18.i686.PAE. The prior kernel version 3.8.2-206.fc18.i686.PAE still exhibits the problem. Although I don't know how to retrieve the changelog at this point, I vaguely remember an update to the Intel video driver within the kernel when reviewing the updates.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.