Created attachment 73686 [details] dmesg /var/log/Xorg.0.log is full with: [ 1599.434] (WW) RADEON(0): flip queue failed: Device or resource busy [ 1599.434] (WW) RADEON(0): Page flip failed: Device or resource busy running up-to-date gentoo-system, with the following (unstable) packages linux-3.8.0-rc5 compiled a few minutes ago xorg-server-1.13.1 compiled a few minutes ago libdrm from git compiled a few minutes ago mesa from git compiled a few minutes ago xf86-video-ati from git compiled a few minutes ago 01:05.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RS880 [Radeon HD 4290] my system is working as an htpc and is running fine, no crashes or oops slim is login my user and starts xbmc automatic xbmc in fullscreen is the only graphical application the system is connected to my tv through hdmi if i switch with my remote through the xbmc-menu or watch a video the xorg-log is spam the whole time with page filp errors if i leave xbmc alone, so the log is spam every few seconds with page flip errors is this related to this bug? https://bugs.freedesktop.org/show_bug.cgi?id=58659 my system is working fine, no crashes or oops so far
Created attachment 73687 [details] Xorg.0.log
Do you still have the issue with the latest 3.8 kernel from Linus that contains the patch mentioned in the last comment in bug 58659?
using linux-3.8.0-rc5
compiled mesa again from master git branch (tree 7cbc1aafe166dd925c5626c7118f523c8b75ae6d) and got this in dmesg [ 9.917097] glxinfo[2482]: segfault at 0 ip (null) sp 00007ffffc441708 error 14 in glxinfo[400000+6000] in the end, xbmc doesn't show up i went back to mesa-9.0.2 and linux-3.8.0-rc5 also here, the Xorg.0.log is spam the whole time with flip errors the same is with linux-3.7.4 and mesa-9.0.2 i never had a look at my Xorg.0.log when i was using linux-3.7.x and mesa-9.0.x hmm ... the log-spam was always there? so what is causing to spam the Xorg.0.log with these flip errors?
(In reply to comment #5) > if i switch with my remote through the xbmc-menu or watch a video the > xorg-log is spam the whole time with page filp errors While that is happening, can you write 2 to /sys/module/drm/parameters/debug and capture some debugging output from dmesg?
* today i recompiled mesa from master git (tree d276e9294d1f1218e374d43c1320b376ee265ad4) and linux-3.8.0-rc5 * xbmc is starting and working fine again * the flip errors still appears in /var/log/Xorg.0.log * with "echo 2 > /sys/module/drm/parameters/debug" nothing special in dmesg (watched a 40min-video) * "echo 1 > /sys/module/drm/parameters/debug" gives a bunch of lines (see attachment dmesg_debug_1 )
Created attachment 73865 [details] dmesg_debug_1
(In reply to comment #6) > * with "echo 2 > /sys/module/drm/parameters/debug" nothing special in dmesg Hmm, so maybe the EBUSY error is coming from this code in drm_mode_page_flip_ioctl(): if (crtc->fb == NULL) { /* The framebuffer is currently unbound, presumably * due to a hotplug event, that userspace has not * yet discovered. */ ret = -EBUSY; goto out; } What does xrandr --current say when the problem occurs? After that, does running xrandr without arguments make any difference?
an option in my xorg.conf is causing the spam of flip errors in Xorg.0.log Section "Monitor" Identifier "Denon-AVAMP" ---> #Option "Enable" "true" <---- Modeline "1920x1080" 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync EndSection if "Option Enable true" in the monitor section is commented out, then there is no log spam this is a left over to force the hdmi-output to 1920x1080 with the Denon-AVAMP off ... but i had no luck
So this was a configuration error and can be resolved as not a bug?
imho .. spam the log with flip errors, when set this option should not happen the Xorg.0.log was some days about 80MB big bit, feel free ... it's up to you
I have found this issue today at FOSDEM after disconnecting the VGA cable from the projector (not sure if before or after putting the computer to sleep). When I came back, this wasw happening and xrandr showed what follows: Screen 0: minimum 320 x 200, current 1366 x 768, maximum 8192 x 8192 LVDS connected 1366x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm 1366x768 59.9*+ 1280x720 59.9 1152x768 59.8 1024x768 59.9 800x600 59.9 848x480 59.7 720x480 59.7 640x480 59.4 HDMI-0 disconnected (normal left inverted right x axis y axis) VGA-0 disconnected 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm 1024x768 (0x6c77) 65.0MHz h: width 1024 start 1048 end 1184 total 1344 skew 0 clock 48.4KHz v: height 768 start 771 end 777 total 806 clock 60.0Hz After running xrandr --output VGA-0 --off to turn VGA off it worked again.
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/325.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.