From: Amos Waterland <apw@us.ibm.com>
To: Michael Ellerman <michael@ellerman.id.au>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: mpic discovery on JS20
Date: Mon, 24 Jul 2006 17:07:40 -0400 [thread overview]
Message-ID: <20060724210740.GA7139@kvasir.watson.ibm.com> (raw)
In-Reply-To: <1153726896.12748.0.camel@localhost.localdomain>
On Mon, Jul 24, 2006 at 05:41:36PM +1000, Michael Ellerman wrote:
> On Thu, 2006-07-20 at 19:16 -0400, Amos Waterland wrote:
> > Current Linus and Paulus trees do this on JS20 blades with SLOF:
> >
> > Failed to locate the MPIC interrupt controller
> > PID hash table entries: 4096 (order: 12, 32768 bytes)
> > Maple: Found RTC at IO 0x1070
> > cpu 0x0: Vector: 700 (Program Check) at [c00000007ef83ab0]
> > pc: c00000000002e0c8: .mpic_request_ipis+0x34/0xc8
> > lr: c00000000036b484: .smp_mpic_probe+0x3c/0x58
> > sp: c00000007ef83d30
> > msr: 9000000000029032
> > current = 0xc00000000194d610
> > paca = 0xc00000000038f180
> > pid = 1, comm = swapper
> > kernel BUG in mpic_request_ipis at arch/powerpc/sysdev/mpic.c:1132!
>
> Does this help?
Yes, it does to some degree. Current paulus tree with your patch applied:
Built 1 zonelists. Total pages: 524288
Kernel command line:
mpic: Setting up MPIC " MPIC " version <unknown> at f8040000, max 28 CPUs
mpic: ISU size: 516, shift: 10, mask: 3ff
Badness in mpic_init at arch/powerpc/sysdev/mpic.c:875
Call Trace:
[C0000000004D3880] [C00000000000EEB8] .show_stack+0x68/0x1b0 (unreliable)
[C0000000004D3920] [C00000000001D558] .program_check_exception+0x1cc/0x598
[C0000000004D39F0] [C0000000000044EC] program_check_common+0xec/0x100
--- Exception: 700 at .mpic_init+0x5c/0x784
LR = .maple_init_IRQ+0x204/0x290
[C0000000004D3CE0] [C0000000004D3DB0] init_thread_union+0x3db0/0x4000
[C0000000004D3DB0] [C00000000036C130] .maple_init_IRQ+0x204/0x290
[C0000000004D3E80] [C000000000361A88] .init_IRQ+0x34/0x48
[C0000000004D3EF0] [C00000000035B6E0] .start_kernel+0x154/0x2b8
[C0000000004D3F90] [C0000000000084FC] .start_here_common+0x50/0x54
mpic: Initializing for 251 sources
mpic: Setting up HT PICs workarounds for U3/U4
mpic: - HT:01.0 [0xb8] vendor 1022 device 7450 has 4 irqs
mpic: - HT:02.0 [0xb8] vendor 1022 device 7450 has 4 irqs
mpic: - HT:03.0 [0xf0] vendor 1022 device 7460 has 24 irqs
PID hash table entries: 4096 (order: 12, 32768 bytes)
Maple: Found RTC at IO 0x1070
cpu 0x0: Vector: 0 at [c00000007ef83940]
pc: c0000000000216bc: .smp_call_function+0x18c/0x1e4
lr: c0000000000216bc: .smp_call_function+0x18c/0x1e4
sp: c00000007ef83ab0
msr: 9000000000009032
current = 0xc00000000194d610
paca = 0xc00000000038c180
pid = 1, comm = swapper
The warning is this:
WARN_ON(mpic->num_sources > MPIC_VEC_IPI_0);
prev parent reply other threads:[~2006-07-24 21:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-20 23:16 mpic discovery on JS20 Amos Waterland
2006-07-21 17:37 ` Benjamin Herrenschmidt
2006-07-24 21:09 ` Amos Waterland
2006-07-24 7:41 ` Michael Ellerman
2006-07-24 18:20 ` Segher Boessenkool
2006-07-25 1:54 ` Michael Ellerman
2006-07-25 3:41 ` Segher Boessenkool
2006-07-24 21:07 ` Amos Waterland [this message]
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=20060724210740.GA7139@kvasir.watson.ibm.com \
--to=apw@us.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=michael@ellerman.id.au \
/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;
as well as URLs for NNTP newsgroup(s).