Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.kernel > #79322 > unrolled thread

Bug#1038271: linux-image-6.1.0-9-amd64: Logitech trackpad T651 doesn't work anymore

Started byDiederik de Haas <didi.debian@cknow.org>
First post2023-06-17 00:20 +0200
Last post2023-06-18 22:50 +0200
Articles 10 — 3 participants

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Bug#1038271: linux-image-6.1.0-9-amd64: Logitech trackpad T651 doesn't work anymore Diederik de Haas <didi.debian@cknow.org> - 2023-06-17 00:20 +0200
    Processed: Re: Bug#1038271: linux-image-6.1.0-9-amd64: Logitech  trackpad T651 doesn't work anymore "Debian Bug Tracking System" <owner@bugs.debian.org> - 2023-06-17 00:20 +0200
    Bug#1038271: linux-image-6.1.0-9-amd64: Logitech trackpad T651 doesn't work anymore Mike Hommey <mh@glandium.org> - 2023-06-17 01:10 +0200
      Bug#1038271: linux-image-6.1.0-9-amd64: Logitech trackpad T651 doesn't work anymore Mike Hommey <mh@glandium.org> - 2023-06-17 01:10 +0200
        Bug#1038271: linux-image-6.1.0-9-amd64: Logitech trackpad T651 doesn't work anymore Diederik de Haas <didi.debian@cknow.org> - 2023-06-17 01:30 +0200
          Processed: Re: Bug#1038271: linux-image-6.1.0-9-amd64: Logitech  trackpad T651 doesn't work anymore "Debian Bug Tracking System" <owner@bugs.debian.org> - 2023-06-17 01:30 +0200
          Bug#1038271: linux-image-6.1.0-9-amd64: Logitech trackpad T651 doesn't work anymore Mike Hommey <mh@glandium.org> - 2023-06-17 23:20 +0200
            Bug#1038271: linux-image-6.1.0-9-amd64: Logitech trackpad T651 doesn't work anymore Mike Hommey <mh@glandium.org> - 2023-06-18 01:20 +0200
              Bug#1038271: linux-image-6.1.0-9-amd64: Logitech trackpad T651 doesn't work anymore Mike Hommey <mh@glandium.org> - 2023-06-18 02:20 +0200
                Bug#1038271: linux-image-6.1.0-9-amd64: Logitech trackpad T651 doesn't work anymore Diederik de Haas <didi.debian@cknow.org> - 2023-06-18 22:50 +0200

#79322 — Bug#1038271: linux-image-6.1.0-9-amd64: Logitech trackpad T651 doesn't work anymore

FromDiederik de Haas <didi.debian@cknow.org>
Date2023-06-17 00:20 +0200
SubjectBug#1038271: linux-image-6.1.0-9-amd64: Logitech trackpad T651 doesn't work anymore
Message-ID<GHpXr-gnUJ-3@gated-at.bofh.it>

[Multipart message — attachments visible in raw view] — view raw

Control: tag -1 moreinfo

On Fri Jun 16, 2023 at 11:21 PM CEST, Mike Hommey wrote:
> Package: src:linux
> Version: 6.1.27-1
>
> After upgrading to bookworm, my bluetooth trackpad stopped working. It's
> properly connected, and `libinput list-devices` displays this message:
>
> event15 - Logitech Rechargeable Trackpad T651: kernel bug: device has min == 
max on ABS_MT_POSITION_X
>
> It worked with earlier kernel versions. I went back to one I had at hand
> from before the upgrade (6.1.0-0.deb11.5-amd64), and it worked again,

Version 6.1.0-0.deb11.5 should be the same as version 6.1.12-1.
If would be useful if you could verify that with the non-backports kernel
it also works again.
If that's the case, could you try newer versions (6.1.15-1, 6.1.20-1 and
6.1.25-1) to find the newest kernel version that still works?

A `git bisect` would be best, but grabbing these intermediate versions
(from snapshot.debian.org) is the quickest way to narrow the range.

[toc] | [next] | [standalone]


#79323 — Processed: Re: Bug#1038271: linux-image-6.1.0-9-amd64: Logitech trackpad T651 doesn't work anymore

From"Debian Bug Tracking System" <owner@bugs.debian.org>
Date2023-06-17 00:20 +0200
SubjectProcessed: Re: Bug#1038271: linux-image-6.1.0-9-amd64: Logitech trackpad T651 doesn't work anymore
Message-ID<GHpXr-gnUJ-7@gated-at.bofh.it>
In reply to#79322
Processing control commands:

> tag -1 moreinfo
Bug #1038271 [src:linux] linux-image-6.1.0-9-amd64: Logitech trackpad T651 doesn't work anymore
Added tag(s) moreinfo.

