[next-20170217] WARN @/arch/powerpc/include/asm/xics.h:124 .icp_hv_eoi+0x40/0x140

[next-20170217] WARN @/arch/powerpc/include/asm/xics.h:124 .icp_hv_eoi+0x40/0x140

[Sachin Sant]

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.

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-20170217] WARN @/arch/powerpc/include/asm/xics.h:124 .icp_hv_eoi+0x40/0x140

[Sachin Sant]

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.

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=20
GPR00: c0000000001389f8 c0000002b2a5f2d0 c000000001025800 =
c0000002b203f498=20
GPR04: 0000000000000000 0000000000000000 0000000000000064 =
0000000000000131=20
GPR08: 0000000000000001 c0000000d3104cb8 ffffffffffffffff =
000000000009b1f8=20
GPR12: 0000000048004082 c00000000edc2400 c00000000000dad0 =
0000000000000000=20
GPR16: 0000000000000000 00003c007efc0000 c000000000a9e848 =
0000000000000000=20
GPR20: d000080080080000 c0000002af4d47f0 c0000000011efda8 =
c000000000a9ea10=20
GPR24: c000000000a9e848 0000000000000000 c0000002af4d4fb8 =
0000000000000000=20
GPR28: 0000000000000000 c0000002b203f498 c000000000ef8928 =
c0000002b203f400=20
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=20=

81090004 3948ffff 7d484378 79080fe2 <0b080000> 2fa80000 40de0050 =
91490004=20
---[ end trace 5e18ae409f46392c ]---
ipr 0200:00:01.0: Initializing IOA.

Thanks
-Sachin=

Re: [next-20170217] WARN @/arch/powerpc/include/asm/xics.h:124 .icp_hv_eoi+0x40/0x140

[Michael Ellerman]

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

Re: [next-20170217] WARN @/arch/powerpc/include/asm/xics.h:124 .icp_hv_eoi+0x40/0x140

[Balbir Singh]

On Sun, 2017-02-19 at 20:39 +0530, Sachin Sant wrote:
> 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.
> 
> 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


This indicates that the CPPR stack underflow'd (we don't know the CPPR value
at the time of the interrupt that we are going to do an EOI for).  The problem
could have occured elsewhere, but shows up at the first interrupt after
the real cause. Could you past the full dmesg and config and follow Michael's
suggestion for debugging SHIRQ's

Balbir

Re: [next-20170217] WARN @/arch/powerpc/include/asm/xics.h:124 .icp_hv_eoi+0x40/0x140

[Sachin Sant]

>> 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 ?
> 

Yes. CONFIG_DEBUG_SHIRQ is enabled.

As suggested by you reverting following commit allows a clean boot.
f91f694540f3 ("genirq: Reenable shared irq debugging in request_*_irq()”)

>> 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
> 

Re: [next-20170217] WARN @/arch/powerpc/include/asm/xics.h:124 .icp_hv_eoi+0x40/0x140

[Sachin Sant]

>> 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.
>=20
> Do you have CONFIG_DEBUG_SHIRQ=3Dy ?
>=20

Yes. CONFIG_DEBUG_SHIRQ is enabled.

As suggested by you reverting following commit allows a clean boot.
f91f694540f3 ("genirq: Reenable shared irq debugging in =
request_*_irq()=E2=80=9D)

>> 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=20
>> GPR00: c0000000001389f8 c0000002b2a5f2d0 c000000001025800 =
c0000002b203f498=20
>> GPR04: 0000000000000000 0000000000000000 0000000000000064 =
0000000000000131=20
>> GPR08: 0000000000000001 c0000000d3104cb8 ffffffffffffffff =
000000000009b1f8=20
>> GPR12: 0000000048004082 c00000000edc2400 c00000000000dad0 =
0000000000000000=20
>> GPR16: 0000000000000000 00003c007efc0000 c000000000a9e848 =
0000000000000000=20
>> GPR20: d000080080080000 c0000002af4d47f0 c0000000011efda8 =
c000000000a9ea10=20
>> GPR24: c000000000a9e848 0000000000000000 c0000002af4d4fb8 =
0000000000000000=20
>> GPR28: 0000000000000000 c0000002b203f498 c000000000ef8928 =
c0000002b203f400=20
>> 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=20
>> 81090004 3948ffff 7d484378 79080fe2 <0b080000> 2fa80000 40de0050 =
91490004=20
>> ---[ end trace 5e18ae409f46392c ]---
>> ipr 0200:00:01.0: Initializing IOA.
>>=20
>> Thanks
>> -Sachin
>=20

Re: [next-20170217] WARN @/arch/powerpc/include/asm/xics.h:124 .icp_hv_eoi+0x40/0x140

[Michael Ellerman]

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 ?
>> 
>
> Yes. CONFIG_DEBUG_SHIRQ is enabled.
>
> As suggested by you reverting following commit allows a clean boot.
> f91f694540f3 ("genirq: Reenable shared irq debugging in request_*_irq()”)

OK. Or disabling CONFIG_DEBUG_SHIRQ :)

The problem is that the xics code saves the CPPR value in get_irq(),
called from __do_irq(), and then restores it in irq_eoi().

But when we're called for CONFIG_DEBUG_SHIRQ get_irq() is not called,
precisely because we're faking an interrupt.

I'm not sure if there's a good way to fix it :/

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
>> 

Re: [next-20170217] WARN @/arch/powerpc/include/asm/xics.h:124 .icp_hv_eoi+0x40/0x140

[Michael Ellerman]

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.
>>=20
>> Do you have CONFIG_DEBUG_SHIRQ=3Dy ?
>>=20
>
> Yes. CONFIG_DEBUG_SHIRQ is enabled.
>
> As suggested by you reverting following commit allows a clean boot.
> f91f694540f3 ("genirq: Reenable shared irq debugging in request_*_irq()=
=E2=80=9D)

OK. Or disabling CONFIG_DEBUG_SHIRQ :)

