On Tue, Dec 18, 2018 at 02:46:43AM +, Zhang, Jun wrote:
> Hello, paul
>
> In softirq context, and current is rcu_preempt-10, rcu_gp_kthread_wake don't
> wakeup rcu_preempt.
> Maybe next patch could fix it. Please help review.
>
> diff --git a/kernel/rcu/tree.c b/kernel/rcu/tree.c
> index 0b
i J ; Chang, Junxiao
; Mei, Paul
Subject: RE: rcu_preempt caused oom
Hello, paul
In softirq context, and current is rcu_preempt-10, rcu_gp_kthread_wake don't
wakeup rcu_preempt.
Maybe next patch could fix it. Please help review.
diff --git a/kernel/rcu/tree.c b/kernel/rcu/tree.c index 0b76
, December 18, 2018 07:16
To: paul...@linux.ibm.com
Cc: Zhang, Jun ; Steven Rostedt ;
linux-kernel@vger.kernel.org; j...@joshtriplett.org;
mathieu.desnoy...@efficios.com; jiangshan...@gmail.com; Xiao, Jin
; Zhang, Yanmin ; Bai, Jie A
; Sun, Yi J ; Chang, Junxiao
; Mei, Paul
Subject: RE: rcu_p
On Mon, Dec 17, 2018 at 03:15:42AM +, He, Bo wrote:
> for double confirm the issue is not reproduce after 90 hours, we tried only
> add the enclosed patch on the easy reproduced build, the issue is not
> reproduced after 63 hours in the whole weekend on 16 boards.
> so current conclusion is t
Zhang, Yanmin ; Bai, Jie A
; Sun, Yi J
Subject: Re: rcu_preempt caused oom
On Thu, Dec 13, 2018 at 09:10:12PM -0800, Paul E. McKenney wrote:
> On Fri, Dec 14, 2018 at 02:40:50AM +, He, Bo wrote:
> > another experiment we have done with the enclosed debug patch, and also
> > h
+ panic("hung_task: blocked in
> > rcu_gp_kthread init");
> > + }
> > + }
> > --------------
> > -Origina
> -Original Message-
> From: Paul E. McKenney
> Sent: Friday, December 14, 2018 10:15 AM
> To: He, Bo
> Cc: Zhang, Jun ; Steven Rostedt ;
> linux-kernel@vger.kernel.org; j...@joshtriplett.org;
> math
Jin
; Zhang, Yanmin ; Bai, Jie A
; Sun, Yi J
Subject: Re: rcu_preempt caused oom
On Fri, Dec 14, 2018 at 01:30:04AM +, He, Bo wrote:
> as you mentioned CONFIG_FAST_NO_HZ, do you mean CONFIG_RCU_FAST_NO_HZ? I
> double checked there is no FAST_NO_HZ in .config:
Yes, you are correct,
gt; CONFIG_RCU_EQS_DEBUG=y
>
> -Original Message-
> From: Paul E. McKenney
> Sent: Friday, December 14, 2018 2:12 AM
> To: He, Bo
> Cc: Zhang, Jun ; Steven Rostedt ;
> linux-kernel@vger.kernel.org; j...@joshtriplett.org;
> mathieu.desnoy...@efficios.com; jiangsh
Zhang, Jun ; Steven Rostedt ;
linux-kernel@vger.kernel.org; j...@joshtriplett.org;
mathieu.desnoy...@efficios.com; jiangshan...@gmail.com; Xiao, Jin
; Zhang, Yanmin ; Bai, Jie A
; Sun, Yi J
Subject: Re: rcu_preempt caused oom
On Thu, Dec 13, 2018 at 03:26:08PM +, He, Bo wrote:
> one of the bo
t state: RCU_GP_WAIT_GPS(1) ->state: 0x402
> delta ->gp_activity 4312486108 ->gp_req_activity 4312486108 ->gp_wake_time
> 4312486108 ->gp_wake_seq 0 ->gp_seq -1200 ->gp_seq_needed -1200
> ->gp_flags 0x0
>
> -Original Message-
> From: Pa
gt; ; Sun, Yi J
> Subject: Re: rcu_preempt caused oom
>
> On Thu, Dec 13, 2018 at 02:11:35AM +, Zhang, Jun wrote:
> > Hello, Paul
> >
> > I think the next patch is better.
> > Because ULONG_CMP_GE could cause double write, which has risk that write
> >
c: Steven Rostedt ; linux-kernel@vger.kernel.org;
> j...@joshtriplett.org; mathieu.desnoy...@efficios.com;
> jiangshan...@gmail.com; Zhang, Jun ; Xiao, Jin
> ; Zhang, Yanmin ; Bai, Jie A
> ; Sun, Yi J
> Subject: Re: rcu_preempt caused oom
>
> On Wed, Dec 12, 2018 at 11:13:22P
hang, Yanmin
; Bai, Jie A ; Sun, Yi J
Subject: Re: rcu_preempt caused oom
On Wed, Dec 12, 2018 at 11:13:22PM +, He, Bo wrote:
> I don't see the rcutree.sysrq_rcu parameter in v4.19 kernel, I also checked
> the latest kernel and the latest tag v4.20-rc6, not see the sysrq_rcu.
>
t; Cc: Steven Rostedt ; linux-kernel@vger.kernel.org;
> j...@joshtriplett.org; mathieu.desnoy...@efficios.com;
> jiangshan...@gmail.com; Zhang, Jun ; Xiao, Jin
> ; Zhang, Yanmin ; Bai, Jie A
>
> Subject: Re: rcu_preempt caused oom
>
> On Wed, Dec 12, 2018 at 07:42:24AM -0800
e, Bo
Cc: Steven Rostedt ; linux-kernel@vger.kernel.org;
j...@joshtriplett.org; mathieu.desnoy...@efficios.com; jiangshan...@gmail.com;
Zhang, Jun ; Xiao, Jin ; Zhang, Yanmin
; Bai, Jie A
Subject: Re: rcu_preempt caused oom
On Wed, Dec 12, 2018 at 07:42:24AM -0800, Paul E. McKenney wrote:
>
On Wed, Dec 12, 2018 at 07:42:24AM -0800, Paul E. McKenney wrote:
> On Wed, Dec 12, 2018 at 01:21:33PM +, He, Bo wrote:
> > we reproduce on two boards, but I still not see the show_rcu_gp_kthreads()
> > dump logs, it seems the patch can't catch the scenario.
> > I double confirmed the CONFIG_P
m: Paul E. McKenney
> Sent: Wednesday, December 12, 2018 10:25 AM
> To: He, Bo
> Cc: Steven Rostedt ; linux-kernel@vger.kernel.org;
> j...@joshtriplett.org; mathieu.desnoy...@efficios.com;
> jiangshan...@gmail.com; Zhang, Jun ; Xiao, Jin
> ; Zhang, Yanmin ; Bai, Jie A
>
Sent: Tuesday, December 11, 2018 12:47 PM
> To: He, Bo
> Cc: Steven Rostedt ; linux-kernel@vger.kernel.org;
> j...@joshtriplett.org; mathieu.desnoy...@efficios.com;
> jiangshan...@gmail.com; Zhang, Jun ; Xiao, Jin
> ; Zhang, Yanmin ; Bai, Jie A
>
> Subject: Re: rcu_preem
, Jun ; Xiao, Jin ; Zhang, Yanmin
; Bai, Jie A
Subject: Re: rcu_preempt caused oom
On Mon, Dec 10, 2018 at 04:38:38PM -0800, Paul E. McKenney wrote:
> On Mon, Dec 10, 2018 at 06:56:18AM +, He, Bo wrote:
> > Hi,
> >We have start the test with the CONFIG_PROVE_RCU=y, and
On Mon, Dec 10, 2018 at 04:38:38PM -0800, Paul E. McKenney wrote:
> On Mon, Dec 10, 2018 at 06:56:18AM +, He, Bo wrote:
> > Hi,
> >We have start the test with the CONFIG_PROVE_RCU=y, and also add one 2s
> > to detect the preempt rcu hang, hope we can get more useful logs tomorrow.
> >
On Mon, Dec 10, 2018 at 06:56:18AM +, He, Bo wrote:
> Hi,
>We have start the test with the CONFIG_PROVE_RCU=y, and also add one 2s to
> detect the preempt rcu hang, hope we can get more useful logs tomorrow.
>I also enclosed the config and the debug patches for you review.
I instead
, December 10, 2018 3:56 AM
To: He, Bo
Cc: Steven Rostedt ; linux-kernel@vger.kernel.org;
j...@joshtriplett.org; mathieu.desnoy...@efficios.com; jiangshan...@gmail.com;
Zhang, Jun ; Xiao, Jin ; Zhang, Yanmin
; Bai, Jie A
Subject: Re: rcu_preempt caused oom
On Fri, Dec 07, 2018 at 06:11:31AM -0800, Paul
he rcu_start_this_gp()
> function is trying to start a new grace period. In contrast, this
> rcu_report_qs_rdp() function reports a quiescent state for a currently
> running grace period. In your earlier trace, there was no currently
> running grace period, so rcu_report_qs_rdp() exiting
exiting early is expected
behavior.
Thanx, Paul
> -Original Message-
> From: Paul E. McKenney
> Sent: Friday, December 7, 2018 1:38 AM
> To: He, Bo
> Cc: Steven Rostedt ; linux-kernel@vger.kernel.org;
> j...@joshtriple
> Thanx, Paul
>
> > -Original Message-
> > From: Paul E. McKenney
> > Sent: Wednesday, December 5, 2018 3:50 AM
> > To: He, Bo
> > Cc: Steven Rostedt ;
> > linux-kernel@vger.kernel.org; j...@joshtri
com;
> jiangshan...@gmail.com; Zhang, Jun ; Xiao, Jin
> ; Zhang, Yanmin ; Bai, Jie A
>
> Subject: Re: rcu_preempt caused oom
>
> On Tue, Dec 04, 2018 at 07:50:04AM +, He, Bo wrote:
> > Hi, Paul:
> > the enclosed is the log trigger the 120s hung_task_panic without othe
l.org;
j...@joshtriplett.org; mathieu.desnoy...@efficios.com; jiangshan...@gmail.com;
Zhang, Jun ; Xiao, Jin ; Zhang, Yanmin
; Bai, Jie A
Subject: Re: rcu_preempt caused oom
On Tue, Dec 04, 2018 at 07:50:04AM +, He, Bo wrote:
> Hi, Paul:
> the enclosed is the log trigger the 120s hung_task_pan
. McKenney
> Sent: Monday, December 3, 2018 9:57 PM
> To: He, Bo
> Cc: Steven Rostedt ; linux-kernel@vger.kernel.org;
> j...@joshtriplett.org; mathieu.desnoy...@efficios.com;
> jiangshan...@gmail.com; Zhang, Jun ; Xiao, Jin
> ; Zhang, Yanmin
> Subject: Re: rcu_preempt
Subject: Re: rcu_preempt caused oom
On Mon, Dec 03, 2018 at 07:44:03AM +, He, Bo wrote:
> Thanks, we have run the test for the whole weekend and not reproduce the
> issue, so we confirm the CONFIG_RCU_BOOST can fix the issue.
Very good, that is encouraging. Perhaps I should t
gt; Sent: Saturday, December 1, 2018 12:49 AM
> To: He, Bo
> Cc: Steven Rostedt ; linux-kernel@vger.kernel.org;
> j...@joshtriplett.org; mathieu.desnoy...@efficios.com;
> jiangshan...@gmail.com; Zhang, Jun ; Xiao, Jin
> ; Zhang, Yanmin
> Subject: Re: rcu_preempt caused oom
>
ang, Jun ; Xiao, Jin ; Zhang, Yanmin
Subject: Re: rcu_preempt caused oom
On Fri, Nov 30, 2018 at 03:18:58PM +, He, Bo wrote:
> Here is the kernel cmdline:
Thank you!
> Kernel command line: androidboot.acpio_idx=0
> androidboot.bootloader=efiwrapper-02_03-userdebug_kernelf
, 2018 11:17 PM
> To: Paul E. McKenney
> Cc: He, Bo ; linux-kernel@vger.kernel.org;
> j...@joshtriplett.org; mathieu.desnoy...@efficios.com;
> jiangshan...@gmail.com; Zhang, Jun ; Xiao, Jin
> ; Zhang, Yanmin
> Subject: Re: rcu_preempt caused oom
>
> On Fri, 30 Nov 2018 0
...@joshtriplett.org; mathieu.desnoy...@efficios.com; jiangshan...@gmail.com;
Zhang, Jun ; Xiao, Jin ; Zhang, Yanmin
Subject: Re: rcu_preempt caused oom
On Fri, 30 Nov 2018 06:43:17 -0800
"Paul E. McKenney" wrote:
> Could you please send me your list of kernel boot parameters? Th
On Fri, 30 Nov 2018 06:43:17 -0800
"Paul E. McKenney" wrote:
> Could you please send me your list of kernel boot parameters? They
> usually appear near the start of your console output.
Or just: cat /proc/cmdline
-- Steve
t; -Original Message-
> From: Paul E. McKenney
> Sent: Thursday, November 29, 2018 10:27 PM
> To: He, Bo
> Cc: linux-kernel@vger.kernel.org; j...@joshtriplett.org; rost...@goodmis.org;
> mathieu.desnoy...@efficios.com; jiangshan...@gmail.com; Zhang, Jun
> ; Xiao, Jin ;
On Thu, Nov 29, 2018 at 05:06:47AM -0800, Paul E. McKenney wrote:
> On Thu, Nov 29, 2018 at 08:49:35AM +, He, Bo wrote:
> > Hi,
> > we test on kernel 4.19.0 on android, after run more than 24 Hours
> > monkey stress test, we see OOM on 1/10 2G memory board, the issue is not
> > seen on
On Thu, Nov 29, 2018 at 08:49:35AM +, He, Bo wrote:
> Hi,
> we test on kernel 4.19.0 on android, after run more than 24 Hours
> monkey stress test, we see OOM on 1/10 2G memory board, the issue is not seen
> on the 4.14 kernel.
> we have done some debugs:
> 1. OOM is due to the filp co
Hi,
we test on kernel 4.19.0 on android, after run more than 24 Hours monkey
stress test, we see OOM on 1/10 2G memory board, the issue is not seen on the
4.14 kernel.
we have done some debugs:
1. OOM is due to the filp consume too many memory: 300M vs 2G board.
2. with the 120s hung task
39 matches
Mail list logo