-- 
1038271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038271
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]


#79324

FromMike Hommey <mh@glandium.org>
Date2023-06-17 01:10 +0200
Message-ID<GHqJP-goxr-3@gated-at.bofh.it>
In reply to#79322
On Sat, Jun 17, 2023 at 12:13:13AM +0200, Diederik de Haas wrote:
> Control: tag -1 moreinfo
> 
> On Fri Jun 16, 2023 at 11:21 PM CEST, Mike Hommey wrote:
> > Package: src:linux
> > Version: 6.1.27-1
> >
> > After upgrading to bookworm, my bluetooth trackpad stopped working. It's
> > properly connected, and `libinput list-devices` displays this message:
> >
> > event15 - Logitech Rechargeable Trackpad T651: kernel bug: device has min == 
> max on ABS_MT_POSITION_X
> >
> > It worked with earlier kernel versions. I went back to one I had at hand
> > from before the upgrade (6.1.0-0.deb11.5-amd64), and it worked again,
> 
> Version 6.1.0-0.deb11.5 should be the same as version 6.1.12-1.
> If would be useful if you could verify that with the non-backports kernel
> it also works again.
> If that's the case, could you try newer versions (6.1.15-1, 6.1.20-1 and
> 6.1.25-1) to find the newest kernel version that still works?

6.1.12-1 and 6.1.15-1 are good. 6.1.20-1 is the first broken one.

> A `git bisect` would be best, but grabbing these intermediate versions
> (from snapshot.debian.org) is the quickest way to narrow the range.

Last time I tried to build Debian linux kernels, it was spending a large
amount of time building packages I don't need, and finding the right
incantation to reduce that load was not straightforward, and I can't
find my notes, unfortunately. If you have instructions I can use to go
through a bisect in a quick manner, I'm all ears.

Mike

[toc] | [prev] | [next] | [standalone]


#79325

FromMike Hommey <mh@glandium.org>
Date2023-06-17 01:10 +0200
Message-ID<GHqJP-goxr-1@gated-at.bofh.it>
In reply to#79324
On Sat, Jun 17, 2023 at 07:59:17AM +0900, Mike Hommey wrote:
> On Sat, Jun 17, 2023 at 12:13:13AM +0200, Diederik de Haas wrote:
> > Control: tag -1 moreinfo
> > 
> > On Fri Jun 16, 2023 at 11:21 PM CEST, Mike Hommey wrote:
> > > Package: src:linux
> > > Version: 6.1.27-1
> > >
> > > After upgrading to bookworm, my bluetooth trackpad stopped working. It's
> > > properly connected, and `libinput list-devices` displays this message:
> > >
> > > event15 - Logitech Rechargeable Trackpad T651: kernel bug: device has min == 
> > max on ABS_MT_POSITION_X
> > >
> > > It worked with earlier kernel versions. I went back to one I had at hand
> > > from before the upgrade (6.1.0-0.deb11.5-amd64), and it worked again,
> > 
> > Version 6.1.0-0.deb11.5 should be the same as version 6.1.12-1.
> > If would be useful if you could verify that with the non-backports kernel
> > it also works again.
> > If that's the case, could you try newer versions (6.1.15-1, 6.1.20-1 and
> > 6.1.25-1) to find the newest kernel version that still works?
> 
> 6.1.12-1 and 6.1.15-1 are good. 6.1.20-1 is the first broken one.
> 
> > A `git bisect` would be best, but grabbing these intermediate versions
> > (from snapshot.debian.org) is the quickest way to narrow the range.
> 
> Last time I tried to build Debian linux kernels, it was spending a large
> amount of time building packages I don't need, and finding the right
> incantation to reduce that load was not straightforward, and I can't
> find my notes, unfortunately. If you have instructions I can use to go
> through a bisect in a quick manner, I'm all ears.

Although, if you have instructions to just build the one module and avoid
rebooting, that would be even better.

Mike

[toc] | [prev] | [next] | [standalone]


#79327

FromDiederik de Haas <didi.debian@cknow.org>
Date2023-06-17 01:30 +0200
Message-ID<GHr3b-goEy-5@gated-at.bofh.it>
In reply to#79325

[Multipart message — attachments visible in raw view] — view raw

Control: tag -1 -moreinfo
Control: found -1 6.1.20-1

On Saturday, 17 June 2023 01:00:58 CEST Mike Hommey wrote:
> > 6.1.12-1 and 6.1.15-1 are good. 6.1.20-1 is the first broken one.

Excellent, thanks. This is already very useful.

