[CCing a few people and the the regression list, as it should be in the
loop for regressions:
https://docs.kernel.org/admin-guide/reporting-regressions.html]
On 11.05.23 23:22, Xose Vazquez Perez wrote:
>
> 6.3.2 kernel identifies "Logitech" "ERGO M575" as "Logitech"
> "(\xc9_O\x04)",
> 6.2.15 works fine.
>
>
> 6.2.15 boot log:
> input: Logitech ERGO M575 as
> /devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.3/3-1.3:1.2/0003:046D:C52B.0003/0003:046D:4096.0005/input/input15
> logitech-hidpp-device 0003:046D:4096.0005: input,hidraw1: USB HID v1.11
> Mouse [Logitech ERGO M575] on usb-0000:00:1a.0-1.3/input2:1
>
> 6.3.2 boot log:
> input: Logitech \xc9_O\x04 as
> /devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.3/3-1.3:1.2/0003:046D:C52B.0003/0003:046D:4096.0005/input/input15
> logitech-hidpp-device 0003:046D:4096.0005: input,hidraw2: USB HID v1.11
> Mouse [Logitech \xc9_O\x04] on usb-0000:00:1a.0-1.3/input2:1
I wonder if this if this is some related to this issue:
https://bugzilla.kernel.org/show_bug.cgi?id=217412
("Since kernel 6.3.1 logitech unify receiver not working properly")
That one so far seems to be ignored by the developers. Your report one
also didn't get any reply yet.
Could you maybe perform a bisection to get down to this?
Side note: there is also
https://bugzilla.kernel.org/show_bug.cgi?id=217330
("Broken Logitech unifying battery names in hid-next tree")
Anyway, for the rest of this mail:
[TLDR: I'm adding this report to the list of tracked Linux kernel
regressions; the text you find below is based on a few templates
paragraphs you might have encountered already in similar form.
See link in footer if these mails annoy you.]
Thanks for the report. To be sure the issue doesn't fall through the
cracks unnoticed, I'm adding it to regzbot, the Linux kernel regression
tracking bot:
#regzbot ^introduced v6.2..v6.3
#regzbot title input: Logitech Trackball M575 misidentified
#regzbot ignore-activity
This isn't a regression? This issue or a fix for it are already
discussed somewhere else? It was fixed already? You want to clarify when
the regression started to happen? Or point out I got the title or
something else totally wrong? Then just reply and tell me -- ideally
while also telling regzbot about it, as explained by the page listed in
the footer of this mail.
Developers: When fixing the issue, remember to add 'Link:' tags pointing
to the report (the parent of this mail). See page linked in footer for
details.
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
That page also explains what to do if mails like this annoy you.
On Tue, 2023-05-16 at 14:33 +0200, Linux regression tracking (Thorsten
Leemhuis) wrote:
> [CCing a few people and the the regression list, as it should be in
> the
> loop for regressions:
> https://docs.kernel.org/admin-guide/reporting-regressions.html]
>
> On 11.05.23 23:22, Xose Vazquez Perez wrote:
> >
> > 6.3.2 kernel identifies "Logitech" "ERGO M575" as "Logitech"
> > "(\xc9_O\x04)",
> > 6.2.15 works fine.
> >
> >
> > 6.2.15 boot log:
> > input: Logitech ERGO M575 as
> > /devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.3/3-
> > 1.3:1.2/0003:046D:C52B.0003/0003:046D:4096.0005/input/input15
> > logitech-hidpp-device 0003:046D:4096.0005: input,hidraw1: USB HID
> > v1.11
> > Mouse [Logitech ERGO M575] on usb-0000:00:1a.0-1.3/input2:1
> >
> > 6.3.2 boot log:
> > input: Logitech \xc9_O\x04 as
> > /devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.3/3-
> > 1.3:1.2/0003:046D:C52B.0003/0003:046D:4096.0005/input/input15
> > logitech-hidpp-device 0003:046D:4096.0005: input,hidraw2: USB HID
> > v1.11
> > Mouse [Logitech \xc9_O\x04] on usb-0000:00:1a.0-1.3/input2:1
>
> I wonder if this if this is some related to this issue:
> https://bugzilla.kernel.org/show_bug.cgi?id=217412
> ("Since kernel 6.3.1 logitech unify receiver not working properly")
>
> That one so far seems to be ignored by the developers. Your report
> one
> also didn't get any reply yet.
>
> Could you maybe perform a bisection to get down to this?
>
> Side note: there is also
> https://bugzilla.kernel.org/show_bug.cgi?id=217330
> ("Broken Logitech unifying battery names in hid-next tree")
The device name problem is tracked in 217330, which I filed.
A bisection would definitely help me if you have time, otherwise I'll
get to it, but it's probably not going to be before a couple of weeks.
You can also test this patch on top of the latest kernel tree:
https://patchwork.kernel.org/project/linux-input/patch/[email protected]/
although I don't expect it to make a difference.
Cheers
>
>
> Anyway, for the rest of this mail:
>
> [TLDR: I'm adding this report to the list of tracked Linux kernel
> regressions; the text you find below is based on a few templates
> paragraphs you might have encountered already in similar form.
> See link in footer if these mails annoy you.]
>
> Thanks for the report. To be sure the issue doesn't fall through the
> cracks unnoticed, I'm adding it to regzbot, the Linux kernel
> regression
> tracking bot:
>
> #regzbot ^introduced v6.2..v6.3
> #regzbot title input: Logitech Trackball M575 misidentified
> #regzbot ignore-activity
>
> This isn't a regression? This issue or a fix for it are already
> discussed somewhere else? It was fixed already? You want to clarify
> when
> the regression started to happen? Or point out I got the title or
> something else totally wrong? Then just reply and tell me -- ideally
> while also telling regzbot about it, as explained by the page listed
> in
> the footer of this mail.
>
> Developers: When fixing the issue, remember to add 'Link:' tags
> pointing
> to the report (the parent of this mail). See page linked in footer
> for
> details.
>
> Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker'
> hat)
> --
> Everything you wanna know about Linux kernel regression tracking:
> https://linux-regtracking.leemhuis.info/about/#tldr
> That page also explains what to do if mails like this annoy you.
On 5/31/23 10:50, Bastien Nocera wrote:
> The device name problem is tracked in 217330, which I filed.
>
> A bisection would definitely help me if you have time, otherwise I'll
> get to it, but it's probably not going to be before a couple of weeks.
>
> You can also test this patch on top of the latest kernel tree:
> https://patchwork.kernel.org/project/linux-input/patch/[email protected]/
> although I don't expect it to make a difference.
It was fixed in 6.3.7.
Thank you.