lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <df6fcd73-fe0a-42fc-97ce-7e458c340553@leemhuis.info>
Date: Fri, 6 Feb 2026 15:55:31 +0100
From: Thorsten Leemhuis <regressions@...mhuis.info>
To: Denis Gessert <denisgessert@...il.com>,
 "angelogioacchino.delregno@...labora.com"
 <angelogioacchino.delregno@...labora.com>
Cc: Evans Jahja <evansjahja13@...il.com>,
 Matthias Brugger <matthias.bgg@...il.com>,
 linux-mediatek@...ts.infradead.org, linux-kernel@...r.kernel.org,
 regressions@...ts.linux.dev, Otto Pflüger
 <otto.pflueger@...cue.de>
Subject: Re: [REGRESSION] mt8183-kukui: dts: changes in dts caused display to
 no longer initialize - Was: Re: mt8183-kukui: drm/mediatek: dts: Invalid
 display hw pipeline when probing mediatek-drm

On 2/6/26 12:33, Denis Gessert wrote:
> 
> I found this email chain while troubleshooting why my Levovo Duet
> (with the MT8183 chip) would not boot using any 6.18.* kernel.
> 
> I can confirm that on my device the current stable 6.18.8 does not
> boot unless I revert the commit
> 
> commit e72d63fa0563f8a6e98c10fed3a9ce74dc0536e6 (HEAD)
> Author: AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>
> Date:   Thu Jul 24 10:39:08 2025 +0200
> 
>     arm64: dts: mediatek: mt8183: Migrate to display controller OF graph
> 
> mentioned below. With the reverted commit the device boots as intended.

There is a fix for it from Otto here that I guess should help
https://lore.kernel.org/lkml/20260106-mt8183-display-graph-v2-1-e7e56054eef5@abscue.de/

Side note: lacks a stable tag and maybe should have been merged this
cycle instead of the next. But given that 6.19 is immanent it might be
good if this could be backported to 6.19.y once it landed in mainline.

> PS: Apologies for the potential double-mail. 
No worries, happens.

Ciao, Thortsten

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