> > > A `git bisect` would be best, but grabbing these intermediate versions
> > > (from snapshot.debian.org) is the quickest way to narrow the range.
> > 
> > Last time I tried to build Debian linux kernels, it was spending a large
> > amount of time building packages I don't need, and finding the right
> > incantation to reduce that load was not straightforward, and I can't
> > find my notes, unfortunately. If you have instructions I can use to go
> > through a bisect in a quick manner, I'm all ears.
> 
> Although, if you have instructions to just build the one module and avoid
> rebooting, that would be even better.

I _think_ building just one module or without rebooting is not possible.

The 'official' instructions: https://wiki.debian.org/DebianKernel/GitBisect

I know some things to reduce what gets build, like f.e. what's described here:
https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#id-1.6.6.7
And there's also a facility to work with _build profiles_.
But I don't know if or how that could be applied to the 'official' instructions
as that deals with the upstream kernel source directly.

Hopefully one of the (more) experienced people chimes in with 
actual useful things ...

[toc] | [prev] | [next] | [standalone]


#79328 — Processed: Re: Bug#1038271: linux-image-6.1.0-9-amd64: Logitech trackpad T651 doesn't work anymore

From"Debian Bug Tracking System" <owner@bugs.debian.org>
Date2023-06-17 01:30 +0200
SubjectProcessed: Re: Bug#1038271: linux-image-6.1.0-9-amd64: Logitech trackpad T651 doesn't work anymore
Message-ID<GHr3b-goEy-13@gated-at.bofh.it>
In reply to#79327
Processing control commands:

> tag -1 -moreinfo
Bug #1038271 [src:linux] linux-image-6.1.0-9-amd64: Logitech trackpad T651 doesn't work anymore
Removed tag(s) moreinfo.
> found -1 6.1.20-1
Bug #1038271 [src:linux] linux-image-6.1.0-9-amd64: Logitech trackpad T651 doesn't work anymore
Marked as found in versions linux/6.1.20-1.

-- 
1038271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038271
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]


#79335

FromMike Hommey <mh@glandium.org>
Date2023-06-17 23:20 +0200
Message-ID<GHLuV-gEY6-5@gated-at.bofh.it>
In reply to#79327
On Sat, Jun 17, 2023 at 01:20:30AM +0200, Diederik de Haas wrote:
> Control: tag -1 -moreinfo
> Control: found -1 6.1.20-1
> 
> On Saturday, 17 June 2023 01:00:58 CEST Mike Hommey wrote:
> > > 6.1.12-1 and 6.1.15-1 are good. 6.1.20-1 is the first broken one.
> 
> Excellent, thanks. This is already very useful.
> 
> > > > A `git bisect` would be best, but grabbing these intermediate versions
> > > > (from snapshot.debian.org) is the quickest way to narrow the range.
> > > 
> > > Last time I tried to build Debian linux kernels, it was spending a large
> > > amount of time building packages I don't need, and finding the right
> > > incantation to reduce that load was not straightforward, and I can't
> > > find my notes, unfortunately. If you have instructions I can use to go
> > > through a bisect in a quick manner, I'm all ears.
> > 
> > Although, if you have instructions to just build the one module and avoid
> > rebooting, that would be even better.
> 
> I _think_ building just one module or without rebooting is not possible.
> 
> The 'official' instructions: https://wiki.debian.org/DebianKernel/GitBisect
> 
> I know some things to reduce what gets build, like f.e. what's described here:
> https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#id-1.6.6.7
> And there's also a facility to work with _build profiles_.
> But I don't know if or how that could be applied to the 'official' instructions
> as that deals with the upstream kernel source directly.
> 
> Hopefully one of the (more) experienced people chimes in with 
> actual useful things ...

I was able to build the relevant module only. The regression comes from
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=337c3624bcb008f92bab38c8fc4cdf97ae5313a2

Mike

[toc] | [prev] | [next] | [standalone]


#79337

FromMike Hommey <mh@glandium.org>
Date2023-06-18 01:20 +0200
Message-ID<GHNn3-gG48-1@gated-at.bofh.it>
In reply to#79335
On Sun, Jun 18, 2023 at 06:09:57AM +0900, Mike Hommey wrote:
> On Sat, Jun 17, 2023 at 01:20:30AM +0200, Diederik de Haas wrote:
> > Control: tag -1 -moreinfo
> > Control: found -1 6.1.20-1
> > 
> > On Saturday, 17 June 2023 01:00:58 CEST Mike Hommey wrote:
> > > > 6.1.12-1 and 6.1.15-1 are good. 6.1.20-1 is the first broken one.
> > 
> > Excellent, thanks. This is already very useful.
> > 
> > > > > A `git bisect` would be best, but grabbing these intermediate versions
> > > > > (from snapshot.debian.org) is the quickest way to narrow the range.
> > > > 
> > > > Last time I tried to build Debian linux kernels, it was spending a large
> > > > amount of time building packages I don't need, and finding the right
> > > > incantation to reduce that load was not straightforward, and I can't
> > > > find my notes, unfortunately. If you have instructions I can use to go
> > > > through a bisect in a quick manner, I'm all ears.
> > > 
> > > Although, if you have instructions to just build the one module and avoid
> > > rebooting, that would be even better.
> > 
> > I _think_ building just one module or without rebooting is not possible.
> > 
> > The 'official' instructions: https://wiki.debian.org/DebianKernel/GitBisect
> > 
> > I know some things to reduce what gets build, like f.e. what's described here:
> > https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#id-1.6.6.7
> > And there's also a facility to work with _build profiles_.
> > But I don't know if or how that could be applied to the 'official' instructions
> > as that deals with the upstream kernel source directly.
> > 
> > Hopefully one of the (more) experienced people chimes in with 
> > actual useful things ...
> 
> I was able to build the relevant module only. The regression comes from
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=337c3624bcb008f92bab38c8fc4cdf97ae5313a2

