[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/491572
Ti
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/curre
** Tags removed: regression-potential
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/491572
Title:
[lucid][rv350] radeon drm error (AGP)
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
htt
This appears to be a duplicate of #550850 and #583891.
--
[lucid][rv350] radeon drm error (AGP)
https://bugs.launchpad.net/bugs/491572
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.
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'
--
[lucid][
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 (bui...@yellow) (gcc version 4.4.3 (Ubuntu
4.4.3-4ubuntu4) ) #27-Ubuntu SMP Fri Mar 26 21:13:44 UTC
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
--
[lucid][rv350] radeon drm error (AGP)
https://bugs.launchpad.net/bugs/491572
You received this bug no
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 s
