From: David Weinehall <tao@acc.umu.se>
To: asenec@senechalle.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: /proc/cpuinfo for Intel P4 D850GB
Date: Mon, 19 Mar 2001 13:02:41 +0100 [thread overview]
Message-ID: <20010319130241.J10321@khan.acc.umu.se> (raw)
In-Reply-To: <200103190207.UAA13397@senechalle.net>
In-Reply-To: <200103190207.UAA13397@senechalle.net>; from asenec@senechalle.net on Sun, Mar 18, 2001 at 08:07:20PM -0600
On Sun, Mar 18, 2001 at 08:07:20PM -0600, asenec@senechalle.net wrote:
> On a 2.0.36 kernel the above-referenced mb
> shows:
>
> dragonwind:/proc# cat cpuinfo
> processor : 0
> cpu : ?86
> model : 386 SX/DX
> vendor_id : GenuineIntel
>
> At the least, java breaks because of the '?' char.
>
> Is the problem is due to the older 2.0.36 kernel,
> or would the problem also present itself on a newer 2.2.x kernel?
Ahhhh, bit by the "IV written as 15 by Intel"-bug.
I'll hack up a fix to apply against v2.0.39.
And no, you won't be bit by this bug in a recent v2.2 or v2.4 kernel.
/David
_ _
// David Weinehall <tao@acc.umu.se> /> Northern lights wander \\
// Project MCA Linux hacker // Dance across the winter sky //
\> http://www.acc.umu.se/~tao/ </ Full colour fire </
next prev parent reply other threads:[~2001-03-19 12:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-19 2:07 asenec
2001-03-19 2:33 ` davej
2001-03-19 3:14 ` 2.4.3-pre4: Unable to handle kernel NULL pointer dereference at virtual address 000000fb Shawn Starr
2001-03-19 12:02 ` David Weinehall [this message]
2001-03-19 21:58 ` Shawn Starr
2001-03-20 17:01 ` Question about memory usage in 2.4 vs 2.2 Josh Grebe
2001-03-20 17:32 ` Jakob Østergaard
2001-03-20 20:29 ` Josh Grebe
2001-03-21 19:16 ` Jan Harkes
2001-03-21 19:54 ` Rik van Riel
2001-03-20 18:54 ` Jan Harkes
2001-03-20 20:29 ` Josh Grebe
2001-03-20 22:18 ` Rik van Riel
2001-03-20 22:29 ` Juha Saarinen
2001-03-21 9:28 ` Zou Min
2001-03-21 9:51 ` Andreas Dilger
2001-03-21 10:56 ` Zou Min
2001-03-21 10:14 Manfred Spraul
2001-03-21 17:42 ` Josh Grebe
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=20010319130241.J10321@khan.acc.umu.se \
--to=tao@acc.umu.se \
--cc=asenec@senechalle.net \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®