Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 26 Apr 2009 00:18:36 +0400
From:      Artem Kim <artem_kim@inbox.ru>
To:        Robert Noland <rnoland@freebsd.org>
Cc:        freebsd-x11@freebsd.org, freebsd-stable@freebsd.org
Subject:   Re: 7.2-PRERELEASE X-server hang in "drmwtq"
Message-ID:  <200904260018.36884.artem_kim@inbox.ru>
In-Reply-To: <1240679716.1946.26.camel@balrog.2hip.net>
References:  <200904030223.27059.artem_kim@inbox.ru> <200904252037.13795.artem_kim@inbox.ru> <1240679716.1946.26.camel@balrog.2hip.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Saturday 25 April 2009 21:15:16 you wrote:
> Ok, so my test is under gnome with metacity in composite mode.  Using
> zsh (I think bash can do this also)
>
> balrog% for ((i=0 ; i < 5 ; i++ )) do firefox &;done
>
> So, I've launched 5 firefox and 10 xterms... Neither produce the hang.
> Sitting in drmwtq means that you are waiting on the rendering engine to
> catch up and send you an interrupt.  Probably the best debugging that we
> are going to get is by:
>
> booting the system without starting X, kldload radeon and then set
> sysctl hw.dri.0.debug=1 and start X/KDE... trigger the lockup and send
> me the output of the debugging from /var/log/messages.
>
> robert.

I used the following script:

#!/bin/sh

TRY = 5

while [$ (TRY)-gt 0]; do

# Konqueror &
  okteta &
  kcalc &
  kwrite &

  TRY = `expr $ (TRY) - 1`

done

sleep 30
killall konqueror
killall okteta
killall kcalc
killall kwrite


If I set "hw.dri.0.debug = 1" the problem is not reproducing, even at very big 
values of ${TRY}.
However if hw.dri.0.debug = 0  one pass reproduces the problem.


If I set "hw.dri.0.debug=1" _after_ the server hang, I see the message:

Apr 25 23:44:04 test kernel: [drm: pid782: drm_ioctl] pid = 782, cmd = 
0x80046457, nr = 0x57, dev 0xffffff0001556d00, auth = 1
Apr 25 23:44:04 test kernel: [drm: pid782: drm_ioctl] returning 4
Apr 25 23:44:04 test kernel: [drm: pid782: drm_ioctl] pid = 782, cmd = 
0x80046457, nr = 0x57, dev 0xffffff0001556d00, auth = 1
Apr 25 23:44:04 test kernel: [drm: pid782: drm_ioctl] returning 4
Apr 25 23:44:04 test kernel: [drm: pid782: drm_ioctl] pid = 782, cmd = 
0x80046457, nr = 0x57, dev 0xffffff0001556d00, auth = 1
Apr 25 23:44:04 test kernel: [drm: pid782: drm_ioctl] returning 4
Apr 25 23:44:04 test kernel: [drm: pid782: drm_ioctl] pid = 782, cmd = 
0x80046457, nr = 0x57, dev 0xffffff0001556d00, auth = 1
Apr 25 23:44:04 test kernel: [drm: pid782: drm_ioctl] returning 4
Apr 25 23:44:04 test kernel: [drm: pid782: drm_ioctl] pid = 782, cmd = 
0x80046457, nr = 0x57, dev 0xffffff0001556d00, auth = 1
Apr 25 23:44:04 test kernel: [drm: pid782: drm_ioctl] returning 4

I try to apply this patch:
http://people.freebsd.org/ ~ rnoland/drm_radeon-copyin-fix-try2.patch

In my case the problem remains.




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200904260018.36884.artem_kim>