[lucid][rv350] radeon drm error (AGP)

Bug #491572 reported by robin0800
24
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned
mesa (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Seeing lots of these messages in the kernel log were not present in ubuntu Jaunty

Dec 2 19:02:08 Robins-Laptop kernel: [21323.577223] [TTM] Failed moving buffer. Proposed placement 0x00060004
Dec 2 19:02:08 Robins-Laptop kernel: [21323.577237] [drm:radeon_object_list_validate] *ERROR* radeon: failed to validate.
Dec 2 19:02:08 Robins-Laptop kernel: [21323.577240] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation !

ProblemType: Bug
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: robin0800 7871 F.... pulseaudio
 /dev/snd/pcmC0D0p: robin0800 7871 F...m pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'I82801DBICH4'/'Intel 82801DB-ICH4 with AD1981B at irq 11'
   Mixer name : 'Analog Devices AD1981B'
   Components : 'AC97a:41445374'
   Controls : 33
   Simple ctrls : 22
Date: Wed Dec 2 20:41:07 2009
DistroRelease: Ubuntu 10.04
HibernationDevice: RESUME=UUID=0768eca1-b0a8-4171-a2ec-bd62d0c2256d
MachineType: Hewlett-Packard HP Compaq nc6000 (PQ491ES#ABU)
Package: linux-image-2.6.32-6-generic 2.6.32-6.8
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-6-generic root=UUID=75592929-a2d6-45af-8d77-3ae360b1d026 ro quiet splash
ProcEnviron:
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-6.8-generic
Regression: Yes
RelatedPackageVersions: linux-firmware 1.27
Reproducible: Yes
RfKill:

SourcePackage: linux
Tags: lucid needs-upstream-testing regression-potential
TestedUpstream: No
Uname: Linux 2.6.32-6-generic i686
dmi.bios.date: 08/30/2006
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68BDD Ver. F.15
dmi.board.name: 0890
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 8051 Version 1A.19
dmi.chassis.asset.tag: CNU447FNCY
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68BDDVer.F.15:bd08/30/2006:svnHewlett-Packard:pnHPCompaqnc6000(PQ491ES#ABU):pvrF.15:rvnHewlett-Packard:rn0890:rvr8051Version1A.19:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP Compaq nc6000 (PQ491ES#ABU)
dmi.product.version: F.15
dmi.sys.vendor: Hewlett-Packard

Revision history for this message
robin0800 (robin-linux-hotmail) wrote :
Revision history for this message
robin0800 (robin-linux-hotmail) wrote :

From Xork-o log Graphic card info.
Not sure why this was not automatically collected perhaps another bug?

PCI:*(0:1:0:0) 1002:4e50:103c:0890 ATI Technologies Inc RV350 [Mobility Radeon 9600 M10] rev 0, Mem @ 0x98000000/134217728, 0x90300000/65536, I/O @ 0x00002000/256, BIOS @ 0x????????/131072

Revision history for this message
Andy Whitcroft (apw) wrote :

The main device is recorded in the LsPci.txt at least:

    01:00.0 VGA compatible controller [0300]: ATI Technologies Inc RV350 [Mobility Radeon 9600 M10] [1002:4e50]
 Subsystem: Hewlett-Packard Company Device [103c:0890]

Adding a mesa task as this could be kernel or mesa related.

tags: added: kernel-lucid
Andy Whitcroft (apw)
summary: - Kernel error messages...... re radeon graphic card
+ [lucid] Kernel error messages...... re radeon graphic card
Andy Whitcroft (apw)
Changed in linux (Ubuntu):
status: New → Triaged
Andy Whitcroft (apw)
tags: removed: kernel-lucid
Surbhi Palande (csurbhi)
Changed in mesa (Ubuntu):
importance: Undecided → Medium
Changed in linux (Ubuntu):
importance: Undecided → Medium
summary: - [lucid] Kernel error messages...... re radeon graphic card
+ [lucid][r300] radeon drm error (AGP)
summary: - [lucid][r300] radeon drm error (AGP)
+ [lucid][rv350] radeon drm error (AGP)
Revision history for this message
Bryce Harrington (bryce) wrote :

A lot has changed in the radeon drm driver between the time of the last comment and now, so this bug may no longer be relevant. It would be good to re-test with the 2.6.33 drm if it is.

In any case, I don't see really solid evidence of it being caused by a bug in mesa; if so it would be good to see that tested with a newer version. But meanwhile I'll close out the mesa task; the kernel task is probably sufficient for now.

Changed in mesa (Ubuntu):
status: New → Invalid
Revision history for this message
Dave Gilbert (ubuntu-treblig) wrote :

I'd never noticeably had the 'failed to parse relocation' before today, and that's on 2.6.32-17 with xorg-edgers on lucid (rv710 card); so feels like there is actually a regression here.

Dave

Revision history for this message
andrew thomas (atswartz) wrote :

I, too, have never noticed the 'failed to parse relocation' before, yet my logs began to fill up when using 2.6.32-18. I also am using the xorg-edgers ppa on lucid.

Linux version 2.6.32-18-generic (buildd@yellow) (gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu4) ) #27-Ubuntu SMP Fri Mar 26 21:13:44 UTC 2010 (Ubuntu 2.6.32-18.27-generic 2.6.32.10+drm33.1)
kernel: [ 1278.936696] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation !

When I switched to the drm-next kernel -
Linux version 2.6.34-996-generic (root@zinc) (gcc version 4.2.3 (Ubuntu 4.2.3-2ubuntu7)) #201003231151 SMP Tue Mar 23 11:56:30 UTC 2010

my Xorg.0.log began to fill with

space check failed in flush

X.Org X Server 1.7.6
Release Date: 2010-03-17
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.24-27-xen x86_64 Ubuntu
Current Operating System: Linux M3A32-MVP 2.6.34-996-generic #201003231151 SMP Tue Mar 23 11:56:30 UTC 2010 x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.34-996-generic root=UUID=c864dd9d-8a3d-4901-b1d1-74139212347f ro quiet splash
Build Date: 31 March 2010 04:05:39AM
xorg-server 2:1.7.6+git20100330+server-1.7-nominations.49a2b55e-0ubuntu0sarvatt (Robert Hooker <email address hidden>)
PCI:*(0:1:0:0) 1002:9501:1043:022a ATI Technologies Inc Radeon HD 3870 rev 0, Mem @ 0xd0000000/268435456, 0xfe7f0000/65536, I/O @ 0x00009000/256, BIOS @ 0x????????/131072
[drm] Loading RV670 Microcode

Any ideas on what to try next?

Revision history for this message
andrew thomas (atswartz) wrote :

I guess that I didn't look in the xorg log very good when running the 2.6.32.18 kernel before, because when I booted to it after noticing the space check errors with the drm-next kernel I noticed that I am getting both the 'failed to parse relocation' and 'space check failed in flush'

Revision history for this message
John Gilmore (gnu-gilmore) wrote :

This appears to be a duplicate of #550850 and #583891.

tags: removed: regression-potential
Revision history for this message
penalvch (penalvch) wrote :

robin0800, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

Changed in linux (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.