Re: Bug#287249: xserver-xfree86: Crashes on SPARC with Elite3D/m6
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sat, 26 Mar 2005, David S. Miller wrote:
On Sat, 26 Mar 2005 20:32:44 +0100
"T.Amm" <feb05@todesstrahlen.de> wrote:
Any other install kernel just gives me a "MMU-Fast Instruction Miss". So
I am actually damned with Solaris - which is not *so* bad - but what's
life without Linux?
Use the latest Sarge testing boot images, I'm happily running
Debian on my 1.5GHZ SB1500
Back to the bug report. The X server already makes a check, but
there was some talk the other week about this check crashing
Creator3D chips (since we poke a register that only exists on
the Elite3D card to check this) so it's possible someone patched
the test out or changed it.
No. That check in sunffb is not changed. Apparently a reboot cured the
original problem; I have heard nothing further on it.
I was prepared to modify the check for the reporter and for the reporter
only: after all, sunffb has been running fine for years, and this looked
like a one-user problem. It seems it was a no-user problem, and sunffb is as it
always has been.
I haven't looked at the X server sources in a year or so unfortunately,
so I'm pretty out of touch with the current state of the tree.
And with a million and a half networking and sparc64 kernel things to
do, I doubt I'll get back to it any time soon.
Only recent changes to sunffb are yours for XAA & friends.
By the way, you get that abort from xfree/xorg and sunffb and Elite when,
as here, you do not have the microcode loaded. If you install and load
the afb microcode, that abort should go away. (As, I believe, the bug
reporter indicates.) Someday I might even look at why this is the case.
Hope this is close to on topic,
Regards,
Ferris
- --
Ferris McCormick (P44646, MI) <fmccor@gentoo.org>
Developer, Gentoo Linux (sparc)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFCRexUQa6M3+I///cRAinxAJ0ZO1s0iPZWoexR04MU/ZM+XPlxPQCfZSs9
y2r4nznr+nrLgj2UdRCdLKs=
=V0en
-----END PGP SIGNATURE-----
Reply to: