From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Gaudenz Steinlin <gaudenz@soziologie.ch>
Cc: linux-kernel@vger.kernel.org, "Rafael J. Wysocki" <rjw@sisk.pl>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: commit "radeonfb: Fix resume from D3Cold on some platforms" breaks resume from RAM on PowerBook
Date: Fri, 06 Mar 2009 16:50:29 +1100 [thread overview]
Message-ID: <1236318629.7260.120.camel@pasglop> (raw)
In-Reply-To: <20090305125919.GA5474@soziologie.ch>
> As already said in an earlier mail, this does not make any difference. I
> now ran some more tests:
>
> -> with ppc32_defconfig: same results, resume with your commit is
> broken, I did not yet test if reverting the commit fixes resume.
> Please tell me if you are interested in this result.
> -> with a minimal config (attached): resume does not work at all with or
> without your commit. I suspect this is another bug with the same
> symptoms.
>
> If you have any ideas, I would be happy to do further tests. I could
> also send you my compiles kernel (as a Debian package or a tar file) or
> you could send me your working kernel image to see if it also works for
> me.
I think that .config fails due to the lack of CPU_FREQ support. I think
I remember that specifically this powerbook model boots at low speed and
fails to resume if not suspended at high speed. The cpufreq driver for
powermacs knows about that and ramps up the frequency before suspend.
Can you give that a try ?
In fact I verified on mine that your minimum config fails the same way
you described but it works when I re-enable cpufreq support.
We might want to do something to warn people in this situation.. maybe
the sleep code can somewhat verify that cpufreq is there.
Cheers,
Ben.
next prev parent reply other threads:[~2009-03-06 5:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-04 8:38 commit "radeonfb: Fix resume from D3Cold on some platforms" breaks resume from RAM on PowerBook Gaudenz Steinlin
2009-03-04 23:22 ` Benjamin Herrenschmidt
2009-03-05 10:25 ` Gaudenz Steinlin
2009-03-05 2:25 ` Benjamin Herrenschmidt
2009-03-05 12:59 ` Gaudenz Steinlin
2009-03-06 5:50 ` Benjamin Herrenschmidt [this message]
2009-03-06 9:09 ` Gaudenz Steinlin
2009-03-06 9:57 ` Benjamin Herrenschmidt
2009-03-06 11:41 ` Gaudenz Steinlin
2009-03-06 21:26 ` Benjamin Herrenschmidt
2009-03-09 22:37 ` Benjamin Herrenschmidt
2009-03-10 9:32 ` Rafael J. Wysocki
2009-03-10 15:01 ` Gaudenz Steinlin
2009-03-10 20:58 ` Benjamin Herrenschmidt
2009-03-10 21:27 ` Gaudenz Steinlin
2009-03-10 21:30 ` Gaudenz Steinlin
2009-03-10 22:07 ` Benjamin Herrenschmidt
2009-03-10 23:04 ` Rafael J. Wysocki
2009-03-11 0:34 ` Benjamin Herrenschmidt
2009-03-09 22:49 ` Benjamin Herrenschmidt
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=1236318629.7260.120.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=akpm@linux-foundation.org \
--cc=gaudenz@soziologie.ch \
--cc=linux-kernel@vger.kernel.org \
--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