From: "Robbert Kouprie" <robbert@radium.jvb.tudelft.nl>
To: "'Keith Owens'" <kaos@ocs.com.au>,
"'Maciej W. Rozycki'" <macro@ds2.pg.gda.pl>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: The buggy APIC of the Abit BP6
Date: Thu, 20 Jun 2002 03:50:10 +0200 [thread overview]
Message-ID: <006e01c217fc$cfd1b620$020da8c0@nitemare> (raw)
In-Reply-To: <25764.1024495399@ocs3.intra.ocs.com.au>
Keith Owens wrote:
> You do not have the data required to (a) detect the problem and (b)
> recover even if you could detect the problem.
Maciej W. Rozycki wrote:
> The reliability of the hardware is next to null. You are not able to
> recover from that.
Okay, you guys convinced me that some hardware can suck *really* bad. I
think I'm just going to stop my effort on this, stay with Raphael
Manfredi's hack to avoid most of the hangs on my BP6 for now, and get a
new board ASAP.
Thanks for all the help,
- Robbert Kouprie
next prev parent reply other threads:[~2002-06-20 1:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-12 22:33 The buggy APIC of the Abit BP6 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
2002-06-19 14:35 ` Maciej W. Rozycki
2002-06-20 1:50 ` Robbert Kouprie [this message]
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
-- strict thread matches above, loose matches on Subject: below --
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='006e01c217fc$cfd1b620$020da8c0@nitemare' \
--to=robbert@radium.jvb.tudelft.nl \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@ds2.pg.gda.pl \
/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