From: torvalds@transmeta.com (Linus Torvalds)
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.1-pre1 breaks XFree 4.0.2 and "w"
Date: 11 Jan 2001 00:41:12 -0800 [thread overview]
Message-ID: <93jrj8$1jc$1@penguin.transmeta.com> (raw)
In-Reply-To: <3A5C6417.6670FCB7@Hell.WH8.TU-Dresden.De> <20010110181516.X10035@nightmaster.csn.tu-chemnitz.de> <3A5C96BB.96B19DB@Hell.WH8.TU-Dresden.De>
In article <3A5C96BB.96B19DB@Hell.WH8.TU-Dresden.De>,
Udo A. Steinberg <sorisor@Hell.WH8.TU-Dresden.De> wrote:
>
>Next backed out the entire XMM and FXSR related stuff and now everything
>is fine again. The CPU in question is an AMD Thunderbird (see cpuinfo
>below). A friend with a similar setup but a Pentium-3 CPU doesn't seem
>to see the problem (couldn't verify myself).
Mind trying it with the "HAVE_FXSR" and "HAVE_XMM" macros in
linux/include/asm-i386/processor.h
fixed? They _should_ be just
#define HAVE_FXSR (cpu_has_fxsr)
#define HAVE_XMM (cpu_has_xmm)
instead of testing random bits in CR4 that have different meaning on
different CPU's.
I'm surprised actually - the same CR4 tests are in newer 2.2.x kernels,
I think. (And in 2.2.x kernels, the above "cpu_has_xxx" do _not_ work
unless FP exception testing etc has been fixed in the 2.2.x tree)
Andrea?
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-11 8:41 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-10 13:31 2.4.1-pre1 breaks XFree 4.0.2 and "w" Udo A. Steinberg
2001-01-10 17:15 ` Ingo Oeser
2001-01-10 17:07 ` Udo A. Steinberg
2001-01-10 20:00 ` Jonathan Hudson
2001-01-11 8:41 ` Linus Torvalds [this message]
2001-01-11 12:54 ` Alan Cox
[not found] ` <200101110841.AAA01652@penguin.transmeta.com>
2001-01-11 10:05 ` Udo A. Steinberg
2001-01-11 10:11 ` Andi Kleen
2001-01-11 10:31 ` Udo A. Steinberg
2001-01-11 17:36 ` Andrea Arcangeli
2001-01-11 17:46 ` Andrea Arcangeli
2001-01-11 17:48 ` Andrea Arcangeli
2001-01-11 18:53 ` Andrea Arcangeli
2001-01-12 2:08 ` Linus Torvalds
2001-01-12 3:45 ` Andrea Arcangeli
2001-01-12 4:26 ` Linus Torvalds
2001-01-12 16:02 ` Andrea Arcangeli
2001-01-12 16:42 ` Richard A Nelson
2001-01-12 17:05 ` Andrea Arcangeli
2001-01-12 17:35 ` Linus Torvalds
2001-01-12 17:54 ` Alan Cox
2001-01-12 18:35 ` Linus Torvalds
2001-01-12 18:57 ` Andrea Arcangeli
2001-01-12 19:19 ` Laramie Leavitt
2001-01-12 20:39 ` Mark Hahn
2001-01-12 18:24 ` Andrea Arcangeli
2001-01-15 20:33 ` [PATCH] i386/setup.c cpuinfo notsc Hugh Dickins
2001-01-15 20:48 ` H. Peter Anvin
2001-01-15 21:38 ` Maciej W. Rozycki
2001-01-15 21:41 ` H. Peter Anvin
2001-01-15 21:51 ` Maciej W. Rozycki
2001-01-16 3:47 ` H. Peter Anvin
2001-01-15 21:34 ` Maciej W. Rozycki
2001-01-18 16:39 ` [PATCH] udf writepage UnlockPage Hugh Dickins
2001-01-28 14:43 ` Hugh Dickins
2001-01-12 4:28 ` 2.4.1-pre1 breaks XFree 4.0.2 and "w" TimO
2001-01-12 6:06 ` Udo A. Steinberg
2001-01-12 9:47 ` Harold Oga
-- strict thread matches above, loose matches on Subject: below --
2001-01-11 4:58 Floating point broken between 2.4.0-ac4 and -ac5? junio
2001-01-11 12:42 ` Alan Cox
2001-01-11 17:16 ` junio
2001-01-12 3:27 ` Aaron Lehmann
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='93jrj8$1jc$1@penguin.transmeta.com' \
--to=torvalds@transmeta.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.