Re: [PATCH 1/2] arm: Fix "NMI" backtrace for Inforce IFC6410

2015-12-18 Thread Marc Zyngier
On 16/12/15 17:08, Daniel Thompson wrote: > SysRq-L does not generate a backtrace from all CPUs when I test it > on my Inforce IFC6410 platform (Snapdragon 600). The stack dump code, > triggered by IPI_CPU_BACKTRACE, never runs on the other CPUs. > Eventually we hit the 10 second timeout and a

Re: [PATCH 1/2] arm: Fix "NMI" backtrace for Inforce IFC6410

2015-12-18 Thread Marc Zyngier
On 16/12/15 17:08, Daniel Thompson wrote: > SysRq-L does not generate a backtrace from all CPUs when I test it > on my Inforce IFC6410 platform (Snapdragon 600). The stack dump code, > triggered by IPI_CPU_BACKTRACE, never runs on the other CPUs. > Eventually we hit the 10 second timeout and a

[PATCH 1/2] arm: Fix "NMI" backtrace for Inforce IFC6410

2015-12-16 Thread Daniel Thompson
SysRq-L does not generate a backtrace from all CPUs when I test it on my Inforce IFC6410 platform (Snapdragon 600). The stack dump code, triggered by IPI_CPU_BACKTRACE, never runs on the other CPUs. Eventually we hit the 10 second timeout and a subset of the expected stack dumps on are shown on

[PATCH 1/2] arm: Fix "NMI" backtrace for Inforce IFC6410

2015-12-16 Thread Daniel Thompson
SysRq-L does not generate a backtrace from all CPUs when I test it on my Inforce IFC6410 platform (Snapdragon 600). The stack dump code, triggered by IPI_CPU_BACKTRACE, never runs on the other CPUs. Eventually we hit the 10 second timeout and a subset of the expected stack dumps on are shown on