From: Michael Ellerman <mpe@ellerman.id.au>
To: Sachin Sant <sachinp@linux.vnet.ibm.com>, linux-next@vger.kernel.org
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [next-20170217] WARN @/arch/powerpc/include/asm/xics.h:124 .icp_hv_eoi+0x40/0x140
Date: Mon, 20 Feb 2017 13:35:42 +1100 [thread overview]
Message-ID: <87zihhh9mp.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <E96217CD-2ADD-430D-86BD-27FF87752D7F@linux.vnet.ibm.com>
Sachin Sant <sachinp@linux.vnet.ibm.com> writes:
> While booting next-20170217 on a POWER6 box, I ran into following
> warning. This is a full system lpar. Previous next tree was good.
> I will try a bisect tomorrow.
Do you have CONFIG_DEBUG_SHIRQ=y ?
cheers
> ipr: IBM Power RAID SCSI Device Driver version: 2.6.3 (October 17, 2015)
> ipr 0200:00:01.0: Found IOA with IRQ: 305
> ------------[ cut here ]------------
> WARNING: CPU: 12 PID: 1 at ./arch/powerpc/include/asm/xics.h:124 .icp_hv_eoi+0x40/0x140
> Modules linked in:
> CPU: 12 PID: 1 Comm: swapper/14 Not tainted 4.10.0-rc8-next-20170217-autotest #1
> task: c0000002b2a4a580 task.stack: c0000002b2a5c000
> NIP: c0000000000731b0 LR: c0000000001389f8 CTR: c000000000073170
> REGS: c0000002b2a5f050 TRAP: 0700 Not tainted (4.10.0-rc8-next-20170217-autotest)
> MSR: 8000000000029032 <SF,EE,ME,IR,DR,RI>
> CR: 28004082 XER: 20000004
> CFAR: c0000000001389e0 SOFTE: 0
> GPR00: c0000000001389f8 c0000002b2a5f2d0 c000000001025800 c0000002b203f498
> GPR04: 0000000000000000 0000000000000000 0000000000000064 0000000000000131
> GPR08: 0000000000000001 c0000000d3104cb8 ffffffffffffffff 000000000009b1f8
> GPR12: 0000000048004082 c00000000edc2400 c00000000000dad0 0000000000000000
> GPR16: 0000000000000000 00003c007efc0000 c000000000a9e848 0000000000000000
> GPR20: d000080080080000 c0000002af4d47f0 c0000000011efda8 c000000000a9ea10
> GPR24: c000000000a9e848 0000000000000000 c0000002af4d4fb8 0000000000000000
> GPR28: 0000000000000000 c0000002b203f498 c000000000ef8928 c0000002b203f400
> NIP [c0000000000731b0] .icp_hv_eoi+0x40/0x140
> LR [c0000000001389f8] .handle_fasteoi_irq+0x1e8/0x270
> Call Trace:
> [c0000002b2a5f2d0] [c0000002b2a5f360] 0xc0000002b2a5f360 (unreliable)
> [c0000002b2a5f360] [c0000000001389f8] .handle_fasteoi_irq+0x1e8/0x270
> [c0000002b2a5f3e0] [c000000000136a08] .request_threaded_irq+0x298/0x370
> [c0000002b2a5f490] [c0000000005895c0] .ipr_probe_ioa+0x1110/0x1390
> [c0000002b2a5f5c0] [c00000000058d030] .ipr_probe+0x30/0x3e0
> [c0000002b2a5f670] [c000000000466860] .local_pci_probe+0x60/0x130
> [c0000002b2a5f710] [c000000000467658] .pci_device_probe+0x148/0x1e0
> [c0000002b2a5f7c0] [c000000000527524] .driver_probe_device+0x2d4/0x5b0
> [c0000002b2a5f860] [c00000000052796c] .__driver_attach+0x16c/0x190
> [c0000002b2a5f8f0] [c0000000005242c4] .bus_for_each_dev+0x84/0xf0
> [c0000002b2a5f990] [c000000000526af4] .driver_attach+0x24/0x40
> [c0000002b2a5fa00] [c000000000526318] .bus_add_driver+0x2a8/0x370
> [c0000002b2a5faa0] [c000000000528a5c] .driver_register+0x8c/0x170
> [c0000002b2a5fb20] [c000000000465a54] .__pci_register_driver+0x44/0x60
> [c0000002b2a5fb90] [c000000000b8efc8] .ipr_init+0x58/0x70
> [c0000002b2a5fc10] [c00000000000d20c] .do_one_initcall+0x5c/0x1c0
> [c0000002b2a5fce0] [c000000000b44738] .kernel_init_freeable+0x280/0x360
> [c0000002b2a5fdb0] [c00000000000daec] .kernel_init+0x1c/0x130
> [c0000002b2a5fe30] [c00000000000baa0] .ret_from_kernel_thread+0x58/0xb8
> Instruction dump:
> f8010010 f821ff71 80e3000c 7c0004ac e94d0030 3d02ffbc 3928f4b8 7d295214
> 81090004 3948ffff 7d484378 79080fe2 <0b080000> 2fa80000 40de0050 91490004
> ---[ end trace 5e18ae409f46392c ]---
> ipr 0200:00:01.0: Initializing IOA.
>
> Thanks
> -Sachin
next prev parent reply other threads:[~2017-02-20 2:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-19 15:09 [next-20170217] WARN @/arch/powerpc/include/asm/xics.h:124 .icp_hv_eoi+0x40/0x140 Sachin Sant
2017-02-20 2:35 ` Michael Ellerman [this message]
2017-02-20 5:04 ` Sachin Sant
2017-02-20 10:55 ` Michael Ellerman
2017-02-20 20:53 ` Benjamin Herrenschmidt
2017-02-20 22:04 ` Thomas Gleixner
2017-02-20 22:18 ` Benjamin Herrenschmidt
2017-02-20 3:44 ` Balbir Singh
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=87zihhh9mp.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=sachinp@linux.vnet.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