The problem is that the xics code saves the CPPR value in get_irq(),
called from __do_irq(), and then restores it in irq_eoi().

But when we're called for CONFIG_DEBUG_SHIRQ get_irq() is not called,
precisely because we're faking an interrupt.

I'm not sure if there's a good way to fix it :/

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_h=
v_eoi+0x40/0x140
>>> Modules linked in:
>>> CPU: 12 PID: 1 Comm: swapper/14 Not tainted 4.10.0-rc8-next-20170217-au=
totest #1
>>> task: c0000002b2a4a580 task.stack: c0000002b2a5c000
>>> NIP: c0000000000731b0 LR: c0000000001389f8 CTR: c000000000073170
>>> REGS: c0000002b2a5f050 TRAP: 0700   Not tainted  (4.10.0-rc8-next-20170=
217-autotest)
>>> MSR: 8000000000029032 <SF,EE,ME,IR,DR,RI>
>>>  CR: 28004082  XER: 20000004
>>> CFAR: c0000000001389e0 SOFTE: 0=20
>>> GPR00: c0000000001389f8 c0000002b2a5f2d0 c000000001025800 c0000002b203f=
498=20
>>> GPR04: 0000000000000000 0000000000000000 0000000000000064 0000000000000=
131=20
>>> GPR08: 0000000000000001 c0000000d3104cb8 ffffffffffffffff 000000000009b=
1f8=20
>>> GPR12: 0000000048004082 c00000000edc2400 c00000000000dad0 0000000000000=
000=20
>>> GPR16: 0000000000000000 00003c007efc0000 c000000000a9e848 0000000000000=
000=20
>>> GPR20: d000080080080000 c0000002af4d47f0 c0000000011efda8 c000000000a9e=
a10=20
>>> GPR24: c000000000a9e848 0000000000000000 c0000002af4d4fb8 0000000000000=
000=20
>>> GPR28: 0000000000000000 c0000002b203f498 c000000000ef8928 c0000002b203f=
400=20
>>> 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=
=20
>>> 81090004 3948ffff 7d484378 79080fe2 <0b080000> 2fa80000 40de0050 914900=
04=20
>>> ---[ end trace 5e18ae409f46392c ]---
>>> ipr 0200:00:01.0: Initializing IOA.
>>>=20
>>> Thanks
>>> -Sachin
>>=20

Re: [next-20170217] WARN @/arch/powerpc/include/asm/xics.h:124 .icp_hv_eoi+0x40/0x140

[Benjamin Herrenschmidt]

On Mon, 2017-02-20 at 21:55 +1100, Michael Ellerman wrote:
> But when we're called for CONFIG_DEBUG_SHIRQ get_irq() is not called,
> precisely because we're faking an interrupt.
> 
> I'm not sure if there's a good way to fix it :/

In the irq_replay path we have code to adjust the CPPR stack. We could
do something similar.

HOWEVER. Looking at current upstream code I don't understand the error,
the DEBUG_SHIRQ code is calling the driver's handler not the flow
handler so it shouldn't be called handle_fasteoi_irq or am I missing
something ?

Cheers,
Ben.

Re: [next-20170217] WARN @/arch/powerpc/include/asm/xics.h:124 .icp_hv_eoi+0x40/0x140

[Thomas Gleixner]

On Tue, 21 Feb 2017, Benjamin Herrenschmidt wrote:

> On Mon, 2017-02-20 at 21:55 +1100, Michael Ellerman wrote:
> > But when we're called for CONFIG_DEBUG_SHIRQ get_irq() is not called,
> > precisely because we're faking an interrupt.
> > 
> > I'm not sure if there's a good way to fix it :/
> 
> In the irq_replay path we have code to adjust the CPPR stack. We could
> do something similar.
> 
> HOWEVER. Looking at current upstream code I don't understand the error,
> the DEBUG_SHIRQ code is calling the driver's handler not the flow
> handler so it shouldn't be called handle_fasteoi_irq or am I missing
> something ?

I tried to invoke the normal handler path which also invokes the flow
handler, but that breaks on x86 as well for different reasons. I zapped
that commit and still need to find a way to do that debug thing proper. So
it's appearence in -next was only temporary.

Thanks,

	tglx

Re: [next-20170217] WARN @/arch/powerpc/include/asm/xics.h:124 .icp_hv_eoi+0x40/0x140

[Benjamin Herrenschmidt]

On Mon, 2017-02-20 at 14:04 -0800, Thomas Gleixner wrote:
> > HOWEVER. Looking at current upstream code I don't understand the error,
> > the DEBUG_SHIRQ code is calling the driver's handler not the flow
> > handler so it shouldn't be called handle_fasteoi_irq or am I missing
> > something ?
> 
> I tried to invoke the normal handler path which also invokes the flow
> handler, but that breaks on x86 as well for different reasons. I zapped
> that commit and still need to find a way to do that debug thing proper. So
> it's appearence in -next was only temporary.

Ok I see. Yes I wouldn't be surprised if we aren't the only ones to
expect that one get_irq() matches *one* invocation of the flow handler.

We had to hack around this for irq_replay already but at least we have
a hook to do that.

You could possibly use replay, but what's wrong with what the code
currently does which is to just call the driver handler directly ?

Cheers,
Ben.