[Bug 50892] New: Invalid command stream with TURKS running Cinnamon

* [Bug 50892] New: Invalid command stream with TURKS running Cinnamon
@ 2012-06-08 18:13 bugzilla-daemon
  2012-06-08 18:18 ` [Bug 50892] " bugzilla-daemon
                   ` (13 more replies)
  0 siblings, 14 replies; 15+ messages in thread
From: bugzilla-daemon @ 2012-06-08 18:13 UTC (permalink / raw)
  To: dri-devel

https://bugs.freedesktop.org/show_bug.cgi?id=50892

             Bug #: 50892
           Summary: Invalid command stream with TURKS running Cinnamon
    Classification: Unclassified
           Product: DRI
           Version: XOrg CVS
          Platform: x86-64 (AMD64)
        OS/Version: Linux (All)
            Status: NEW
          Severity: major
          Priority: medium
         Component: DRM/Radeon
        AssignedTo: dri-devel@lists.freedesktop.org
        ReportedBy: zboszor@pr.hu

I got these errors on my AMD A4-3300 notebook (ASUS K53TA) after I upgraded to
kernel 3.4.0 and xorg-x11-drv-ati-6.14.4-6.20120602git930760942 yesterday
evening (CET):

Jun  7 19:26:41 localhost kernel: [  889.757979] radeon 0000:00:01.0:
evergreen_cs_track_validate_cb:439 cb[0] bo too small (layer size 18874368,
offset 0, max layer 1, bo size 4718592, slice 18431)
Jun  7 19:26:41 localhost kernel: [  889.757986] radeon 0000:00:01.0:
evergreen_cs_track_validate_cb:443 problematic surf: (1536 768) (4 4 1 1 1 64
1)
Jun  7 19:26:41 localhost kernel: [  889.757989] radeon 0000:00:01.0:
evergreen_packet3_check:2055 invalid cmd stream 2587
Jun  7 19:26:41 localhost kernel: [  889.757993] [drm:radeon_cs_ib_chunk]
*ERROR* Invalid command stream !
Jun  7 19:26:50 localhost systemd-tmpfiles[1176]: Successfully loaded SELinux
database in 20ms 513us, size on heap is 532K.
Jun  7 19:26:50 localhost systemd-tmpfiles[1176]: stat(/run/user/zozo/gvfs)
failed: Permission denied
Jun  7 19:27:04 localhost kernel: [  913.093258] radeon 0000:00:01.0:
evergreen_cs_track_validate_cb:439 cb[0] bo too small (layer size 10223616,
offset 0, max layer 1, bo size 2555904, slice 9983)
Jun  7 19:27:04 localhost kernel: [  913.093272] radeon 0000:00:01.0:
evergreen_cs_track_validate_cb:443 problematic surf: (1024 624) (4 4 1 1 1 64
1)
Jun  7 19:27:04 localhost kernel: [  913.093280] radeon 0000:00:01.0:
evergreen_packet3_check:2055 invalid cmd stream 5344
Jun  7 19:27:04 localhost kernel: [  913.093286] [drm:radeon_cs_ib_chunk]
*ERROR* Invalid command stream !
Jun  7 19:27:05 localhost kernel: [  914.074877] radeon 0000:00:01.0:
evergreen_cs_track_validate_texture:796 texture bo too small (layer size
10223616, offset 0, max layer 1, depth 1, bo size 2555904) (1024 624)
Jun  7 19:27:05 localhost kernel: [  914.074883] [drm:radeon_cs_ib_chunk]
*ERROR* Invalid command stream !
Jun  7 19:27:06 localhost kernel: [  915.073121] radeon 0000:00:01.0:
evergreen_cs_track_validate_texture:796 texture bo too small (layer size
10223616, offset 0, max layer 1, depth 1, bo size 2555904) (1024 624)
Jun  7 19:27:06 localhost kernel: [  915.073127] [drm:radeon_cs_ib_chunk]
*ERROR* Invalid command stream !
Jun  7 19:27:06 localhost kernel: [  915.166232] radeon 0000:00:01.0:
evergreen_cs_track_validate_texture:796 texture bo too small (layer size
10223616, offset 0, max layer 1, depth 1, bo size 2555904) (1024 624)
Jun  7 19:27:06 localhost kernel: [  915.166237] [drm:radeon_cs_ib_chunk]
*ERROR* Invalid command stream !
Jun  7 19:27:07 localhost kernel: [  915.193506] radeon 0000:00:01.0:
evergreen_cs_track_validate_texture:796 texture bo too small (layer size
10223616, offset 0, max layer 1, depth 1, bo size 2555904) (1024 624)
Jun  7 19:27:07 localhost kernel: [  915.193511] [drm:radeon_cs_ib_chunk]
*ERROR* Invalid command stream !
Jun  7 19:27:07 localhost kernel: [  915.291245] radeon 0000:00:01.0:
evergreen_cs_track_validate_texture:796 texture bo too small (layer size
10223616, offset 0, max layer 1, depth 1, bo size 2555904) (1024 624)
Jun  7 19:27:07 localhost kernel: [  915.291251] [drm:radeon_cs_ib_chunk]
*ERROR* Invalid command stream !
Jun  7 19:27:07 localhost kernel: [  915.317023] radeon 0000:00:01.0:
evergreen_cs_track_validate_texture:796 texture bo too small (layer size
10223616, offset 0, max layer 1, depth 1, bo size 2555904) (1024 624)
Jun  7 19:27:07 localhost kernel: [  915.317028] [drm:radeon_cs_ib_chunk]
*ERROR* Invalid command stream !
Jun  7 19:27:07 localhost kernel: [  915.327642] radeon 0000:00:01.0:
evergreen_cs_track_validate_texture:796 texture bo too small (layer size
10223616, offset 0, max layer 1, depth 1, bo size 2555904) (1024 624)
Jun  7 19:27:07 localhost kernel: [  915.327649] [drm:radeon_cs_ib_chunk]
*ERROR* Invalid command stream !
Jun  7 19:27:07 localhost kernel: [  915.343749] radeon 0000:00:01.0:
evergreen_cs_track_validate_texture:796 texture bo too small (layer size
10223616, offset 0, max layer 1, depth 1, bo size 2555904) (1024 624)
Jun  7 19:27:07 localhost kernel: [  915.343761] [drm:radeon_cs_ib_chunk]
*ERROR* Invalid command stream !
Jun  7 19:27:07 localhost kernel: [  915.360748] radeon 0000:00:01.0:
evergreen_cs_track_validate_texture:796 texture bo too small (layer size
10223616, offset 0, max layer 1, depth 1, bo size 2555904) (1024 624)
Jun  7 19:27:07 localhost kernel: [  915.360760] [drm:radeon_cs_ib_chunk]
*ERROR* Invalid command stream !

