On Tue, Dec 25, 2007 at 10:39:55 +0100, Michael Karcher wrote:
> But if a bug prevents the use of certain features completely, nothing
> can be broken by fixing this bug, so a fix might be appropriate for
> stable. Debian isn't doing it because of the philosophy of only adding
> security updates t
Am Montag, den 24.12.2007, 23:28 +0100 schrieb Brice Goglin:
> Thank you very much for your input, I am going to forward all your
> analysis in the upstream bug and I hope someone will be here to confirm
> that you're right.
I got around to test a patched xserver on my 6x86 machine. The X server
Am Montag, den 24.12.2007, 15:58 +0100 schrieb Brice Goglin:
> > this bug is uncorrelated to Cyrix CPUs. It is caused by an bad
> > expression in the MMX detection code. Apparently, gas changed the
> > handling of local labels, so "jnz 1" does not assemble to the same as
> > "jnz 1f", which it once
Michael Karcher wrote:
The jump is only taken if CPUID is not present. The 6x68 CPUs are the
last ones where CPUID is not present (not enabled by some Cyrix-special
CPU configuration bit, in fact). Any Pentium has CPUID, the later Intel
486 (DX2 and upwards) has CPUID, any AMD processor since the
Michael Karcher wrote:
Package: xorg-server
Tags: patch
Hello,
this bug is uncorrelated to Cyrix CPUs. It is caused by an bad
expression in the MMX detection code. Apparently, gas changed the
handling of local labels, so "jnz 1" does not assemble to the same as
"jnz 1f", which it once did, IIRC
Package: xorg-server
Tags: patch
Hello,
this bug is uncorrelated to Cyrix CPUs. It is caused by an bad
expression in the MMX detection code. Apparently, gas changed the
handling of local labels, so "jnz 1" does not assemble to the same as
"jnz 1f", which it once did, IIRC. The documentation for g
Walter wrote:
> I can report that is problem is exists. I have this problem with my
> 6x86 processor / Mystique and Debian Etch.
>
> I can confirm that in XFree86 3.3.6 it worked fine. Problems started
> when I tried XFree86 4.0 and apparently they are still there now that
>
Walter wrote:
> I can report that is problem is exists. I have this problem with my
> 6x86 processor / Mystique and Debian Etch.
>
> I can confirm that in XFree86 3.3.6 it worked fine. Problems started
> when I tried XFree86 4.0 and apparently they are still there now that
> I've tried a new instal
Hi,
I can report that is problem is exists. I have this problem with my
6x86 processor / Mystique and Debian Etch.
I can confirm that in XFree86 3.3.6 it worked fine. Problems started
when I tried XFree86 4.0 and apparently they are still there now that
I've tried a new installation with a d
Brice Goglin wrote:
Hi,
About 2 years ago, you reported (or replied to) a bug in the Debian BTS
regarding the X server not starting on a Cyrix 6x86 processor. Did any
of you guys reproduce this problem recently? With Xorg/Etch? With latest
xserver-xorg-core in unstable?
Thanks,
Brice
I have
Hi,
About 2 years ago, you reported (or replied to) a bug in the Debian BTS
regarding the X server not starting on a Cyrix 6x86 processor. Did any
of you guys reproduce this problem recently? With Xorg/Etch? With latest
xserver-xorg-core in unstable?
Thanks,
Brice
--
To UNSUBSCRIBE, email to
I did some more checking, and I can reproduce the bug running
kernel-image-2.4.27-586tsc on the same machine. I also cross-checked
with another OS (FreeBSD 6.1-RELEASE) to see if this is an upstream
problem, and X.org crashed in the same place (while drawing the default
stipple) with a SIGSEGV;
I think I may have found the part that's causing trouble here.
In fb/fbpict.c, there's a function fbHaveMMX that uses inline assembler,
and appears to check for a 486 before trying to use CPUID. The Cyrix
chips support CPUID, but it's turned off by default (!!), so trying to
use it here makes
Package: xserver-xorg
Version: 1:7.0.20
Followup-For: Bug #353494
I'm playing with unstable on an old 486 (Cyrix 486DX2) and it's giving me the
same problem -- a SIGILL in the server while trying to draw the default
stipple. I have the latest Xorg.log.0 attached.
X Window System Ver
Package: xserver-xorg
Version: 6.9.0.dfsg.1-4
Severity: important
Hello,
After migration to testing, the X server crashes during startup on a
6x86L Cyrix CPU based machine (ie, i586 non MMX).
Xfree86 was working w/o problem.
Note that kernel 2.6 (tried 2.6.12 and 2.6.15) is very bad at detecting
15 matches
Mail list logo
