Hide Forgot
Created attachment 487708 [details] Photo of kernel crash screen. Waking up xscreensaver resulted in the kernel panic pictured in the attached JPEG (I'm guessing due to a openGL app exiting). Hand transcribing the top few functions in the stack: kref_sub ttm_bo_list_ref_sub ttm_bo_reserve ? radeon unpin_work_func radeon_bo_reserve.constprop radeon_unpin_work_func process_one_work worker_thread kernel-2.6.38.1-6.fc15.x86_64
Created attachment 487709 [details] Older but clearer image of similar crash. This is a somewhat similar stack trace, captured from an older kernel 2.6.38-1.
In drivers/gpu/drm/ttm/ttm_bo.c:ttm_bo_reserve(): ttm_bo_list_ref_sub(bo, put_count, true); ttm_bo_list_ref_sub() was called with a put_count that would have resulted in freeing the bo_list, but never_free was set, causing ttm_bo_ref_bug() to be called. RSI is 0x54 in the dump, which probably means the put_count was 84, but I didn't confirm that.
What is your configuration ? (GPU + motherboard) Does this still happen with more recent software ?
GPU is integrated graphics HD3300 in an AMD 790GX chipset on a Gigabyte GA-MA790GP-DS4 motherboard. 01:05.0 VGA compatible controller [0300]: ATI Technologies Inc Radeon HD 3300 Graphics [1002:9614] I'll reboot with the latest F15 kernel & turn xscreensaver back on which should exhibit the bug within a day if it's still present.
Just opened bug 692250 for problem that I suspect is similar but with different symptoms. (Might well be same problem but newer kernel coping better).
Crash happened again with 2.6.38.2-8.fc15.x86_64. Photo'd stack trace again but doesn't appear significantly different from those attached already.
Created attachment 491122 [details] photo of same or similar oops I encountered what appears to be this issue with kernel-2.6.38.2-9.fc15.i686. 01:00.0 VGA compatible controller: ATI Technologies Inc M56P [Radeon Mobility X1600] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. A6J-Q008 Flags: bus master, fast devsel, latency 0, IRQ 44 Memory at c0000000 (32-bit, prefetchable) [size=256M] I/O ports at b000 [size=256] Memory at feff0000 (32-bit, non-prefetchable) [size=64K] Expansion ROM at fefc0000 [disabled] [size=128K] Capabilities: [50] Power Management version 2 Capabilities: [58] Express Legacy Endpoint, MSI 00 Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit+ Kernel driver in use: radeon Kernel modules: radeon photo of oops attached.
Does using lastest f15 package (kernel,ddx) still lead to such issue ?
I believe so. Setting xscreensaver to run random screensavers and then leaving for a while left the machine locked up with a black screen.
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