Message-ID: <ac5d5415-bcc5-4db0-b1bb-6a8d193d43a7@leemhuis.info>
Date: Sat, 13 Jul 2024 14:26:27 +0200
From: Thorsten Leemhuis <regressions@...mhuis.info>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Linux kernel regressions list <regressions@...ts.linux.dev>,
 LKML <linux-kernel@...r.kernel.org>
Subject: Re: Quick extra regression report listing regression which available
 fixes

Quick update:

On 10.07.24 17:15, Thorsten Leemhuis wrote:

> There are two issues that worry me somewhat:
> 
> * A btrfs regression that leads to increased execution time of the
> kswapd0 process and symptoms as if there is not enough memory;
> [...]
> * bpf: build error with CONFIG_WERROR and CONFIG_BPF. 

Fixers for those to were mainlined, yeah. \o/

> There are a few regressions with available fixes, which seem to be
> unlikely to be submitted for mainline inclusion during this week afaics:
> 
> * net: dsa: mt7530-mdio: mt7531 switch on Bananapi-R64 not detected
> (known for 8 weeks already):
> https://lore.kernel.org/lkml/20240516204847.171029-1-linux@fw-web.de/
> https://lore.kernel.org/lkml/f485d1d4f7b34cc2ebf3d60030d1c67b4016af3c.1720107535.git.daniel@makrotopia.org/

No progress here afaics. This BTW is caused by 868ff5f4944aa9 ("net:
dsa: mt7530-mdio: read PHY address of switch from device tree")
[v6.10-rc1], which brings support for MT7530 and is part of a small
patch-set:
https://lore.kernel.org/all/20240418-b4-for-netnext-mt7530-phy-addr-from-dt-and-simplify-core-ops-v3-0-3b5fb249b004@arinc9.com/
Makes me wonder if this could be fixed through a temporary revert; I
argued for that some time ago, but in the end found no support for it:
https://lore.kernel.org/lkml/2cac4cf68304e81abffbd9ff0387ee100323c2b7.camel@redhat.com/

> * drm/qxl: VM graphics often malfunction after boot and sometimes
> shutdowns occur (known for 5 weeks already):
> https://lore.kernel.org/regressions/DS7PR12MB57665F9F4BDF0598D7CC53DD94FF2@DS7PR12MB5766.namprd12.prod.outlook.com/
> https://lore.kernel.org/dri-devel/20240708142208.194361-1-tzimmermann@suse.de/

That issue is caused by b33651a5c98dbd ("drm/qxl: Do not pin buffer
objects for vmap") [v6.10-rc1]; the fix was queued for -next a few days
ago as c537fb4e3d36e7 ("drm/qxl: Pin buffer objects for internal
mappings") [next-20240711]

> There are a few regressions for which fixes are available, but those
> might or might not will be submitted for mainline inclusion during this
> week:
> 
> * ASoC: SOF: Intel: Lenovo Thinkpad X1 Carbon Gen 10 first S2idle fails,
> S0ix not even tried to enter from there on:
> https://github.com/thesofproject/linux/issues/5072
> https://bugzilla.kernel.org/show_bug.cgi?id=218961#c10

This issue is caused by d5263dbbd8af02 ("ASoC: SOF: Intel: don't ignore
IOC interrupts for non-audio transfers"); the fix "ASOC: SOF: Intel:
hda-loader: only wait for HDaudio IOC for IPC4 devices" is in a github
repo for more than a week already:
https://github.com/plbossart/sound/commit/7a8379a0d960ea48ef4ec8e682f0ea46e27e8020

> * pinctrl: rockchip: boot broke on RK3328 / Rock64
> https://lore.kernel.org/all/705544af-d615-4ff0-a54c-72a69140ce6d@eh5.me/
> https://lore.kernel.org/lkml/20240709105428.1176375-1-i@eh5.me/

That fix is still waiting for review.

> * drm/bridge: adv7511: Intermittent EDID failures; the fix after six
> weeks finally made it to a branch that likely will be submitted for
> mainline inclusion later this week.
> https://lore.kernel.org/lkml/20240521011614.496421-1-aford173@gmail.com/
> https://lore.kernel.org/lkml/20240630221931.1650565-1-aford173@gmail.com/

That fix is in the DRM PR airlied sent on Friday morning.

Ciao, Thorsten

Powered by blists - more mailing lists