linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Seth Forshee <seth.forshee@canonical.com>
Cc: Len Brown <lenb@kernel.org>,
	Azael Avalos <coproscefalo@gmail.com>,
	Thomas Renninger <trenn@suse.de>,
	platform-driver-x86@vger.kernel.org, linux-acpi@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 4/4] toshiba_acpi: Add blacklist for models with hotkey problems
Date: Thu, 5 Jan 2012 18:26:27 +0000	[thread overview]
Message-ID: <20120105182627.GE24242@srcf.ucam.org> (raw)
In-Reply-To: <1325617358-8286-5-git-send-email-seth.forshee@canonical.com>

On Tue, Jan 03, 2012 at 01:02:38PM -0600, Seth Forshee wrote:
> Several Satellite models have a buggy implementation of the INFO method
> that causes ACPI exceptions when executed:
> 
>  ACPI Error: Result stack is empty! State=ffff88012d70f800 (20110413/dswstate-98)
>  ACPI Exception: AE_AML_NO_RETURN_VALUE, Missing or null operand (20110413/dsutils-646)
>  ACPI Exception: AE_AML_NO_RETURN_VALUE, While creating Arg 0 (20110413/dsutils-763)
>  ACPI Error: Method parse/execution failed [\_SB_.VALZ.GETE] (Node ffff880131175eb0), AE_AML_NO_RETURN_VALUE (20110413/psparse-536)
>  ACPI Error: Method parse/execution failed [\_SB_.VALZ.INFO] (Node ffff880131175ed8), AE_AML_NO_RETURN_VALUE (20110413/psparse-536)
>  toshiba_acpi: ACPI INFO method execution failed
>  toshiba_acpi: Failed to query hotkey event

Ugh, in several ways. The hotkeys on these machines are presumably 
supposed to work - do we have any idea what we should be doing?

-- 
Matthew Garrett | mjg59@srcf.ucam.org

  reply	other threads:[~2012-01-05 18:26 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-03 19:02 [PATCH v2 0/4] toshiba_acpi: Expanded hotkey support Seth Forshee
2012-01-03 19:02 ` [PATCH v2 1/4] ACPI: EC: Add ec_get_handle() Seth Forshee
2012-01-05 18:22   ` Matthew Garrett
     [not found]   ` <CAPbh3ruqMQ8UFSehm7vX5i8YWzRFwF5=TX_f4n4dVkvmQa9Njw@mail.gmail.com>
2012-01-05 19:34     ` Seth Forshee
2012-01-07 20:55       ` Konrad Rzeszutek Wilk
2012-01-07 21:26         ` Matthew Garrett
2012-01-03 19:02 ` [PATCH v2 2/4] toshiba_acpi: Support alternate hotkey interfaces Seth Forshee
2012-01-05 18:25   ` Matthew Garrett
2012-01-05 19:43     ` Seth Forshee
2012-01-05 19:47       ` Matthew Garrett
2012-01-03 19:02 ` [PATCH v2 3/4] toshiba_acpi: Support additional hotkey scancodes Seth Forshee
2012-01-03 19:02 ` [PATCH v2 4/4] toshiba_acpi: Add blacklist for models with hotkey problems Seth Forshee
2012-01-05 18:26   ` Matthew Garrett [this message]
2012-01-05 19:32     ` Seth Forshee
2012-01-05 19:34       ` Matthew Garrett
2012-01-05 20:04         ` Seth Forshee
2012-01-05 20:09           ` Matthew Garrett
2012-01-05 20:24             ` Seth Forshee
2012-01-05 20:46       ` Moore, Robert
2012-01-05 20:58         ` Seth Forshee

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=20120105182627.GE24242@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --cc=coproscefalo@gmail.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=seth.forshee@canonical.com \
    --cc=trenn@suse.de \
    /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;
as well as URLs for NNTP newsgroup(s).