At first I thought I had to RMA the notebook because the display only showed a
single horizontal line in the middle of the screen. Rebooting the machine
showed various problems: missing icons (like the "faces" icon for users on the
GDM screen) and after logging in various bluish - magentaish rectangles on the
screen. Rebooting back to 3.3.7 at the time didn't fix the problem but after
yum reinstall "*" at least 3.3.7-1.fc17 is usable. 3.4.0-1.fc17 reliably shows
this problem.

Today I accidentally reproduced this on my desktop machine with AMD Radeon
HD6570 and kernel 3.4.0-1.fc17. I use Cinnamon on both machines. It turns out
that the bad behaviour only shows up (but reliably) if I move the mouse pointer
to the "magic spot" on the screen, i.e. the top-left corner so the workspace
switcher kicks in. Killing X with Ctrl-Alt-BkSp cures it. The difference
between my desktop machine and the notebook is that for some reason, when X
starts, the cursor shows up in the top-left corner on my notebook but in the
middle of the screen on my desktop machine. So, the error occurred on the
notebook as soon login was attempted without moving the mouse.

Currently installed relevant software versions:

kernel-3.3.7-1.fc17.x86_64
kernel-3.4.0-1.fc17.x86_64
mesa-libGL-8.0.3-1.fc17.i686
mesa-libGL-8.0.3-1.fc17.x86_64
mesa-dri-drivers-8.0.3-1.fc17.x86_64
mesa-dri-drivers-8.0.3-1.fc17.i686
xorg-x11-server-Xorg-1.12.0-5.fc17.x86_64
xorg-x11-drv-ati-6.14.4-6.20120602git930760942.fc17.x86_64
cinnamon-1.4.0-5.UP1.fc17.x86_64
muffin-1.0.3-3.fc17.x86_64

Since I heard about the current state of ColorTiling2D is not yet usable, I
thought it might somehow kick in and created this file on my notebook:

# cat /etc/X11/xorg.conf.d/01-radeon.conf 
###########################
Section "Device"
    Identifier    "Radeon"
    Driver        "radeon"
    Option "ColorTiling2D" "off"
EndSection
###########################

Xorg.0.conf confirms setting ColorTiling2D to off explicitly but it didn't
solve the problem on the notebook.

The order of events on the notebook:

yum upgrade installed these:

