From: Martin Schlemmer <azarah@nosferatu.za.org>
To: Jeff Garzik <jgarzik@pobox.com>
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 21:28:11 +0200 [thread overview]
Message-ID: <1076700491.22542.38.camel@nosferatu.lan> (raw)
In-Reply-To: <20040213184316.GA28871@gtf.org>
[-- Attachment #1: Type: text/plain, Size: 912 bytes --]
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 ....
Thanks,
--
Martin Schlemmer
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-02-13 19:27 UTC|newest]
Thread overview: 9+ 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 [this message]
2004-02-13 21:03 ` Jeff Garzik
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
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=1076700491.22542.38.camel@nosferatu.lan \
--to=azarah@nosferatu.za.org \
--cc=akpm@osdl.org \
--cc=jgarzik@pobox.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox