From: "Nícolas F. R. A. Prado" <nfraprado@collabora.com> To: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>, Matthias Brugger <matthias.bgg@gmail.com>, Srinivas Kandagatla <srinivas.kandagatla@linaro.org>, Chen-Yu Tsai <wenst@chromium.org> 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: Probe regression of efuse@11f10000 on mt8183-kukui-jacuzzi-juniper-sku16 running next-20240202 Date: Tue, 6 Feb 2024 11:10:56 -0500 [thread overview] Message-ID: <47cdeac1-121d-4b1a-a3ac-e2affc7a2fc3@notapiano> (raw) Hi, KernelCI has identified a regression [1] on the mt8183-kukui-jacuzzi-juniper-sku16 machine running on next-20240202 compared to next-20240118: <4>[ 0.627077] sysfs: cannot create duplicate filename '/bus/nvmem/devices/mtk-efuse0' <4>[ 0.634945] CPU: 7 PID: 1 Comm: swapper/0 Not tainted 6.8.0-rc2-next-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 error -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 regression while the fixes don't land on linux-next. Thanks, Nícolas [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
WARNING: multiple messages have this Message-ID (diff)
From: "Nícolas F. R. A. Prado" <nfraprado@collabora.com> To: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>, Matthias Brugger <matthias.bgg@gmail.com>, Srinivas Kandagatla <srinivas.kandagatla@linaro.org>, Chen-Yu Tsai <wenst@chromium.org> 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: Probe regression of efuse@11f10000 on mt8183-kukui-jacuzzi-juniper-sku16 running next-20240202 Date: Tue, 6 Feb 2024 11:10:56 -0500 [thread overview] Message-ID: <47cdeac1-121d-4b1a-a3ac-e2affc7a2fc3@notapiano> (raw) Hi, KernelCI has identified a regression [1] on the mt8183-kukui-jacuzzi-juniper-sku16 machine running on next-20240202 compared to next-20240118: <4>[ 0.627077] sysfs: cannot create duplicate filename '/bus/nvmem/devices/mtk-efuse0' <4>[ 0.634945] CPU: 7 PID: 1 Comm: swapper/0 Not tainted 6.8.0-rc2-next-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 error -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 regression while the fixes don't land on linux-next. Thanks, Nícolas [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 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2024-02-06 16:11 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-06 16:10 Nícolas F. R. A. Prado [this message] 2024-02-06 16:10 ` Probe regression of efuse@11f10000 on mt8183-kukui-jacuzzi-juniper-sku16 running next-20240202 Nícolas F. R. A. Prado 2024-03-08 14:31 ` Nícolas F. R. A. Prado 2024-03-08 14:31 ` Nícolas F. R. A. Prado 2024-03-09 14:06 ` Thorsten Leemhuis 2024-03-09 14:06 ` Thorsten Leemhuis 2024-03-11 13:54 ` Nícolas F. R. A. Prado 2024-03-11 13:54 ` Nícolas F. R. A. Prado
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=47cdeac1-121d-4b1a-a3ac-e2affc7a2fc3@notapiano \ --to=nfraprado@collabora.com \ --cc=angelogioacchino.delregno@collabora.com \ --cc=kernel@collabora.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mediatek@lists.infradead.org \ --cc=matthias.bgg@gmail.com \ --cc=regressions@lists.linux.dev \ --cc=srinivas.kandagatla@linaro.org \ --cc=wenst@chromium.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.