From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: "Michael S. Tsirkin" <mst@dev.mellanox.co.il>
Cc: Hugh Dickins <hugh@veritas.com>,
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,
ibm-acpi-devel@lists.sourceforge.net
Subject: Re: 2.6.21-rc1: T60 ACPI issues
Date: Wed, 1 Aug 2007 12:47:49 -0300 [thread overview]
Message-ID: <20070801154749.GK23111@khazad-dum.debian.net> (raw)
In-Reply-To: <20070801145607.GB8480@mellanox.co.il>
(CC changed from Borislav to ibm-acpi-devel).
On Wed, 01 Aug 2007, Michael S. Tsirkin wrote:
> > > 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.)
>
> Bingo.
> sudo rmmod thinkpad_acpi cures both 2 and 3.
> Thanks for pointing this out.
I can see how it would help with (2), as that prompty tells the firmware to
issue its default ACPI events for Fn+F4 upon removal. But I have *NO* idea
what thinkpad_acpi might be doing that is causing issues with the wake up
after a resume.
Please open a bug in bugzilla.kernel.org about it, and attach the full debug
output of a suspend+resume cycle with and without thinkpad-acpi loaded.
Also, please try the same with thinkpad-acpi loaded, but
CONFIG_THINKPAD_ACPI_INPUT_ENABLED set to N. If the problem goes away,
please retest, but set hotkey_enable to 1 and do an "cat
/sys/bus/platform/devices/thinkpad_acpi/hotkey_recommended_mask >
/sys/bus/platform/devices/thinkpad_acpi/hotkey_mask" before the sleep.
You will probably need to enable a bunch of debug options in ACPI and
thinkpad-acpi to get good enough logs. It is probably worth posting the
acpid logs too: the real difference might be there.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
next prev parent reply other threads:[~2007-08-01 15:48 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
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 [this message]
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=20070801154749.GK23111@khazad-dum.debian.net \
--to=hmh@hmh.eng.br \
--cc=hugh@veritas.com \
--cc=ibm-acpi-devel@lists.sourceforge.net \
--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®