On Thu, 8 Jul 2004 at 17:49:30 -0500, Branden Robinson wrote:
retitle 256356 xserver-xfree86: [ati/radeon] X server freezes computer with
2.6.7 kernel, but not 2.6.6 on Radeon Mobility M6 LY rev 0
tag 256356 + moreinfo
thanks
On Sat, Jun 26, 2004 at 03:16:30PM +0200, Samuel Mimram wrote:
I have no problems running X under the 2.6.6 kernel (built from Debian
sources). However when I start it under a 2.6.7 kernel (built from
vanilla sources) there is a black screen when X starts and the
computer is freezed (I am not able to switch to a console). I believe
this is related to the radeon driver:
- when I use the vesa driver or when I disable the hardware acceleration
(NoAccel option), X starts correctly
- when I enable hardware acceleration but I comment the line which sets
AGPMode to 4, X runs correctly for about 1 minute an then freezes (I
cannot switch to a console)
- when hardware acceleration is activated and AGPMode is set to 4 X
freezes immediately
I did not find anything suspicious in the syslog but I might have missed
something. Feel free to tell me if you want me to do some experiments,
etc.
Can you tell me why you think this is an XFree86 bug, and not a kernel bug?
Brandon -
Sorry for such a late addition to this thread. I'm running debian unstable (sue me)
with a 2.6.8 kernel, using nvidia drivers. XFree is version 4.3.0.1
(Debian 4.3.0.dfsg.18 20040928112350).
My problem is that I can be running for a while and then the X server seems to
freeze up. The cursor still follows the mouse, but I cannot get to the virtual
consoles (CTRL-ALT-F1, etc) and CTRL-ALT-DELETE doesn't respond either. When this
system is on the network, however, I can log in via ssh and top shows me that the
X server is running at 80% or more of the CPU. If I kill it, X restarts and I can
again work for a while on the console/head. A while can be a minute or an
hour;
it really seems to be random.
I _have_ tried searches for xfree freeze and xfree hang but these do not
seem to
come up with descriptions that map to my experience. If you or someone can
suggest
a way to better report this problem (it's not trivially reproducible) I'd
appreciate
the help. I am willing to put XFree into a higher level of debug mode. I
didn't see
anything obvious in the XFree86.0.log or in /var/log/messages, but perhaps I
didn't
filter the forest well enough to see the important trees.
Thanks,
-Del
