Message-ID: <3D99A53D.2090008@attbi.com>
Date: Tue, 01 Oct 2002 08:38:05 -0500
From: Jordan Breeding <jordan.breeding@attbi.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020826
MIME-Version: 1.0
To: linux-kernel@vger.kernel.org
Subject: [BUG] problem with 2.5.x and X
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1496
Lines: 32

Hello,

   I have been having some strange problems with X for a while in 2.5.x 
(I started noticing them around 2.5.33 or 2.5.35 I believe) but I was 
having other problems as well so I waited for those to go away in hope 
that the problems with X would as well.  The other problems I was seeing 
are gone with 2.5.39-bk from last night, but my problems with X are 
still here.  Here they are:

1) Whether I have a frame buffer active or not I can not log into a gdm 
session and then lof out without my machine completely locking up when 
it gets back to the gdm screen, no sysrq, no nothing.

2) If a framebuffer is active I cannot even switch between VTs and my X 
session using ctrl-alt-f<vt> without the same lockup as above happening.

I don't really know what is causing this since I though it might have 
been the framebuffer/console stuff but not using the framebuffer only 
fixes part of the problem not the whole thing so I now think that the 
framebuffer code simply makes the problem more noticeable.

My machine is a dual cpu Athlon (Athlon MPs) with 1 GB and only scsi 
drives.  It has smp, preempt, and highmem enabled in the config.  Please 
let me know if you need more info to try and figure out what is going on.

Jordan Breeding

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/