From: Jeff Garzik <jgarzik@pobox.com>
To: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Cc: Jens Axboe <axboe@suse.de>,
Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.4-rc-bk3: hdparm -X locks up IDE
Date: Thu, 11 Mar 2004 12:59:47 -0500 [thread overview]
Message-ID: <4050A913.50809@pobox.com> (raw)
In-Reply-To: <200403111607.39235.bzolnier@elka.pw.edu.pl>
Bartlomiej Zolnierkiewicz wrote:
> On Thursday 11 of March 2004 15:48, Jens Axboe wrote:
>
>>On Thu, Mar 11 2004, Bartlomiej Zolnierkiewicz wrote:
>>
>>>On Thursday 11 of March 2004 15:14, Denis Vlasenko wrote:
>>>
>>>>I discovered that hdparm -X <mode> /dev/hda can lock up IDE
>>>>interface if there is some activity.
>>>
>>>Known bug and is on TODO but fixing it ain't easy.
>>>Thanks for a report anyway.
>>
>>Wouldn't it be possible to do the stuff that needs serializing from the
>>end_request() part and get automatic synchronization with normal
>>requests?
>
>
> That's the way to do it (REQ_SPECIAL) but unfortunately on some chipsets
> we need to synchronize both channels (whereas we don't need to serialize
> normal operations).
blk_stop_queue() on all queues attached to the hardware?
You need to synchronize anyway for the rare hardware that reports itself
as "simplex" -- one DMA engine for both channels.
Jeff
next prev parent reply other threads:[~2004-03-11 18:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-11 14:14 2.6.4-rc-bk3: hdparm -X locks up IDE Denis Vlasenko
2004-03-11 14:52 ` Bartlomiej Zolnierkiewicz
2004-03-11 14:48 ` Jens Axboe
2004-03-11 15:07 ` Bartlomiej Zolnierkiewicz
2004-03-11 15:02 ` Jens Axboe
2004-03-11 17:59 ` Jeff Garzik [this message]
2004-03-12 0:21 ` [PATCH] hdparm_X.patch (was: Re: 2.6.4-rc-bk3: hdparm -X locks up IDE) Denis Vlasenko
2004-03-12 1:02 ` Bartlomiej Zolnierkiewicz
2004-03-12 7:24 ` Denis Vlasenko
2004-03-12 9:39 ` Denis Vlasenko
2004-03-12 14:34 ` Bartlomiej Zolnierkiewicz
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=4050A913.50809@pobox.com \
--to=jgarzik@pobox.com \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
/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