From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Pavel Machek <pavel@suse.cz>
Cc: Adrian Bunk <bunk@stusta.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
len.brown@intel.com, linux-acpi@vger.kernel.org,
linux-pm@osdl.org
Subject: Re: x60 backlight Re: [discuss] 2.6.19-rc1: known regressions (v2)
Date: Sun, 08 Oct 2006 16:44:37 -0700 [thread overview]
Message-ID: <45298D65.8090503@goop.org> (raw)
In-Reply-To: <20061008071254.GA5672@ucw.cz>
Pavel Machek wrote:
> Strange, problem went away after reboot. I guess I'll write it off as
> an acpi glitch... there's definitely something strange going on with
> backlight around s2ram: during normal operation, backlight changes are
> fast. After s2ram, backlight change from keyboard takes 300msec or so.
>
Yes, I'm seeing that too. It's not just keyboard brightness changes;
gnome does some fadeup effect, which takes ~300ms/step as well.
J
next prev parent reply other threads:[~2006-10-08 23:44 UTC|newest]
Thread overview: 87+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-05 3:29 Merge window closed: v2.6.19-rc1 Linus Torvalds
2006-10-05 4:28 ` 2.6.19-rc1: known regressions Adrian Bunk
2006-10-05 4:45 ` Benjamin Herrenschmidt
2006-10-05 6:37 ` Jens Axboe
2006-10-05 6:52 ` Benjamin Herrenschmidt
2006-10-05 11:01 ` Gene Heskett
2006-10-05 14:04 ` Adrian Bunk
2006-10-05 20:27 ` Andreas Schwab
2006-10-05 21:15 ` Mel Gorman
2006-10-06 0:24 ` Andreas Schwab
2006-10-06 9:51 ` [PATCH] Use symbolic names instead of indices for zone initialisation Mel Gorman
2006-10-05 7:16 ` 2.6.19-rc1: known regressions Nigel Cunningham
2006-10-05 8:27 ` [patch] x86, fix rwsem build bug on CONFIG_M386=y Ingo Molnar
2006-10-05 9:41 ` [discuss] " Andi Kleen
2006-10-10 12:18 ` cpufreq not working on AMD K8 (was Re: 2.6.19-rc1: known regressions) Christian
2006-10-10 14:59 ` Langsdorf, Mark
2006-10-10 16:37 ` Christian
2006-10-10 16:43 ` Langsdorf, Mark
2006-10-11 14:06 ` Christian
2006-10-11 17:33 ` Langsdorf, Mark
2006-10-11 18:16 ` Christian
2006-10-11 18:38 ` Tomasz Torcz
2006-10-11 4:23 ` Adrian Bunk
2006-10-11 9:30 ` Christian
2006-10-11 14:57 ` Adrian Bunk
2006-10-05 15:09 ` Merge window closed: v2.6.19-rc1 Alistair John Strachan
2006-10-05 18:56 ` ohci1394 regression in 2.6.19-rc1 (was Re: Merge window closed: v2.6.19-rc1) Stefan Richter
2006-10-05 20:30 ` Alistair John Strachan
2006-10-05 20:32 ` Alistair John Strachan
2006-10-05 22:16 ` Stefan Richter
2006-10-05 22:37 ` Alistair John Strachan
2006-10-05 23:22 ` ohci1394 regression in 2.6.19-rc1 Stefan Richter
2006-10-06 13:55 ` Stefan Richter
2006-10-06 17:17 ` Stefan Richter
2006-10-06 18:33 ` Stefan Richter
2006-10-06 22:52 ` Alistair John Strachan
2006-10-05 15:41 ` Merge window closed: v2.6.19-rc1 Gene Heskett
2006-10-06 8:36 ` usb resets [Was Re: Merge window closed: v2.6.19-rc1] Uwe Zeisberger
2006-10-06 12:18 ` Gene Heskett
2006-10-05 19:17 ` Merge window closed: v2.6.19-rc1 Peter Osterlund
2006-10-05 19:21 ` Eric Sandeen
2006-10-05 20:49 ` [patch] fix qla{2,4} build error Frederik Deweerdt
2006-10-05 22:01 ` Andrew Vasquez
2006-10-06 16:54 ` [PATCH] Maintain module-parameter name consistency with qla2xxx/qla4xxx Andrew Vasquez
2006-10-05 21:09 ` monitor not active after boot (was Re: Merge window closed: v2.6.19-rc1) Olaf Hering
2006-10-08 10:12 ` Olaf Hering
2006-10-06 4:31 ` Merge window closed: v2.6.19-rc1 Alex Romosan
2006-10-06 18:47 ` 2.6.19-rc1 regression: airo suspend fails Adrian Bunk
2006-10-07 3:54 ` Alex Romosan
2006-10-07 19:52 ` Dave Kleikamp
2006-10-07 20:17 ` Alex Romosan
2006-10-08 6:43 ` Pavel Machek
2006-10-06 17:49 ` Merge window closed: v2.6.19-rc1 caszonyi
2006-10-06 18:12 ` Linus Torvalds
2006-10-06 19:05 ` Eric W. Biederman
2006-10-07 18:23 ` Gabor Gombas
2006-10-07 20:29 ` Eric W. Biederman
2006-10-06 22:43 ` Grant Coady
2006-10-06 22:47 ` Jesper Juhl
2006-10-07 2:33 ` Linus Torvalds
2006-10-07 13:16 ` James Bottomley
2006-10-08 11:47 ` BUG when doing parallel NFS mounts (WAS: Re: Merge window closed: v2.6.19-rc1) Peter Osterlund
2006-10-08 15:19 ` Peter Osterlund
2006-10-08 18:35 ` Trond Myklebust
2006-10-08 18:54 ` Peter Osterlund
2006-10-08 19:21 ` Trond Myklebust
2006-10-09 0:31 ` 2.6.19-rc1: DVB frontend selection causes compile errors Adrian Bunk
2006-10-09 7:53 ` [v4l-dvb-maintainer] " Michael Krufky
2006-10-09 8:05 ` Adrian Bunk
2006-10-09 8:27 ` Michael Krufky
2006-10-14 5:23 ` Randy Dunlap
2006-10-14 13:32 ` Trent Piepho
[not found] ` <20061007214620.GB8810@stusta.de>
2006-10-07 23:02 ` 2.6.19-rc1: known regressions (v2) Prakash Punnoor
2006-10-08 7:12 ` x60 backlight Re: [discuss] " Pavel Machek
2006-10-08 17:38 ` Adrian Bunk
2006-10-08 17:59 ` Michael S. Tsirkin
2006-10-08 19:30 ` Adrian Bunk
2006-10-16 19:39 ` Michael S. Tsirkin
2006-10-08 18:36 ` Pavel Machek
2006-10-08 19:29 ` Adrian Bunk
2006-10-08 23:44 ` Jeremy Fitzhardinge [this message]
2006-10-08 11:10 ` [GIT PULL] ieee1394 update (was 2.6.19-rc1: known regressions (v2)) Stefan Richter
2006-10-09 15:32 ` 2.6.19-rc1: known regressions (v2) - xfrm_register_mode Steve Fox
2006-10-09 15:51 ` Mel Gorman
[not found] ` <20061010051019.GB3650@stusta.de>
2006-10-10 5:16 ` 2.6.19-rc1: known regressions (v3) Benjamin Herrenschmidt
2006-10-10 8:41 ` Mel Gorman
[not found] ` <17708.9637.569670.824121@cargo.ozlabs.ibm.com>
2006-10-11 3:08 ` Adrian Bunk
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=45298D65.8090503@goop.org \
--to=jeremy@goop.org \
--cc=bunk@stusta.de \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@osdl.org \
--cc=pavel@suse.cz \
/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