From: Matthias-Christian Ott <matthias.christian@tiscali.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Cyrix 6x86 Comma Bug 2.6
Date: Tue, 21 Dec 2004 14:30:47 +0100 [thread overview]
Message-ID: <41C82587.6030705@tiscali.de> (raw)
In-Reply-To: <1103588598.32550.1.camel@localhost.localdomain>
Alan Cox wrote:
>On Llu, 2004-12-20 at 22:26, Denis Vlasenko wrote:
>
>
>>It is very unlikely that you see "Coma" bug. It can be triggered only
>>by deliberately coded tight endless loop. "Ugly tokens on the screen"
>>suggest that you see something else.
>>
>>
>
>Presumably those tokens included "Oops" somewhere near the top and
>function names. The Cyrix stuff is notoriously hard to keep cool so that
>may be a good thing to check, as well as running memtest86+ to check the
>RAM.
>
>Also some very early stepping 6x86 Cyrixes simply don't run Linux
>reliably and it seemed to be cache problems in the CPU.
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.tux.org/lkml/
>
>
>
Hi!
The problem wasn't the comma bug, one of the pci slots is broken. But
thanks for your interest.
Sincerely
Matthias-Christian Ott
prev parent reply other threads:[~2004-12-21 13:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-18 11:52 Cyrix 6x86 Comma Bug 2.6 Matthias-Christian Ott
2004-12-20 22:26 ` Denis Vlasenko
2004-12-21 0:23 ` Alan Cox
2004-12-21 13:30 ` Matthias-Christian Ott [this message]
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=41C82587.6030705@tiscali.de \
--to=matthias.christian@tiscali.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
/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