Possibly related to bug 69983.  Does reverting to an older version of mesa fix the issue?  If so, can you bisect mesa?

If you only updated the kernel, can you bisect the kernel?

Created attachment 86963 [details]
dmesg_grep_radeon_3.12rc3

Created attachment 86964 [details]
dmesg_grep_drm_3.12rc3

I am not a power user. I can purge the Oibaf ppa if you want.
I dont no how to revert to an older version of Mesa or bisecting.
Sorry

(In reply to comment #2)
> If you only updated the kernel, can you bisect the kernel?

The kernel 3.12-rc3 was running fine before the update of the Oibaff PPA
so is probably not the problem.

(In reply to comment #1)
> Possibly related to bug 69983.

That is indeed likely — current master (since 68f6dec32ed5eede361f76c8dbdf897652659baf) locks up my RS880 even with glxgears, though only using LLVM.

Hello,

I found this thread on the phoronix forums, i don't no but maybe is related .

http://phoronix.com/forums/showthread.php?50038-Updated-and-Optimized-Ubuntu-Free-Graphics-Drivers/page66

comment #652 from berklay 

I was getting the whole wm freeze up immediately after logging into my Openbox desktops and had to switch console to reinstall the last working debs. There was nothing in any of the system logfiles and disabling things like conky and compton (the compositor) didn't resolve anything.

Through trial and error I traced a regression caused by the 'winsys/radeon: remove cs_queue_empty' commit from Sept 22. Doing a git revert -n 0653c66ef40ac553f91b29bbda7f59f7ce6948fa and recompiling fixed the issue for me.

I was using the latest 32-bit ubuntu mainline kernel and the freezes happened on a laptop with a Mobility Radeon HD 4530/4570 and also on a desktop with an X850 XT. I haven't yet had a chance to see if the desktop machine works with the above solution, but both machines were previously in sync and went wrong with the same update (the set that was released on Sept 23).

The bug is reported here https://bugs.freedesktop.org/show_bug.cgi?id=70123

Tasev,

If your issue is related to mine then the corresponding debs from the 9.3~git1309201759 Sept 20th release should work :-

https://launchpad.net/~oibaf/+archive/graphics-drivers/+build/5036069 [amd64]
https://launchpad.net/~oibaf/+archive/graphics-drivers/+build/5036070 [i386]


...and the debs from Sept 23rd 9.3~git1309231016 should fail :-

https://launchpad.net/~oibaf/+archive/graphics-drivers/+build/5042397 [amd64]
https://launchpad.net/~oibaf/+archive/graphics-drivers/+build/5042398 [i386]


To find out which mesa packages you have installed (hopefully nothing else has a matching version string) :-

dpkg -l | grep ".*9.3~git[0-9]*.[0-9a-z]*~gd~.*"


To install the debs download the appropriate packages to /path/to/some/directory and then :-

cd /path/to/some/directory

sudo dpkg -i *.deb


You can usually find the debs from an older mesa version by looking in apt's archives :-

ls -lrt /var/cache/apt/archives/*_9.3~git[0-9]*.[0-9a-z]*~gd~*

And copy them somewhere for easy installation :-

cp /var/cache/apt/archives/*_9.3~git1309040912.644fbb~gd~* /path/to/some/directory


Hopefully you can find out which version breaks your install or at least get things working again.

(In reply to comment #9)
> Tasev,
> 
> If your issue is related to mine then the corresponding debs from the
> 9.3~git1309201759 Sept 20th release should work :-
> 
> https://launchpad.net/~oibaf/+archive/graphics-drivers/+build/5036069 [amd64]
> https://launchpad.net/~oibaf/+archive/graphics-drivers/+build/5036070 [i386]
> 
> 
> ...and the debs from Sept 23rd 9.3~git1309231016 should fail :-
> 
> https://launchpad.net/~oibaf/+archive/graphics-drivers/+build/5042397 [amd64]
> https://launchpad.net/~oibaf/+archive/graphics-drivers/+build/5042398 [i386]
> 
> 
> To find out which mesa packages you have installed (hopefully nothing else
> has a matching version string) :-
> 
> dpkg -l | grep ".*9.3~git[0-9]*.[0-9a-z]*~gd~.*"
> 
> 
> To install the debs download the appropriate packages to
> /path/to/some/directory and then :-
> 
> cd /path/to/some/directory
> 
> sudo dpkg -i *.deb
> 
> 
> You can usually find the debs from an older mesa version by looking in apt's
> archives :-
> 
> ls -lrt /var/cache/apt/archives/*_9.3~git[0-9]*.[0-9a-z]*~gd~*
> 
> And copy them somewhere for easy installation :-
> 
> cp /var/cache/apt/archives/*_9.3~git1309040912.644fbb~gd~*
> /path/to/some/directory
> 
> 
> Hopefully you can find out which version breaks your install or at least get
> things working again.

Thank you Blake,

I reverted the mesa deb's to 9.3~git1309201759 Sept 20th version and my system
is working again.

Then i update my system with the debs from Sept 23rd 9.3~git1309231016 but my system is still ok.

Only updating to the deb's from Sept 30th 9.3~git1309300954.868791 break my system so it's probably a different issue from your.

Thank you again for your help, i have a working system again now.

Hi, 

Just to report dat i updated my system today to the latest deb's of the oibaff
ppa from october 7th 9.3~git1310070927.cfbfb5+glvdpau~gd~p and the system is running ok for now 30 min of use.

*** This bug has been marked as a duplicate of bug 69983 ***

Hi,

I was just lucky yesterday.
Today during boot the gpu lockup once again for 10 seconds, after that the boot goes normaly. The dmesg is attached.

I update again the system now to version 9.3~git1310080951.20bf50+glvdpau~gd~p
from the oibaf ppa.

I use the system normaly for 15 minutes now.

Created attachment 87338 [details]
dmesg-3.12rc4.txt

The lockup occurs at the 34 seconds of the boot process

Hi,

Everything is working fine for more than 4 days now so
i'm closing this bug.

Thank's to every one for the help.