From: David Woodhouse <dwmw2@infradead.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.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: Sat, 09 Apr 2005 17:36:34 +0100 [thread overview]
Message-ID: <1113064594.4636.28.camel@localhost.localdomain> (raw)
In-Reply-To: <1112594783.26086.22.camel@gaston>
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?
I'll rebuild the Fedora kernel without any of the patches to eliminate
the possibility that it's caused by some other change.
--
dwmw2
next prev parent reply other threads:[~2005-04-09 16:37 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 [this message]
2005-04-09 23:37 ` Benjamin Herrenschmidt
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=1113064594.4636.28.camel@localhost.localdomain \
--to=dwmw2@infradead.org \
--cc=benh@kernel.crashing.org \
--cc=debian-powerpc@lists.debian.org \
--cc=fedora-ppc@lists.infradead.org \
--cc=linuxppc-dev@ozlabs.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.