[rv710] drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -12! from google-maps in chromium-browser

[Dave Gilbert]

Binary package hint: xserver-xorg-video-ati

So we have:
   an HD4350 (rv710) with current Maverick, and the chromium-browser daily ppa, running with KDE with desktop effects enabled.
Go to maps.google.co.uk, zoom in and out of the uk once or twice and if it doesn't just crash you'll get a:

[ 179.736595] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -12!

and the chromium-browser process will hang.

I've also managed to trigger this once in Gnome without desktop effects; but it's much rarer.

I added some debug and managed to trace it back as far as:
Oct 4 13:11:27 major kernel: [ 795.810631] [drm:ttm_bo_validate] *ERROR* ttm_bo_validate: ttm_bo_move_buffer gave ENOMEM
 Oct 4 13:11:27 major kernel: [ 795.810634] [drm:radeon_bo_list_validate] *ERROR* radeon_bo_list_validate: ttm_bo_validate gave NOMEM
 Oct 4 13:11:27 major kernel: [ 795.810636] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -12!

Dave

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: xserver-xorg-video-ati 1:6.13.1-1ubuntu5
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
Architecture: amd64
CheckboxSubmission: f2d10bd9f943a85b486a282e7840a570
CheckboxSystem: 0531969bcfd4f03af7405c98dc94a948
DRM.card0.HDMI_Type_A.1:
 status: disconnected
 enabled: disabled
 dpms: On
 modes:
 edid-base64:
DRM.card0.VGA.1:
 status: disconnected
 enabled: disabled
 dpms: On
 modes:
 edid-base64:
Date: Thu Oct 7 21:30:20 2010
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic root=UUID=d8314979-8ace-401c-88df-728ad6b89cb5 ro ignore_loglevel netconsole=4444@192.168.66.33/eth0,514@192.168.66.25/00:a0:d1:63:68:a6 nointremap crashkernel=384M-2G:64M,2G-:128M quiet splash
ProcEnviron:
 LANGUAGE=
 PATH=(custom, user)
 LANG=en_GB.utf8
 SHELL=/bin/bash
SourcePackage: xserver-xorg-video-ati
dmi.bios.date: 09/10/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.50
dmi.board.name: P55M Pro
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd09/10/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnP55MPro:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
system:
 distro: Ubuntu
 codename: maverick
 architecture: x86_64
 kernel: 2.6.35-22-generic

[Dave Gilbert (ubuntu-treblig)]

Still does it with 6.13.2-0ubuntu1~xup1 version of xserver-xorg-video-ati from http://ppa.launchpad.net/ubuntu-x-swat/x-updates/ubuntu

[Dave Gilbert (ubuntu-treblig)]

OK some more data for the record:

  1) I don't seem to be able to get this to trigger with Gnome with desktop effects (even with those pesky wobbly windows....)
  2) The chromium-browser in the standard Maverick repo doesn't trigger it either; hence i guess it's not using any GL stuff.
  3) When running the daily-ppa chromium-browser on maps, /sys/kernel/debug/dri/0/gem_objects is showing object bytes in the many hundreds of MB (it's about 90MB quiescent on Gnome with desktop effects, about 100MB KDE with desktop effects) and it jumps well over 400MB at times which is I guess what's killing it.

Dave

[RdeWit (rdewit)]

I've got the same error when I run Moovida (1.0,9) and select 'TV Shows / Library'. It also happens whilst running xbmc (from Lucid PPA from team-xbmc). The latter gave me a nice error that I'll attach here. HTH.

[RdeWit (rdewit)]

dmesg gives me:

...
kernel: [17654.140890] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -12!
...

and lspci gives me:
...
01:05.0 VGA compatible controller: ATI Technologies Inc RC410 [Radeon Xpress 200M]
...

[Steve Hogg (steveblakehogg)]

I'm getting the same message when running Boxee (based on xbmc). dmesg shows:
[drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -12!

Looking back though, I also get on startup:
[drm:radeon_i2c_put_byte] *ERROR* i2c 0x08 0x31 write failed
[drm:radeon_i2c_put_byte] *ERROR* i2c 0x0a 0x00 write failed
[drm:radeon_i2c_put_byte] *ERROR* i2c 0x0c 0x89 write failed

I had the same problem with Ubuntu 10.04 and had found at the time on bugs.freedesktop.org bug #27284

lspci shows:
01:05.0 VGA compatible controller: ATI Technologies Inc RS480 [Radeon Xpress 200G Series]

[bugbot (bugbot)]

Hey Dave,

Thanks for testing maverick during its development period. Unfortunately it looks like this bug report didn't get attention during the maverick development period. But I see there's not been more comments on the bug since the release, which makes me wonder if this is still an issue for you?

If you've not seen this issue since maverick's release yourself, it may have been solved by kernel or X or other updates that occurred late in the release; if so, would you mind please closing the bug for us? Go to the URL mentioned in this bug report, click the yellow icon(s) in the status column and set to 'Fix Released'.

If you no longer have the hardware needed to reproduce the problem, or otherwise feel the bug no longer needs tracked in Launchpad, you can set the status to 'Invalid'.

If you are the original reporter and still have this issue, just reply to this email saying so. (Or set the bug status to Confirmed.) If you are able to re-test this against 11.04 Natty Narwhal (our current development focus) and find the issue still affects Natty, please also run 'apport-collect <bug-number>' while running natty, which will add fresh logs and debug data, and flag it for the Ubuntu-X development team to look at.

[bugbot (bugbot)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.