Created attachment 537791 [details] Backtrace screenshot with EIP at nouveau_fence_update Description of problem: Oops, backtrace in screenshot. Version-Release number of selected component (if applicable): kernel-3.1.1-2.fc16.i686 from http://koji.fedoraproject.org/koji/taskinfo?taskID=3545261 xorg-x11-drv-nouveau-0.0.16-27.20110720gitb806e3f.fc16.i686 My hardware's smolt page is at http://www.smolts.org/client/show/pub_eafd4357-c35b-4b7f-8ead-ce167a9052c0 F16 up-to-date in a Dell Inspiron 9300 laptoop with NV41.8 [GeForce Go 6800]. How reproducible: 1) Once "[drm] nouveau 0000:01:00.0: GPU lockup - switching to software > fbcon" 2) Once "EIP is at nouveau_fence_update+0xe/0xa5 [nouveau]" Steps to Reproduce: To get this, I have glxgears running, and I was loading/reloading the fft-atlas page mentioned above, and hitting Ctrl-Alt-PgUp/PgDn randomly. Actual results: 1) Mouse cursor moving, no other updates to screen 2) Oops window, backtrace screenshot attached (point-and-shoot version). Expected results: Additional info: Perhaps related bugs https://bugs.freedesktop.org/show_bug.cgi?id=40642 https://bugs.freedesktop.org/show_bug.cgi?id=38931 I will try to find an easy pattern to reproduce the bug.
Reproducible with kernel-3.1.4-1.fc16.i686 as well. Start two glxgears on one workspace, Firefox on another workspace. Switch between workspaces randomly Ctrl+Alt+Up/Down in gnome. Wait a bit. => Drops to console, mouse pointer moves, keyboard does not respond. Should the compoonent be 'kernel' instead of 'xorg-x11-drv-nouveau'?
*** Bug 768692 has been marked as a duplicate of this bug. ***
I believe I have solved this issue now, but it's very hard to say with this kind of bug. I may just not be triggering it. I've posted a scratch build [1] for you guys to test and see if it's gone away for you too. It hasn't finished building at the time I'm posting this, but it should be done in an hour or two. Thanks! Ben. [1] http://koji.fedoraproject.org/koji/taskinfo?taskID=3634340
Tested current kernel-3.1.7-1.fc16.i686 and koji kernel-3.1.8-3.fc16.i686. 3.1.7 crashed in ~3 minutes, 3.1.8 did not even after trying hard for ~15 min. Promising! Testing with glxgears, sometimes the window goes completely black and does not recover. However, no crashing.
(In reply to comment #4) > Tested current kernel-3.1.7-1.fc16.i686 and koji kernel-3.1.8-3.fc16.i686. > 3.1.7 crashed in ~3 minutes, 3.1.8 did not even after trying hard for ~15 min. > Promising! Great! > > Testing with glxgears, sometimes the window goes completely black and does not > recover. However, no crashing. Hmm, I don't think the patch fixing this issue can cause this problem.
(In reply to comment #5) > (In reply to comment #4) > > Testing with glxgears, sometimes the window goes completely black and does not > > recover. However, no crashing. > > Hmm, I don't think the patch fixing this issue can cause this problem. Sorry for bringing up some other issue. With earlier kernels, the glxgears window going black used to be a precursor to the lockup, but not anymore. This patched kernel works for me.
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. 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 '16'. 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 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 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 to click on "Clone This Bug" and open it against that version of Fedora. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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. Thank you for reporting this bug and we are sorry it could not be fixed.