From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: xen-devel@lists.xensource.com,
julie Sullivan <kernelmail.jms@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: 3.0-rc kernels unbootable since -rc3
Date: Tue, 12 Jul 2011 03:55:06 -0700 [thread overview]
Message-ID: <20110712105506.GB2253@linux.vnet.ibm.com> (raw)
In-Reply-To: <20110711210954.GA15745@dumpdata.com>
On Mon, Jul 11, 2011 at 05:09:54PM -0400, Konrad Rzeszutek Wilk wrote:
> On Mon, Jul 11, 2011 at 01:15:08PM -0700, Paul E. McKenney wrote:
> > On Mon, Jul 11, 2011 at 03:30:22PM -0400, Konrad Rzeszutek Wilk wrote:
> > > >
> > > > Hmmm... Does the stall repeat about every 3.5 minutes after the first stall?
> > >
> > > Starting Configure read-only root support...
> > > [ 81.335070] INFO: rcu_sched_state detected stalls on CPUs/tasks: { 0} (detected by 3, t=60002 jiffies)
> > > [ 81.335091] sending NMI to all CPUs:
> > > [ 261.367071] INFO: rcu_sched_state detected stalls on CPUs/tasks: { 0} (detected by 3, t=240034 jiffies)
> > > [ 261.367092] sending NMI to all CPUs:
> > > [ 441.399066] INFO: rcu_sched_state detected stalls on CPUs/tasks: { 0} (detected by 3, t=420066 jiffies)
> > > [ 441.399089] sending NMI to all CPUs:
> >
> > OK, then the likely cause is something hanging onto the CPU. Do the later
> > stalls also show stack traces? If so, what shows up?
>
> I don't really get any stack traces from the guest. Not sure why it does
> not print them out (probably b/c the NMI functionality is not accessible
> somehow?). I get the stack traces using a 'xenctx' tool and this is what
> I get from the guest before the stall, and after the stall:
>
> 20:45:56 # 12 :/mnt/tmp/FC15-32/
> /usr/lib64/xen/bin/xenctx 29 -s System.map-3.0.0-rc6-disabled-options+ -a 2
> cs:eip: 0061:c042d0f5 task_waking_fair+0x14
> flags: 00001286 i s nz p
> ss:esp: 0069:e94cff0c
> eax: c18dbed0 ebx: ffffffff ecx: fff00000 edx: c14a10c0
> esi: 00000000 edi: 00000000 ebp: e94cff18
> ds: 007b es: 007b fs: 00d8 gs: 00e0
>
> cr0: 8005003b
> cr2: b7743000
> cr3: 97348001
> cr4: 00000660
>
> dr0: 00000000
> dr1: 00000000
> dr2: 00000000
> dr3: 00000000
> dr6: ffff0ff0
> dr7: 00000400
> Code (instr addr c042d0f5)
> c3 55 89 e5 57 56 53 3e 8d 74 26 00 8b 90 58 01 00 00 8b 7a 1c <8b> 72 20 8b 5a 18 8b 4a 14 39 f3
>
>
> Stack:
> c18dbed0 00000003 00000002 e94cff38 c0439a45 c18d00c0 c18dc2c0 00000000
> e8bd1ec4 e8bd1ef8 00000003 e94cff40 c0439b0c e94cff64 c042d4db 00000000
> e8bd1f04 00000001 00000001 e8bd1f00 e8bd0200 e8bd1efc e94cff80 c042ea69
> 00000000 00000000 e8bd1ef4 ea9c4918 c0a43a80 e94cff88 c0455e14 e94cffb4
>
> Call Trace:
> [<c042d0f5>] task_waking_fair+0x14 <--
Hmmm... This is a 32-bit system, isn't it?
Could you please add a check to the loop in task_waking_fair() and
do a printk() if the loop does (say) more than 1000 passes without
exiting?
Thanx, Paul
> [<c0439a45>] try_to_wake_up+0xb2
> [<c0439b0c>] default_wake_function+0x10
> [<c042d4db>] __wake_up_common+0x3b
> [<c042ea69>] complete+0x3e
> [<c0455e14>] wakeme_after_rcu+0x10
> [<c048fd26>] __rcu_process_callbacks+0x172
> [<c048fe14>] rcu_process_callbacks+0x1e
> [<c044567d>] __do_softirq+0xa2
next prev parent reply other threads:[~2011-07-12 10:55 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-06 21:10 PROBLEM: 3.0-rc kernels unbootable since -rc3 julie Sullivan
2011-07-06 21:23 ` Paul E. McKenney
2011-07-07 19:31 ` Paul E. McKenney
2011-07-07 19:47 ` julie Sullivan
2011-07-07 19:58 ` Paul E. McKenney
2011-07-07 20:28 ` julie Sullivan
2011-07-07 20:47 ` julie Sullivan
2011-07-08 0:29 ` Paul E. McKenney
2011-07-09 10:09 ` Paul E. McKenney
2011-07-10 0:45 ` julie Sullivan
2011-07-10 3:25 ` Paul E. McKenney
2011-07-10 16:38 ` julie Sullivan
2011-07-10 17:16 ` Paul E. McKenney
2011-07-10 17:35 ` Paul E. McKenney
2011-07-10 20:30 ` julie Sullivan
2011-07-10 21:46 ` Paul E. McKenney
2011-07-10 21:50 ` julie Sullivan
2011-07-10 23:14 ` Paul E. McKenney
2011-07-11 16:24 ` Konrad Rzeszutek Wilk
2011-07-11 17:13 ` Paul E. McKenney
2011-07-11 19:30 ` Konrad Rzeszutek Wilk
2011-07-11 20:15 ` Paul E. McKenney
2011-07-11 21:09 ` Konrad Rzeszutek Wilk
2011-07-12 10:55 ` Paul E. McKenney [this message]
2011-07-12 14:12 ` Konrad Rzeszutek Wilk
2011-07-12 14:49 ` Paul E. McKenney
2011-07-12 15:07 ` Paul E. McKenney
2011-07-12 15:15 ` Paul E. McKenney
2011-07-12 15:22 ` Paul E. McKenney
2011-07-12 16:32 ` PROBLEM: 3.0-rc kernels unbootable since -rc3 - under Xen, 32-bit guest only Konrad Rzeszutek Wilk
2011-07-12 16:32 ` Konrad Rzeszutek Wilk
2011-07-12 16:46 ` Paul E. McKenney
2011-07-12 16:03 ` PROBLEM: 3.0-rc kernels unbootable since -rc3 Konrad Rzeszutek Wilk
2011-07-12 16:39 ` Paul E. McKenney
2011-07-12 18:01 ` Konrad Rzeszutek Wilk
2011-07-12 18:59 ` Paul E. McKenney
2011-07-12 19:07 ` Konrad Rzeszutek Wilk
2011-07-12 20:52 ` Paul E. McKenney
2011-07-12 19:10 ` Peter Zijlstra
2011-07-12 19:57 ` Konrad Rzeszutek Wilk
2011-07-12 20:46 ` Paul E. McKenney
2011-07-12 21:04 ` Julie Sullivan
2011-07-12 21:07 ` Paul E. McKenney
2011-07-12 20:05 ` Paul E. McKenney
2011-07-12 6:33 ` [Xen-devel] " Sander Eikelenboom
2011-07-12 6:33 ` Sander Eikelenboom
2011-07-12 14:05 ` [Xen-devel] " Paul E. McKenney
[not found] ` <CAAVPGOMSprJSkzziH6hJv9PweOONzsMaRZEK2ZSrV3xFBReTPw@mail.gmail.com>
[not found] ` <20110711214301.GP2245@linux.vnet.ibm.com>
2011-07-12 21:15 ` Julie Sullivan
2011-07-12 21:29 ` Paul E. McKenney
2011-07-12 21:35 ` Julie Sullivan
2011-07-12 21:49 ` Julie Sullivan
2011-07-12 22:00 ` Paul E. McKenney
2011-07-13 7:18 ` RKK
2011-07-13 15:47 ` Paul E. McKenney
2011-07-13 20:57 ` Julie Sullivan
2011-07-13 21:23 ` Paul E. McKenney
2011-07-07 17:28 ` julie Sullivan
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=20110712105506.GB2253@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=kernelmail.jms@gmail.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.