From: Hugh Dickins <hugh@veritas.com>
To: "Michael S. Tsirkin" <mst@dev.mellanox.co.il>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
len.brown@intel.com, linux-acpi@vger.kernel.org,
Ingo Molnar <mingo@elte.hu>,
mingo@redhat.com, linux-pm@linux-foundation.org
Subject: Re: 2.6.21-rc1: T60 ACPI issues
Date: Wed, 1 Aug 2007 15:24:28 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0708011516540.15447@blonde.wat.veritas.com> (raw)
In-Reply-To: <20070801135820.GA8266@mellanox.co.il>
On Wed, 1 Aug 2007, Michael S. Tsirkin wrote:
> Hi!
> ACPI appears to have been broken with 2.6.23-rc1 on my T60
> Userspace from ubuntu dapper.
(Whereas I'm using a T43p with openSUSE 10.2.)
>
> 1. During boot, I see a lot of messages like this:
> [ 41.034204] acpi LNXSYSTM:00: uevent: unsupported action-string; this will be ignored in a future kernel version
(I've not seen those.)
>
> 2. Pressing Fn/F4 does not trigger suspend to ram
> This normally triigers ACPI event which triggers suspend to RAM on Ubuntu
> (echo mem > /sys/power/state works)
I'll bet this is your CONFIG_THINKPAD_ACPI_INPUT_ENABLED=y.
I got the same, see my "THINKPAD_ACPI_INPUT_ENABLED seems regressive"
mail to Henrique and lkml an hour ago.
>
> 3. After suspend to RAM, system wakes up but laptop's screen is blank,
> switching VTs etc does not help.
> External screen wakes up OK though.
> dmesg output from boot attached.
(I've not had that.)
Hugh
next prev parent reply other threads:[~2007-08-01 14:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-01 13:58 Michael S. Tsirkin
2007-08-01 14:24 ` Hugh Dickins [this message]
2007-08-01 14:56 ` Michael S. Tsirkin
2007-08-01 15:00 ` Henrique de Moraes Holschuh
2007-08-01 15:47 ` Henrique de Moraes Holschuh
2007-08-01 15:55 ` Michael S. Tsirkin
2007-08-01 16:18 ` Henrique de Moraes Holschuh
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=Pine.LNX.4.64.0708011516540.15447@blonde.wat.veritas.com \
--to=hugh@veritas.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@linux-foundation.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=mst@dev.mellanox.co.il \
/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
all inboxes | Powered by JetHome®