7.2-PRERELEASE X-server hang in "drmwtq"
rnoland at FreeBSD.org
Sat Apr 25 17:15:38 UTC 2009
On Sat, 2009-04-25 at 20:37 +0400, Artem Kim wrote:
> On Saturday 25 April 2009 19:18:43 Robert Noland wrote:
> > On Sat, 2009-04-25 at 16:24 +0400, Artem Kim wrote:
> > > I checked 7.2 RC2 problem still here.
> > >
> > > I found a way to reproduce the problem easily.
> > >
> > > I used KDE 4.2.2 composite manager is enabled. The problem occurs when
> > > two applications run in a way that their window to appear at the same
> > > time.
> > Ok, luckily I don't think that KDE is important... compositing might be.
> > Can you give a more complete example of how to trigger the hang? I
> > don't have any r300 based cards handy right now. AMD is sending them
> > though, so it shouldn't be long...
> > > I can reproduce the problem on the cards Radeon 9800 XT (AMD64 UP) and
> > > Radeon X550 (AMD64 SMP).
> > Are these AGP or PCI(e)?
> > robert.
> I'm using KDE 4.2.2 as a test.
> The problem occurs only if the composite manager is enabled.
> The problem occurs spontaneously when the new window is created.
> A reliable way to reproduce the problem - run concurrently
> several applications that create new windows. Typically, a window appears on
> the screen with some delay after starting the application.
> Time delays occur (drawing) of a new window depending on the application.
> The problem occurs if one or more applications have opened new windows
> (the window starts to draw on the screen) at about the same time.
> You can run fast (this is important) one after another "Konqueror", "System
> Settings", "File Manager", it is enough to reproduce the problem.
> The problem looks like this:
> X-server in "drmwtq" state.
> The screen freezes or just turns off.
> The keyboard sometimes works, sometimes not.
> I used a 9800 AGP at the UP and X550 PCI-E to the SMP AMD64 system.
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 Noland <rnoland at FreeBSD.org>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 196 bytes
Desc: This is a digitally signed message part
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090425/62d0207b/attachment.pgp
More information about the freebsd-stable