Description of problem: xine-ui's on-screen display freezes the video playback beneath it. (Audio is unaffected.) Meanwhile, the dmesg log fills up with lots of errors like this: [drm:r100_cs_track_check] *ERROR* [drm] No buffer for color buffer 0 ! [drm:radeon_cs_ioctl] *ERROR* Invalid command stream ! My card is a Radeon 9550, so I've no idea why it's complaining in r100_cs_track_check. Version-Release number of selected component (if applicable): My kernel is 2.6.31.5-127.fc12.i686, and xorg-drv-ati is xorg-x11-drv-ati-6.13.0-0.10.20091006git457646d73.fc12.i686. How reproducible: Always Steps to Reproduce: 1. Configure xine to use Textured Video Xv. 2. Activate xine-ui's on-screen display while playing a video file. (Right-click on the video window to bring up the menu, then select "Stream" / "Information (OSD)".) Actual results: The OSD appears correctly, but the video beneath it freezes until the OSD disappears again. Expected results: The OSD should overlay the video as it plays. Additional info: I have attached the dmesg output from when my PC boots.
Created attachment 372909 [details] dmesg output from booted kernel (before the problem) The output after the problem isn't particularly interesting - just: [drm:r100_cs_track_check] *ERROR* [drm] No buffer for color buffer 0 ! [drm:radeon_cs_ioctl] *ERROR* Invalid command stream ! over and over again.
I can also reproduce this problem with a stock 2.6.31.6 kernel, except in this case I get the following error messages instead: [drm:r300_cs_track_check] *ERROR* [drm] No buffer for color buffer 0 ! [drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
This bug still happens with the following packages: xorg-x11-drv-ati-6.13.0-0.11.20091119git437113124.fc12.i686 libdrm-2.4.15-5.fc12.i686 mesa-dri-drivers-7.6-0.15.fc12.i686 mesa-libGL-7.6-0.15.fc12.i686 kernel-2.6.31.5-127.fc12.i686
This bug still exists with the following packages: libdrm-2.4.17-1.fc12.i686 mesa-dri-drivers-7.7-2.fc12.i686 mesa-libGL-7.7-2.fc12.i686 The kernel is stock 2.6.32.4, and the xorg-x11-drv-ati driver is from git (as of 2010-Jan-19). The dmesg output is now: [drm:r100_cs_track_check] *ERROR* [drm] No buffer for color buffer 0 ! [drm:radeon_cs_ioctl] *ERROR* Invalid command stream ! Both my rv100 and rv280 experience a similar bug, albeit with more serious consequences. In their cases, the X-server stops responding and must be restarted via a console, although the GPU continues to function.
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. 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 '12'. 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 12'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 12 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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
This bug is fixed in xf86-video-ati git, and has been for some time. The next update of Fedora's driver should fix it, if it's not fixed already.
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.