Bug 12093 - XF86_S3 crash with Diamond Stealth 64
XF86_S3 crash with Diamond Stealth 64
Product: Red Hat Linux
Classification: Retired
Component: XFree86 (Show other bugs)
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Preston Brown
Depends On:
  Show dependency treegraph
Reported: 2000-06-11 14:36 EDT by Tim Waugh
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-06-12 07:32:28 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
XF86_S3 -xf86config /tmp/XF86Config.test (3.43 KB, text/plain)
2000-06-11 14:40 EDT, Tim Waugh
no flags Details
echo where | gdb XF86_S3 core (1.08 KB, text/plain)
2000-06-11 14:41 EDT, Tim Waugh
no flags Details

  None (edit)
Description Tim Waugh 2000-06-11 14:40:01 EDT
(My report got eaten by bugzilla.  I'll try attaching files instead.)

Got an X crash.  Managed to reproduce it on VT2 with VT1 on scroll-lock to
prevent rebooting.  Used ulimit -c unlimited to get a core.  Used ftp to
analyse it.

I've mailed XFree86@XFree86.org already.
Comment 1 Tim Waugh 2000-06-11 14:40:56 EDT
Created attachment 400 [details]
XF86_S3 -xf86config /tmp/XF86Config.test
Comment 2 Tim Waugh 2000-06-11 14:41:34 EDT
Created attachment 401 [details]
echo where | gdb XF86_S3 core
Comment 3 Tim Waugh 2000-06-12 07:32:26 EDT
Incidentally, this is on a 486 that's it's happening.  I guess that's probably
relevant since the crash is from a SIGILL.  Is the XF86_S3 binary built i386?
Comment 4 Tim Waugh 2000-06-15 06:07:21 EDT
I've investigated this a bit further.

The XF86_S3 that's actually _installed_ works fine with the XF86Config.test from
the installer, but the one on the CD that I burnt doesn't.  I think it must just
be a bad CD (the XF86_S3 grabbed from the CD is different than the one in the
iso image).

Sorry for the bogus report.

Note You need to log in before you can comment on or make changes to this bug.