eeh-powernv.c: Unbalanced IRQ warning

Gavin Shan gwshan at linux.vnet.ibm.com
Tue Jul 28 11:11:26 AEST 2015


On Mon, Jul 27, 2015 at 05:37:03PM +1000, Daniel Axtens wrote:
>Hi Alistair,
>
>I've just rebased some CAPI patches on top of 4.2-rc4 and I'm getting a
>new WARN relating to IRQs in EEH, which I believe is related to your
>patch 79231448c929 ("powernv/eeh: Update the EEH code to use the opal
>irq domain").
>
>This is what I see after injecting a PHB fence on a CAPI card.
>
>[  126.022390] EEH: Notify device driver to resume
>[  126.022421] Unbalanced enable for IRQ 17
>[  126.022432] ------------[ cut here ]------------
>[  126.022440] WARNING: at /scratch/dja/linux-capi/kernel/irq/manage.c:511
>[  126.022451] Modules linked in: cxl
>[  126.022465] CPU: 3 PID: 123 Comm: eehd Not tainted 4.2.0-rc4-00013-g86caa74-dirty #86
>[  126.022479] task: c000000751b0af50 ti: c000000751b94000 task.ti: c000000751b94000
>[  126.022493] NIP: c0000000000f1760 LR: c0000000000f175c CTR: c0000000006000c0
>[  126.022509] REGS: c000000751b97710 TRAP: 0700   Not tainted  (4.2.0-rc4-00013-g86caa74-dirty)
>[  126.022522] MSR: 9000000100029032 <SF,HV,EE,ME,IR,DR,RI>  CR: 22008022  XER: 20000000
>[  126.022560] CFAR: c0000000008a8680 SOFTE: 0 
>GPR00: c0000000000f175c c000000751b97990 c000000000e80c00 000000000000001c 
>GPR04: 0000000000000000 000000000000002c 00000000000000ff 000000000000001f 
>GPR08: c000000000d86cc0 c000000000d86cb8 c000000000d86cc0 0000000000000000 
>GPR12: 0000000042008028 c00000000fdc0d80 c0000000000bb460 c000000758162580 
>GPR16: 0000000000000000 0000000000000000 c00000074d3a1000 c000000000b35240 
>GPR20: c000000000b35210 c000000000b35278 c000000000b352e8 c000000000b2e2a8 
>GPR24: c0000000008d35b8 c0000000008d3510 c000000000efa408 c000000751b97c10 
>GPR28: 0000000000000000 c000000000d7a330 0000000000000011 c000000751eaec00 
>[  126.022735] NIP [c0000000000f1760] .__enable_irq+0x30/0xd0
>[  126.022747] LR [c0000000000f175c] .__enable_irq+0x2c/0xd0
>[  126.022756] Call Trace:
>[  126.022764] [c000000751b97990] [c0000000000f175c] .__enable_irq+0x2c/0xd0 (unreliable)
>[  126.022780] [c000000751b97a20] [c0000000000f1848] .enable_irq+0x48/0x90
>[  126.022796] [c000000751b97ab0] [c00000000006ab00] .pnv_eeh_next_error+0x1f0/0x6f0
>[  126.022812] [c000000751b97ba0] [c000000000035908] .eeh_handle_event+0xb8/0x2f0
>[  126.022827] [c000000751b97c70] [c000000000035cf8] .eeh_event_handler+0x1b8/0x1c0
>[  126.022844] [c000000751b97d30] [c0000000000bb564] .kthread+0x104/0x130
>[  126.022860] [c000000751b97e30] [c0000000000095a4] .ret_from_kernel_thread+0x58/0xb4
>[  126.022874] Instruction dump:
>[  126.022882] 7c0802a6 fbe1fff8 7c7f1b78 f8010010 f821ff71 81230170 2f890000 409e0034 
>[  126.022915] 3c62ffcd 3863a730 487b6ec9 60000000 <0fe00000> 38210090 e8010010 ebe1fff8 
>[  126.022935] ---[ end trace 26e6323a0534e98d ]---
>
>manage.c:511 suggests that this is probably the result of the IRQ being
>enabled when it's already enabled.
>
>Do you know what might be causing this and how it might be fixed?
>Thanks in advance!
>

Daniel, could you check if the attached patch fixes the issue? If it helps,
I'll clean it up and send it out for review together other cleanup patches.

Thanks,
Gavin


-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-powerpc-powernv-Reenable-EEH-IRQ-if-necessary.patch
Type: text/x-diff
Size: 3021 bytes
Desc: not available
URL: <http://lists.ozlabs.org/pipermail/linuxppc-dev/attachments/20150728/98975d65/attachment.patch>


More information about the Linuxppc-dev mailing list