2009-06-29, 13:39
I've just run into a spate of hard lockups with XBMC where even sudo kill -9 PID won't kill xbmc.bin. Every single time I stopped playing a video I would get the blank screen of death. Nothing works from then on and there is no way to kill the xbmc.bin process.
I have just upgraded to Catalyst 9.6 and was testing out the ATI patch for improved vsync behavior (http://trac.xbmc.org/ticket/5951).
Tried with and without the patch installed, and with and without vsync enabled as well. Turning off "Sync Playback to Display" was what finally what let XBMC behave nicely after the video was stopped. The box has never had so many restarts!
http://pastebin.com/m7b895ee3
Furthermore, after trying to sudo kill -9 the xbmc.bin process it would start using 100% CPU and become a zombie (shows <defunct> after the process name in top).
I'm successfully now running with the ATI patch, vsync set to "Let Driver Decide" in XBMC and Vsync turned to "Always On" in the Catalyst Control Center. Adjust Refresh Rate is also turned on in XBMC and playback is pretty darn smooth.
Turning on "Sync Playback with Display" causes carnage though when a video stops. Hopefully this helps someone else out.
I have just upgraded to Catalyst 9.6 and was testing out the ATI patch for improved vsync behavior (http://trac.xbmc.org/ticket/5951).
Tried with and without the patch installed, and with and without vsync enabled as well. Turning off "Sync Playback to Display" was what finally what let XBMC behave nicely after the video was stopped. The box has never had so many restarts!
http://pastebin.com/m7b895ee3
Furthermore, after trying to sudo kill -9 the xbmc.bin process it would start using 100% CPU and become a zombie (shows <defunct> after the process name in top).
I'm successfully now running with the ATI patch, vsync set to "Let Driver Decide" in XBMC and Vsync turned to "Always On" in the Catalyst Control Center. Adjust Refresh Rate is also turned on in XBMC and playback is pretty darn smooth.
Turning on "Sync Playback with Display" causes carnage though when a video stops. Hopefully this helps someone else out.
