Re: WARN_ON after gic_reserve_range

2018-11-21 Thread Richter, Robert
On 20.11.18 17:37:37, Marc Zyngier wrote: > On 20/11/2018 17:30, John Garry wrote: > > I see it also: > > > > [0.00] Booting Linux on physical CPU 0x01 [0x410fd082] > > [0.00] Linux version 4.20.0-rc3 > > (johnpgarry@johnpgarry-ThinkCentre-M93p) (gcc version 7.3.1 20180425

Re: WARN_ON after gic_reserve_range

2018-11-21 Thread Richter, Robert
On 20.11.18 17:37:37, Marc Zyngier wrote: > On 20/11/2018 17:30, John Garry wrote: > > I see it also: > > > > [0.00] Booting Linux on physical CPU 0x01 [0x410fd082] > > [0.00] Linux version 4.20.0-rc3 > > (johnpgarry@johnpgarry-ThinkCentre-M93p) (gcc version 7.3.1 20180425

Re: WARN_ON after gic_reserve_range

2018-11-20 Thread Marc Zyngier
On 20/11/2018 17:30, John Garry wrote: > On 20/11/2018 16:23, Jan Glauber wrote: >> Hi Marc, >> >> with 4.20-rc3 I see two WARN_ON's firing on a ThunderX2 system that come from >> commit 3fb68faee867 (irqchip/gic-v3-its: Register LPI tables with EFI config >> table). >> >> Global

Re: WARN_ON after gic_reserve_range

2018-11-20 Thread Marc Zyngier
On 20/11/2018 17:30, John Garry wrote: > On 20/11/2018 16:23, Jan Glauber wrote: >> Hi Marc, >> >> with 4.20-rc3 I see two WARN_ON's firing on a ThunderX2 system that come from >> commit 3fb68faee867 (irqchip/gic-v3-its: Register LPI tables with EFI config >> table). >> >> Global

Re: WARN_ON after gic_reserve_range

2018-11-20 Thread John Garry
On 20/11/2018 16:23, Jan Glauber wrote: Hi Marc, with 4.20-rc3 I see two WARN_ON's firing on a ThunderX2 system that come from commit 3fb68faee867 (irqchip/gic-v3-its: Register LPI tables with EFI config table). Global efi_memreserve_root is NULL as it will only be set when early initcalls

Re: WARN_ON after gic_reserve_range

2018-11-20 Thread John Garry
On 20/11/2018 16:23, Jan Glauber wrote: Hi Marc, with 4.20-rc3 I see two WARN_ON's firing on a ThunderX2 system that come from commit 3fb68faee867 (irqchip/gic-v3-its: Register LPI tables with EFI config table). Global efi_memreserve_root is NULL as it will only be set when early initcalls

Re: WARN_ON after gic_reserve_range

2018-11-20 Thread Marc Zyngier
[+ Ard] Hi Jan, On 20/11/2018 16:23, Jan Glauber wrote: > Hi Marc, > > with 4.20-rc3 I see two WARN_ON's firing on a ThunderX2 system that come from > commit 3fb68faee867 (irqchip/gic-v3-its: Register LPI tables with EFI config > table). > > Global efi_memreserve_root is NULL as it will only

Re: WARN_ON after gic_reserve_range

2018-11-20 Thread Marc Zyngier
[+ Ard] Hi Jan, On 20/11/2018 16:23, Jan Glauber wrote: > Hi Marc, > > with 4.20-rc3 I see two WARN_ON's firing on a ThunderX2 system that come from > commit 3fb68faee867 (irqchip/gic-v3-its: Register LPI tables with EFI config > table). > > Global efi_memreserve_root is NULL as it will only

WARN_ON after gic_reserve_range

2018-11-20 Thread Jan Glauber
Hi Marc, with 4.20-rc3 I see two WARN_ON's firing on a ThunderX2 system that come from commit 3fb68faee867 (irqchip/gic-v3-its: Register LPI tables with EFI config table). Global efi_memreserve_root is NULL as it will only be set when early initcalls are running, but from the backtrace the

WARN_ON after gic_reserve_range

2018-11-20 Thread Jan Glauber
Hi Marc, with 4.20-rc3 I see two WARN_ON's firing on a ThunderX2 system that come from commit 3fb68faee867 (irqchip/gic-v3-its: Register LPI tables with EFI config table). Global efi_memreserve_root is NULL as it will only be set when early initcalls are running, but from the backtrace the