freebsd stable - Feb 2010 - freebsd7, radeon, xorg-server -> deadlock or so

Hi all!

After updated the xorg* and dri* and dependency, the system going to
deadlock at second start of xserver. I think it is not an uniqe issue,
as others wrote them at freebsd-x11:
http://lists.freebsd.org/pipermail/freebsd-x11/2010-February/009370.html

The symptoms:
* independent from enabled or disabled DRI or GLX, first I think, this
is the error, but not
* the system going to deadlock state
* no coredumps of xorgs
* no panic, but the system is unusuable
* independent from the driver: probed the radeon and radeonhd driver
* independent from the WITHOUT_NOUVEAU or WITH_NOUVEAU compile options
(make.conf)
* the system is: FreeBSD peonia.teteny.bme.hu 7.3-PRERELEASE FreeBSD
7.3-PRERELEASE #29 r203612+fa83fdf: Mon Feb  8 02:11:08 CET 2010
root@peonia.teteny.bme.hu:/usr/obj/usr/src/sys/stable  amd64

On 02/10/10 00:24, Oliver Pinter wrote:
> Hi all!
>
> After updated the xorg* and dri* and dependency, the system going to
> deadlock at second start of xserver. I think it is not an uniqe issue,
> as others wrote them at freebsd-x11:
> http://lists.freebsd.org/pipermail/freebsd-x11/2010-February/009370.html
>
> The symptoms:
> * independent from enabled or disabled DRI or GLX, first I think, this
> is the error, but not
> * the system going to deadlock state
> * no coredumps of xorgs
> * no panic, but the system is unusuable
> * independent from the driver: probed the radeon and radeonhd driver
> * independent from the WITHOUT_NOUVEAU or WITH_NOUVEAU compile options
> (make.conf)
> * the system is: FreeBSD peonia.teteny.bme.hu 7.3-PRERELEASE FreeBSD
> 7.3-PRERELEASE #29 r203612+fa83fdf: Mon Feb  8 02:11:08 CET 2010
> root@peonia.teteny.bme.hu:/usr/obj/usr/src/sys/stable  amd64
> _______________________________________________
> freebsd-stable@freebsd.org mailing list,
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to
"freebsd-stable-unsubscribe@freebsd.org"
I had a similar freezing on several FreeBSD 8.0 boxes with either 
'radeon' or 'radeonhd/radeonhd-devel' with recent ports. With
more
expensive graphics cards, like HD4830, HD4850 we never had the issue, 
but with smaller cards, like HD4670. HD4670 never worked. HD4770 cards 
work with explicit set

option "DRI" "OFF"

As far as I know,  WITHOUT_NOUVEAU does have no effect on the current 
ports, since it is reported in ports/UPDATING, it prevents building 
nouveau driver which is broken when using newer libdrm/dri and libGLUT, 
but those new ports do not seem to be merged into the tree.

The situation is heavily unsatisfying, since one need an expensive 
AMD/ATi Radeon card to gain non-3D poor functionality, where a cheaper 
one should be do the same - but the cheaper ones don't work. Even if one 
uses AMD64, the situattion is worse and I have no reason using 
Linux-driver on a FreeBSD box. Hope the situation gets cleared in the 
nearest future. It's a kind of deadlock. As I said, either spenig a lot 
of money for a working RV770 based AMD graphics card with poor 
functionality or nothing so far, since most smaller RV730 chips aren't 
supported properly by the most recent drivers.

Regards,
Oliver

