[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Lockups in Xorg with Radeon HD 3450 and different drivers



On Wed, 23 Jun 2010 18:06:23 -0400, Nick Lidakis wrote:

> On Wed, Jun 23, 2010 at 01:36:10PM +0000, Camaleón wrote:
>> Have you tried with the proprietary driver? Just for testing purposes.
> 
> No. I really don't want to use a closed driver. I purchased this card
> because I read (Xorg wiki) that this slightly older tech was well
> supported for a 2D desktop under Linux.

Then your best bet is reporting the problem at BTS.

With open drivers and KMS, Xorg should work "out-of-the-box" without the 
needing of creating or tweaking the "/etc/X11/xorg.conf" file so if you 
are experiencing such errors (hard locks) it is worth to open a bug 
report.
 
>> Another thing to try could be using KMS and no "xorg.conf"
>> configuration file to see what happens.
> 
> Ok, I just did and the machine locked up. No Magic SysRq. No SSH. Screen
> goes blank and monitor turns off. Thenm I did a dist-upgrade as there
> was a kernel upgrade to 2.6.32-5-686. Same result.
> 
> With the newer kernel, I can lockup the machine whether: KMS is on or
> off
> There is my aforementioned xorg.conf (radeon driver) or not.
> 
> Using the radeon driver in xorg.conf, commenting out the DRI section,
> and not using KMS I get X up but with a very slow cursor and no other
> response.
> 
> This from Xorg.log
> 
> 
> [mi] EQ overflowing. The server is probably stuck in an infinite loop.
> 
> Backtrace:
> 0: /usr/bin/X (xorg_backtrace+0x3b) [0x80addcb] 1: /usr/bin/X
> (mieqEnqueue+0x1ab) [0x80a053b] 2: /usr/bin/X
> (xf86PostMotionEventP+0xd2) [0x80b3492] 3:
> /usr/lib/xorg/modules/input/evdev_drv.so (0xb740f000+0x4831)
> [0xb7413831] 4: /usr/lib/xorg/modules/input/evdev_drv.so
> (0xb740f000+0x4b26) [0xb7413b26] 5: /usr/bin/X (0x8048000+0x6997f)
> [0x80b197f] 6: /usr/bin/X (0x8048000+0x1077d4) [0x814f7d4] 7: (vdso)
> (__kernel_sigreturn+0x0) [0xb7867400] 8: /usr/lib/libdrm.so.2
> (drmCommandNone+0x32) [0xb74082a2] 9:
> /usr/lib/xorg/modules/drivers/radeon_drv.so (0xb7310000+0x33c86)
> [0xb7343c86]10: /usr/lib/xorg/modules/drivers/radeon_drv.so
> (0xb7310000+0xb7ec1) [0xb73c7ec1]
> 11: /usr/lib/xorg/modules/libexa.so (0xb7140000+0x48c8) [0xb71448c8] 12:
> /usr/lib/xorg/modules/libexa.so (0xb7140000+0x4e76) [0xb7144e76] 13:
> /usr/lib/xorg/modules/libexa.so (0xb7140000+0x4fc3) [0xb7144fc3] 14:
> /usr/lib/xorg/modules/libexa.so (0xb7140000+0x5742) [0xb7145742] 15:
> /usr/lib/xorg/modules/libexa.so (0xb7140000+0x2439) [0xb7142439] 16:
> /usr/lib/xorg/modules/libexa.so (0xb7140000+0x449b) [0xb714449b] 17:
> /usr/lib/xorg/modules/libexa.so (0xb7140000+0x3842) [0xb7143842] 18:
> /usr/lib/xorg/modules/libexa.so (0xb7140000+0x3c3b) [0xb7143c3b] 19:
> /usr/bin/X (0x8048000+0xa076d) [0x80e876d]

That sounds serious :-/
 
> And from /var/log/messages I get pages of this: Jun 23 17:47:58 phobos
> kernel: [  160.567936] [drm] wait idle failed status : 0xA0003030
> 0x00000003
> 
> Anybody have any ideas why I'm having so much trouble just getting 2D
> working?

Because "Xorg" is getting updates and changes very quickly.

Greetings,

-- 
Camaleón


Reply to: