From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
Cc: Alexey Starikovskiy <astarikovskiy@suse.de>,
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 15:58:53 +0100 [thread overview]
Message-ID: <200810311558.53888.rjw@sisk.pl> (raw)
In-Reply-To: <490B0DCB.40009@tuffmail.co.uk>
On Friday, 31 of October 2008, 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.
Hm, so in fact it _is_ a regression from 2.6.27 (this commit could not be
present in that kernel).
Thanks,
Rafael
> >> 27663c5855b10af9ec67bc7dfba001426ba21222 is first bad commit
> >> commit 27663c5855b10af9ec67bc7dfba001426ba21222
> >> Author: Matthew Wilcox <willy@linux.intel.com>
> >> Date: Fri Oct 10 02:22:59 2008 -0400
> >>
> >> ACPI: Change acpi_evaluate_integer to support 64-bit on 32-bit
> >> kernels
> >>
> >> As of version 2.0, ACPI can return 64-bit integers. The current
> >> acpi_evaluate_integer only supports 64-bit integers on 64-bit
> >> platforms.
> >> Change the argument to take a pointer to an acpi_integer so we
> >> support
> >> 64-bit integers on all platforms.
> >>
> >> lenb: replaced use of "acpi_integer" with "unsigned long long"
> >> lenb: fixed bug in acpi_thermal_trips_update()
> >>
> >> Signed-off-by: Matthew Wilcox <willy@linux.intel.com>
> >> Signed-off-by: Len Brown <len.brown@intel.com>
> >
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
next prev parent 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
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 [this message]
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=200810311558.53888.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=alan-jenkins@tuffmail.co.uk \
--cc=astarikovskiy@suse.de \
--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