linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Elias Oltmanns <oltmanns@uni-bonn.de>
To: linux-kernel@vger.kernel.org
Cc: linux-ide@vger.kernel.org, hdaps-devel@sourceforge.net
Subject: Re: Debugging strange system lockups possibly triggered by ATA commands
Date: Tue, 10 Oct 2006 20:58:30 +0200	[thread overview]
Message-ID: <87ejtgatgp.fsf@denkblock.local> (raw)
In-Reply-To: 742hc-4n3-25@gated-at.bofh.it

Hi Shem,

"Shem Multinymous" <multinymous@gmail.com> wrote:
> Hi Elias,
>
> On 10/9/06, Elias Oltmanns <oltmanns@uni-bonn.de> wrote:
>
>> A slightly stripped version of the patch is available too, which has
>> been verified to trigger the described problem in exactly the same way
>> as the original but lacks the IDLE IMMEDIATE feature (leaving the
>> STANDBY IMMEDIATE option only) in order to make it (hopefully) more
>> readable and easier to understand.
>
> What happens if you strip away *all* the head parking code, leaving
> only the queue freeze code? Conversely, what happens if you issue the
> head park command but don't freeze the queue?

In all setups the loop
# while true; do hdparm -q -y /dev/hda; hdparm -q -C /dev/hda; done
didn't trigger the freeze. This should be very close to the effect of
the patch with all queue freezing stuff removed.

Regarding your question, it seems rather difficult to test the right
thing. Just issuing the commands and leaving the queue alone is easy
to implement and I couldn't reproduce the problem running such a
kernel. Testing the queue handling stuff without actually issuing any
commands seems rather difficult to me as its the callback mechanism
used to freeze the queue after command completion which I'd really
like to test. If I don't issue any command, I don't know how to test
whether the callback procedure and all the rest works as expected.

Regards,

Elias

       reply	other threads:[~2006-10-10 18:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <741Eo-2m9-5@gated-at.bofh.it>
     [not found] ` <742hc-4n3-25@gated-at.bofh.it>
2006-10-10 18:58   ` Elias Oltmanns [this message]
2006-10-11 13:19     ` Debugging strange system lockups possibly triggered by ATA commands Shem Multinymous
2006-10-10 18:58 ` Elias Oltmanns
2006-10-09 11:32 Elias Oltmanns
     [not found] ` <877iz9ohbe.fsf-tKmc6CDQn9GVtrcxygCVqg@public.gmane.org>
2006-10-09 12:12   ` Shem Multinymous

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=87ejtgatgp.fsf@denkblock.local \
    --to=oltmanns@uni-bonn.de \
    --cc=hdaps-devel@sourceforge.net \
    --cc=linux-ide@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).