From: Benjamin Herrenschmidt <benh@kernel•crashing.org>
To: David Woodhouse <dwmw2@infradead•org>
Cc: fedora-ppc@lists•infradead.org,
linuxppc-dev list <linuxppc-dev@ozlabs•org>,
"debian-powerpc@lists•debian.org"
<debian-powerpc@lists•debian.org>
Subject: Re: iBook G3 owners
Date: Sun, 10 Apr 2005 09:37:10 +1000 [thread overview]
Message-ID: <1113089830.9518.444.camel@gaston> (raw)
In-Reply-To: <1113064594.4636.28.camel@localhost.localdomain>
On Sat, 2005-04-09 at 17:36 +0100, David Woodhouse wrote:
> On Mon, 2005-04-04 at 16:06 +1000, Benjamin Herrenschmidt wrote:
> > There have been various reports of issues with sleep among others on
> > iBook G3 equiped with the 750FX processor. Also, the cpufreq code on
> > these so far didn't change the CPU voltage, which limited the actual
> > power saving at low frequency.
>
> Sleep hasn't worked properly on my PowerBook G4 since I applied your
> first pair of patches. The current behaviour seems to be that short
> periods of sleep appear to work OK, but a fairly random death happens
> after a longer sleep. Last time it was ohci_hcd complaining of an
> uninitialised spinlock.
>
> I'm half inclined to suspect RAM isn't being refreshed properly -- but
> most of the kernel text still seems to be there and it manages to oops
> and panic OK, so perhaps it's just that the dcache isn't correctly
> disabled, or isn't correctly flushed when we enable it again?
That kind of sleep is usually related to cache flush issues ... the
setup of RAM auto refresh isn't under kernel code control, it's entirely
done by the chipset when entering sleep state.
What is strange however is that none of these 2 patches have _any_
effect on your machine model. Can you confirm that's indeed the patches
you were talking about ?
ppc32-750-errata-fix.diff
ppc32-pmac-sleep-fix.diff
> I'll rebuild the Fedora kernel without any of the patches to eliminate
> the possibility that it's caused by some other change.
Make sure you have the 2 cpufreq related patches though, there are
issues with CPU voltage possibly not correct on wakeup that can cause
similar problems.
Ben.
next prev parent reply other threads:[~2005-04-09 23:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-04 6:06 iBook G3 owners Benjamin Herrenschmidt
2005-04-04 12:06 ` Benjamin Herrenschmidt
2005-04-07 22:05 ` Andreas Schwab
2005-04-07 22:38 ` Benjamin Herrenschmidt
2005-04-07 23:20 ` Andreas Schwab
2005-04-07 23:42 ` Benjamin Herrenschmidt
2005-04-09 16:36 ` David Woodhouse
2005-04-09 23:37 ` Benjamin Herrenschmidt [this message]
2005-04-09 23:48 ` David Woodhouse
2005-04-10 0:07 ` Benjamin Herrenschmidt
2005-04-10 8:28 ` David Woodhouse
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=1113089830.9518.444.camel@gaston \
--to=benh@kernel$(echo .)crashing.org \
--cc=debian-powerpc@lists$(echo .)debian.org \
--cc=dwmw2@infradead$(echo .)org \
--cc=fedora-ppc@lists$(echo .)infradead.org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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