Message-ID: <3AE1DE3F.5000101@bigfoot.com>
Date: Sat, 21 Apr 2001 15:23:43 -0400
From: "Trever L. Adams" <trever_Adams@bigfoot.com>
User-Agent: Mozilla/5.0 (X11; U; Linux 2.4.3 i686; en-US; rv:0.8.1+) Gecko/20010421
MIME-Version: 1.0
To: Juri Haberland <juri@koschikode.com>
CC: linux-kernel@vger.kernel.org
Subject: Re: Crash: XFree86 4.0.3 and Kernel 4.0.3
In-Reply-To: <20010421180845.18802.qmail@babel.spoiled.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org

Juri Haberland wrote:

> 
> Hi Trevor,
> 
> I have the same problem with almost the same combination (RH 7.0 instead of
> RH 7.1). Did you compile the XFree server yourself and if so, did you
> optimize it for i686? The reason why I'm asking is that I did that and
> suspected the optimazions to cause the crashes.
> 
> Juri
> 
> 

Juri, et al.

    I did some searches on google.  It seems that it is the combination 
of kernel 2.4, glibc2.2.x, and possibly the i686 optimizations.  I found 
my machine was alive from a network connection.  The problem is, I cant 
get my keyboard back even with sysrq (syslog does show it changing into 
XLATE mode... I thought alt-ctrl-r was raw?).  Of course the machine was 
alive, but X was dead. xscreensaver and the screen save it ran along 
with most of the desktop stuff was still running.

  Anyway, I tried 'shutdown -r now'over the network. Didn't work.  I had 
to do a hard reset.  So it seems the kernel may be slightly left in an 
unknown or confused state.

I did not compile it myself.  Using RedHat 7.1 standard.

Since I saw this mentioned here recently, does gcc still think 686=cmov? 
If so, Alan or someone else, does Athlon classic (slot 800 Mhz) support 
cmov?

Trever Adams

-
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/