** No longer affects: xserver-xorg-video-ati (Ubuntu Precise)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1085751
Title:
[drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -35!
To manage
** Package changed: fedora => xorg (Fedora)
** Changed in: xorg (Fedora)
Importance: High => Undecided
** Changed in: xorg (Fedora)
Status: Confirmed => New
** Changed in: xorg (Fedora)
Remote watch: freedesktop.org Bugzilla #54133 => None
** No longer affects: linux (Ubuntu
** No longer affects: hwe-next
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1085751
Title:
[drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -35!
To manage notifications about this bug go
quantal has seen the end of its life and is no longer receiving any
updates. Marking the quantal task for this ticket as Won't Fix.
** Changed in: xserver-xorg-video-ati (Ubuntu Quantal)
Status: Confirmed = Won't Fix
--
You received this bug notification because you are a member of
** Changed in: linux (Ubuntu Quantal)
Assignee: Timo Aaltonen (tjaalton) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1085751
Title:
[drm:radeon_cs_ioctl] *ERROR* Failed to
Dave Gilbert, as per
http://www.asrock.com/mb/Intel/P55M%20Pro/?cat=Downloados=BIOS an
update is available for your BIOS (2.30). If you update to this, does it
change anything?
If not, could you please both specify what happened, and provide the output of
the following terminal command:
sudo
Tested with raring : cannot reproduce the problem. I only had it with
the 3.5 kernel on my machine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1085751
Title:
[drm:radeon_cs_ioctl] *ERROR* Failed
I have just updated to Raring and I am hit by this bug. It happens with
a ATI Radeon HD4330, and it is triggered each time I suspend or
hibernate the laptop, which is quite nasty. As this is a lenghty bug, I
would like to provide any useful information you may request.
--
You received this bug
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xserver-xorg-video-ati (Ubuntu Precise)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xserver-xorg-video-ati (Ubuntu Quantal)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Dave: that's not the same bug then, the upstream/fedora patch is in the
-ati driver version 7.1.0, which raring has had for some time.
** Also affects: xserver-xorg-video-ati (Ubuntu)
Importance: Undecided
Status: New
** Changed in: xserver-xorg-video-ati (Ubuntu)
Status: New =
Problem still exist with 3.5.0-27-generic #46~precise1-Ubuntu SMP.
Is someone at Cannonical working seriously on this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1085751
Title:
Hi ClaudeD, Matthew, Coolman,
Hmph - that's really interesting; for me on my Raring box it fails reliably,
but I've never got a Quantal kernel to fail (see above).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have the same problem with 3.5.0-25 kernel on ubuntu 12.04.2 LTS and I
had same problem with ubuntu 12.10. By the it seems that fedora team
solved the problem with xorg-x11-drv-ati-7.0.0-0.9 driver. Is it
possible to use the same driver with ubuntu?
Thanks
--
You received this bug
Confirmed on Quantal with kernel 3.5.0-25-generic and a Radeon HD4850
[RV770].
** Changed in: linux (Ubuntu Quantal)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I can confirm this bug on a Precise installation with the new Quantal
backported kernel and xorg :
laptop:~$ uname -a
Linux laptop 3.5.0-23-generic #35~precise1-Ubuntu SMP Fri Jan 25 17:15:33 UTC
2013 i686 i686 i386 GNU/Linux
laptop:~$ lspci | grep VGA
02:00.0 VGA compatible controller:
Timo: Can you explain why you believe that patch is relevant to this bug?
To me that patch looks like something on the display hardware side, and I
thought the -35's were some sort of memory allocation screw up (but I may be
wrong)?
--
You received this bug notification because you are a
Upstream pointed out that this commit should fix it for evergreen gpu's:
http://cgit.freedesktop.org/~agd5f/linux/commit/?h=drm-
fixes-3.8id=bb588820ef421c6098dca1fec29c3b347f1c8c19
there is a similar commit for earlier gpu's, both sent to the stable
list so they should end up in 3.5 before too
well, we have Quantal's backported kernels in Precise, hence the Precise
task.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1085751
Title:
[drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation
** Also affects: linux (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Precise)
Importance: Undecided = Medium
** Changed in: linux (Ubuntu Precise)
Status: New = Incomplete
** Tags removed: performing-bisect
--
You received this bug
3.5-rc4 3.5.0-030500rc4-generic #201206241635 exhibits the bug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1085751
Title:
[drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -35!
To manage
3.5.0-030500rc1-generic #201206022335 also fails.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1085751
Title:
Chris Van Hoof: Can you explain why you've got Precise and Quantal tasks on
here?
If you look through the bug you'll see that Quantal kernels work fine for me,
this only failed for me after an upgrade to Raring,
and usign the Quantal kernels of the time was fine.
--
You received this bug
** Tags added: blocks-hwcert-enablement
** Also affects: linux (Ubuntu Quantal)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Quantal)
Importance: Undecided = Medium
** Changed in: linux (Ubuntu Quantal)
Status: New = Incomplete
** Changed in: linux (Ubuntu
** No longer affects: hwe-next
** No longer affects: hwe-next/quantal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1085751
Title:
[drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -35!
To
** No longer affects: hwe-next
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1085751
Title:
[drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -35!
To manage notifications about this bug go
** No longer affects: hwe-next
** No longer affects: hwe-next
** No longer affects: hwe-next
** No longer affects: hwe-next
** No longer affects: hwe-next
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** No longer affects: hwe-next
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1085751
Title:
[drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -35!
To manage notifications about this bug go
It would be really helpful to be able to identify the last good and
first bad upstream kernels. Then we can bisect to find the commit that
caused this regression. It appears an Ubuntu SAUCE patch fixes this
issue, but I've been unable to identify which one.
Can you test the following kernel:
** Bug watch added: Red Hat Bugzilla #883536
https://bugzilla.redhat.com/show_bug.cgi?id=883536
** Bug watch added: Red Hat Bugzilla #849347
https://bugzilla.redhat.com/show_bug.cgi?id=849347
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Launchpad has imported 7 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=54133.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
Ash: While it's possible the bug watch you added is the same one as
this, it's certainly not a slamdunk; it gives the same symptom but I
don't know enough about the driver to know if it's actually the same.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Joseph:
3.5.0-22.34 works nicely; it's done 20 full cycles and still going fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1085751
Title:
[drm:radeon_cs_ioctl] *ERROR* Failed to parse
3.5.0-18.29 also works fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1085751
Title:
[drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -35!
To manage notifications about this bug go
and just to confirm 3.8.0-1.5 still exhibits the bug.
[ 329.150568] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -35!
[ 329.166480] radeon :07:00.0: GPU softreset: 0x0007
[ 329.193800] radeon :07:00.0: GPU reset succeeded, trying to resume
[ 329.210521] [drm] probing
** Bug watch added: freedesktop.org Bugzilla #54133
https://bugs.freedesktop.org/show_bug.cgi?id=54133
** Also affects: fedora via
https://bugs.freedesktop.org/show_bug.cgi?id=54133
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
Those are some interesting results since 3.5.0-19 has the upstream 3.5.7
updates. Can you also test the following two kernels:
v3.5.0-18: https://launchpad.net/ubuntu/+source/linux/3.5.0-18.29
v3.5.0-22: https://launchpad.net/ubuntu/+source/linux/3.5.0-22.34
Look at the links under Builds for
3.5.6-030506-generic #201210130527 from
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.5.6-quantal/ failed
(One cycle of switching user and back)
[ 73.068583] [drm] ring test on 0 succeeded in 1 usecs
[ 73.068607] [drm] ib test on ring 0 succeeded in 0 usecs
[ 73.666523]
I can reproduce this bug on both an Ubuntu 13.04 Raring Ringtail Live
USB and an installed system upgraded from Ubuntu 12.10 Quantal Quetzal.
Steps to reproduce:
1. Log in from the graphical interface.
2. Switch to tty1 (Ctrl-Alt-F1)
3. Switch to tty2 (Ctrl-Alt-F2)
4. Switch to X11 [tty7]
Syslog attached.
** Attachment added: syslog
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1085751/+attachment/3480435/+files/syslog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1085751
Can you test the following kernel:
v3.5.6: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.5.6-quantal/
** Changed in: linux (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ok, sorry - seems like I was going in the wrong direction there.
So I've had it fail on the 3.5.7-030507 generic but 3.5.0-19-generic #30 works
fine
and nothing newer works either.
The number of diffs looks tiny, and I don't see anything obvious.
--
You received this bug notification because
Rebuilding 3.5.0-19-generic in my raring user space produces a kernel
which also doesn't seem to exhibit the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1085751
Title:
[drm:radeon_cs_ioctl]
..and a rebuilt 3.5.7 mainline fails.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1085751
Title:
[drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -35!
To manage notifications about this
I can get it to fail with 3.5.0-030500-generic #201207211835
so I guess that's a fairly small gap relative to 3.5.0-19-generic #30.
Is it something we added/unconfigured?
Dave
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi,
Chopped it down a bit further, 3.5.1-030501-generic #201208091310 also
triggers,
but I still can't get 3.5.0-19-generic #30-ubuntu to fail.
Haven't tried a mainline 3.5.0 yet.
Dave
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hi Joseph,
this still occurs for me with the 3.5.7 from that link (and with current
raring), but as stated not with the 3.5.0-19 from quantal.
My test procedure on my box is:
* Fresh boot
* Log in via kdm as my default user
* Wait for my standard KDE desktop to settle
* K
I encountered this trouble on a laptop upgraded from precise to quantal
(linux 3.5.0-19). Using previous linux version (3.2 from precise) or 3.6
from PPA didn't helped. After backuping and removing
~/.{compiz,config,gconf{,d},gnome2} directories, it now works normally.
I haven't find the main
Are you now unable to reproduce this bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1085751
Title:
[drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -35!
To manage notifications about
I can reproduce the bug when putting back the files I reviously backed up.
However I tried to do the same on a second computer with a new test account and
the same file without being able to reproduce the trouble (the first computer
wasn't mine but the one of an user that I take care of in my
I'd like to perform a bisect to figure out what commit caused this
regression. It would be very helpful to know the earliest kernel where
the issue started happening as well as the latest kernel that did not
have this issue.
Can you test the following kernels and report back? We are looking for
Does this issue go away if you boot back into the Precise kernel, but
stay on a Raring install?
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
** Changed in: linux (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of
(You said Precise, but I assume you mean Quantal since that's what I was
previously on - if you really meant precise just ask and I'll try)
I don't seem to be able to trigger it on the Quantal 3.5.0-19, but
managed to repeat the failure on the Raring 3.7.0 (same Raring
userspace)
My test
53 matches
Mail list logo
