public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Lass <stevenlass1@home.com>
To: Rob Turk <r.turk@chello.nl>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.[<=6] kernel has Cyrix 'coma' bug?
Date: Sun, 22 Jul 2001 12:08:26 -0500	[thread overview]
Message-ID: <3B5B088A.8C48D55D@home.com> (raw)
In-Reply-To: <032701c112bb$170c2220$0101a8c0@aster>


Rob,

My CPU is a bit different than yours (sorry for not posting this with
the original message).

[root /root]# cat /proc/cpuinfo
processor       : 0
vendor_id       : CyrixInstead
cpu family      : 4
model           : 1
model name      : MediaGX 3x Core/Bus Clock
stepping        : 2
fdiv_bug        : no
hlt_bug         : no
sep_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : -1
wp              : yes
flags           :
bogomips        : 59.59

I posted my .config file if anyone is interested.  MTRR is not set.
http://members.home.net/stevenlass1/.config.txt

-steve

> ----- Original Message -----
> From: "Rob Turk" <r.turk@chello.nl>
> Newsgroups: lists.linux.kernel
> Sent: Sunday, July 22, 2001 4:23 PM
> Subject: Re: 2.4.[<=6] kernel has Cyrix 'coma' bug?
> 
> > "Steven Lass" <stevenlass1@home.com> wrote in message
> > news:cistron.3B5AD0DF.8DDC5D1E@home.com...
> > >
> > > dev-list,
> > >
> > > Every 2.4 kernel that I've tried freezes my Cyrix MediaGX system at boot
> > > up.
> > >
> >
> > For what it's worth, I use the Slackware 8.0 distribution, and have no
> > trouble running 2.4.[5-7] on my Cyrix MediaGX 233 MHz. Make sure MTTR is
> off
> > in your configuration, this has bit me in the *ss once...
> >
> > Rob
> >
> > ======
> > CPU: Before vendor init, caps: 00808131 01818131 00000000, vendor = 1
> > Working around Cyrix MediaGX virtual DMA bugs.
> > CPU: After vendor init, caps: 00808121 00818131 00000000 00000001
> > CPU:     After generic, caps: 00808121 00818131 00000000 00000001
> > CPU:             Common caps: 00808121 00818131 00000000 00000001
> > CPU: Cyrix MediaGXtm MMXtm Enhanced stepping 02
> > Checking 'hlt' instruction... OK.
> > POSIX conformance testing by UNIFIX
> > =======
> > robtu@pi8nos:/proc$ cat cpuinfo
> > processor       : 0
> > vendor_id       : CyrixInstead
> > cpu family      : 5
> > model           : 7
> > model name      : Cyrix MediaGXtm MMXtm Enhanced
> > stepping        : 2
> > cache size      : 16 KB
> > fdiv_bug        : no
> > hlt_bug         : no
> > f00f_bug        : no
> > coma_bug        : no
> > fpu             : yes
> > fpu_exception   : yes
> > cpuid level     : 2
> > wp              : yes
> > flags           : fpu msr cx8 cmov mmx cxmmx
> > bogomips        : 76.80
> >


       reply	other threads:[~2001-07-22 17:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <032701c112bb$170c2220$0101a8c0@aster>
2001-07-22 17:08 ` Steven Lass [this message]
2001-07-22 13:10 bug: 2.4.[<=6] kernel has Cyrix 'coma' bug? Steven Lass
2001-07-22 14:23 ` Rob Turk

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=3B5B088A.8C48D55D@home.com \
    --to=stevenlass1@home.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=r.turk@chello.nl \
    /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