Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp9703087rwd; Wed, 21 Jun 2023 10:39:48 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ6MB7h9e86v1c3auZHhyw/fY7oPf684LPt9sqJk05+7PK6Js4MInzeQacGLnScbOkUkExD/ X-Received: by 2002:a05:6808:18a9:b0:39e:c744:eaef with SMTP id bi41-20020a05680818a900b0039ec744eaefmr15156776oib.48.1687369187819; Wed, 21 Jun 2023 10:39:47 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1687369187; cv=none; d=google.com; s=arc-20160816; b=Y0p3WKxv8sQD1WNEHM9G8CvyoldvVhrW+iNtAcuRg0UtU0zAwRlmOR80eSxq2m50Z9 +ZHn+9v+jHssk+k91kgmFJ/qwFG2kIp3ZeteNpzCrSEl+FC6PIqTnMuLJDD4zoxJE8Tz Z1gamWEVH/Bl28Yc+8oeMja8dXdAvqLBsuwo71mWe5MuFYpU8vpwIq2kaIhdtpsOG0Tz XXDkgGYjxb5qeU1ZdOP4Rvqe3dTtPCQKVO/ZYywjG3sh2sY+QTc1G0PEnS5rIrhuOSlL C3WnydRx3nzv1bxFGyG3PUbpXRq2Q9oTmuk+/ouTFAcMc4i8hiGqKSweFeZRuyKgU6AY GpIQ== 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:reply-to :from:references:cc:to:content-language:subject:user-agent :mime-version:date:message-id; bh=USURf3rV0HXF6PYRiUpsGdY99s1SsHtaWnRoRNm1Bzs=; b=KKRH4n1x84AB8RsrDwbadpxJY4qo2w1ckKHcJJFK8kaGSHWVMiiTE0Gq8Q+qUQE8Af f3v/c1fQtk/tiNSWZTFxFkx3ljGY9qvREjzumMVjylCZ8FncyZf1J7SClQh/+mrOUvHK sgpIsSKjesqepxI/m7NpBdQ1PusoBUicHsxAoLc7FXIJ10BZD5WvLQ4WS85v5MjuTT9o d90/wC/Adu3UjMb7JQdnr0ewfXnjqJDx9AbYXVSBSQU6Vs+VFeKfTA2ocdvyFvicYYKx xHFlF3cSKI66o+S2gIuVt+Bb8RyQb1fO8JtBkH2fp/p0hsX8sol21oFVnEmhD2rSw2Xk 1/4A== 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 b67-20020a633446000000b0053f29758cd1si4491179pga.839.2023.06.21.10.39.35; Wed, 21 Jun 2023 10:39:47 -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 S230221AbjFURTm (ORCPT + 99 others); Wed, 21 Jun 2023 13:19:42 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58172 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229502AbjFURTl (ORCPT ); Wed, 21 Jun 2023 13:19:41 -0400 Received: from wp530.webpack.hosteurope.de (wp530.webpack.hosteurope.de [80.237.130.52]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5971CE2; Wed, 21 Jun 2023 10:19:38 -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 1qC1UL-00010x-87; Wed, 21 Jun 2023 19:19:25 +0200 Message-ID: Date: Wed, 21 Jun 2023 19:19:24 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.12.0 Subject: Re: [PATCH] HID: logitech-hidpp: Handle timeout differently from busy Content-Language: en-US, de-DE To: Benjamin Tissoires , Linux regressions mailing list Cc: Mark Lord , Jiri Kosina , Bastien Nocera , linux-input@vger.kernel.org, linux-kernel@vger.kernel.org, "Peter F . Patel-Schneider" , =?UTF-8?Q?Filipe_La=c3=adns?= , Nestor Lopez Casado References: <20230531082428.21763-1-hadess@hadess.net> <15bb2507-a145-7f1b-8e84-58aeb02484b9@leemhuis.info> <42b6e582-f642-7521-135a-449140984211@leemhuis.info> <53903462-2552-b707-3831-cad3ef873b0d@leemhuis.info> From: "Linux regression tracking (Thorsten Leemhuis)" Reply-To: Linux regressions mailing list In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-bounce-key: webpack.hosteurope.de;regressions@leemhuis.info;1687367978;f40bdf3e; X-HE-SMSGID: 1qC1UL-00010x-87 X-Spam-Status: No, score=-2.0 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 On 21.06.23 17:10, Benjamin Tissoires wrote: > On Wed, Jun 21, 2023 at 4:09 PM Linux regression tracking (Thorsten > Leemhuis) wrote: >> >> On 15.06.23 13:24, Mark Lord wrote: >>> On 2023-06-15 03:24 AM, Linux regression tracking (Thorsten Leemhuis) wrote: >>> ... >>>> https://bugzilla.kernel.org/show_bug.cgi?id=217412 >>>> >>>> --- Comment #47 from Mark Blakeney --- >>>> @Juha, kernel 6.3.7 adds the 2 patches intended to fix this bug and the >>>> startup delay is now gone. However, I have had 2 cases over the last 5 >>>> days in which I have been running 6.3.7 where my mouse fails to be >>>> detected at all after startup. I have to pull the Logitech receiver >>>> out/in to get the mouse working. Never seen this issue before so I >>>> suspect the patches are not right. >>>> ``` >>> >>> I too have had that happen with recent kernels, >> >> Ahh, good to know! >> >>> but have not yet put >>> a finger to a specific version or cause. >>> >>> Just toggling the power button on the wireless mouse is enough for >>> it to "re-appear". >>> >>> The 5.4.xx kernels never had this issue. I went straight from those >>> to the 6.3.xx ones, where it does happen sometimes, both with and without >>> the recent "delay" fixes. >> >> From Mark Blakeney it sounded a lot like this is something that started >> with 6.3, but would be good to confirm. Which brings me to the reason >> why I write this mail: >> >> Is anyone still working on this? There was radio silence already for a >> week now. Okay, it's not really urgent, but I guess this should not fall >> through the cracks. > > Sorry for the radio silence. No worries, we all have much to do. But I thought it was time for a quick status inquiry. > I worked on hidpp yesterday and submitted > a new patch for a problem that was overlooked in the previous fixes: > https://lore.kernel.org/linux-input/20230621-logitech-fixes-v1-1-32e70933c0b0@redhat.com/ Great, many thx! > The loop was not properly initializing all its local states, meaning > that when we encountered a "please retry" from the device, we could > never do the actual retry and returned a different error than in the > 6.2 series. > > Would anyone give it a shot? Might be worth mentioning it in the bugzilla ticket, as I sadly can't CC those people here. I'll do this for once (konstantin's bugbot will soon solve this problem...) 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 If I did something stupid, please tell me, as explained on that page.