public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Peter Zijlstra <peterz@infradead.org>,
	Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: [PATCH 0/5] [GIT PULL] updates for tip/tracing/ftrace
Date: Fri, 20 Mar 2009 10:43:31 -0700	[thread overview]
Message-ID: <20090320174331.GH6698@linux.vnet.ibm.com> (raw)
In-Reply-To: <alpine.DEB.2.00.0903191309170.16987@gandalf.stny.rr.com>

On Thu, Mar 19, 2009 at 01:21:47PM -0400, Steven Rostedt wrote:
> 
> I'm still not able to reproduce, but...
> 
> On Thu, 19 Mar 2009, Ingo Molnar wrote:
> 
> > * Ingo Molnar <mingo@elte.hu> wrote:
> > 
> > > these latest ftrace changes caused a lockup on a -tip testsystem:
> > 
> > Note, even with Rusty's offstack-cpumask fix applied (in latest 
> > -tip), i can reproduce a lockup:
> > 

[ . . . ]

> This looks like it is RCU/stop_machine related. The CPU is stuck in
> in stop_machine? I see that rcu_torture is running. Does this go away if 
> you turn off rcu_torture?

Grasping at straws...  Does Lai's rcu_barrier() fix help?

							Thanx, Paul

> -- Steve
> 
> > [   18.620342]  [<ffffffff80294a29>] ? run_workqueue+0x1a0/0x2e2
> > [   18.620342]  [<ffffffff802949d6>] ? run_workqueue+0x14d/0x2e2
> > [   18.620342]  [<ffffffff802ceb5d>] ? stop_cpu+0x0/0x1d1
> > [   18.620342]  [<ffffffff826b4140>] ? early_idt_handler+0x0/0x73
> > [   18.620342]  [<ffffffff80295d1b>] ? worker_thread+0x138/0x14c
> > [   18.620342]  [<ffffffff80299e63>] ? autoremove_wake_function+0x0/0x4f
> > [   18.620342]  [<ffffffff80295be3>] ? worker_thread+0x0/0x14c
> > [   18.620342]  [<ffffffff80299d20>] ? kthread+0x60/0xa0
> > [   18.620342]  [<ffffffff8021606a>] ? child_rip+0xa/0x20
> > [   18.620342]  [<ffffffff8026fd4b>] ? finish_task_switch+0x56/0x180
> > [   18.620342]  [<ffffffff80215a10>] ? restore_args+0x0/0x30
> > [   18.620342]  [<ffffffff80299cc0>] ? kthread+0x0/0xa0
> > [   18.620342]  [<ffffffff80216060>] ? child_rip+0x0/0x20
> > [   64.758749] INFO: RCU detected CPU 0 stall (t=4294710313/40000 jiffies)
> > [   64.758749] Pid: 858, comm: kstop/0 Not tainted 2.6.29-rc8-tip-02638-g1c002f5-dirty #3067
> > 
> > (the hang is real - it lasted overnight without the system ever 
> > managing to boot up.)
> > 
> > Config (note, it's different from the config i sent last) and full 
> > bootlog attached.
> > 
> > 	Ingo
> > 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

  reply	other threads:[~2009-03-20 17:43 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-18  3:14 [PATCH 0/5] [GIT PULL] updates for tip/tracing/ftrace Steven Rostedt
2009-03-18  3:14 ` [PATCH 1/5] ring-buffer: add api to allow a tracer to change clock source Steven Rostedt
2009-03-18  3:14 ` [PATCH 2/5] tracing: add global-clock option to provide cross CPU clock to traces Steven Rostedt
2009-03-18  3:14 ` [PATCH 3/5] tracing: optimization of branch tracer Steven Rostedt
2009-03-18  3:14 ` [PATCH 4/5] tracing: make sched_switch stop/start light weight Steven Rostedt
2009-03-18  3:14 ` [PATCH 5/5] tracing: make power tracer start/stop methods lighter weight Steven Rostedt
2009-03-18  5:59 ` [PATCH 0/5] [GIT PULL] updates for tip/tracing/ftrace Ingo Molnar
2009-03-18  7:39   ` Ingo Molnar
2009-03-19  7:33     ` Ingo Molnar
2009-03-19 17:21       ` Steven Rostedt
2009-03-20 17:43         ` Paul E. McKenney [this message]
2009-03-20 18:36           ` Ingo Molnar
2009-03-20 18:38             ` Ingo Molnar
2009-03-20 19:19               ` Paul E. McKenney
2009-03-20 19:27                 ` Ingo Molnar
2009-03-20 19:41                   ` Paul E. McKenney
2009-03-20 19:46                   ` Frederic Weisbecker
2009-03-20 19:54                     ` Ingo Molnar
2009-03-20 20:48                       ` Frederic Weisbecker
2009-03-20 21:05                         ` Steven Rostedt
2009-03-21 10:01                           ` Ingo Molnar
2009-03-21 16:58                             ` Ingo Molnar
2009-03-21 17:25                               ` Steven Rostedt
2009-03-21 19:07                                 ` Paul E. McKenney
2009-03-21 20:09                                   ` Ingo Molnar
2009-03-21 21:01                                     ` Paul E. McKenney
2009-03-22 14:24                                       ` Ingo Molnar
2009-03-22 15:06                                         ` Ingo Molnar
2009-03-22 17:02                                           ` Ingo Molnar
2009-03-22 18:33                                             ` Steven Rostedt
2009-03-22 19:52                                               ` Ingo Molnar
2009-03-23 18:44                                           ` Steven Rostedt
2009-03-21 17:32                               ` Frederic Weisbecker
2009-03-21 17:44                                 ` Steven Rostedt
2009-03-21 17:53                                   ` Frederic Weisbecker
2009-03-21 18:17                                     ` Steven Rostedt
2009-03-21 20:03                                       ` Frederic Weisbecker
2009-03-21 18:18                                 ` Ingo Molnar
2009-03-21 20:09                                   ` Frederic Weisbecker
2009-03-21 20:46                                     ` Frederic Weisbecker
2009-03-22 19:41                               ` Ingo Molnar
2009-03-22 20:41                                 ` Ingo Molnar
2009-03-20 21:39                         ` Paul E. McKenney
2009-03-20 17:05       ` Frederic Weisbecker
2009-03-20 17:57         ` Frederic Weisbecker
2009-03-20 18:22           ` Steven Rostedt
2009-03-20 18:39             ` Frederic Weisbecker
2009-03-20 18:42             ` Ingo Molnar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090320174331.GH6698@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox