From: Federico Gamio <federico@gamio.net>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: fedora-ppc@lists.infradead.org, gentoo-ppc-user@gentoo.org,
linuxppc-dev list <linuxppc-dev@ozlabs.org>,
Debian PowerPC <debian-powerpc@lists.debian.org>
Subject: Re: TEST: Sleep patch #6
Date: Fri, 03 Dec 2004 15:06:05 -0200 [thread overview]
Message-ID: <1102093565.4272.6.camel@eva> (raw)
In-Reply-To: <1101877409.5672.2.camel@gaston>
[-- Attachment #1: Type: text/plain, Size: 2042 bytes --]
With patch #6 in some random situations, my PowerBook G4 (ATI 9600)
doesn't goes to sleep.
One situation is:
- Turn PB
- Work
- Sleep
- 14 hours of sleep
- Turn back from sleep (perfect, no problem at all)
- Work for 4 hours (mails, www, no USB, Bluetooth, etc)
- Try to sleep and problem...
When I try to make sleep my PB, nothing happens (in X), and I can't
switch from X to console.
Sorry, I can't help you more with this bug, I will keep trying to
establish which are the events that trigger this bug.
Federico
On Wed, 2004-12-01 at 16:03 +1100, Benjamin Herrenschmidt wrote:
> (As usual, I'm cross posting several lists, please don't reply to all of them,
> and CC me as I'm not subscribed to all of them neither)
>
> Ok, here's the 6th version of the sleep patch for ATI based albooks &
> iBook G4. Other machine users, please test too as it may cause
> regressions (or improvements) as well.
>
> This one fixes finally the cache flush problem that made cpufreq (on machines
> using the PMU for the switch) and sleep/wake unreliable occasionally (memory
> corruption would occur on some CPUs at least). It improves bits here or there
> too, and adds the sungem wake-on-lan feature.
>
> There are still pending issues, like cpufreq on some machines will
> "think" it's running at full speed on wakeup while it's in fact running
> at slow speed (thankfully not the opposite). I don't think I'll fix this one
> in 2.6.9, but rather in 2.6.10.
>
> http://gate.crashing.org/~benh/albook-ibookg4-sleep-6.diff
>
> I'll post a 2.6.10-rc2-bk* based version of the patch soon.
>
> Ben.
>
>
>
--
My software never has bugs. | ASCII Ribbon Campaign /"\
It just develops random features. | For Standards-Complaint Email \ /
Public GnuPG key available at: http://www.keyserver.net X
1024D/203E154B 2003-10-03 Federico Gamio <federico@gamio.net> / \
Key fingerprint = 0B9E 3A19 C88B EBAC 5422 C05F 76B5 B922 203E 154B
sub 2048g/32D2F465 2003-10-03
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-12-03 17:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-01 5:03 TEST: Sleep patch #6 Benjamin Herrenschmidt
2004-12-01 7:36 ` Colin Leroy
2004-12-01 9:05 ` Benjamin Herrenschmidt
2004-12-01 9:11 ` Colin Leroy
2004-12-01 9:22 ` Benjamin Herrenschmidt
2004-12-01 13:09 ` Colin Leroy
2004-12-01 17:46 ` David Woodhouse
2004-12-02 0:55 ` Timo Reimerdes
2004-12-02 11:08 ` Colin Leroy
2004-12-02 11:24 ` Benjamin Herrenschmidt
2004-12-03 16:41 ` Kjetil Ørbekk
2004-12-03 17:06 ` Federico Gamio [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-05 10:25 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=1102093565.4272.6.camel@eva \
--to=federico@gamio.net \
--cc=benh@kernel.crashing.org \
--cc=debian-powerpc@lists.debian.org \
--cc=fedora-ppc@lists.infradead.org \
--cc=gentoo-ppc-user@gentoo.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.