From: Sachin Sant <sachinp@in.ibm.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [ppc64] 2.6.29-git7 : offlining a cpu causes an exception
Date: Wed, 01 Apr 2009 12:10:08 +0530 [thread overview]
Message-ID: <49D30C48.4090902@in.ibm.com> (raw)
In-Reply-To: <1238539469.17330.70.camel@pasglop>
Benjamin Herrenschmidt wrote:
> On Tue, 2009-03-31 at 14:57 +0530, Sachin Sant wrote:
>
>> While executing CPU HotPlug[1] tests i observed that during
>> every cpu offline process an exception is thrown.
>>
>
> Looks like a BUG_ON() to me... can you look at what other
> messages just before that ?
>
I don't get any other messages when the problem occurs. Infact
if i don't have xmon enabled the machine just hangs without
any messages on the console. I extracted the dmesg log
(attached in my previous mail) through xmon. Here are last few
related messages from 2.6.29-git8 kernel during problem recreation.
<4>IRQ 18 affinity broken off cpu 2
<4>cpu 2 (hwid 2) Ready to die....
<7>CPU0 attaching NULL sched-domain..
<7>CPU1 attaching NULL sched-domain..
<7>CPU2 attaching NULL sched-domain..
<7>CPU3 attaching NULL sched-domain..
<7>CPU0 attaching sched-domain:.
<7> domain 0: span 0-1 level SIBLING.
<7> groups: 0 1.
<7> domain 1: span 0-1,3 level CPU.
<7> groups: 0-1 3.
<7> domain 2: span 0-1,3 level NODE
<7> groups: 0-1,3.
<7>CPU1 attaching sched-domain:.
<7> domain 0: span 0-1 level SIBLING.
<7> groups: 1 0.
<7> domain 1: span 0-1,3 level CPU.
<7> groups: 0-1 3.
<7> domain 2: span 0-1,3 level NODE.
<7> groups: 0-1,3.
<7>CPU3 attaching sched-domain:.
<7> domain 0: span 0-1,3 level CPU.
<7> groups: 3 0-1.
<7> domain 1: span 0-1,3 level NODE.
<7> groups: 0-1,3...
> That or lookup where the PC and LR values are in System.map
> and maybe get us a backtrace from xmon ?
>
> (You seem to have no symbols, have you built with kallsyms ?)
I have kallsyms and debug info options enabled.
CONFIG_KALLSYMS=y
CONFIG_KALLSYMS_ALL=y
# CONFIG_KALLSYMS_EXTRA_PASS is not set
CONFIG_DEBUG_INFO=y
Here is the related information from 2.6.29-git8 kernel.
llm62 login: cpu 0x2: Vector: 700 (Program Check) at [c0000000074c7ca0]
pc: 00000000007b6640
lr: 000000000079ddc0
sp: c0000000074c7f20
msr: 8000000000081002
current = 0xc0000000fe1c8580
paca = 0xc000000000ab2800
pid = 0, comm = swapper
enter ? for help
[c0000000074c7f20] 0000000000018694 (unreliable)
[c0000000074c7f90] 0000000000008278
SP (4f00000003) is in userspace
2:mon> la %pc
00000000007b6640
2:mon> la c0000000007b6640
c0000000007b6640: .kmem_cache_init+0x2d8/0x528
2:mon> la %lr
000000000079ddc0
2:mon> la c00000000079ddc0
c00000000079ddc0: .mem_init+0x150/0x22c
2:mon>
Regards
-Sachin
--
---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------
next prev parent reply other threads:[~2009-04-01 6:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-31 9:27 [ppc64] 2.6.29-git7 : offlining a cpu causes an exception Sachin Sant
2009-03-31 22:44 ` Benjamin Herrenschmidt
2009-04-01 6:40 ` Sachin Sant [this message]
2009-04-01 11:48 ` Sachin Sant
2009-04-16 5:36 ` Sachin Sant
2009-04-16 8:25 ` Michael Ellerman
2009-04-16 10:15 ` Sachin Sant
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=49D30C48.4090902@in.ibm.com \
--to=sachinp@in.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
/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.