Created attachment 26546 [details] Xorg.0.log.bz2 I've been seeing occasional hard locking of X when I change the size of my video player from windowed to full screen or from full screen to windowed. Here's my setup: Debian Squeeze AMD64 Kernel 2.6.30-rc5 (self compiled) Xorg 7.4 (self-compiled) Gnome 2.26.1 (debian packages) Totem 2.26.2 (debian package) radeonhd (I git pull every 2-3 days.) drm (native, built into kernel 2.6.30) Two 1920x1200 panels over DVI DVI-I_1/digital is Left Panel DVI-I_2/digital is Right Panel I've been using randr to disable the left monitor when I watch videos. This seems to be a necessary condition for the bug. I see the bug when running totem on the remaining right display. X locks hard when totem transitions between full screen and windowed mode. It happens on both directions. All keyboard input is ignored. I have to ssh in and kill X. It's always at 100% cpu utilization. This doesn't happen on every transition between windowed and full screen but it happens often enough. I've been using the power switch to disable my left monitor. I want to verify that the bug happens only when randr is used to disable the left screen. It has been proven true so far. I have tried the "radeon-test-ring.patch" from Bug 21849. It didn't help. The logs attached were produced wile running a kernel with that patch.
Created attachment 26547 [details] /var/log/messages.bz2
I hit this bug again but under different circumstances. I launched SMPlayer to watch a program. As soon as SMPlayer initialized its overlay X crashed. It was unkillable. I had to reboot. The video in question was in 1920x1080 resolution. It was an American terrestrial HDTV broadcast.
-- 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/48.
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.