From: Winfried Truemper <winni@xpilot.org>
To: Mark Hahn <hahn@coffee.psychology.mcmaster.ca>
Cc: Andre Hedrick <andre@linux-ide.org>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.0-test10pre5: still IDE lockups on HPT366 controller.
Date: Sun, 29 Oct 2000 20:11:15 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.21.0010291807580.3243-100000@localhost> (raw)
In-Reply-To: <Pine.LNX.4.10.10010242047010.31835-100000@coffee.psychology.mcmaster.ca>
On Tue, 24 Oct 2000, Mark Hahn wrote:
> > APIC error on CPU1 00(02) or 02(02) or 00(08) or 00(04)
>
> BP6 bugs, not linux's, and especially not ide's fault. you have to
> do the usual BP6 voodoo: bios update, extra fans, big PS, higher voltage.
On friday I bought a power supply with 431 watts, updated the BIOS to the
latest versions, put a fan on the BX chip like described on www.bp6.com,
screwed two high performance fans on the top of the non-overclocked
celerons (what a waste :) ) and set the voltage to 2.1 volts (tested 2.0,
too). No improvement in stability: after a few seconds bonnie crashes the
machine when used on hde4 or hdg4. Today I replaced the cables to enforce
UDMA 33 instead of UDMA 66 on hde and hdg. No problems so far. I can start
20 parallel bonnie's on the disks without any errors. This is an
acceptable fix for me, because the raid5-array would be limited by UDMA33
on hda and hdc anyways.
Regarding the APIC messages... I see no rule when they occur. I believe
they were gone when using the better power supply, but perhaps I just
didn't tested long enough before I returned this expensive box...
Regards
-Winfried
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
parent reply other threads:[~2000-10-29 19:14 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <Pine.LNX.4.10.10010242047010.31835-100000@coffee.psychology.mcmaster.ca>]
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=Pine.LNX.4.21.0010291807580.3243-100000@localhost \
--to=winni@xpilot.org \
--cc=andre@linux-ide.org \
--cc=hahn@coffee.psychology.mcmaster.ca \
--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®