public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Maciej Rutecki <maciej.rutecki@gmail.com>
To: Natanji <natanji@gmail.com>,
	linux-acpi@vger.kernel.org, lenb@kernel.org, ibm-acpi@hmh.eng.br,
	ibm-acpi-devel@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: Regression in thinkpad-acpi events
Date: Mon, 14 Nov 2011 21:18:46 +0100	[thread overview]
Message-ID: <201111142118.47256.maciej.rutecki@gmail.com> (raw)
In-Reply-To: <4EC16F8E.7060601@gmail.com>

(add more CCs)

On poniedziałek, 14 listopada 2011 o 20:44:14 Natanji wrote:
> With 3.0 it was still fine, that much is for sure. The problem came
> with the upgrade to 3.1. I've never even compiled my own kernel so I
> cannot bisect. Sorry...
> 
> Regards,
> Natanji
> 
> On Mon 14 Nov 2011 08:31:06 PM CET, Maciej Rutecki wrote:
> > On środa, 9 listopada 2011 o 19:17:25 Natanji wrote:
> >> Hello everyone,
> >> first time posting on this last, and I'm not subscribed, so please CC
> >> any replies to me. ;)
> >> 
> >> I'm running Kernel version 3.1-4 using Arch Linux (32 Bit) on a Thinkpad
> >> X60 Tablet. Since upgrading from a pre-3.1 kernel to a post-3.1 kernel,
> >> the Thinkpad-specific ACPI events (from thinkpad-acpi) are completely
> >> gone.
> >> 
> >> This can be observed by using the acpi_listen command. For instance, no
> >> ACPI events happen when swiveling the display, and the sleep button
> >> returns
> >> 
> >> 	button/sleep SBTN 00000080 00000000
> >> 
> >> instead of the previous
> >> 
> >> 	ibm/hotkey HKEY 00000080 00001004
> >> 
> >> The bug was reported in the Arch Linux bugtracker [1] and it was
> >> suggested to report this upstream, so this is what I did now. Sadly I
> >> have no idea how I could find out if this is indeed a kernel bug or not;
> >> I have never compiled my own kernel so what I can give you is probably
> >> limited. But I suppose quite a few members of this list use a Thinkpad.
> >> If there is anything else I can help out with, just tell me.
> >> 
> >> [1] https://bugs.archlinux.org/index.php?do=details&task_id=26658
> > 
> > Can you check that 3.1 works or not? Or try bisection that it is
> > regression after 3.0 or 3.1 kernel.
> > 
> > Regards

-- 
Maciej Rutecki
http://www.mrutecki.pl

  reply	other threads:[~2011-11-14 20:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-09 18:17 Regression in thinkpad-acpi events Natanji
2011-11-14 19:31 ` Maciej Rutecki
2011-11-14 19:44   ` Natanji
2011-11-14 20:18     ` Maciej Rutecki [this message]
2011-11-15  7:09       ` Tom Gundersen
2011-11-15 23:03         ` Henrique de Moraes Holschuh
2011-11-24  9:25           ` Tom Gundersen
2011-11-25  0:25             ` Henrique de Moraes Holschuh
2011-11-27  1:23           ` [ibm-acpi-devel] " Henning Schild
2011-11-30  9:22             ` Natanji
2011-11-30 11:15               ` Henrique de Moraes Holschuh
2011-11-30 13:34                 ` Natanji
2011-11-14 20:30     ` Henrique de Moraes Holschuh
2011-11-14 21:52       ` Natanji
2011-11-15  2:39         ` 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=201111142118.47256.maciej.rutecki@gmail.com \
    --to=maciej.rutecki@gmail.com \
    --cc=ibm-acpi-devel@lists.sourceforge.net \
    --cc=ibm-acpi@hmh.eng.br \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=natanji@gmail.com \
    /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