linux-kernel - Re: intel-gpio interrupts stop firing with Focaltech I2C-HID touchpad

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAB4CAwdYsQPmfm5HrrP7DMwwH7mQVfwgkG7xEXvMPzP+wB7n-A@mail.gmail.com>
Date:   Fri, 17 Nov 2017 16:50:45 +0800
From:   Chris Chiu <chiu@...lessm.com>
To:     Mika Westerberg <mika.westerberg@...ux.intel.com>
Cc:     Daniel Drake <drake@...lessm.com>, heikki.krogerus@...ux.intel.com,
        linux-gpio@...r.kernel.org,
        Linux Kernel <linux-kernel@...r.kernel.org>,
        Endless Linux Upstreaming Team <linux@...lessm.com>
Subject: Re: intel-gpio interrupts stop firing with Focaltech I2C-HID touchpad

The dmesg log is here
https://gist.github.com/mschiu77/5dfe91ef319de16fb343c5d907b2cbc5
And the acpidump is here
https://gist.github.com/mschiu77/d9b72d89a6a21efb616f153f164c0d18

On Fri, Nov 17, 2017 at 4:27 PM, Chris Chiu <chiu@...lessm.com> wrote:
> On Thu, Nov 16, 2017 at 9:07 PM, Mika Westerberg
> <mika.westerberg@...ux.intel.com> wrote:
>> On Thu, Nov 16, 2017 at 12:01:24PM +0000, Daniel Drake wrote:
>>> On Thu, Nov 16, 2017 at 11:52 AM, Mika Westerberg
>>> <mika.westerberg@...ux.intel.com> wrote:
>>> > Please first check the signal with some analyzator if it works as
>>> > expected and let's then figure out what needs to be fixed and where ;-)
>>>
>>> It works fine under Windows, so I think it's already clear that there
>>> is a Linux bug to be solved here.
>>
>> Can you remove all the "debugging" patches and hacks and then add
>> "i2c_hid.debug=1" to the kernel command line.
>>
>> Then reproduce the issue and send me full dmesg and acpidump of the
>> system. Thanks.
>
> Hi Mika,
>     Here's the dmesg log which stops at 214th seconds and no more
> further output and archive of "acpidump -b" output files FYI.
>
> Chris