Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp617244rwd; Tue, 16 May 2023 05:52:14 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ5VVA/TPsrfv4q35OUlG0FykV9F3vQ4yhowhqKOkcHbt9irC80TnbVd6jD0Q0FCRR7m0Iyc X-Received: by 2002:a05:6a20:8f23:b0:106:4e09:151f with SMTP id b35-20020a056a208f2300b001064e09151fmr7450454pzk.60.1684241534108; Tue, 16 May 2023 05:52:14 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1684241534; cv=none; d=google.com; s=arc-20160816; b=WtipSARfio0W8SoYnSrFmXVg7TTu3a6aaKm65ejxK3ONkWuSAsn6rpV0VNjtBpt6ne aoLQOTaBr2GEwEaPVaKlAqAi7eUIfurKY2c8fKnHIlOyCAC44zEiOm8ky7wsWZtixn6r WhhRj397r5/bOYTzrr6YmSJvtXxR5fF9YwhMID8HyO7e8cuBApFcAezWhx0cPsYPD8n9 NZ3w11V0y+Z3diaYslb58Cuh7HdkR0OcWB0UQE3JiYPXHUdhywqZXSzXnmYLkDS1+bWE dY1EnbOyM+ixbduIVCBklhnn129LSHj+43NpZyA1SfsQ5zBSiAJOvuEW4Qs92WaMi3Wq 8ilg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:cc:from :references:to:content-language:subject:reply-to:user-agent :mime-version:date:message-id; bh=fV8X+k8xneTLVlppRgTeRZaWIFsHH/LLzazZm+P3yt0=; b=UnXiqrRzuq9tV8xBzQTFG/62odmV3vcQ4rlwS+HNNoy+ezeoYBLwlbTAFndgc4ceqN uezjka6P3KmZve9i44oeOg2BsWE7pscisYBK0oeKtTgECo3ZzdNZ2ZClSpSqrlCikuH6 BX+AU4mkfBozYHxoCLXe1fzXhx+JJXsWoP8tF4b3NXDQhv+f+W49T7gKii3kHqBrBEhS EtpIcL9MxP1LyUraBYqJrLIcFAaSF2kbO0oKj8Ezp78kvyY1/6oD6CseCwzyE5wjQFrs M0F3znI53iQeVahpWvvLYLpXplkijZc5BwdgXyrkQI/BKnDC30StOUtDASHI7nhj5DvD esYQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id w14-20020a63a74e000000b00524ba7e95c3si19176011pgo.785.2023.05.16.05.52.01; Tue, 16 May 2023 05:52:14 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232770AbjEPMd3 (ORCPT + 99 others); Tue, 16 May 2023 08:33:29 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50106 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231887AbjEPMd1 (ORCPT ); Tue, 16 May 2023 08:33:27 -0400 Received: from wp530.webpack.hosteurope.de (wp530.webpack.hosteurope.de [80.237.130.52]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4A44B109; Tue, 16 May 2023 05:33:26 -0700 (PDT) Received: from [2a02:8108:8980:2478:8cde:aa2c:f324:937e]; authenticated by wp530.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) id 1pytro-0005Hc-6i; Tue, 16 May 2023 14:33:24 +0200 Message-ID: <8941c5f2-3861-da68-06ca-adc68a37e53b@leemhuis.info> Date: Tue, 16 May 2023 14:33:23 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.10.0 Reply-To: Linux regressions mailing list Subject: Re: [BUG: 6.3 kernel] Logitech Trackball M575 misidentified Content-Language: en-US, de-DE To: Xose Vazquez Perez , linux-input@vger.kernel.org References: From: "Linux regression tracking (Thorsten Leemhuis)" Cc: Linux kernel regressions list , Bastien Nocera , =?UTF-8?Q?Filipe_La=c3=adns?= , Jiri Kosina , Benjamin Tissoires , LKML In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-bounce-key: webpack.hosteurope.de;regressions@leemhuis.info;1684240406;c7f7ccdc; X-HE-SMSGID: 1pytro-0005Hc-6i X-Spam-Status: No, score=-4.6 required=5.0 tests=BAYES_00,NICE_REPLY_A, RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE, URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org [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.