[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2a3fa097-8ba0-5b0e-f506-779fee5b8fef@sdinet.de>
Date: Wed, 14 Jun 2023 15:45:41 +0200 (CEST)
From: Sven-Haegar Koch <haegar@...net.de>
To: Luiz Capitulino <luizcap@...zon.com>
cc: Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
"Bhatnagar, Rishabh" <risbhat@...zon.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"sashal@...nel.org" <sashal@...nel.org>, abuehaze@...zon.com,
"stable@...r.kernel.org" <stable@...r.kernel.org>
Subject: Re: Observing RCU stalls in kernel 5.4/5.10/5.15/6.1 stable trees
On Wed, 14 Jun 2023, Luiz Capitulino wrote:
> On 2023-06-14 05:20, Sebastian Andrzej Siewior wrote:
>
> > On 2023-06-14 11:14:49 [+0200], gregkh@...uxfoundation.org wrote:
> > > Oops, missed this.
> > >
> > > Yes, there might be, can you do 'git bisect' and track down the patch
> > > that fixed this?
> >
> > There was a report of a lockup during boot in VMs yesterday. If I
> > remember correctly this still exists and might be related to this
> > report. I'm going to have a look.
>
> Thanks, Sebastian. Do you have a link for the discussion?
May be this, talking about the same commit as cause as this thread:
Subject: Re: [PATCH] timekeeping: Align tick_sched_timer() with the HZ
tick. -- regression report
https://lore.kernel.org/lkml/5a56290d-806e-b9a5-f37c-f21958b5a8c0@grsecurity.net/
May not have been the best idea to respond with such big analysis to a 3
months old dead thread, gets lost extremely easy.
c'ya
sven-haegar
--
Three may keep a secret, if two of them are dead.
- Ben F.
Powered by blists - more mailing lists