public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexey Starikovskiy <astarikovskiy@suse.de>
To: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
Cc: Alexey Starikovskiy <aystarik@gmail.com>,
	linux acpi <linux-acpi@vger.kernel.org>,
	Matthew Wilcox <willy@linux.intel.com>
Subject: Re: Bisection result: eeepc hotk breakage
Date: Fri, 31 Oct 2008 17:54:52 +0300	[thread overview]
Message-ID: <490B1C3C.2080305@suse.de> (raw)
In-Reply-To: <490B132A.3000904@tuffmail.co.uk>

[-- Attachment #1: Type: text/plain, Size: 987 bytes --]

Alan Jenkins wrote:
> Alexey Starikovskiy wrote:
>> Alan Jenkins wrote:
>>> Alexey Starikovskiy wrote:
>>>> Alan Jenkins wrote:
>>>>> Alexey Starikovskiy wrote:
>>>>>> Alan Jenkins wrote:
>>>>>>> Well, that didn't work.
>>>>>> Pity...
>>>>>> Could you produce a debug log from EC?
>>>>>> Probably it's a good time to open a new bug report...
>>>>> <http://bugzilla.kernel.org/show_bug.cgi?id=11917>
>>>>> "Asus Eee PC hotkeys stop working after prolonged usage"
>>>>>
>>>>> I stuck at it, found a reliable test and bisected successfully.
>>>>> 2.6.28-rc2 is broken, but I can fix it by reverting the bad commit.
>>>>> (There were some conflicts, I fixed up the dock driver manually and
>>>>> avoided building the rest).
>>>> Alan, to make things clear -- reverting following commit makes EC work
>>>> without
>>>> a problem?
>>>>
>>>
>>> Yes, that's right.
>> Great!
>> What kernel version is that -- 32 or 64?
> 
> 32 bit, my EeePC doesn't do 64.
is the attached patch enough to fix ?


[-- Attachment #2: x.patch --]
[-- Type: text/x-diff, Size: 426 bytes --]

diff --git a/drivers/acpi/ec.c b/drivers/acpi/ec.c
index ef42316..e0f1534 100644
--- a/drivers/acpi/ec.c
+++ b/drivers/acpi/ec.c
@@ -751,6 +751,7 @@ ec_parse_device(acpi_handle handle, u32 Level, void *context, void **retval)
 		return status;
 	ec->gpe = tmp;
 	/* Use the global lock for all EC transactions? */
+	tmp = 0;
 	acpi_evaluate_integer(handle, "_GLK", NULL, &tmp);
 	ec->global_lock = tmp;
 	ec->handle = handle;

  reply	other threads:[~2008-10-31 14:54 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-28 23:49 2.6.28-rc1: rapid hotkeys break on eeepc again :( Alan Jenkins
2008-10-29  0:03 ` Alexey Starikovskiy
2008-10-29  9:44   ` Alan Jenkins
2008-10-29 14:12     ` Alexey Starikovskiy
2008-10-29 14:27       ` Alan Jenkins
2008-10-29 20:27         ` Alan Jenkins
2008-10-29 20:34           ` Alexey Starikovskiy
2008-10-31 10:26             ` Bisection result: eeepc hotk breakage Alan Jenkins
2008-10-31 13:51               ` Alexey Starikovskiy
2008-10-31 13:53                 ` Alan Jenkins
2008-10-31 14:15                   ` Alexey Starikovskiy
2008-10-31 14:16                     ` Alan Jenkins
2008-10-31 14:54                       ` Alexey Starikovskiy [this message]
2008-10-31 15:46                         ` Alan Jenkins
2008-10-31 16:05                           ` Alexey Starikovskiy
2008-11-03  1:03                         ` Zhao Yakui
2008-10-31 14:58                   ` Rafael J. Wysocki
2008-10-31 15:04                     ` Alan Jenkins

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=490B1C3C.2080305@suse.de \
    --to=astarikovskiy@suse.de \
    --cc=alan-jenkins@tuffmail.co.uk \
    --cc=aystarik@gmail.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=willy@linux.intel.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