linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Henrik Rydberg <rydberg@bitmath.org>,
	Verot <verot.wrongdoer713@simplelogin.com>
Cc: Linux Input Devices <linux-input@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Regressions <regressions@lists.linux.dev>,
	Linux Stable <stable@vger.kernel.org>
Subject: Fwd: Kernel 6.4.4 breaks Elan Touchpad 1206
Date: Tue, 25 Jul 2023 07:00:21 +0700	[thread overview]
Message-ID: <42bc8e02-5ee0-f1c8-610e-e16391e54ee2@gmail.com> (raw)

Hi,

I notice a regression report on Bugzilla [1]. Quoting from it:

> 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.

See Bugzilla for the full thread:

To the reporter (Verot): Can you attach dmesg and lspci output?

Anyway, I'm adding this regression to be tracked by regzbot:

#regzbot introduced: 7b63a88bb62ba2 https://bugzilla.kernel.org/show_bug.cgi?id=217701
#regzbot title: OOB protocol access fix breaks Elan Touchpad 1206

Thanks.

[1]: https://bugzilla.kernel.org/show_bug.cgi?id=217701

-- 
An old man doll... just what I always wanted! - Clara

             reply	other threads:[~2023-07-25  0:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-25  0:00 Bagas Sanjaya [this message]
2023-07-25  0:10 ` Fwd: Kernel 6.4.4 breaks Elan Touchpad 1206 Dmitry Torokhov
2023-07-25  0:14   ` Dmitry Torokhov
2023-07-25  5:53 ` Bagas Sanjaya
2023-09-26  0:55 ` Bagas Sanjaya

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=42bc8e02-5ee0-f1c8-610e-e16391e54ee2@gmail.com \
    --to=bagasdotme@gmail.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    --cc=rydberg@bitmath.org \
    --cc=stable@vger.kernel.org \
    --cc=verot.wrongdoer713@simplelogin.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;
as well as URLs for NNTP newsgroup(s).