From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751516Ab1JJC3L (ORCPT ); Sun, 9 Oct 2011 22:29:11 -0400 Received: from e7.ny.us.ibm.com ([32.97.182.137]:35469 "EHLO e7.ny.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750854Ab1JJC3K (ORCPT ); Sun, 9 Oct 2011 22:29:10 -0400 Message-ID: <4E925873.2020501@linux.vnet.ibm.com> Date: Sun, 09 Oct 2011 22:29:07 -0400 From: Stefan Berger User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.18) Gecko/20110621 Fedora/3.1.11-1.fc14 Lightning/1.0b3pre Thunderbird/3.1.11 MIME-Version: 1.0 To: =?UTF-8?B?QXJrYWRpdXN6IE1pxZtraWV3aWN6?= CC: linux-kernel@vger.kernel.org, tpmdd-devel@lists.sourceforge.net, Debora Velarde , Rajiv Andrade , Marcel Selhorst Subject: Re: [tpmdd-devel] Linux 3.1-rc9 References: <201110092251.15618.a.miskiewicz@gmail.com> In-Reply-To: <201110092251.15618.a.miskiewicz@gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 10/09/2011 04:51 PM, Arkadiusz Miśkiewicz wrote: > On Wednesday 05 of October 2011, Linus Torvalds wrote: >> Another week, another -rc. > suspend to ram regression is annoying (still visible on rc9; > https://lkml.org/lkml/2011/9/24/76) but unfortunately maintainers are silent. > I tried -rc9 on my Lenovo W500 with that same TPM. I cannot reproduce the 'scheduling while atomic' problem you had reported earlier. I also could suspend / resume fine as long as I did the following: - suspended with the tpm_tis driver as module in the kernel - once a suspend was done without the tpm_tis driver the subsequent suspends were all done without the tpm_tis driver Once I had done a suspend/resume with the tpm_tis driver *not* in the kernel and then again a suspend with the tpm_tis driver in the kernel, it did not resume anymore. I believe previously (previous version of kernel and/or Fedora) it refused to even suspend. The reason why this doesn't work properly is that the driver has to send a command to the TPM upon suspend and the BIOS then sends the corresponding wakeup command. Did you maybe previously suspend/resume without a tpm_tis driver and then try to suspend with it ? Also, my Lenovo W500 shows particularly odd behavior when I switch from Windows to Linux. The first suspend with a Linux booted after Windows (with or without tpm_tis driver) does *not* resume (reboot required). A subsequently rebooted Linux makes the suspend/resume work fine. Stefan