public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rogerio Theodoro de Brito <rbrito@ime.usp.br>
To: "Rogério Brito" <rbrito@ime.usp.br>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Arjan van de Ven <arjan@linux.intel.com>,
	linux-kernel@vger.kernel.org, yakui.zhao@intel.com,
	bugme-daemon@bugzilla.kernel.org, rbrito@ime.usp.br
Subject: Re: [Bugme-new] [Bug 11717] New: Pressing suspend button suspends, but does not wakes up
Date: Fri, 07 Nov 2008 06:00:55 -0200	[thread overview]
Message-ID: <1226044855.4913f5b7f2f45@webmail.ime.usp.br> (raw)
In-Reply-To: <20081107014535.GA19201@ime.usp.br>

Hi.

Some more information that may prove to be useful.

Quoting Rogério Brito <rbrito@ime.usp.br>:
> If any further information is needed, please let me know.

I just discovered that the "suspend button" is overloaded: it is actually 
a poweroff button, which would explain the behaviour when the kernel is in 
suspend to RAM.

(This notebook doesn't have a suspend hehaviour when closing the lid, as 
far as I could observe right now).

I just reinstalled Windows Vista (from the rescue DVD) and it suspends and 
resumes fine. I don't know where Windows stores its logs (sorry, I've been 
using Unix systems for more than a decade).

So, summarizing, it seems that the "suspend to RAM" button is actually a 
poweroff button, but this behaviour of powering off the machine manifests 
only when the kernel is already in a suspend to ram state. I can provide 
more information under guidance. Please, just let me know what is needed 
and I will test anything, as this notebook has not yet been used for 
production.


Thanks in advance for any help, Rogério Brito.

-- 
Rogério Brito : rbrito@ime.usp.br : http://www.ime.usp.br/~rbrito
Homepage of the algorithms package : http://algorithms.berlios.de
Homepage on freshmeat:  http://freshmeat.net/projects/algorithms/

  reply	other threads:[~2008-11-07  8:00 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-06 19:47 [Bugme-new] [Bug 11717] New: Pressing suspend button suspends, but does not wakes up Rogério Brito
2008-11-07  1:45 ` Rogério Brito
2008-11-07  8:00   ` Rogerio Theodoro de Brito [this message]
2008-11-08  7:50     ` Rogério Brito
2008-11-08  8:20       ` Justin Mattock
2008-11-09  2:45         ` Rogério Brito
2008-11-09  4:38           ` Justin P. Mattock
2008-11-10 14:06             ` Rogério Brito
2008-11-09 11:33           ` Pavel Machek
2008-11-10  5:17             ` Justin Mattock
2008-11-10  7:45               ` Pavel Machek
2008-11-10 15:00                 ` Justin Mattock
2008-11-11  9:37                   ` Rogério Brito
2009-08-20  2:54                     ` Rogério Brito
2009-08-12  4:10                 ` Rogério Brito
2009-08-12  4:31                   ` Justin P. Mattock
2008-11-10 14:15             ` Rogério Brito
2008-11-11  9:53               ` Pavel Machek
2008-11-11 15:22                 ` Justin Mattock

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=1226044855.4913f5b7f2f45@webmail.ime.usp.br \
    --to=rbrito@ime.usp.br \
    --cc=akpm@linux-foundation.org \
    --cc=arjan@linux.intel.com \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yakui.zhao@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox