Hide Forgot
Description of problem: Playing neverball in kde (in that case, amarok was playing and opera/firefox was opened) screen flickered and went black... i was able to switch to another vt, verified that something crashed in the kernel and went back an ctrl+alt+backspace. Version-Release number of selected component (if applicable): kernel 2.6.40.6-0.fc15.x86_64 xorg-x11-drv-ati.x86_64 6.14.1-2.20110525gitfe5c42f51.fc15 neverball.x86_64 1.5.4-4.fc15 How reproducible: sometimes Steps to Reproduce: 1. neverball 2. 3. Actual results: black screen, vt switch works, reboot not requiered to restore functionality but xorg must be restarted. (amarok keeps playing songs...) Expected results: Additional info: I have experienced crashes in the past with neverball, will check. In xorg, i think that the offendig stuff is: (WW) RADEON(0): flip queue failed: Device or resource busy (WW) RADEON(0): Page flip failed: Device or resource busy And in dmesg: BUG: sleeping function called from invalid context at kernel/mutex.c:85 in_atomic(): 0, irqs_disabled(): 1, pid: 1944, name: X Pid: 1944, comm: X Not tainted 2.6.40.6-0.fc15.x86_64 #1 Call Trace: [<ffffffff81047514>] __might_sleep+0xeb/0xf0 [<ffffffff814878f9>] mutex_lock+0x24/0x4a [<ffffffff81488703>] ? _raw_write_unlock_irqrestore+0x1b/0x1d [<ffffffffa00a4037>] drm_gem_object_unreference_unlocked+0x24/0x40 [radeon] [<ffffffffa00a4610>] radeon_crtc_page_flip+0x438/0x467 [radeon] [<ffffffffa0022753>] drm_mode_page_flip_ioctl+0x165/0x1b1 [drm] [<ffffffffa00157ff>] drm_ioctl+0x29e/0x37b [drm] [<ffffffffa00225ee>] ? drm_mode_gamma_get_ioctl+0x10f/0x10f [drm] [<ffffffff811f68e8>] ? inode_has_perm+0x32/0x34 [<ffffffff811f6991>] ? file_has_perm+0xa7/0xc9 [<ffffffff811350de>] do_vfs_ioctl+0x460/0x4a1 [<ffffffff81135175>] sys_ioctl+0x56/0x79 [<ffffffff8148ed02>] system_call_fastpath+0x16/0x1b 02:00.0 VGA compatible controller [0300]: ATI Technologies Inc Redwood [Radeon HD 5670] [1002:68d8]
I managed to repeat it after some minutes: messages: * nothing xorg.log.old: [ 41204.806] (II) RADEON(0): Modeline "1680x1050"x0.0 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz) [ 41346.420] (WW) RADEON(0): flip queue failed: Device or resource busy [ 41346.420] (WW) RADEON(0): Page flip failed: Device or resource busy [ 41346.428] (WW) RADEON(0): flip queue failed: Device or resource busy [ 41346.428] (WW) RADEON(0): Page flip failed: Device or resource busy [ 41357.916] (II) AIGLX: Suspending AIGLX clients for VT switch I played neverball, passed some levels. I used it in full-sceen 1920x1080 and with music disabled, sound enabled. Amarok was playing music. but i noticed that the flicker that dooms neverball & xorg may be related to amarok's song change notification. it flickers when songs change, and some moments after the fliker, it freezes. luckily, vt switch works. killing neverball manually -even -9- does not recover xorg. i have replaced the motherboard, now using 990FX chipset, the vga is the same. 01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Redwood [Radeon HD 5670] [1002:68d8] Versions: kernel = 2.6.41.1-1.fc15.x86_64 neverball.x86_64 1.5.4-4.fc15 xorg-x11-drv-ati.x86_64 6.14.1-2.20110525gitfe5c42f51.fc15 amarok.x86_64 2.4.3-1.fc15 When i play normally (with both music and sound and no amarok) it does not crash.
you get the same with the 2.6.41.1-1 kernel? I thought the fix was in the 3.1 kernel.
It is the same result, but at log/error level, with 2.6.41.1-1 there is no errors in messages, just the xorg flip queue and the stuck xorg. I did not see any messages. I today also upgraded the cpu to an FX6100, let's see if it is still there. When i assemble back the old machine, i will also try to reproduce it.
Happened again, i am sure that it happens when amarok changes songs, the pop-up appears in neverball and after a while (it slightly slows down neverball), then blink, then neverball gets frozen and xorg must be restarted. kernel 2.6.41.1-1.fc15.x86_64 There are no more messages in the kernel, just the xorg logfile messages: [ 57713.016] (WW) RADEON(0): flip queue failed: Device or resource busy [ 57713.016] (WW) RADEON(0): Page flip failed: Device or resource busy [ 57713.023] (WW) RADEON(0): flip queue failed: Device or resource busy [ 57713.023] (WW) RADEON(0): Page flip failed: Device or resource busy Maybe there where two bugs, and the kernel one got fixed. I tried to reproduce it with f16, but strangely it does not have any sound whatsoever (but that is another issue).
Playing neverball, with sounds and no music (background music using amarok). Just after the amarok song change pop-up, that somewhat appears briefly, these is a very short time in wich neverball works choppy and then screen flickers and stalls until ctrl+alt+backspace. No kernel messages. Definitively, the amarok song change poput triggers it most of the time. Shoudl i open a bug-report upstream (kde)? [ 1684.813] (WW) RADEON(0): flip queue failed: Device or resource busy [ 1684.813] (WW) RADEON(0): Page flip failed: Device or resource busy [ 1684.823] (WW) RADEON(0): flip queue failed: Device or resource busy [ 1684.823] (WW) RADEON(0): Page flip failed: Device or resource busy kernel 2.6.41.4-1.fc15.x86_64 xorg-x11-drv-ati.x86_64 6.14.1-2.20110525gitfe5c42f51.fc15
If i play it with amarok configured with the notification pop-up disabled, it does not happen.
I replaced the VGA (finally a FANLESS VGA, let's see how it performs/melts...) , and i can reproduce it enabling amarok's notification (default/transparency). It crashed neverball on the first song change with this card also. New affected VGA: VGA compatible controller [0300]: ATI Technologies Inc NI Caicos [AMD RADEON HD 6450] [1002:6779] So: Evergreen:Redwood (XFX HD5670) N.Islands:Caicos (XFX HD6450) Have these 'page flip' issues. I saw that there are some package in testing. I will update kernel, ati and gl stuff. Then i will retest.
Tesed again with these packages updated: Dec 20 21:03:37 ulquiorra yum[3378]: Installed: mesa-dri-filesystem-7.11.2-1.fc15.i686 Dec 20 21:03:37 ulquiorra yum[3378]: Updated: mesa-dri-filesystem-7.11.2-1.fc15.x86_64 Dec 20 21:03:39 ulquiorra yum[3378]: Installed: mesa-dri-drivers-7.11.2-1.fc15.x86_64 Dec 20 21:03:39 ulquiorra yum[3378]: Updated: mesa-libGL-7.11.2-1.fc15.x86_64 Dec 20 21:03:44 ulquiorra yum[3378]: Installed: kernel-2.6.41.5-4.fc15.x86_64 Dec 20 21:03:44 ulquiorra yum[3378]: Installed: libffi-3.0.10-1.fc15.i686 Dec 20 21:03:44 ulquiorra yum[3378]: Updated: xorg-x11-drv-ati-6.14.2-1.20110921gitd78860ba5.fc15.x86_64 Dec 20 21:03:44 ulquiorra yum[3378]: Updated: mesa-libGLU-7.11.2-1.fc15.x86_64 Dec 20 21:03:45 ulquiorra yum[3378]: Installed: llvm-libs-2.8-14.fc15.i686 Dec 20 21:03:47 ulquiorra yum[3378]: Installed: mesa-dri-drivers-7.11.2-1.fc15.i686 Dec 20 21:03:47 ulquiorra yum[3378]: Updated: mesa-libGL-7.11.2-1.fc15.i686 Dec 20 21:03:47 ulquiorra yum[3378]: Updated: mesa-libGLU-7.11.2-1.fc15.i686 Dec 20 21:03:47 ulquiorra yum[3378]: Erased: mesa-dri-llvmcore Also still found these in xorg logs: [ 309.648] (WW) RADEON(0): flip queue failed: Device or resource busy [ 309.648] (WW) RADEON(0): Page flip failed: Device or resource busy [ 519.173] (WW) RADEON(0): flip queue failed: Device or resource busy [ 519.173] (WW) RADEON(0): Page flip failed: Device or resource busy [ 643.280] (WW) RADEON(0): flip queue failed: Device or resource busy [ 643.280] (WW) RADEON(0): Page flip failed: Device or resource busy So, the previous xorg freeze was messageless... i really thought that these were fatal errors (even if they were warnings). Probably there were three bugs, the kernel one, the freeze, and the slowdown one. And found that neverball NO LONGER FREEZES (time will tell) xorg, but the slowdown while the notification is displayed still persists. It is an improvement over previous status. Regarding the notification, it is correct for it to be displayed on a full-screen open-gl application? Disabling such notification is the current workaround. (even if it does not crash, the slowdown makes your ball to fall to the void...).
On F17, this does not happen. I no longer have F15.
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached 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" (top right of this page) 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