x-kernel@vger.kernel.org
> > Subject: Re: kdump always hangs in rcu_barrier() -> wait_for_completion()
> >
> > On Thu, Nov 26, 2020 at 10:59:19PM +, Dexuan Cui wrote:
> > > > From: Paul E. McKenney
> > > > Sent: Thursday, November 26, 2020 1:42 PM
> From: Paul E. McKenney
> Sent: Thursday, November 26, 2020 3:55 PM
> To: Dexuan Cui
> Cc: boqun.f...@gmail.com; Ingo Molnar ;
> r...@vger.kernel.org; vkuznets ; Michael Kelley
> ; linux-kernel@vger.kernel.org
> Subject: Re: kdump always hangs in rcu_barrier() -> wait_
On Thu, Nov 26, 2020 at 10:59:19PM +, Dexuan Cui wrote:
> > From: Paul E. McKenney
> > Sent: Thursday, November 26, 2020 1:42 PM
> >
> > > > Another possibility is that rcu_state.gp_kthread is non-NULL, but that
> > > > something else is preventing RCU grace periods from completing, but in
>
> From: Paul E. McKenney
> Sent: Thursday, November 26, 2020 1:42 PM
>
> > > Another possibility is that rcu_state.gp_kthread is non-NULL, but that
> > > something else is preventing RCU grace periods from completing, but in
> >
> > It looks like somehow the scheduling is not working here: in rcu
On Thu, Nov 26, 2020 at 09:25:28PM +, Dexuan Cui wrote:
> > From: Paul E. McKenney
> > Sent: Thursday, November 26, 2020 7:47 AM
> > ...
> > The rcu_segcblist_n_cbs() function returns non-zero because something
> > invoked call_rcu() some time previously. The ftrace facility (or just
> > a p
> From: Paul E. McKenney
> Sent: Thursday, November 26, 2020 7:47 AM
> ...
> The rcu_segcblist_n_cbs() function returns non-zero because something
> invoked call_rcu() some time previously. The ftrace facility (or just
> a printk) should help you work out where that call_rcu() is located.
call_
On Wed, Nov 25, 2020 at 04:56:33AM +, Dexuan Cui wrote:
> Hi,
> I happened to hit a kdump hang issue in a Linux VM running on some
> Hyper-V host. Please see the attached log: the kdump kernel always hangs,
> even if I configure only 1 virtual CPU to the VM.
>
> I firstly hit the issue in RHEL
Hi,
I happened to hit a kdump hang issue in a Linux VM running on some
Hyper-V host. Please see the attached log: the kdump kernel always hangs,
even if I configure only 1 virtual CPU to the VM.
I firstly hit the issue in RHEL 8.3's 4.18.x kernel, but later I found that
the latest upstream v5.10-
8 matches
Mail list logo
