From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id B4C4AC54E4A for ; Fri, 8 Mar 2024 14:32:16 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=pda/UHIOF4oxySnFzOgoIClejs4hlU0zWseCEHZi1gM=; b=Q6gji1+jCGnxeq fkVhrtHD1as3ExzWzp2AtiBTfZDw+tZfve6Oc/Bl1pmUnh5soOf41yupn7AaXd0uFwB4LsrggYQ9R XiF6LzTfE1NTYU+yiPbgup+arT5doxRJgugb380j27qhx4PQhDy3C2Pg4TI+DzbUQoWzFuvU/eVEF J+15RvQ9WgyN99+pTnVFDHRrU/YO6TtMHXEH6z2as7H/THR0DprMbH0T1eT4uoz3jfIQQ620HTy1v 7tIjHj3Vyza8DPkriWjJOlxv+yGxVRvbb0+erZDdgkuk3GAYqRuTi45Pb/yFoz75jBsSEXfCbV9Uc jPT9jDu2R4aci28CLCtQ==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.97.1 #2 (Red Hat Linux)) id 1ribGV-00000009aPk-1Tl0; Fri, 08 Mar 2024 14:32:03 +0000 Received: from madrid.collaboradmins.com ([46.235.227.194]) by bombadil.infradead.org with esmtps (Exim 4.97.1 #2 (Red Hat Linux)) id 1ribGS-00000009aNS-14da; Fri, 08 Mar 2024 14:32:01 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=collabora.com; s=mail; t=1709908317; bh=wdtYuwWx8ORQMwU47Qj5g2L7s2yOzijaUjNod58MtHc=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=WOV78bzOtFgbkclVF1IHUAojPBKxxPeMbLzSqAkg93ILAG1TPRonZhHVToLUUKerl OBGMcXxyT9ozJdaCYQcLI1absu/0fJ3VL3mG6siOMAWwkbpRvVbJaNwx5xzDIMWj4o t8B8DrXILMB+OgyhVvbTHlFGQL4VOQk/zQXdTpRpaulErM4EcQsj1N6wePREhWHlQk KkqXUCBn8BPY/urVHoe+xqOBr+6+gu9eGWu2ky2tDZOdyQ8GBDPgNMyDn9n4AZGExc lg3p2EFHPey7EMKIJu7kOVhofva1YqpBdgsxYASnZst/+wCQgYrWGyjn/PafgWZ8Mo Dsi/vkQHKarig== Received: from notapiano (zone.collabora.co.uk [167.235.23.81]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (prime256v1) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: nfraprado) by madrid.collaboradmins.com (Postfix) with ESMTPSA id A282D37820C3; Fri, 8 Mar 2024 14:31:54 +0000 (UTC) Date: Fri, 8 Mar 2024 09:31:52 -0500 From: =?utf-8?B?TsOtY29sYXMgRi4gUi4gQS4=?= Prado To: AngeloGioacchino Del Regno , Matthias Brugger , Srinivas Kandagatla , Chen-Yu Tsai Cc: regressions@lists.linux.dev, linux-mediatek@lists.infradead.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, kernel@collabora.com Subject: Re: Probe regression of efuse@11f10000 on mt8183-kukui-jacuzzi-juniper-sku16 running next-20240202 Message-ID: References: <47cdeac1-121d-4b1a-a3ac-e2affc7a2fc3@notapiano> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <47cdeac1-121d-4b1a-a3ac-e2affc7a2fc3@notapiano> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20240308_063200_488512_36C7C137 X-CRM114-Status: GOOD ( 17.60 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Tue, Feb 06, 2024 at 11:11:00AM -0500, N=EDcolas F. R. A. Prado wrote: > Hi, > = > KernelCI has identified a regression [1] on the > mt8183-kukui-jacuzzi-juniper-sku16 machine running on next-20240202 compa= red to > next-20240118: > = > <4>[ 0.627077] sysfs: cannot create duplicate filename '/bus/nvmem/dev= ices/mtk-efuse0' > <4>[ 0.634945] CPU: 7 PID: 1 Comm: swapper/0 Not tainted 6.8.0-rc2-nex= t-20240202 #1 > <4>[ 0.642542] Hardware name: Google juniper sku16 board (DT) > <4>[ 0.648237] Call trace: > <4>[ 0.650917] dump_backtrace+0x94/0xec > <4>[ 0.654815] show_stack+0x18/0x24 > <4>[ 0.658359] dump_stack_lvl+0x48/0x60 > <4>[ 0.662252] dump_stack+0x18/0x24 > <4>[ 0.665796] sysfs_warn_dup+0x64/0x80 > <4>[ 0.669688] sysfs_do_create_link_sd+0xf0/0xf8 > <4>[ 0.674353] sysfs_create_link+0x20/0x40 > <4>[ 0.678500] bus_add_device+0x64/0x104 > <4>[ 0.682475] device_add+0x33c/0x778 > <4>[ 0.686193] nvmem_register+0x514/0x714 > <4>[ 0.690256] devm_nvmem_register+0x1c/0x6c > <4>[ 0.694577] mtk_efuse_probe+0xe8/0x170 > <4>[ 0.698637] platform_probe+0x68/0xd8 > <4>[ 0.702525] really_probe+0x148/0x2b4 > <4>[ 0.706413] __driver_probe_device+0x78/0x12c > <4>[ 0.710990] driver_probe_device+0xdc/0x160 > <4>[ 0.715394] __driver_attach+0x94/0x19c > <4>[ 0.719453] bus_for_each_dev+0x74/0xd4 > <4>[ 0.723512] driver_attach+0x24/0x30 > <4>[ 0.727312] bus_add_driver+0xe4/0x1e8 > <4>[ 0.731284] driver_register+0x60/0x128 > <4>[ 0.735343] __platform_driver_register+0x28/0x34 > <4>[ 0.740265] mtk_efuse_init+0x20/0x5c > <4>[ 0.744155] do_one_initcall+0x6c/0x1b0 > <4>[ 0.748214] kernel_init_freeable+0x1c8/0x290 > <4>[ 0.752795] kernel_init+0x20/0x1dc > <4>[ 0.756512] ret_from_fork+0x10/0x20 > <4>[ 0.760353] mediatek,efuse: probe of 11f10000.efuse failed with err= or -17 > = > This efuse probe failure causes the probe failure of other components that > depend on it, including the display pipeline: > = > /soc/dsi-phy@11e50000 > /soc/dsi@14014000 > /soc/efuse@11f10000 > /soc/i2c@11008000/anx7625@58 > /soc/i2c@11008000/anx7625@58/aux-bus/panel > /soc/thermal@1100b000 > = > There is a series already addressing the issue [2]. The first two patches= have > been merged into the mediatek tree, but that tree isn't currently being > integrated into linux-next. Besides that, patch 3 hasn't been merged into= the > nvmem tree yet, and it is required in order to solve the issue. > = > I'm sending this regression report so we can properly track the regressio= n while > the fixes don't land on linux-next. > = > Thanks, > N=EDcolas > = > [1] https://linux.kernelci.org/test/plan/id/65bd63c3f12d8a95e200a225/ > [2] https://lore.kernel.org/linux-mediatek/20240130095656.3712469-1-wenst= @chromium.org/ > = > #regzbot introduced next-20240118..next-20240202 Not sure why this got filed by regzbot under the mainline tab rather than n= ext. Maybe it was the missing collon? Let me try again: #regzbot introduced: next-20240118..next-20240202 In any case, the fix has already made it to linux-next, so this should clos= e the regression: #regzbot fix: nvmem: mtk-efuse: Drop NVMEM device name Thanks, N=EDcolas _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel