From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from stravinsky.debian.org (stravinsky.debian.org [82.195.75.108]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 8A2D934DB56; Sat, 20 Jun 2026 21:53:06 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=82.195.75.108 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1781992389; cv=none; b=jIZZOwco/X/oeLoSHFLeq/EjDmd/RSmHwtrFtY+77d4dLTffR9njHBmVZh5RMYgtMAfEjQ1t5WVVkJ/9t8CWqy8ZGFM1PtS0ijgk7OXgez9aZC3AdtDd1aOzpLSkQAAaphtbLQm07CG/0A3N5BXpdEG/fH6vvzRcJeNhQbRA4cQ= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1781992389; c=relaxed/simple; bh=bVXlPmPwJ0rPp3wYMWuA3fygPjTET6mnR8d+OxryGTY=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=obeQSpx5/S9TM/S0GSx3gWW0Zng44WWg8qp+sj20zGvLAtbaQJjJ5FkIcweiKqelOxXk+eAucx/gskca5TpPhWCKy9ZMXSZM0ogGsUXh69AXEAItnBaI/eIwmmOHOnQtIukX/S8j24cojb263LM++9acgtnUHg1kBvErAoxjVnI= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=debian.org; spf=pass smtp.mailfrom=debian.org; dkim=pass (2048-bit key) header.d=debian.org header.i=@debian.org header.b=ngwkL0ab; arc=none smtp.client-ip=82.195.75.108 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=debian.org Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=debian.org Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=debian.org header.i=@debian.org header.b="ngwkL0ab" DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=debian.org; s=smtpauto.stravinsky; h=X-Debian-User:In-Reply-To:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description; bh=+Pc3ozWWUVFYeoggo3AZJrZF+AfDxlh/3NZlYKMxKuY=; b=ngwkL0abNyshdqa5KF8fyzVtAX iS4vGoyqqWJCeQ2cr9XRSaS/H+5AOnlPIznnhbQKA1N7mrBbM80m9PrNPjc8u6YKENI+BVbBBFaTk ysCLuZmC5B+dgk3gVLHtfHu4It3EofCYpc1nYqhehPvZgsDh4WOgUkuxqAZscgnILEmxbcHkEc+IL fXqa33+LFrMwdhc3UXX7uO/o3SYaiSuurcHbBbrL5xwOVunlin9ox7hqizOp92PYBEvcNK2Z9zZ6h 7qJ1SvlbLiiA3bDtMGXqFwpVPIdHCur7Lsqu8cAfpEBoYZs7Wa2UGqZEbMohJ21sTQiZkNYByJMrR Ga2Ncfig==; Received: from authenticated-user by stravinsky.debian.org with esmtpsa (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.96) (envelope-from ) id 1wb3cX-00HEO5-39; Sat, 20 Jun 2026 21:52:59 +0000 Received: by eldamar.lan (Postfix, from userid 1000) id D3BB4BE2EE7; Sat, 20 Jun 2026 23:52:56 +0200 (CEST) Date: Sat, 20 Jun 2026 23:52:56 +0200 From: Salvatore Bonaccorso To: Jaak Ristioja , Mario Limonciello , Dianne Skoll , Chris Park , Matthew Stewart , Dan Wheeler , Alex Deucher , Greg Kroah-Hartman , Harry Wentland , Leo Li , Rodrigo Siqueira , Christian =?iso-8859-1?Q?K=F6nig?= , David Airlie , Simona Vetter Cc: 1139950@bugs.debian.org, regressions@lists.linux.dev, stable@vger.kernel.org, amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org Subject: Re: [resend] [regression] amdgpu carrizo: no display signal after modeset Message-ID: References: <9fba2020-24d1-4235-9869-319d4aab3a4c@ristioja.ee> <178198613176.3658222.16247101620976737948@eldamar.lan> Precedence: bulk X-Mailing-List: regressions@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <178198613176.3658222.16247101620976737948@eldamar.lan> X-Debian-User: carnil Hi Resending because of typ in mailing list address. On Sat, Jun 20, 2026 at 10:11:25PM +0200, Salvatore Bonaccorso wrote: > Control: forwarded -1 https://lore.kernel.org/regressions/178198613176.3658222.16247101620976737948@eldamar.lan > > Hi > > Jaak Ristioja reported the following issue in Debian at > https://bugs.debian.org/1139950 . Part of the original report contains > Debian specific version information, but Jaak did as well a bisecion > for the regression see below: > > On Sun, Jun 14, 2026 at 02:27:01AM +0300, Jaak Ristioja wrote: > > Package: linux-modules-7.0.10+deb13-amd64 > > Version: 7.0.10-1~bpo13+1 > > > > Hi, > > > > Upgrading (after a long while) Debian Trixie installations on two different > > HP EliteDesk 705 G4 DM 35W computers with AMD PRO A10-9700E R7 (carrizo) > > resulted in both machines blanking the screen right after kernel modesetting > > activates via amdgpu, with the monitor reporting "no signal". There are no > > other symptoms besides losing the display as the system continues to run and > > is accessible using keyboard and network. > > > > Bug first discovered with stable kernel linux-image-6.12.90+deb13.1-amd64 > > (6.12.90-2) and the one from trixie-backports. The device is connected to a > > monitor using a DisplayPort to HDMI adapter. The bug occurs regardless of > > which if the two available physical DisplayPort ports to use. > > > > I don't remember this being an issue some months ago, so I tried to > > reproduce this booting the Debian 13.1.0 and 13.4.0 install DVD images and > > using the kernel modules/firmware therein: > > > > 13.1.0 installer: > > firmware-amd-graphics_20250410-2 > > linux-image-6.12.43+deb13-amd64_6.12.43-1 > > 13.4.0 installer: > > firmware-amd-graphics 20250410-2 > > linux-image-6.12.73+deb13-amd64_6.12.73-1 > > > > I essentially unpacked the two *.deb files manually, depmod -a; modprobe drm > > debug=0x1ff; modprobe amdgpu. > > > > I observed the bug reproduce using the 13.4.0 installer, but not on the > > 13.1.0 installer, meaning this is a regression somewhere between kernel > > versions 6.12.43-1 and 6.12.73-1. > > The reporter did a bisection and found as offending commit: > > drm/amd/display: Bump the HDMI clock to 340MHz > > commit fee50077656d8a58011f13bca48f743d1b6d6015 upstream. > > [Why] > DP-HDMI dongles can execeed bandwidth requirements on high resolution > monitors. This can lead to pruning the high resolution modes. > > HDMI 1.3 bumped the clock to 340MHz, but display code never matched it. > > [How] > Set default to (DVI) 165MHz. Once HDMI display is identified update > to 340MHz. > > Reported-by: Dianne Skoll > Closes: https://gitlab.freedesktop.org/drm/amd/-/issues/4780 > Reviewed-by: Chris Park > Signed-off-by: Mario Limonciello > Signed-off-by: Matthew Stewart > Tested-by: Dan Wheeler > Signed-off-by: Alex Deucher > (cherry picked from commit ac1e65d8ade46c09fb184579b81acadf36dcb91e) > Cc: stable@vger.kernel.org > Signed-off-by: Greg Kroah-Hartman > > Does this ring any bell? > > #regzbot introduced: ae5b1d291c814a2884c3d54a56e83bc99052b1eb > #regzbot link: https://bugs.debian.org/1139950 > > Regards, > Salvatore