From: "Trever L. Adams" <trever_Adams@bigfoot.com>
To: Juri Haberland <juri@koschikode.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Crash: XFree86 4.0.3 and Kernel 4.0.3
Date: Sat, 21 Apr 2001 15:23:43 -0400 [thread overview]
Message-ID: <3AE1DE3F.5000101@bigfoot.com> (raw)
In-Reply-To: <20010421180845.18802.qmail@babel.spoiled.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
next prev parent reply other threads:[~2001-04-21 19:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-21 16:40 Crash: XFree86 4.0.3 and Kernel 4.0.3 Trever L. Adams
2001-04-21 18:08 ` Juri Haberland
2001-04-21 19:23 ` Trever L. Adams [this message]
2001-04-22 2:43 ` Horst von Brand
2001-04-22 3:24 ` Crash: XFree86 4.0.3 and Kernel 2.4.3 Trever L. Adams
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3AE1DE3F.5000101@bigfoot.com \
--to=trever_adams@bigfoot.com \
--cc=juri@koschikode.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox