From: Jeffrey Ingber <jhingber@ix.netcom.com>
To: linux-kernel@vger.kernel.org, xpert@XFree86.org,
alan@lxorguk.ukuu.org.uk
Subject: [FIXED] Random Sig'11 in XF864 with kernel > 2.2.x
Date: Tue, 18 Sep 2001 00:59:44 -0400 [thread overview]
Message-ID: <3BA6D4C0.1010309@ix.netcom.com> (raw)
The problem mentioned in the following threads:
http://www.uwsg.indiana.edu/hypermail/linux/kernel/0109.1/0932.html
http://www.xfree86.org/pipermail/xpert/2001-September/011055.html
http://www.xfree86.org/pipermail/xpert/2001-September/011230.html
Is fixed in at least 2.4.9-ac10. I haven't been a regular user of the
-ac series so I can't say when exactly this was fixed. However, this
problem still persists in Linus 2.4.10-pre10. Can anyone who chimed in
with similar problems to mine try said kernel (2.4.9-ac10) and provide
any feedback? It would excellent if the exact fix could be identified.
Thanks,
Jeffrey H. Ingber (jhingber _at_ ix.netcom.com)
> The random Sig 11's are observed in the stock XFree86 4.x drivers with
> none of the 'extras' enabled, such as DRI on several sets of video cards
> (Matrox and ATI). I can run both UP and SMP kernels in the 2.2 series
> and 2.4 UP kernels with unlimited uptimes. However, switching to a 2.4
> SMP kernel will cause random Sig 11's in X, seemingly irregardless of
> video card/vendor.=20
I'm aware of the reports. Its very hard to figure out what might be
involved. Later 2.4 kernels we have fixed the odd possible candidate where
segment registers or LDT propogation on SMP might go awry but nothing that
really explains the X11 ones and whether they are PCI/AGP setup , power
management or kernel bug triggered
Alan
next reply other threads:[~2001-09-18 4:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-18 4:59 Jeffrey Ingber [this message]
2001-09-18 8:31 ` [FIXED] Random Sig'11 in XF864 with kernel > 2.2.x Tobias Diedrich
2001-09-18 10:28 ` Polymorphic Anomaly
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=3BA6D4C0.1010309@ix.netcom.com \
--to=jhingber@ix.netcom.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=xpert@XFree86.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