I sent a patch upstream, but it's not showing up on the archives yet.
I'll update with a link when I have one.

Mike

[toc] | [prev] | [next] | [standalone]


#79338

FromMike Hommey <mh@glandium.org>
Date2023-06-18 02:20 +0200
Message-ID<GHOj8-gGC2-11@gated-at.bofh.it>
In reply to#79337
On Sun, Jun 18, 2023 at 08:15:43AM +0900, Mike Hommey wrote:
> On Sun, Jun 18, 2023 at 06:09:57AM +0900, Mike Hommey wrote:
> > On Sat, Jun 17, 2023 at 01:20:30AM +0200, Diederik de Haas wrote:
> > > Control: tag -1 -moreinfo
> > > Control: found -1 6.1.20-1
> > > 
> > > On Saturday, 17 June 2023 01:00:58 CEST Mike Hommey wrote:
> > > > > 6.1.12-1 and 6.1.15-1 are good. 6.1.20-1 is the first broken one.
> > > 
> > > Excellent, thanks. This is already very useful.
> > > 
> > > > > > A `git bisect` would be best, but grabbing these intermediate versions
> > > > > > (from snapshot.debian.org) is the quickest way to narrow the range.
> > > > > 
> > > > > Last time I tried to build Debian linux kernels, it was spending a large
> > > > > amount of time building packages I don't need, and finding the right
> > > > > incantation to reduce that load was not straightforward, and I can't
> > > > > find my notes, unfortunately. If you have instructions I can use to go
> > > > > through a bisect in a quick manner, I'm all ears.
> > > > 
> > > > Although, if you have instructions to just build the one module and avoid
> > > > rebooting, that would be even better.
> > > 
> > > I _think_ building just one module or without rebooting is not possible.
> > > 
> > > The 'official' instructions: https://wiki.debian.org/DebianKernel/GitBisect
> > > 
> > > I know some things to reduce what gets build, like f.e. what's described here:
> > > https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#id-1.6.6.7
> > > And there's also a facility to work with _build profiles_.
> > > But I don't know if or how that could be applied to the 'official' instructions
> > > as that deals with the upstream kernel source directly.
> > > 
> > > Hopefully one of the (more) experienced people chimes in with 
> > > actual useful things ...
> > 
> > I was able to build the relevant module only. The regression comes from
> > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=337c3624bcb008f92bab38c8fc4cdf97ae5313a2
> 
> I sent a patch upstream, but it's not showing up on the archives yet.
> I'll update with a link when I have one.

Here we go:
https://patchwork.kernel.org/project/linux-input/patch/20230617230957.6mx73th4blv7owqk@glandium.org/

Mike

[toc] | [prev] | [next] | [standalone]


#79349

FromDiederik de Haas <didi.debian@cknow.org>
Date2023-06-18 22:50 +0200
Message-ID<GI7vr-gSrg-7@gated-at.bofh.it>
In reply to#79338

[Multipart message — attachments visible in raw view] — view raw

Control: forwarded -1 https://lore.kernel.org/all/20230617230957.6mx73th4blv7owqk@glandium.org/
Control: tag -1 upstream

On Sunday, 18 June 2023 02:14:22 CEST Mike Hommey wrote:
> > > I was able to build the relevant module only. The regression comes from
> > > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/
> > > ?id=337c3624bcb008f92bab38c8fc4cdf97ae5313a2> 
> > I sent a patch upstream, but it's not showing up on the archives yet.
> > I'll update with a link when I have one.
> 
> Here we go:
> https://patchwork.kernel.org/project/linux-input/patch/20230617230957.6mx73t
> h4blv7owqk@glandium.org/

That was awesome :) Updated bug metadata accordingly

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.kernel


csiph-web