On Wed, Feb 10, 2010 at 4:54 AM, Oliver Pinter
<oliver.pntr@gmail.com>wrote:
> Hi all!
>
> After updated the xorg* and dri* and dependency, the system going to
> deadlock at second start of xserver. I think it is not an uniqe issue,
> as others wrote them at freebsd-x11:
> http://lists.freebsd.org/pipermail/freebsd-x11/2010-February/009370.html
>
> The symptoms:
> * independent from enabled or disabled DRI or GLX, first I think, this
> is the error, but not
> * the system going to deadlock state
> * no coredumps of xorgs
> * no panic, but the system is unusuable
> * independent from the driver: probed the radeon and radeonhd driver
> * independent from the WITHOUT_NOUVEAU or WITH_NOUVEAU compile options
> (make.conf)
> * the system is: FreeBSD peonia.teteny.bme.hu 7.3-PRERELEASE FreeBSD
> 7.3-PRERELEASE #29 r203612+fa83fdf: Mon Feb  8 02:11:08 CET 2010
> root@peonia.teteny.bme.hu:/usr/obj/usr/src/sys/stable  amd64
> _______________________________________________
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to
"freebsd-stable-unsubscribe@freebsd.org"
>
are you using intel wireless cards ? I had/having similar issues when such
freeze happens hard boot is the only option. I think it has something to do
with wlandev or something related to wpi driver. I cannot comment more since
coredumps are occasional and back trace suggests it is doadump().

here is my report earlier
http://lists.freebsd.org/pipermail/freebsd-questions/2009-November/207768.html

Oliver Pinter wrote:
> After updated the xorg* and dri* and dependency, the system going to
> deadlock at second start of xserver. I think it is not an uniqe issue,
> as others wrote them at freebsd-x11:
> http://lists.freebsd.org/pipermail/freebsd-x11/2010-February/009370.html
I have a similar problem with ATI Mobility Radeon 9000 (r250) and
FreeBSD 8.0-RELEASE-p2 i386 (dmesg is at [1]). The system hangs when I
run Xorg with xorg.conf obtained by `Xorg -configure' and do either of
these:

* pkill Xorg
* close xorg via ^C and start it again
* close xorg via ^C and kldunload radeon

I did not try using 'option "DRI" "OFF"' though, I
will this evening.

Unfortunately I can't currently say if it works under different
conditions, since after a number of hangs I switched to VESA. But if
anyone is interested, I'll investigate further and will provide any
additional information -- just name it.

[1] http://tx97.net/~magv/dmesg-t40.80-p2.txt

on 10/02/2010 18:01 Vitaly Magerya said the following:
> Andriy Gapon wrote:
>> Please check if your X binary is linked with libthr (using ldd).
>> I saw similar problems when it was not.
>> That was because it was compiled without HAL support.
> 
> It is not, and yes I use WITHOUT_HAL. Currently disabling DRI helps;
> should I try rebuilding xorg-server with HAL?
Please try, if even just to see if it helps.

-- 
Andriy Gapon

On Wed, 2010-02-10 at 18:01 +0200, Vitaly Magerya wrote:
> Andriy Gapon wrote:
> > Please check if your X binary is linked with libthr (using ldd).
> > I saw similar problems when it was not.
> > That was because it was compiled without HAL support.
> 
> It is not, and yes I use WITHOUT_HAL. Currently disabling DRI helps;
> should I try rebuilding xorg-server with HAL?
Yes, you can still disable hal at runtime by setting AutoAddDevices
"Off" in xorg.conf.

robert.

-- 
Robert Noland <rnoland@FreeBSD.org>
FreeBSD

Robert Noland wrote:
>> It is not, and yes I use WITHOUT_HAL. Currently disabling DRI helps;
>> should I try rebuilding xorg-server with HAL?
> 
> Yes, you can still disable hal at runtime by setting AutoAddDevices
> "Off" in xorg.conf.
Seems to work with HAL.

Unloading radeon also works, but the kernel prints this warning:

    Warning: memory type drm_bufs leaked memory on destroy (4
    allocations, 128 bytes leaked).

And Xorg fails on start afterward with:

    Fatal server error:
    no screens found

(The number of allocations and the amount of leaked memory may vary; 32
bytes per allocation is constant though).

I guess this means I should not unload it.