From: Alexey Starikovskiy <astarikovskiy@suse.de>
To: "Michael S. Tsirkin" <m.s.tsirkin@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
Len Brown <len.brown@intel.com>,
linux-acpi@vger.kernel.org
Subject: Re: new regression in 2.6.25-rc3: no keyboard/lid acpi events on thinkpad T61p
Date: Mon, 25 Feb 2008 23:50:37 +0300 [thread overview]
Message-ID: <47C32A1D.8030604@suse.de> (raw)
In-Reply-To: <8f53421d0802251239h6b872d94w677995789990e31b@mail.gmail.com>
Michael S. Tsirkin wrote:
> Did you guys stop accepting reports by mail?
> I hope not.
It is easier to track bug information in bugzilla.
If you for some reason do not wish to create a bug report,
I can do it for you. You only need to provide acpidump.
>
>> and attach acpidump?
>
> I'll see if I can get acpidump output - in which state do you want it?
> Right after boot on the broken kernel?
acpidump output does not change over time, you could get it even with some other kernel.
next prev parent reply other threads:[~2008-02-25 20:50 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-25 19:19 new regression in 2.6.25-rc3: no keyboard/lid acpi events on thinkpad T61p Michael S. Tsirkin
2008-02-25 19:19 ` Michael S. Tsirkin
2008-02-25 19:42 ` Alexey Starikovskiy
2008-02-25 20:39 ` Michael S. Tsirkin
2008-02-25 20:50 ` Alexey Starikovskiy [this message]
2008-02-25 21:01 ` Michael S. Tsirkin
2008-02-25 22:33 ` Alexey Starikovskiy
2008-02-25 23:18 ` Michael S. Tsirkin
2008-02-25 19:46 ` Andrew Morton
2008-02-25 20:39 ` Michael S. Tsirkin
2008-02-25 20:45 ` Michael S. Tsirkin
2008-02-25 20:57 ` broken suspend in .2.6.25-rc3 on T61p (was Re: new regression in 2.6.25-rc3: no keyboard/lid acpi events on thinkpad T61p) Rafael J. Wysocki
2008-02-25 21:26 ` Pavel Machek
2008-02-25 21:31 ` Michael S. Tsirkin
2008-02-25 21:50 ` Pavel Machek
2008-02-25 22:15 ` Michael S. Tsirkin
2008-02-25 22:20 ` Pavel Machek
2008-02-25 22:36 ` Michael S. Tsirkin
2008-02-25 22:39 ` Andrew Morton
2008-02-25 22:48 ` Michael S. Tsirkin
2008-02-25 22:53 ` Andrew Morton
2008-02-25 22:58 ` Michael S. Tsirkin
2008-02-25 22:58 ` Pavel Machek
[not found] ` <20080225155550.4a020dfb.akpm@linux-foundation.org>
[not found] ` <20080226000007.GB22102@atrey.karlin.mff.cuni.cz>
2008-02-26 10:11 ` Pavel Machek
2008-02-26 17:46 ` Dave Jones
2008-02-26 17:59 ` Pavel Machek
2008-02-26 18:10 ` Dave Jones
2008-02-26 18:16 ` Pavel Machek
2008-02-26 18:22 ` Dave Jones
2008-02-26 21:56 ` Pavel Machek
2008-02-26 22:23 ` Dave Jones
2008-02-26 22:31 ` Rafael J. Wysocki
2008-02-26 22:51 ` Pavel Machek
2008-02-27 13:12 ` Matthew Garrett
2008-02-27 13:23 ` Rafael J. Wysocki
2008-02-27 15:51 ` Stefan Seyfried
2008-02-27 15:55 ` Matthew Garrett
2008-02-26 18:56 ` Andrew Morton
2008-02-26 20:09 ` Len Brown
2008-02-26 23:31 ` Ray Lee
2008-02-27 0:12 ` Rafael J. Wysocki
2008-02-25 21:32 ` Jeff Garzik
2008-02-25 22:21 ` Pavel Machek
2008-02-26 8:54 ` new regression in 2.6.25-rc3: no keyboard/lid acpi events on thinkpad T61p Klaus S. Madsen
2008-02-26 21:32 ` Klaus S. Madsen
2008-02-26 21:44 ` Jiri Kosina
2008-02-27 22:13 ` Klaus S. Madsen
2008-02-27 23:20 ` Jiri Kosina
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=47C32A1D.8030604@suse.de \
--to=astarikovskiy@suse.de \
--cc=akpm@linux-foundation.org \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.s.tsirkin@gmail.com \
--cc=rjw@sisk.pl \
/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.