All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
To: Oliver Neukum <oneukum@suse.de>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	linux-pm@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Len Brown <len.brown@intel.com>, Pavel Machek <pavel@ucw.cz>,
	Greg Kroah-Hartman <gregkh@suse.de>,
	Alan Stern <stern@rowland.harvard.edu>
Subject: Re: Suspend and resume on ASUS Laptops
Date: Thu, 01 Dec 2011 20:31:03 +0530	[thread overview]
Message-ID: <4ED796AF.60606@linux.vnet.ibm.com> (raw)
In-Reply-To: <201112011538.06912.oneukum@suse.de>

On 12/01/2011 08:08 PM, Oliver Neukum wrote:

> Am Donnerstag, 1. Dezember 2011, 15:28:54 schrieb Steven Rostedt:
>> On Thu, 2011-12-01 at 12:48 +0100, Oliver Neukum wrote:
>>
>>> What errors are seen in the kernel log?
>>
>> Without the script, I don't see any errors. Is there some debug thing
>> you want me to do? There's no error messages but the system just hangs
>> on suspend. It never makes it to the suspend state. The only way out of
>> it is to press and hold the power button for 10 seconds to force a hard
>> reboot.
> 
> I see. I thought the system just refuses to enter S3/4. That it hangs was
> new to me. Has there been a mail thread about this problem already?
> If not, what is the last thing you see if you go to S3 after you booted
> with no_console_suspend on the kernel command line?
> 


Hi Steven,
Since without the script your system refuses to suspend, you could also use the
'pm_test' framework (documented in Documentation/power/basic-pm-debugging.txt)
to find out more about the failing step when suspend is attempted without using
the script. Trying 'echo devices > /sys/power/pm_test' might be helpful in your
case.

Regards,
Srivatsa S. Bhat
IBM Linux Technology Center


  reply	other threads:[~2011-12-01 15:01 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-01  4:11 Suspend and resume on ASUS Laptops Steven Rostedt
2011-12-01  9:35 ` Rafael J. Wysocki
2011-12-01 11:48   ` Oliver Neukum
2011-12-01 14:28     ` Steven Rostedt
2011-12-01 14:38       ` Oliver Neukum
2011-12-01 15:01         ` Srivatsa S. Bhat [this message]
2011-12-01 18:16           ` Steven Rostedt
2011-12-01 18:41             ` Steven Rostedt
2011-12-02 15:43             ` Alan Stern
2011-12-02 16:09               ` Steven Rostedt
2011-12-02 16:23                 ` Alan Stern
2011-12-02 17:41                   ` Steven Rostedt
2011-12-02 21:57                     ` Alan Stern
2011-12-05 11:03                       ` Pavel Machek
2011-12-05 13:37                         ` Steven Rostedt
2011-12-03  2:43               ` Michal Jaegermann
2011-12-03 15:19                 ` Alan Stern
2011-12-03 20:23                   ` Michal Jaegermann
2011-12-04 16:54                     ` Alan Stern
2011-12-04 19:57                       ` Rafael J. Wysocki
2011-12-03 18:48                 ` Mantas M.
2011-12-01 15:20         ` Steven Rostedt
2011-12-02  4:04   ` Michal Jaegermann

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=4ED796AF.60606@linux.vnet.ibm.com \
    --to=srivatsa.bhat@linux.vnet.ibm.com \
    --cc=gregkh@suse.de \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=oneukum@suse.de \
    --cc=pavel@ucw.cz \
    --cc=rjw@sisk.pl \
    --cc=rostedt@goodmis.org \
    --cc=stern@rowland.harvard.edu \
    /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.