[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YO56HTE3k95JLeje@kroah.com>
Date: Wed, 14 Jul 2021 07:46:05 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Holger Kiehl <Holger.Kiehl@....de>
Cc: linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
akpm@...ux-foundation.org, linux@...ck-us.net, shuah@...nel.org,
patches@...nelci.org, lkft-triage@...ts.linaro.org, pavel@...x.de,
jonathanh@...dia.com, f.fainelli@...il.com, stable@...r.kernel.org
Subject: Re: [PATCH 5.13 000/800] 5.13.2-rc1 review
On Wed, Jul 14, 2021 at 05:39:43AM +0000, Holger Kiehl wrote:
> Hello,
>
> On Mon, 12 Jul 2021, Greg Kroah-Hartman wrote:
>
> > This is the start of the stable review cycle for the 5.13.2 release.
> > There are 800 patches in this series, all will be posted as a response
> > to this one. If anyone has any issues with these being applied, please
> > let me know.
> >
> > Responses should be made by Wed, 14 Jul 2021 06:02:46 +0000.
> > Anything received after that time might be too late.
> >
> With this my system no longer boots:
>
> [ OK ] Reached target Swap.
> [ 75.213852] NMI watchdog: Watchdog detected hard LOCKUP on cpu 0
> [ 75.213926] NMI watchdog: Watchdog detected hard LOCKUP on cpu 2
> [ 75.213962] NMI watchdog: Watchdog detected hard LOCKUP on cpu 4
> [FAILED] Failed to start Wait for udev To Complete Device Initialization.
> See 'systemctl status systemd-udev-settle.service' for details.
> Starting Activation of DM RAID sets...
> [ ] (1 of 2) A start job is running for Activation of DM RAID sets (..min ..s / no limit)
> [ ] (2 of 2) A start job is running for Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling (..min ..s / no limit)
>
> System is a Fedora 34 with all updates applied. Two other similar
> systems with AMD CPUs (Ryzen 4750G + 3400G) this does not happen
> and boots fine. The system where it does not boot has an Intel
> Xeon E3-1285L v4 CPU. All of them use a dm_crypt root filesystem.
>
> Any idea which patch I should drop to see if it boots again. I already
> dropped
>
> [PATCH 5.13 743/800] ASoC: Intel: sof_sdw: add quirk support for Brya and BT-offload
>
> and I just see that this one should also be dropped:
>
> [PATCH 5.13 768/800] hugetlb: address ref count racing in prep_compound_gigantic_page
>
> Will still need to test this.
Can you run 'git bisect' to see what commit causes the problem?
thanks,
greg k-h
Powered by blists - more mailing lists