Bug 217701

(In reply to Verot from comment #0)
> Description:
> When booting into Linux 6.4.4, system no longer recognizes touchpad input
> (confirmed with xinput). On the lts release, 6.1.39, the input is still
> recognized.
> 
> Additional info:
> * package version(s): Linux 6.4.4, 6.1.39
> * Device: ELAN1206:00 04F3:30F1 Touchpad
> 
> Steps to reproduce:
> - Install 6.4.4 with Elan Touchpad 1206
> - Reboot
> 
> The issue might be related to bisected commit id:
> 7b63a88bb62ba2ddf5fcd956be85fe46624628b9
> This is the only recent commit related to Elantech drivers I've noticed that
> may have broken the input.

Can you show dmesg?

Commit 7b63a88bb62ba2ddf5fcd956be85fe46624628b9 is present in 6.1.39, so it cannot be the cause of your issue:

commit f9172a0bb57d62a42122075a124c071a1c56e455
Author: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Date:   Thu May 11 12:08:37 2023 -0700

    Input: psmouse - fix OOB access in Elantech protocol

    commit 7b63a88bb62ba2ddf5fcd956be85fe46624628b9 upstream.

    The kernel only allocate 5 MT slots; check that transmitted slot ID
    falls within the acceptable range.

    Link: https://lore.kernel.org/r/ZFnEL91nrT789dbG@google.com
    Cc: stable@vger.kernel.org
    Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

$ git describe --contains f9172a0bb57d62a42122075a124c071a1c56e455
v6.1.34~73

Created attachment 304690 [details]
Dmesg output from kernel 6.1.39

Created attachment 304691 [details]
Dmesg output from kernel 6.4.4

(In reply to Bagas Sanjaya from comment #1) 
> Can you show dmesg?

I've attached the full dmesg outputs for both kernels. Let me know if you need anything else

(In reply to Dmitry Torokhov from comment #2)
> Commit 7b63a88bb62ba2ddf5fcd956be85fe46624628b9 is present in 6.1.39, so it
> cannot be the cause of your issue:
> 
> commit f9172a0bb57d62a42122075a124c071a1c56e455
> Author: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> Date:   Thu May 11 12:08:37 2023 -0700
> 
>     Input: psmouse - fix OOB access in Elantech protocol
> 
>     commit 7b63a88bb62ba2ddf5fcd956be85fe46624628b9 upstream.
> 
>     The kernel only allocate 5 MT slots; check that transmitted slot ID
>     falls within the acceptable range.
> 
>     Link: https://lore.kernel.org/r/ZFnEL91nrT789dbG@google.com
>     Cc: stable@vger.kernel.org
>     Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
>     Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> 
> $ git describe --contains f9172a0bb57d62a42122075a124c071a1c56e455
> v6.1.34~73

That was a guess at what could maybe be the issue - which is why I didn't link it in the commit field for this report. You are correct that it probably is not the cause, I'm not really sure where the issue originated honestly.

(In reply to Verot from comment #5)
> (In reply to Bagas Sanjaya from comment #1) 
> > Can you show dmesg?
> 
> I've attached the full dmesg outputs for both kernels. Let me know if you
> need anything else

From the mailing list discussion and here, 7b63a88bb62ba2ddf5fcd956be85fe46624628b9 is not the culprit.
Can you perform bisection between v6.1 and v6.4 to find the proper culprit?

(In reply to Bagas Sanjaya from comment #7)
> (In reply to Verot from comment #5)
> > (In reply to Bagas Sanjaya from comment #1) 
> > > Can you show dmesg?
> > 
> > I've attached the full dmesg outputs for both kernels. Let me know if you
> > need anything else
> 
> From the mailing list discussion and here,
> 7b63a88bb62ba2ddf5fcd956be85fe46624628b9 is not the culprit.
> Can you perform bisection between v6.1 and v6.4 to find the proper culprit?

I did try, but since it was my first time manually compiling and bisecting the kernel, I ran into some trouble I'm not sure how to get past. 

However, I did find the log I made of this issue from a previous install on the day I noticed (after my touchpad stopped responding). It has a journalctl log up until the device disappeared. I'm adding it to the attachments above.
The issue had appeared on an earlier kernel, so it should help pin it down.

I apologize I cannot be of much help in terms of the bisection, but let me let me know if there is anything else I can do.

Created attachment 304696 [details]
Touchpad Error Document

This is a log I made when I noticed what had happened.
It might be of some help.

(In reply to Verot from comment #8)
> (In reply to Bagas Sanjaya from comment #7)
> > (In reply to Verot from comment #5)
> > > (In reply to Bagas Sanjaya from comment #1) 
> > > > Can you show dmesg?
> > > 
> > > I've attached the full dmesg outputs for both kernels. Let me know if you
> > > need anything else
> > 
> > From the mailing list discussion and here,
> > 7b63a88bb62ba2ddf5fcd956be85fe46624628b9 is not the culprit.
> > Can you perform bisection between v6.1 and v6.4 to find the proper culprit?
> 
> I did try, but since it was my first time manually compiling and bisecting
> the kernel, I ran into some trouble I'm not sure how to get past. 
> 
> However, I did find the log I made of this issue from a previous install on
> the day I noticed (after my touchpad stopped responding). It has a
> journalctl log up until the device disappeared. I'm adding it to the
> attachments above.
> The issue had appeared on an earlier kernel, so it should help pin it down.
> 
> I apologize I cannot be of much help in terms of the bisection, but let me
> let me know if there is anything else I can do.

There is a primer on compiling kernel at [1]. Please try.

[1]: https://www.kernel.org/doc/html/latest/admin-guide/quickly-build-trimmed-linux.html

(In reply to Verot from comment #8)
> (In reply to Bagas Sanjaya from comment #7)
> > (In reply to Verot from comment #5)
> > > (In reply to Bagas Sanjaya from comment #1) 
> > > > Can you show dmesg?
> > > 
> > > I've attached the full dmesg outputs for both kernels. Let me know if you
> > > need anything else
> > 
> > From the mailing list discussion and here,
> > 7b63a88bb62ba2ddf5fcd956be85fe46624628b9 is not the culprit.
> > Can you perform bisection between v6.1 and v6.4 to find the proper culprit?
> 
> I did try, but since it was my first time manually compiling and bisecting
> the kernel, I ran into some trouble I'm not sure how to get past. 
> 
> However, I did find the log I made of this issue from a previous install on
> the day I noticed (after my touchpad stopped responding). It has a
> journalctl log up until the device disappeared. I'm adding it to the
> attachments above.
> The issue had appeared on an earlier kernel, so it should help pin it down.
> 
> I apologize I cannot be of much help in terms of the bisection, but let me
> let me know if there is anything else I can do.

In the mean time you can connect your USB mouse instead while bisecting.