Received: by 2002:a05:6358:16cc:b0:ea:6187:17c9 with SMTP id r12csp7535873rwl; Tue, 10 Jan 2023 02:01:03 -0800 (PST) X-Google-Smtp-Source: AMrXdXuxogAYSTqzdVe0S9hEHLgqiTsvYCqbu3M6vT67EGY9yEfGy+HYJ1hOOJZ+jJc0ShTnQGso X-Received: by 2002:a17:902:bc81:b0:192:bb38:c412 with SMTP id bb1-20020a170902bc8100b00192bb38c412mr34105027plb.44.1673344862872; Tue, 10 Jan 2023 02:01:02 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1673344862; cv=none; d=google.com; s=arc-20160816; b=eHXPTljVTT7wYEdkwZdFXUXq9mKt2Gs+AztCIN+P80JNzeDoIiBEAdy0ofxvA8uABm 7pMpXitYMlEXjpV+G+EI9qoECOjKVKw0Fq2zTiQLMYgSY4aQ9rdBmz/dc1vGQRl31n1T wTdd/3da4K5JPrZV0Iam/LbVjsxxmMN0xgPqolhqBS/L6RCiPAipnnB9MA5BDsxFiCOw +FccmIAl6FOMWoIlJ3nXbRXXXKPCCkzXoMjUbbRWSObFOB4hZxzmavpxBlHsSQi0NSVP duPj98Ffx8101arnIZB8JEBcARTQQ/MCN3/5aC3pExCVE738gFWUWDJW8hzwJn1Wsmzf HgIw== 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:from :references:cc:to:content-language:subject:reply-to:user-agent :mime-version:date:message-id; bh=AneCvXQ4hxCGv5KM/B3xnusoAhXGxO1aFQGUEkf5EIQ=; b=dj9eGbJvSbx2l5WJteP+W83JCp+dcjeIxOYrciRhbCnNYLaDFtRmmo9QH9pdEYd6cO IxX0QRr2FFpgzDd9SpNHngOypFS4SlxOfCX/JiezC69ByWucS5R327t+05K2/WvN3VdT hX/yndtrCNKTFvpuO7aUiEUpQoekD+LByfGHjVMeNVYxXHae3V6oG1vD9xWARjjRnzAB n+VJ8cWuUtE7I3T2M0HW9KWSt0ZC70NicEn0oLXlylslGtYvFgtgulwwrvSjqw3+UxLt 5/z1adAOTONJaYyMZqDxcuFlbF8N6vffa0uGAxxLGRi4g4Q24ntl1ytK2VLMqGsfuloz q0Jw== 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 a11-20020a170902eccb00b0019246b52629si11663968plh.604.2023.01.10.02.00.56; Tue, 10 Jan 2023 02:01:02 -0800 (PST) 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 S238103AbjAJJds (ORCPT + 53 others); Tue, 10 Jan 2023 04:33:48 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45212 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238234AbjAJJdj (ORCPT ); Tue, 10 Jan 2023 04:33:39 -0500 Received: from wp530.webpack.hosteurope.de (wp530.webpack.hosteurope.de [80.237.130.52]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4277713D72 for ; Tue, 10 Jan 2023 01:33:37 -0800 (PST) Received: from [2a02:8108:963f:de38:eca4:7d19:f9a2:22c5]; authenticated by wp530.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) id 1pFB0e-0002ya-EF; Tue, 10 Jan 2023 10:33:32 +0100 Message-ID: <169efa7b-917f-34b8-9edf-1b8c6345c277@leemhuis.info> Date: Tue, 10 Jan 2023 10:33:31 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.6.0 Reply-To: Linux regressions mailing list Subject: =?UTF-8?Q?Re=3a_=5bregression=5d_Bug=c2=a0216818_-_The_microphone_m?= =?UTF-8?Q?ute_led_not_working_after_linux_6?= Content-Language: en-US, de-DE To: Jaroslav Kysela , Pierre-louis Bossart Cc: sonic82003@gmail.com, plum , "regressions@lists.linux.dev" , alsa-devel@alsa-project.org, LKML , Hans de Goede , Takashi Iwai References: <572159b3-a1a4-8735-d435-ea574c07851f@redhat.com> <9f0e95d1-5057-93f0-ad9e-985eaeed0226@leemhuis.info> <7ab2be50-11c6-f79f-e3f5-a5dc5ec41708@perex.cz> From: "Linux kernel regression tracking (Thorsten Leemhuis)" In-Reply-To: <7ab2be50-11c6-f79f-e3f5-a5dc5ec41708@perex.cz> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-bounce-key: webpack.hosteurope.de;regressions@leemhuis.info;1673343217;47d452a4; X-HE-SMSGID: 1pFB0e-0002ya-EF X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,NICE_REPLY_A, RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS 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 [now that the holiday season is over I'd like to get this rolling again] On 19.12.22 18:01, Jaroslav Kysela wrote: > On 19. 12. 22 11:27, Thorsten Leemhuis wrote: >> On 19.12.22 11:00, Hans de Goede wrote: >>> On 12/19/22 10:17, Thorsten Leemhuis wrote: >>>> I noticed a regression report in bugzilla.kernel.org. As many (most?) >>>> kernel developer don't keep an eye on it, I decided to forward it by >>>> mail. Quoting from https://bugzilla.kernel.org/show_bug.cgi?id=216818 : >>>> >>>>>   sonic82003@gmail.com 2022-12-18 08:52:32 UTC >>>>> >>>>> The mic mute led of my ThinkPad X1 Carbon Gen 9 doesn't work >>>>> anymore after updating linux to version 6. >>>>> I can still turn it on by  running >>>>> >>>>> echo 1 > /sys/class/leds/platform::micmute/brightness >>>>> >>>>> With linux-lts it still works fine. >>>> >>>> See the ticket for more details. >>>> >>>> Note, I found a similar report that (despite my attempts to prevent >>>> things like this from happening) fell through the cracks here: >>>> https://bugzilla.kernel.org/show_bug.cgi?id=216355 >>>> >>>>>   plum 2022-08-13 02:11:01 UTC >>>>> >>>>> I upgrade to kernel 5.19.1 but found my thinkpad x1 carbon 2021's >>>>> mute led stop working. >>>>> >>>>> Function is okay but LED won't light up. >>>>> >>>>> Back to kernel 5.18 and it's normal and working again. >>>>> >>>>> Fedora 36 64 bit >>>>> Gnome-shell 42 >>>> >>>>  From a quick research it looks to me like this is an issue for the >>>> sounds maintainers, as the LED itself apparently works. If that is >>>> something for the platform people instead please speak up. >>> >>> Thanks for bringing this up, we recently hit this in Fedora too >>> and we have a fix/workaround there. Let me copy and paste what >>> I just added to bko216355 : >> >> Many thx for sharing these details, really helpful. >> >>> This is caused by a behavior change of the kernel code controlling >>> the LED to only turn on the LED when all inputs, including e.g. the >>> jack mic input are turned off in the alsa-mixer settings. >>> >>> But most userspace code only turns the mic which it is actually using >>> on/off when you hit the mic-mute hotkey. >>> >>> Also see: https://bugzilla.redhat.com/show_bug.cgi?id=2134824 >> >> Ahh, lot's of helpful information and even a bisect there. :-D >> >> #regzbot introduced: 9b014266ef8ad0159 > > It's not a regression from my view. Please elaborate. Afaics it is one, as something that used to work stopped working with a newer kernel version; it doesn't matter it worked by accident beforehand or can be fixed by updating userland, as Linus explained multiple times in the past: https://docs.kernel.org/process/handling-regressions.html#quotes-from-linus-about-regression But maybe I'm missing something. >>> Which is the same bug. >>> >>> There is a set of fixes available in the form of an alsa-ucm update >>> which tells the kernel to ignore the state of the jack mic input >>> restoring the old behavior: >>> >>> https://git.alsa-project.org/?p=alsa-ucm-conf.git;a=commitdiff;h=79a8ec44d3dcf097f4a4492c506cbcf338324175 >>> https://git.alsa-project.org/?p=alsa-ucm-conf.git;a=commitdiff;h=9ce9ddb4a84fb467602b716575ea1d8f2bab0c39 >> >> Hmmm, that's nice, but well, by Linux' "no regressions rule" the issue >> is caused by kernel change and thus must be fixed in the kernel, e.g. >> without forcing users to update anything in userspace. >> >> Jaroslav, are there any plans to do that? > > I wrote all relevant information to > https://bugzilla.redhat.com/show_bug.cgi?id=2134824 . The problem exists > from the initial microphone LED support in the SOF HDA driver, because > two drivers control the microphone LED simultaneously (sof-hda-dsp + > hda-intel). My recent update just made this thing more visible - the LED > state may be updated wrongly in all previous kernels. Original behavior: > last write wins. New behavior: all off = LED ON. The UCM fix (update the > default kernel runtime configuration from the user space) is sufficient > in my eyes for now because even the use case when the microphone LED > follows the state when all internal inputs are turned off makes sense. > > I think that the sof-hda-dsp driver maintainer may decide to change the > default settings in the HDA driver when the digital microphone is > detected. Adding Pierre-Louis to the chain. Pierre-Louis? 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. #regzbot poke