From: Keith Owens <kaos@ocs.com.au>
To: "Robbert Kouprie" <robbert@radium.jvb.tudelft.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: The buggy APIC of the Abit BP6
Date: Thu, 20 Jun 2002 00:03:19 +1000 [thread overview]
Message-ID: <25764.1024495399@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Wed, 19 Jun 2002 15:23:13 +0200." <005f01c21794$7702b520$020da8c0@nitemare>
On Wed, 19 Jun 2002 15:23:13 +0200,
"Robbert Kouprie" <robbert@radium.jvb.tudelft.nl> wrote:
>I know the hardware sucks bad, but what's wrong with trying to work
>around the problem providing noone else is bugged by the workaround?
You do not have the data required to (a) detect the problem and (b)
recover even if you could detect the problem. The APIC bus has a
single bit checksum, the APIC hardware detects single bit errors and
does a retransmission. It _cannot_ detect double bit errors, the bad
data is accepted and processed with undefined side effects.
What you see in the logs for a BP6 are error messages for single bit
errors that were recovered by the hardware. You will never see
messages for double bit errors, just unexplained oops and/or machine
hangs.
Yes, I have a BP6 :(.
next prev parent reply other threads:[~2002-06-19 14:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-12 22:33 Robbert Kouprie
2002-06-13 9:05 ` Helge Hafting
2002-06-13 13:30 ` Robbert Kouprie
2002-06-14 10:54 ` Helge Hafting
2002-06-18 15:30 ` Robbert Kouprie
2002-06-18 15:17 ` Zwane Mwaikambo
2002-06-19 12:47 ` Maciej W. Rozycki
2002-06-19 13:23 ` Robbert Kouprie
2002-06-19 14:03 ` Keith Owens [this message]
2002-06-19 14:35 ` Maciej W. Rozycki
2002-06-20 1:50 ` Robbert Kouprie
2002-06-19 14:22 ` Maciej W. Rozycki
2002-06-20 12:21 ` Helge Hafting
2002-06-20 13:10 ` Maciej W. Rozycki
2002-06-21 13:02 ` Helge Hafting
2002-06-20 22:29 ` Kevin Krieser
2002-06-14 15:07 ` Raphael Manfredi
2002-06-14 16:49 Robbert Kouprie
2002-06-14 18:41 ` Raphael Manfredi
2002-06-18 7:33 ` Helge Hafting
2002-06-18 9:53 Robbert Kouprie
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=25764.1024495399@ocs3.intra.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=robbert@radium.jvb.tudelft.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
all inboxes | Powered by JetHome®