Bug 54133

Can you bisect?

I will try, but it can be long as the problem is not systematic.

I am experiencing same problem. My log repeats this messages almost 4times/second:

[drm] PCIE GART of 512M enabled (table at 0x0000000000040000).
radeon 0000:01:00.0: WB enabled
radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000020000c00 and cpu addr 0xffff880220418c00
[drm] ring test on 0 succeeded in 1 usecs
[drm] ib test on ring 0 succeeded in 0 usecs
[drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -35!
radeon 0000:01:00.0: GPU reset succeeded, trying to resume
[drm] probing gen 2 caps for device 8086:29e1 = 2/0
[drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0

HW is desktop pc with GPU
01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RV770 [Radeon HD 4850]

using openSUSE 12.2 with kernel 3.6.3

But I think I didn't encounter this issue back in august when this report was created and I always try to use the latest kernel released. I start to hitting this after upgrading to xorg server 1.13 (default openSUSE has 1.12) and Mesa 9.0 (default openSUSE is Mesa 8.x)

Noticed that this can be easily triggered by switching between text and X console few times.

My current versions:
# uname -a
Linux Cerberos 3.6.5-10-desktop #1 SMP PREEMPT Wed Oct 31 20:15:15 UTC 2012 (cefb3b0) x86_64 x86_64 x86_64 GNU/Linux
# rpm -q libdrm_radeon1
libdrm_radeon1-2.4.39-94.1.x86_64

Since upgrade to kernel 3.7.1 (from openSUSE Tumbleweed) I can no longer replicate this. For me this problem appears to be fixed.

I am using kernel 3.7.2-201.fc18.x86_64 (Fedora 18) and no libdrm_radeon and am also experiencing this problem. Problem not present in Fedora 17.

Downstream reports:
https://bugzilla.redhat.com/show_bug.cgi?id=883536
https://bugzilla.redhat.com/show_bug.cgi?id=849347

I'm kinda wondering if this has something to do with 64-bits (probably not, as comment 6 hints that this was not present in Fedora 17 64-bits).

Can anyone bisect and track down what broke it?

I don't think I have the knowledge to build (and git bisect!) my own driver, however there is some additional clue I can give from https://bugzilla.redhat.com/show_bug.cgi?id=883536 :

the issue does not seem to be strictly related to suspend & resume. It is very easy to trigger the problem in Fedora 18 by booting up to the GDM login screen, switching to another virtual terminal by pressing ctrl+alt+F3, then trying to switch back to GDM by doing ctrl+alt+F1.

Created attachment 141375 [details]
Screen when resuming on RV610 gpu

Hello all, my RV610 gpu has issues when resuming. I usually get the screen i posted. When that screen appears, the only solution ive found is to Ctrl+alt+f3 and reboot the system. That screen will sometimes flicker, or even briefly show the login screen before going back to it. One day I noticed some messages maybe describing the bug shown in attachment 2 [details] [review] 

Relevant Dmesg|grep radeon

[   12.079128] [drm] radeon kernel modesetting enabled.
[   12.079207] fb: switching to radeondrmfb from VESA VGA
[   12.079781] radeon 0000:01:00.0: VRAM: 256M 0x0000000000000000 - 0x000000000FFFFFFF (256M used)
[   12.079783] radeon 0000:01:00.0: GTT: 512M 0x0000000010000000 - 0x000000002FFFFFFF
[   12.084832] [drm] radeon: 256M of VRAM memory ready
[   12.084834] [drm] radeon: 512M of GTT memory ready.
[   13.837201] [drm] radeon: power management initialized
[   13.868698] radeon 0000:01:00.0: WB enabled
[   13.868702] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000010000c00 and cpu addr 0x00000000196569de
[   13.869146] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x00000000000521d0 and cpu addr 0x000000000d3aa4f8
[   13.869151] radeon 0000:01:00.0: radeon: MSI limited to 32-bit
[   13.869201] radeon 0000:01:00.0: radeon: using MSI.
[   13.869226] [drm] radeon: irq initialized.
[   14.843499] fbcon: radeondrmfb (fb0) is primary device
[   14.869372] radeon 0000:01:00.0: fb0: radeondrmfb frame buffer device
[   14.888793] [drm] Initialized radeon 2.50.0 20080528 for 0000:01:00.0 on minor

I dont understand why "attachment 2 [details] [review]" was highlighted. sorry

Created attachment 141376 [details]
Possible error messages relating to the bug

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/295.