compiz exits with radeon error
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: xorg
compiz runs fine initially but eventually reports:
drmRadeonCmdBuffer: -12. Kernel failed to parse or rejected command stream. See dmesg for more info.
and then exits.
dmesg reveals:
[ 1217.412221] [drm:radeon_
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: xorg 1:7.5+3ubuntu1
ProcVersionSign
Uname: Linux 2.6.32-17-generic i686
Architecture: i386
Date: Mon Mar 29 12:57:10 2010
DkmsStatus: Error: [Errno 2] No such file or directory
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318)
Lsusb:
Bus 001 Device 002: ID 050d:705c Belkin Components 802.11bg
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: IBM 2684HVG
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcCmdLine: BOOT_IMAGE=
ProcEnviron:
LANG=en_GB.utf8
SHELL=/bin/bash
SourcePackage: xorg
Symptom: display
dmi.bios.date: 03/22/2005
dmi.bios.vendor: IBM
dmi.bios.version: 1SET68WW (1.36 )
dmi.board.name: 2684HVG
dmi.board.vendor: IBM
dmi.board.version: Not Available
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: IBM
dmi.chassis.
dmi.modalias: dmi:bvnIBM:
dmi.product.name: 2684HVG
dmi.product.
dmi.sys.vendor: IBM
glxinfo: Error: [Errno 2] No such file or directory
system:
distro: Ubuntu
codename: lucid
architecture: i686
kernel: 2.6.32-17-generic
affects: | xorg (Ubuntu) → xserver-xorg-video-ati (Ubuntu) |
Changed in xserver-xorg-video-ati (Ubuntu): | |
status: | New → Confirmed |
Changed in linux (Ubuntu): | |
status: | Incomplete → Confirmed |
Hrm, none of the attachments reveal a backtrace or error message other than the relocation error you mentioned. However, I suspect the Failed to parse relocation message is a warning message more than a distinct error; it's something we've seen before on other bugs like #513011 and I think it just means that hardware rendering didn't work or some such. It's not enough information for us to troubleshoot this bug. Try to gather some more data, such as by running compiz from the terminal and collecting all of its output. Maybe dmesg or syslog could provide more info. I think there's also some debugging flags that can be set in the kernel to get more info.
Anyway, the one thing that is clear is that something went wrong in the kernel drm code, so at least we can refile it to the kernel.