From: Jeff Garzik <jgarzik@pobox.com>
To: Martin Schlemmer <azarah@nosferatu.za.org>
Cc: akpm@osdl.org, torvalds@osdl.org,
Linux Kernel Mailing Lists <linux-kernel@vger.kernel.org>
Subject: Re: [BK PATCHES] 2.6.x libata update
Date: Fri, 13 Feb 2004 16:03:19 -0500 [thread overview]
Message-ID: <402D3B97.70005@pobox.com> (raw)
In-Reply-To: <1076700491.22542.38.camel@nosferatu.lan>
Martin Schlemmer wrote:
> On Fri, 2004-02-13 at 20:43, Jeff Garzik wrote:
>
> Hi
>
>
>><jgarzik@redhat.com> (04/02/13 1.1634)
>> [libata] catch, and ack, spurious DMA interrupts
>>
>> Hardware issue on Intel ICH5 requires an additional ack sequence
>> over and above the normal IDE DMA interrupt ack requirements. Issue
>> described in post to freebsd list:
>> http://www.mail-archive.com/freebsd-stable@freebsd.org/msg58421.html
>>
>> Since the bug workaround only requires a single additional PIO or
>> MMIO read in the interrupt handler, it is applied to all chipsets
>> using the standard libata interrupt handler.
>>
>> Credit for research the issue, creating the patch, and testing the
>> patch all go to Jon Burgess.
>>
>
>
> Did you miss the mail I sent about this locking my box in under
> 20-30 mins? It still looks the same as the previous one ....
Yes, I did. Can you test 2.6.3-rc2 + this patch?
Jeff
next prev parent reply other threads:[~2004-02-13 21:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-13 18:43 [BK PATCHES] 2.6.x libata update Jeff Garzik
2004-02-13 19:28 ` Martin Schlemmer
2004-02-13 21:03 ` Jeff Garzik [this message]
2004-02-14 18:29 ` Martin Schlemmer
2004-02-14 20:32 ` Jeff Garzik
2004-02-15 8:18 ` Martin Schlemmer
2004-02-15 15:17 ` Jon Smirl
-- strict thread matches above, loose matches on Subject: below --
2004-02-15 16:07 Jon Smirl
2004-02-15 16:11 Jon Smirl
2004-08-14 11:49 Jeff Garzik
2004-09-16 7:10 Jeff Garzik
2005-01-27 23:44 Jeff Garzik
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=402D3B97.70005@pobox.com \
--to=jgarzik@pobox.com \
--cc=akpm@osdl.org \
--cc=azarah@nosferatu.za.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.