Starting from CVS from the beginning of february my IGP 320M stopped to work. If i have dri activated ,when i start Xorg i just get blank screen. In Xorg logs i can see a lot of messages like: (EE) RADEON(0): RADEONWaitForIdleCP: CP idle -16 (EE) RADEON(0): Idle timed out, resetting engine... (**) RADEON(0): EngineRestore (32/32) Xserver use all cpu but still i can login with ssh. When i activated debug in radeon kernel module i got next error messages: [drm:radeon_do_wait_for_idle] *ERROR* failed! radeon_status: RBBM_STATUS = 0x80010140 CP_RB_RTPR = 0x00000000 CP_RB_WTPR = 0x0000000c AIC_CNTL = 0x00000002 AIC_STAT = 0x00000004 AIC_PT_BASE = 0x00000000 TLB_ADDR = 0x00000000 TLB_DATA = 0x00000000 I use debian/unstable 2.6.15 kernel and use drm cvs , by the way i have the same problems with drm from 2.6.15 kernel. I have no problem with Xorg 6.9
Does this also happen with the recently created ati-1-0-branch in CVS? In either case, please attach (as opposed to paste) the X server logfile and corresponding config file.
I used ati driver from ati-1-0-branch ,but it could not be compiled with current HEAD of xserver. So i applied manually patches for EXA which were already in ati HEAD . After this , at least with XAA, i donot have problems anymore. So after merging ati-1-0-branch to HEAD bug can be closed. I had still different type of problem with EXA but it is probably because of my manual applying.
Created attachment 4930 [details] xorg.conf
Created attachment 4931 [details] Xorg log with EXA
I tried again ati-1-0 branch with EXA and it does not work. So i attached my config and logs.
You mean that stock 7.0 server with ati-1-0-branch works with XAA and not EXA ? Hrm... that's interesting. Can you double check that it was the only difference between your tests ? That is, you didn't for example, inadvertently have DRI disabled in your XAA test or something like that ?
It was not stock 7.0 server it was CVS checkout from march 14 the same for Mesa. Also i experienced already hard lock 2 times even with XAA during 2-3 hours. I will try to post logs later. Concerning EXA , yes i can not even start it with ati-branch or trunk.It give me black screen. But errors are little different.
yes i am sure DRI was enabled for both cases (XAA and EXA)
Created attachment 4947 [details] Xorg log with EXA
Can you try the current CVS ? Either ati-1-0-branch if you are compiling against 7.0 or the HEAD of trunk if you are compiling against a recent cvs server...
Ok, look like, with current cvs of ati and xorg al my problems are fixed. I can start xserver with exa and not lockup for several hours. I will continue to run it for several more hours and if no lockups , bug can be closed.
Created attachment 4975 [details] Xorg log for EXA cvs 16 March
After verification i found out that configure script did not detect exa version and disabled it for radeon . So what i tested was XAA. After several hours of running even XAA still locked up my laptop. And there is nothing in Xorg log. I manually activated EXA , and xserver still lock pc during start up. I attached Xorg log. This time logs are different after your latest fixes, but still result the same.
Marking broken (status null/blank) bugs in xorg with no activity in a long time as fixed. Please reopen if you think it's necessary, but first do a search if a similar bug report is already filed and in a NEW/ASSIGNED state. These bugs do not currently show in most search results as they do not have any status. Sorry for this janitorial spam, you know where to send hate mails to when your inbox gets full of bugs you're subscribed to.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.