All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Andrew Paprocki <andrew@ishiboo.com>
Cc: Jeff Garzik <jeff@garzik.org>,
	linux-ide@vger.kernel.org,
	Bruce Allen <ballen@gravity.phys.uwm.edu>
Subject: Re: [PATCH #upstream 2/2] libata: track SLEEP state and issue SRST to wake it up
Date: Sat, 13 Oct 2007 22:55:36 +0900	[thread overview]
Message-ID: <4710CE58.9060903@gmail.com> (raw)
In-Reply-To: <76366b180710122157s506fd467m10181ceca7badf6f@mail.gmail.com>

Andrew Paprocki wrote:
> Tejun,
> 
> I'm able to break my system using this patch. I had a hunch this might
> be possible.. :) In short, if you issue a sleep command while the
> drive is already sleeping, it puts libata into an infinite loop
> resetting the port. I've illustrated the working test and the evil
> hunch below. The sleep command itself will need a short-circuit out of
> this logic in order to prevent this loop.

Heh... I guess you're much better a software engineer than I am.  Thanks
for finding it out.  It was stupid of me.  :-)

> Also, in the working case below the hddtemp command actually blocked
> until the drive was spun up before returning a valid temp. While
> testing, I was able to get hddtemp to trigger the drive wake-up when
> it was sleeping, but hddtemp then returned stating the drive was
> sleeping. Re-running hddtemp until the drive was fully spun up
> (another 5 seconds) kept returning that it was sleeping. I'll see if I
> can reproduce this reliably. Am I correct in assuming the process
> which triggers the wake-up should block?

Yeah, it should.  I'll test with hddtemp myself.

Jeff, please forget about this patchset.  I'll re-post updated version.

-- 
tejun

  reply	other threads:[~2007-10-13 13:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-12 11:56 [PATCH #upstream 1/2] libata: move command post processing to __ata_qc_complete() Tejun Heo
2007-10-12 11:56 ` [PATCH #upstream 2/2] libata: track SLEEP state and issue SRST to wake it up Tejun Heo
2007-10-13  4:57   ` Andrew Paprocki
2007-10-13 13:55     ` Tejun Heo [this message]
2007-10-14  1:02       ` Andrew Paprocki
2007-10-12 12:13 ` [PATCH #upstream 1/2] libata: move command post processing to __ata_qc_complete() Jeff Garzik
2007-10-13 13:09   ` Tejun Heo
2007-10-18  1:23     ` Jeff Garzik
2007-10-18  3:55       ` Bruce Allen

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=4710CE58.9060903@gmail.com \
    --to=htejun@gmail.com \
    --cc=andrew@ishiboo.com \
    --cc=ballen@gravity.phys.uwm.edu \
    --cc=jeff@garzik.org \
    --cc=linux-ide@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 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.