From nobody Sat Nov 30 07:49:15 2024 Received: from mail-pf1-f179.google.com (mail-pf1-f179.google.com [209.85.210.179]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id D83AC1A2853 for ; Tue, 10 Sep 2024 17:49:09 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.210.179 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1725990552; cv=none; b=GPcJIRrFElR+FKrLzjHU4PBpek+V5p5LPEEUia7mPNQgsQXiPYWlXMEdmJFm/Mo/dgVDjRiMf0m5YhYS6R7YqiJpXvg+jIybzCncwOF1lcM5e3UE1yE1AgZqeMjPnRwDwYMjz+9vMUktPsQBdvPmdpMSqlHIC1jCy/vMGtup2dY= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1725990552; c=relaxed/simple; bh=8r6/Z7cYCZt0C2pPNRt5red4H6C/cN0pEDVkXGwQVxo=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=iPweYGxC9ndp/ReaN8E5RwdM5feq/ym/tibbynqwzfrrhGZtq5Uj4ZRheUB9EAHIRxz5n6jmW7bHMSEGT9mr4JREd+5HxEioAJMCI9YfmV13kWQVX+v61ZX0PJzR+xro7o9ceSUzzKtPHoq7TBFqHMj75LIW7Ojy4vaS6+wuvWI= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=chromium.org; spf=pass smtp.mailfrom=chromium.org; dkim=pass (1024-bit key) header.d=chromium.org header.i=@chromium.org header.b=l61a+BAc; arc=none smtp.client-ip=209.85.210.179 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=chromium.org Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=chromium.org Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=chromium.org header.i=@chromium.org header.b="l61a+BAc" Received: by mail-pf1-f179.google.com with SMTP id d2e1a72fcca58-717934728adso4230848b3a.2 for ; Tue, 10 Sep 2024 10:49:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; t=1725990549; x=1726595349; darn=vger.kernel.org; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=XjTGqVxL/lXZ4Xq5oA9wMyb/w66vC8I8vd+hq2N9dLc=; b=l61a+BAcMfl0ZI8RYMQZQ215fOi2LNlR9Zt0CXTonGtcLzgEhaLy4alvQa/3dLAmfp IKM1QFkrT4W8igkhrMb0dc4vx6z84RJu17nMk6qbNKIX1O27yVbaEBklvQwQrj9T6u45 ins597PHcm3sldWKMslfHbU+1xR+0oZuMuzZ4= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1725990549; x=1726595349; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=XjTGqVxL/lXZ4Xq5oA9wMyb/w66vC8I8vd+hq2N9dLc=; b=bB60G3yNmvelDNvONYbQ2UkInzi7m49GeApjeht0SXF8yQcV+t3J6siwLvRUiabYP2 wrCfzlpC8A071UAUmo+C5Upgkqyo0WhK9mlsqjrmr68qLuR/DCX+Bj1YYUIxuXy0tfx1 YLetf/9vby04yYMr4hjhB69olv+LwLYBB/L6D3vsHZ9iLC1kT2EpLaORYJ4Q37TtooJK g7et2r+zCe+FwHFGmt/AVzIWU/10x1SDFyRbQGQKIKJpeDlvYBehKI3xKmO7UvJsAT5m TAHT9avlMDjeOiTADcLtUYJEj9oNDyQLJh2IUUCCNKdNgJ/OiHhPNm7028jy3NNCRBxv l53w== X-Forwarded-Encrypted: i=1; AJvYcCWpRpHcEFu7d9noHdmdsp+1pJ4iAmuRBEQjbx6t68oDChT2w2FEYrTsWcWaPibjcZbf2yIMhh/ippkKtxM=@vger.kernel.org X-Gm-Message-State: AOJu0YyC8YMgZnxVENDOjRz0a4IvKioXeSF+BmEAP02NSpFRY0PaBdqw ImRwjLby4xnU2AQxqEtQu2orlPSqouPi+h4FQXqjTRe/7RXmOHN+tiPgLwVVew== X-Google-Smtp-Source: AGHT+IH7ewLbjt6vpK16Q9MSvs4t2UHHLsqVCiuJv68f8tihw1AECgjvOqgbtRKJbxklGND7j0FnJg== X-Received: by 2002:a05:6a21:6481:b0:1cf:37bd:b553 with SMTP id adf61e73a8af0-1cf5e1ab920mr1717836637.46.1725990549167; Tue, 10 Sep 2024 10:49:09 -0700 (PDT) Received: from localhost ([2a00:79e0:2e14:7:a9f8:b780:a61c:6acb]) by smtp.gmail.com with UTF8SMTPSA id d9443c01a7336-20710f3229esm51179035ad.268.2024.09.10.10.49.07 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 10 Sep 2024 10:49:08 -0700 (PDT) Date: Tue, 10 Sep 2024 10:49:06 -0700 From: Brian Norris To: Borislav Petkov Cc: Hugues Bruant , stable@vger.kernel.org, regressions@lists.linux.dev, linux-kernel@vger.kernel.org, Fenghua Yu , Reinette Chatre , Tony Luck , Tzung-Bi Shih , Julius Werner , chrome-platform@lists.linux.dev, Jani Nikula , Joonas Lahtinen , Rodrigo Vivi , Tvrtko Ursulin , intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org Subject: [NOT A REGRESSION] firmware: framebuffer-coreboot: duplicate device name "simple-framebuffer.0" Message-ID: References: <20240909080200.GAZt6reI9c98c9S_Xc@fat_crate.local> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20240909080200.GAZt6reI9c98c9S_Xc@fat_crate.local> Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" (Tweaking subject; this indeed isn't related to the regression at all) Hi, On Mon, Sep 09, 2024 at 10:02:00AM +0200, Borislav Petkov wrote: > Looking at your log, the first warn is in framebuffer_coreboot. Some mess= in > the sysfs platform devices registration. >=20 > Adding the relevant people for that: >=20 > Aug 20 20:29:36 luna kernel: sysfs: cannot create duplicate filename '/bu= s/platform/devices/simple-framebuffer.0' > Aug 20 20:29:36 luna kernel: CPU: 5 PID: 571 Comm: (udev-worker) Tainted:= G OE 6.10.6-arch1-1 #1 703d152c24f1971e36f16e505405e456fc9e= 23f8 > Aug 20 20:29:36 luna kernel: Hardware name: Purism Librem 14/Librem 14, B= IOS 4.14-Purism-1 06/18/2021 > Aug 20 20:29:36 luna kernel: Call Trace: > Aug 20 20:29:36 luna kernel: > Aug 20 20:29:36 luna kernel: dump_stack_lvl+0x5d/0x80 > Aug 20 20:29:36 luna kernel: sysfs_warn_dup.cold+0x17/0x23 > Aug 20 20:29:36 luna kernel: sysfs_do_create_link_sd+0xcf/0xe0 > Aug 20 20:29:36 luna kernel: bus_add_device+0x6b/0x130 > Aug 20 20:29:36 luna kernel: device_add+0x3b3/0x870 > Aug 20 20:29:36 luna kernel: platform_device_add+0xed/0x250 > Aug 20 20:29:36 luna kernel: platform_device_register_full+0xbb/0x140 > Aug 20 20:29:36 luna kernel: platform_device_register_resndata.constprop= .0+0x54/0x80 [framebuffer_coreboot a587d2fc243ebaa0205c3badd33442a004d284e0] > Aug 20 20:29:36 luna kernel: framebuffer_probe+0x165/0x1b0 [framebuffer_= coreboot a587d2fc243ebaa0205c3badd33442a004d284e0] > Aug 20 20:29:36 luna kernel: really_probe+0xdb/0x340 > Aug 20 20:29:36 luna kernel: ? pm_runtime_barrier+0x54/0x90 > Aug 20 20:29:36 luna kernel: ? __pfx___driver_attach+0x10/0x10 > Aug 20 20:29:36 luna kernel: __driver_probe_device+0x78/0x110 > Aug 20 20:29:36 luna kernel: driver_probe_device+0x1f/0xa0 > Aug 20 20:29:36 luna kernel: __driver_attach+0xba/0x1c0 > Aug 20 20:29:36 luna kernel: bus_for_each_dev+0x8c/0xe0 > Aug 20 20:29:36 luna kernel: bus_add_driver+0x112/0x1f0 > Aug 20 20:29:36 luna kernel: driver_register+0x72/0xd0 > Aug 20 20:29:36 luna kernel: ? __pfx_framebuffer_driver_init+0x10/0x10 [= framebuffer_coreboot a587d2fc243ebaa0205c3badd33442a004d284e0] > Aug 20 20:29:36 luna kernel: do_one_initcall+0x58/0x310 > Aug 20 20:29:36 luna kernel: do_init_module+0x60/0x220 > Aug 20 20:29:36 luna kernel: init_module_from_file+0x89/0xe0 > Aug 20 20:29:36 luna kernel: idempotent_init_module+0x121/0x320 > Aug 20 20:29:36 luna kernel: __x64_sys_finit_module+0x5e/0xb0 > Aug 20 20:29:36 luna kernel: do_syscall_64+0x82/0x190 > Aug 20 20:29:36 luna kernel: ? __do_sys_newfstatat+0x3c/0x80 > Aug 20 20:29:36 luna kernel: ? syscall_exit_to_user_mode+0x72/0x200 > Aug 20 20:29:36 luna kernel: ? do_syscall_64+0x8e/0x190 > Aug 20 20:29:36 luna kernel: ? do_sys_openat2+0x9c/0xe0 > Aug 20 20:29:36 luna kernel: ? syscall_exit_to_user_mode+0x72/0x200 > Aug 20 20:29:36 luna kernel: ? do_syscall_64+0x8e/0x190 > Aug 20 20:29:36 luna kernel: ? clear_bhb_loop+0x25/0x80 > Aug 20 20:29:36 luna kernel: ? clear_bhb_loop+0x25/0x80 > Aug 20 20:29:36 luna kernel: ? clear_bhb_loop+0x25/0x80 > Aug 20 20:29:36 luna kernel: entry_SYSCALL_64_after_hwframe+0x76/0x7e > Aug 20 20:29:36 luna kernel: RIP: 0033:0x7b1bee2f81fd Looks like it might be a conflict with drivers/firmware/sysfb_simplefb.c, which also uses the "simple-framebuffer" name with a constant ID of 0. It's possible both drivers should be switched to use PLATFORM_DEVID_AUTO? Or at least one of them. Or they should use different base names. I'm not really sure what the best option is (does anyone rely on or care about the device naming?), and I don't actually use this driver. But here's an untested diff to try if you'd really like. If you test it, feel free to submit as a proper patch with my: Signed-off-by: Brian Norris diff --git a/drivers/firmware/google/framebuffer-coreboot.c b/drivers/firmw= are/google/framebuffer-coreboot.c index daadd71d8ddd..3f1b8f664c3f 100644 Reported-by: Brian Norris Reviewed-by: Brian Norris Reviewed-by: Thomas Zimmermann Suggested-by: Julius Werner Suggested-by: Thomas Zimmermann --- a/drivers/firmware/google/framebuffer-coreboot.c +++ b/drivers/firmware/google/framebuffer-coreboot.c @@ -62,7 +62,8 @@ static int framebuffer_probe(struct coreboot_device *dev) return -EINVAL; =20 pdev =3D platform_device_register_resndata(&dev->dev, - "simple-framebuffer", 0, + "simple-framebuffer", + PLATFORM_DEVID_AUTO, &res, 1, &pdata, sizeof(pdata)); if (IS_ERR(pdev))