Jun  7 15:56:23 localhost yum[876]: Updated: avahi-0.6.31-3.fc17.x86_64
Jun  7 15:56:23 localhost yum[876]: Updated: avahi-glib-0.6.31-3.fc17.x86_64
Jun  7 15:56:27 localhost yum[876]: Updated: xulrunner-13.0-1.fc17.x86_64
Jun  7 15:56:28 localhost yum[876]: Updated: xsane-common-0.998-10.fc17.x86_64
Jun  7 15:56:28 localhost yum[876]: Updated: xsane-gimp-0.998-10.fc17.x86_64
Jun  7 15:56:33 localhost yum[876]: Updated: firefox-13.0-1.fc17.x86_64
Jun  7 15:56:34 localhost yum[876]: Updated: avahi-ui-gtk3-0.6.31-3.fc17.x86_64
Jun  7 15:56:34 localhost yum[876]: Updated: avahi-gobject-0.6.31-3.fc17.x86_64
Jun  7 15:56:36 localhost yum[876]: Updated:
fontconfig-devel-2.8.0-7.fc17.x86_64
Jun  7 15:56:39 localhost yum[876]: Updated: kernel-headers-3.4.0-1.fc17.x86_64
Jun  7 15:56:39 localhost yum[876]: Updated:
xorg-x11-drv-synaptics-1.6.1-1.fc17.x86_64
Jun  7 15:56:40 localhost yum[876]: Updated: avahi-autoipd-0.6.31-3.fc17.x86_64
Jun  7 15:56:41 localhost yum[876]: Updated: kpartx-0.4.9-26.fc17.x86_64
Jun  7 15:56:45 localhost yum[876]: Updated: fontconfig-2.8.0-7.fc17.i686
Jun  7 15:56:55 localhost yum[876]: Installed: kernel-3.4.0-1.fc17.x86_64

yum --enablerepo=updates-testing upgrade libX11* xorg-x11-drv-ati installed
these:

Jun  7 15:59:23 localhost yum[10612]: Updated:
libX11-common-1.5.0-1.fc17.noarch
Jun  7 15:59:26 localhost yum[10612]: Updated: libX11-1.5.0-1.fc17.x86_64
Jun  7 15:59:31 localhost yum[10612]: Updated: libX11-devel-1.5.0-1.fc17.x86_64
Jun  7 15:59:33 localhost yum[10612]: Updated:
xorg-x11-drv-ati-6.14.4-6.20120602git930760942.fc17.x86_64
Jun  7 15:59:34 localhost yum[10612]: Updated: libX11-1.5.0-1.fc17.i686

Then the error kicked in after a reboot.

I flashed the BIOS from version 207 to 214 after that, didn't solve anything.

Then yum distro-sync downgraded these:

Jun  7 19:28:28 localhost yum[1392]: Installed:
libX11-common-1.4.99.901-2.fc17.noarch
Jun  7 19:28:29 localhost yum[1392]: Installed: libX11-1.4.99.901-2.fc17.x86_64
Jun  7 19:28:32 localhost yum[1392]: Installed:
libX11-devel-1.4.99.901-2.fc17.x86_64
Jun  7 19:28:33 localhost yum[1392]: Installed:
xorg-x11-drv-ati-6.14.4-5.20120417git0bda305f7.fc17.x86_64
Jun  7 19:28:34 localhost yum[1392]: Installed: libX11-1.4.99.901-2.fc17.i686
Jun  7 19:28:57 localhost yum[1403]: Updated: libX11-common-1.5.0-1.fc17.noarch
Jun  7 19:28:57 localhost yum[1403]: Updated: libX11-1.5.0-1.fc17.x86_64
Jun  7 19:29:01 localhost yum[1403]: Updated: libX11-devel-1.5.0-1.fc17.x86_64
Jun  7 19:29:02 localhost yum[1403]: Updated: libX11-1.5.0-1.fc17.i686

Since yesterday the above libX11* and xorg-x11-drv-ati versions were moved to
updated from updates-testing.

Today I performed a yum reinstall "*" to ensure that every packages are ok.
memtest86+ was ran on the machine after I bought it in January, it happily ran
Fedora 16. Then it was upgraded to F17 during its RC series and only yum
upgrade was performed since then, possibly missing some rebuilds which yum
reinstall "*" finally included. Or it was simply a gremlin in the machine.

After this yum reinstall "*", I rebooted several times switching between 3.4.0
and 3.3.7. 3.3.7 is usable, 3.4.0 triggers the "invalid command stream"
messages in the syslog.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

^ permalink raw reply	[flat|nested] 15+ messages in thread