public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: Jeff Chua <jeff.chua.linux@gmail.com>
Cc: Takashi Iwai <tiwai@suse.de>,
	Peter Hurley <peter@hurleysoftware.com>,
	lkml <linux-kernel@vger.kernel.org>,
	Dave Airlie <airlied@redhat.com>
Subject: Re: Lenovo X240 (haswell) suspend-to-ram hangs on 3-14.0-rc2
Date: Mon, 17 Feb 2014 14:54:32 -0500	[thread overview]
Message-ID: <20140217195432.GE16660@thunk.org> (raw)
In-Reply-To: <CAAJw_ZtK+jTOhCPZKhCu_f2nHwUahE8jcR8G4+FbocEc66Ei4g@mail.gmail.com>

On Tue, Feb 18, 2014 at 01:54:40AM +0800, Jeff Chua wrote:
> Any suggestion on how to debug this? bisect? Ted, does your T540p work
> with CONFIG_SND_HDA_INTEL=y instead of "m" ?

I can give this a try on my next kernel rebuild.

BTW, I am noticing some other suspend-to-ram wierdnesses.  In
particular, in about 1 in 10 to 1 in 20 suspend, the led lights on the
ethernet port are stuck on after the suspend, which I suspect means
we're not shutting down the peripherals all the way, and thus wasting
battery while the laptop is suspended.

Also, I am using a password to secure my HDD, and in most cases, the
HDD is left powered on so I can still access the HDD.  However, about
10% of the time, the HDD seems to get completely powered down, such
that it needs to have the password sent again to unlock the drive.
Since I am using the BIOS to send the password to the HDD, it means I
have to force a reboot in order to regain access to the drive.

So this is either a S2R bug in that we're not powering down the HDD
sufficiently to maximize power savings most of the time, or that we
need to be able to reauthenticate the HDD to unlock it after a
suspend/resume cycle --- something which it sounds like Linux doesn't
support all that well.  (I only recently started using HDD/SSD
passwords because I now have devices with FDE, and I've been trying to
secure my computing environment as much as possible.)

       	  	    		   	- Ted

  reply	other threads:[~2014-02-17 19:54 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-13 13:02 Lenovo X240 (haswell) suspend-to-ram hangs on 3-14.0-rc2 Jeff Chua
2014-02-13 17:14 ` Peter Hurley
2014-02-13 17:28   ` Takashi Iwai
2014-02-13 21:21     ` Theodore Ts'o
2014-02-14 13:46     ` Jeff Chua
2014-02-14 13:57       ` Takashi Iwai
2014-02-14 14:00         ` Peter Hurley
2014-02-14 19:01         ` Jeff Chua
2014-02-14 19:10           ` Steven Noonan
2014-02-14 20:07           ` Takashi Iwai
2014-02-17 17:54             ` Jeff Chua
2014-02-17 19:54               ` Theodore Ts'o [this message]
2014-02-18 19:06                 ` Theodore Ts'o
2014-02-18 20:28                   ` Takashi Iwai
2014-02-18 21:32                     ` Theodore Ts'o
2014-02-19  2:01                       ` Jeff Chua
2014-02-27 12:01                         ` Takashi Iwai

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=20140217195432.GE16660@thunk.org \
    --to=tytso@mit.edu \
    --cc=airlied@redhat.com \
    --cc=jeff.chua.linux@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter@hurleysoftware.com \
    --cc=tiwai@suse.de \
    /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