From: Jaco Kroon <jkroon@cs.up.ac.za>
To: Balazs Ree <ree@ree.hu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: HPT370 locks up (2.4/2.6)
Date: Thu, 01 Apr 2004 13:40:42 +0200 [thread overview]
Message-ID: <406BFFBA.2030502@cs.up.ac.za> (raw)
In-Reply-To: <pan.2004.04.01.10.32.57.982363@ree.hu>
[-- Attachment #1: Type: text/plain, Size: 1267 bytes --]
Weird question, but do you perhaps have the APIC enabled?
Balazs Ree wrote:
>On Wed, 31 Mar 2004 10:54:01 +0200, Denis Vlasenko wrote:
>
>
>>You may need to serialize channel usage in driver code if it indeed
>>happens when both channels are working at the same time.
>>
>>
>
>Thank you, this tip was really useful.
>
>Setting #define HPT_SERIALIZE_IO in hpt366.h solves the lockups on my
>machine (ABIT KT7-RAID). There seems to be a small (10-20%) performance
>penalty involved according to the benchmarks on my RAID1 setup, but that's
>acceptable.
>
>If this solves the "hdd led stays on" freezups for others with HPT370
>(rev. 3) on motherboards with possibly buggy IRQ handling, then maybe this
>option could even be made settable through kernel config, together with an
>appropriate explanation.
>
>
>
--
Cohen's Law:
There is no bottom to worse.
===========================================
This message and attachments are subject to a disclaimer. Please refer to www.it.up.ac.za/documentation/governance/disclaimer/ for full details.
Hierdie boodskap en aanhangsels is aan 'n vrywaringsklousule onderhewig. Volledige besonderhede is by www.it.up.ac.za/documentation/governance/disclaimer/ beskikbaar.
===========================================
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3174 bytes --]
next prev parent reply other threads:[~2004-04-01 11:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-30 12:36 Balazs Ree
2004-03-31 8:54 ` Denis Vlasenko
2004-04-01 10:32 ` Balazs Ree
2004-04-01 11:40 ` Jaco Kroon [this message]
2004-04-01 18:14 ` Balazs Ree
2004-03-30 12:47 Balazs Ree
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=406BFFBA.2030502@cs.up.ac.za \
--to=jkroon@cs.up.ac.za \
--cc=linux-kernel@vger.kernel.org \
--cc=ree@ree.hu \
/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®