From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: C S Rosenmund <gnuman@comcast.net>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.0-test8 backlight and sound problems (PMU) on PPC
Date: Sun, 26 Oct 2003 18:35:26 +0100 [thread overview]
Message-ID: <1067189725.4055.17.camel@gaston> (raw)
In-Reply-To: <3F970199.2050404@comcast.net>
On Thu, 2003-10-23 at 00:15, C S Rosenmund wrote:
> Hardware is an early iBook (first gen - Clamshell)
First, please CC me or linuxppc-dev at least on PowerMac related
reports.
> with 2.6.0-test8, sound does not recover from sleep when an application
> is using it when the notebook is slept (can be reproduced: using pysol,
> with sound enabled, close the lid to sleep the laptop, then anytime
> after the sound stops (indicating that the laptop is sleeping) open the
> lid. Sound does not return, and the application does not close) The
> symptoms (indicated above) seem to point to the sound module (also when
> compiled into the kernel) hanging up on sleep. Sound hardware is
> pmac-dmasound.
Looks like the dbdma channel is stuck. I'll investigate. (Note,
Christoph Hellwig is now maintaining this driver in 2.6, also note
that Linus tree misses some sound bits, you may want to use my
bk tree from bk://ppc.bkbits.net/linuxppc-2.5-benh for now, I hope
to have everything merged upstream by 2.6.1)
> two problems on the backlight (probably related):
> the backlight control buttons do not work (the brightness of the
> backlight does not change) and when the laptop goes to sleep, the
> backlight does not turn off (it does turn off for console blanking as in
> when the unit is left idle for some time, and the screen goes blank).
You aren't using the proper video driver it seems.
prev parent reply other threads:[~2003-10-26 17:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-22 22:15 2.6.0-test8 backlight and sound problems (PMU) on PPC C S Rosenmund
2003-10-26 17:35 ` Benjamin Herrenschmidt [this message]
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=1067189725.4055.17.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=gnuman@comcast.net \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox