From: "Rogério Brito" <rbrito@ime.usp.br>
To: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
Cc: "Rogério Brito" <rbrito@gmail.com>,
linux-kernel@vger.kernel.org, "Rafael J. Wysocki" <rjw@sisk.pl>,
linuxppc-dev@ozlabs.org, debian-powerpc@lists.debian.org,
"Linux-pm mailing list" <linux-pm@lists.linux-foundation.org>
Subject: Re: Sleep problems with kernels >= 2.6.21 on powerpc
Date: Mon, 27 Aug 2007 03:52:46 -0300 [thread overview]
Message-ID: <20070827065246.GA21220@ime.usp.br> (raw)
In-Reply-To: <6bffcb0e0708261621q25316becqce7b3ae2176f45a8@mail.gmail.com>
Hi, Thanks, Michal.
I didn't know who to include as the wizards of the matter.
On Aug 27 2007, Michal Piotrowski wrote:
> [Adding STR wizards to CC]
>
> On 26/08/07, Rogério Brito <rbrito@gmail.com> wrote:
> > If I, on the other hand, use Debian's kernel 2.6.22 or compile my own
> > kernel with just the necessary parts for my work (version 2.6.23-rc3
> > taken from kernel.org), then I can't make the machine sleep: when I
> > press the button, it acts like if I had, in sequence, pressed anything
> > to wake it up (say, like pressing shift).
Things are getting now a little bit fishy.
Before, I was using gnome and all the little daemons that come with it
(even though I just prefer a plain window manager), but, as I mentioned
before, it didn't matter if I pressed the power button on X or on a
console.
I had the gnomee power-thingy sounding like an alarm (an ambulance!) on me
when I pressed the power button with Debian kernels 2.6.22, for instance. I
compiled my own (this time, from kernel.org) 2.6.23-rc3, with many modules
and subsystems removed (e.g., bluetooth, as this laptop doesn't have it)
and I got the exact same behavior.
If I booted, OTOH, with Debian's kernel 2.6.18, things were fine and the
machine would go to sleep without any problems.
I am now suspecting of some module that prevented the machine from going to
sleep and I now using just a fluxbox as my window manager. This time, even
with a 2.6.23-rc3 kernel (again, from kernel.org) the machine went to sleep
normally.
I did 13 compiles with git bisect and some of them were unsucessfuly
compiled, which I am afraid that may miss the real cause if I tag them as
being "bad" (which I did). (This was with just a bare minimum installation
of Debian).
The course of action that I am taking right now is to pull GNOME and see if
my current 23-rc3 kernel has any problems and see which modules are loaded.
If things progress well, I will incrementally include features on the
kernel that I need (I left out, for instance, the Firewire subsystem, so
that compilation wouldn't take more than an hour here, despite the fact
that I do need Firewire support on the kernel) and see the point where
things are not normal.
Again, I am willing to test anything that is useful to getting PowerPC
working as well as it should with the final 2.6.23 release.
Please, don't hesitate to ask for any further information.
Regards, Rogério Brito.
--
Rogério Brito : rbrito@{mackenzie,ime.usp}.br : GPG key 1024D/7C2CAEB8
http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito
Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.org
next prev parent reply other threads:[~2007-08-27 6:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-26 2:37 Sleep problems with kernels >= 2.6.21 on powerpc Rogério Brito
2007-08-26 23:21 ` Michal Piotrowski
2007-08-27 6:52 ` Rogério Brito [this message]
2007-08-27 7:14 ` Tim Teulings
2007-08-30 20:42 ` Tim Teulings
2007-09-05 17:07 ` Andrew Morton
2007-09-05 17:28 ` Randy Dunlap
2007-09-05 17:43 ` Stefan Richter
2007-09-05 17:58 ` Randy Dunlap
2007-09-05 17:47 ` Stefan Richter
2007-09-05 18:06 ` [PATCH] " Stefan Richter
2007-09-05 18:24 ` Stefan Richter
2007-09-05 19:01 ` firewire in prebuilt kernel packages (was Re: Sleep problems with kernels >= 2.6.21 on powerpc) Stefan Richter
2007-09-05 19:44 ` Sleep problems with kernels >= 2.6.21 on powerpc Andrew Morton
2007-09-05 20:12 ` Stefan Richter
2007-09-06 7:50 ` [PATCH update] " Stefan Richter
2007-08-27 8:37 ` Michel Dänzer
2007-08-27 9:55 ` Pavel Machek
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=20070827065246.GA21220@ime.usp.br \
--to=rbrito@ime.usp.br \
--cc=debian-powerpc@lists.debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=michal.k.k.piotrowski@gmail.com \
--cc=rbrito@gmail.com \
--cc=rjw@sisk.pl \
/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;
as well as URLs for NNTP newsgroup(s).