From: "Tim Teulings" <rael@edge.ping.de>
To: "Michal Piotrowski" <michal.k.k.piotrowski@gmail.com>,
"Rogério Brito" <rbrito@gmail.com>,
linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org,
debian-powerpc@lists.debian.org,
"Rafael J. Wysocki" <rjw@sisk.pl>,
"Linux-pm mailing list" <linux-pm@lists.linux-foundation.org>
Subject: Re: Sleep problems with kernels >= 2.6.21 on powerpc
Date: 27 Aug 2007 09:14:48 +0200 [thread overview]
Message-ID: <46D279E8.10001@edge.ping.de> (raw)
In-Reply-To: <20070827065246.GA21220@ime.usp.br>
Hallo!
I also have 800MHz iBook (2.2, 2 USB) and had the same problem with the=20
21.6.22 kernel a while ago and reverted back to 2.6.21. I'm not a kernel =
guy but I think I remember from kernel traces that it looked like (wise=20
chosen words ;-)) that the problems had something to do with=20
deactivating the firewire "subsystem".
I don't have traces at hand and due to lack of time cannot reproduce it=20
up to tomorrow. However this hint may speed up your analysis!
[rather long To-list, is everybody happy with this?]
--=20
Gru=DF...
Tim
next prev parent reply other threads:[~2007-08-27 7:21 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
2007-08-27 7:14 ` Tim Teulings [this message]
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=46D279E8.10001@edge.ping.de \
--to=rael@edge.ping.de \
--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).