All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Lord <liml@rtr.ca>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Randy Dunlap <randy_d_dunlap@linux.intel.com>,
	linux-scsi@vger.kernel.org, linux-ide@vger.kernel.org,
	axboe@suse.de, hch@lst.de
Subject: Re: [PATCH/RFC] SCSI mid-layer suspend/resume
Date: Wed, 26 Oct 2005 23:35:48 -0400	[thread overview]
Message-ID: <43604B14.7080903@rtr.ca> (raw)
In-Reply-To: <435EA5AB.9010805@pobox.com>

Jeff Garzik wrote:
>
> We have emperical evidence that Jens' patch works on SATA, so see if the 
> two patches can meet in the middle somewhere?

And just to muddy the waters somewhat..

I have an extra hard drive caddy for my Dell notebook,
with a different 2.5" drive mounted in it.

When using THAT drive, my machine cannot resume successully
from suspend-to-RAM.  Hangs with the hard drive light on solid
some of the time, and not on other times.
Drove me crazy figuring this out, but I eventually tried a
different drive and it worked fine.

So.. not all drives work for me.

Now, the drive that doesn't work with suspend/resume (RAM)
happens to claim to support Advanced Power Management.
Except that "hdparm -Bxx" has zero effect on it -- cannot enable
it or modify the setting in anyway.

My other drives also have the APM feature, and have it turned *on*,
and "hdparm -Bxx" can be used to turn it on/off and modify the setting.

Very weird, possibly not related to the resume failures.  Or maybe.

Cheers

  reply	other threads:[~2005-10-27  3:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-24 23:05 [PATCH/RFC] SCSI mid-layer suspend/resume Randy Dunlap
2005-10-24 23:29 ` Jeff Garzik
2005-10-25 21:25   ` Randy Dunlap
2005-10-25 21:37     ` Jeff Garzik
2005-10-27  3:35       ` Mark Lord [this message]
2005-10-27  9:17         ` Erik Slagter
2005-10-27 12:51           ` Mark Lord
2005-10-27 12:56             ` Mark Lord
2005-10-27 15:07             ` Erik Slagter
2005-10-26  4:26     ` Stefan Richter
2005-10-25  2:55 ` Mark Lord
2005-10-25  3:08 ` Mark Lord
2005-10-25 21:22   ` Randy Dunlap

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=43604B14.7080903@rtr.ca \
    --to=liml@rtr.ca \
    --cc=axboe@suse.de \
    --cc=hch@lst.de \
    --cc=jgarzik@pobox.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=randy_d_dunlap@linux.intel.com \
    /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.