From: Dipankar Sarma <dipankar@in.ibm.com>
To: V Srivatsa <vatsa@in.ibm.com>, nathanl@in.ibm.com
Cc: Joel Schopp <jschopp@austin.ibm.com>,
Rusty Russell <rusty@rustcorp.com.au>,
linux-kernel@vger.kernel.org, nickp@in.ibm.com
Subject: CPU hotplug broken in 2.6.8-rc2 ?
Date: Mon, 2 Aug 2004 15:19:07 +0530 [thread overview]
Message-ID: <20040802094907.GA3945@in.ibm.com> (raw)
Could it be that recent sched domain stuff broke CPU hotplug ?
While testing cpu hotplug with some RCU changes, I got the following
panic (while onlining).
Thanks
Dipankar
cpu 0x2: Vector: 380 (Data SLB Access) at [c00000000152f4a0]
pc: c00000000004b1b0: .find_busiest_group+0x274/0x464
lr: c00000000004b0e4: .find_busiest_group+0x1a8/0x464
sp: c00000000152f720
msr: 8000000000001032
dar: 10
current = 0xc000000001520040
paca = 0xc000000000535200
pid = 0, comm = swapper
enter ? for help
2:mon>
2:mon> t
[c00000000152f720] c000000000654f30 (unreliable)
[c00000000152f830] c00000000004b4cc .rebalance_tick+0x12c/0x2d4
[c00000000152f920] c00000000005b954 .update_process_times+0xc4/0x154
[c00000000152f9c0] c0000000000385e8 .smp_local_timer_interrupt+0x3c/0x58
[c00000000152fa30] c000000000015088 .timer_interrupt+0x11c/0x3fc
[c00000000152fb10] c00000000000a2b4 Decrementer_common+0xb4/0x100
--- Exception: 901 (Decrementer) at c000000000013bc0 .default_idle+0x70/0x110
[c00000000152fe90] c0000000000139e4 .cpu_idle+0x38/0x50
[c00000000152ff00] c000000000038e18 .start_secondary+0xfc/0x150
[c00000000152ff90] c00000000000bf20 .enable_64b_mode+0x0/0x28
2:mon> r
R00 = 000000000000002b R16 = 0000000000000040
R01 = c00000000152f720 R17 = 0000000000000180
R02 = c0000000006d6d40 R18 = 0000000000000040
R03 = 0000000000000020 R19 = c000000000828e08
R04 = 0000000000000020 R20 = 0000000000000002
R05 = 0000000000000002 R21 = 0000000000000000
R06 = c00000000073f9b0 R22 = 0000000000000000
R07 = 000000000000000b R23 = c00000000152f790
R08 = c0000000006fc728 R24 = c0000000006d5008
R09 = 0000000000000015 R25 = c000000000529c38
R10 = 0000000000000000 R26 = c000000000529c38
R11 = 0000000000000080 R27 = c00000000073f9b0
R12 = 0000000028282482 R28 = 0000000000000001
R13 = c000000000535200 R29 = 0000000000000015
R14 = c00000000073f980 R30 = c0000000005bbe00
R15 = 0000000000000000 R31 = c00000000152f720
pc = c00000000004b1b0 .find_busiest_group+0x274/0x464
lr = c00000000004b0e4 .find_busiest_group+0x1a8/0x464
msr = 8000000000001032 cr = 28282488
ctr = c000000000013b50 xer = 0000000000000000 trap = 380
next reply other threads:[~2004-08-02 9:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-02 9:49 Dipankar Sarma [this message]
2004-08-02 9:57 ` CPU hotplug broken in 2.6.8-rc2 ? Dipankar Sarma
2004-08-02 13:46 ` Anton Blanchard
2004-08-02 19:38 ` Nathan Lynch
2004-08-02 20:26 ` Nathan Lynch
2004-08-03 21:07 ` Nathan Lynch
2004-08-04 10:06 ` Srivatsa Vaddagiri
2004-08-04 13:12 ` Nathan Lynch
2004-08-04 14:50 ` Zwane Mwaikambo
2004-08-04 21:07 ` Con Kolivas
2004-08-03 0:13 ` Rusty Russell
2004-08-02 16:00 ` Zwane Mwaikambo
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=20040802094907.GA3945@in.ibm.com \
--to=dipankar@in.ibm.com \
--cc=jschopp@austin.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nathanl@in.ibm.com \
--cc=nickp@in.ibm.com \
--cc=rusty@rustcorp.com.au \
--cc=vatsa@in.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox