From: Brian Gerst <bgerst@didntduck.org>
To: James Nord <teilo@cdt.luth.se>
Cc: linux-kernel@vger.kernel.org
Subject: Re: K6 sig11 Bug detection.
Date: Fri, 17 Aug 2001 06:22:24 -0400 [thread overview]
Message-ID: <3B7CF060.D3E1F6B5@didntduck.org> (raw)
In-Reply-To: <3B7CEE40.90100@cdt.luth.se>
James Nord wrote:
>
> Hi,
>
> I have a Debian based system with a custom 2.4.7 kernel compiled with
> gcc version 2.95.4 20010703 (Debian prerelease)
> (also saw the same with 2.2.10+ gcc 2.95)
>
> The CPU in the machine is a AMD K6 200MHz, and has 64MB of SDRAM
>
> I reomved the heatsink and the serial is Cxxxxxxxx, however in the
> kernel boot messages I get the following,
>
> Aug 17 09:06:49 phoenix kernel: CPU: Before vendor init, caps: 008001bf
> 008005bf 00000000, vendor = 2
> Aug 17 09:06:49 phoenix kernel: AMD K6 stepping B detected - <6>K6 BUG
> 9016725 20000000 (Report these if test report is incorrect)
> Aug 17 09:06:49 phoenix kernel: AMD K6 stepping B detected - probably OK
> (after B9730xxxx).
> Aug 17 09:06:49 phoenix kernel: Please see
> http://www.mygale.com/~poulot/k6bug.html
> Aug 17 09:06:49 phoenix kernel: CPU: L1 I Cache: 32K (32 bytes/line), D
> cache 32K (32 bytes/line)
> Aug 17 09:06:49 phoenix kernel: CPU: After vendor init, caps: 008001bf
> 008005bf 00000000 00000000
> Aug 17 09:06:49 phoenix kernel: CPU: After generic, caps: 008001bf
> 008005bf 00000000 00000000
> Aug 17 09:06:49 phoenix kernel: CPU: Common caps: 008001bf
> 008005bf 00000000 00000000
> Aug 17 09:06:49 phoenix kernel: CPU: AMD-K6tm w/ multimedia extensions
> stepping 01
>
> Is the stepping not the first part of the serial? I have 64MB (the
> amount that triggers the bug IIRC) in the system and the the kernel and
> everything else compiles without generating a SIG11.
>
> Is this a false detection or would it be possible that I have a wrongly
> tagged CPU?
>
> Also the link http://www.mygale.com/~poulot/k6bug.html does not exist.
>
> Please CC replies to me as I am not on the list.
You have a later B step CPU with that bug fixed. Otherwise you would
have seen "system stability may be impaired when more than 32 MB are
used." in the logs. For some reason, AMD didn't bump the stepping when
they fixed that bug.
--
Brian Gerst
next prev parent reply other threads:[~2001-08-17 10:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-17 10:13 K6 sig11 Bug detection James Nord
2001-08-17 10:22 ` Brian Gerst [this message]
2001-08-17 12:05 ` [New URL FOR K6 bug] " André Dahlqvist
[not found] <no.id>
2001-08-17 10:28 ` Alan Cox
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=3B7CF060.D3E1F6B5@didntduck.org \
--to=bgerst@didntduck.org \
--cc=linux-kernel@vger.kernel.org \
--cc=teilo@cdt.luth.se \
/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