On 06/07/2019 03:49 AM, Ard Biesheuvel wrote:
> On Thu, 6 Jun 2019 at 23:52, Jonathan Richardson
> wrote:
>>
>> On 06/06/2019 02:07 PM, Bhupesh Sharma wrote:
>>> Hi,
>>>
>>> On Thu, Jun 6, 2019 at 3:45 AM Jonathan Richardson
>>> wrote:
Hi,
As of the 5.0 kernel we're seeing
On Thu, 6 Jun 2019 at 23:52, Jonathan Richardson
wrote:
>
> On 06/06/2019 02:07 PM, Bhupesh Sharma wrote:
> > Hi,
> >
> > On Thu, Jun 6, 2019 at 3:45 AM Jonathan Richardson
> > wrote:
> >>
> >> Hi,
> >>
> >> As of the 5.0 kernel we're seeing the crash dump kernel crash when the
> >> gicv3-its
On 06/06/2019 02:07 PM, Bhupesh Sharma wrote:
> Hi,
>
> On Thu, Jun 6, 2019 at 3:45 AM Jonathan Richardson
> wrote:
>>
>> Hi,
>>
>> As of the 5.0 kernel we're seeing the crash dump kernel crash when the
>> gicv3-its driver calls gic_reserve_range():
>>
>> root@bcm958804a8040c:~# echo c >
Hi,
On Thu, Jun 6, 2019 at 3:45 AM Jonathan Richardson
wrote:
>
> Hi,
>
> As of the 5.0 kernel we're seeing the crash dump kernel crash when the
> gicv3-its driver calls gic_reserve_range():
>
> root@bcm958804a8040c:~# echo c > /proc/sysrq-trigger
> [ 2285.405357] sysrq: SysRq : Trigger a crash
On Thu, 6 Jun 2019 at 16:32, Marc Zyngier wrote:
>
> Hi Jonathan,
>
> On 05/06/2019 23:14, Jonathan Richardson wrote:
> > Hi,
> >
> > As of the 5.0 kernel we're seeing the crash dump kernel crash when the
> > gicv3-its driver calls gic_reserve_range():
>
> [...]
>
> > On crash dump boot, gic
Hi Jonathan,
On 05/06/2019 23:14, Jonathan Richardson wrote:
> Hi,
>
> As of the 5.0 kernel we're seeing the crash dump kernel crash when the
> gicv3-its driver calls gic_reserve_range():
[...]
> On crash dump boot, gic calls the same function, efi_mem_reserve_persistent,
> finds the entry
Hi,
As of the 5.0 kernel we're seeing the crash dump kernel crash when the
gicv3-its driver calls gic_reserve_range():
root@bcm958804a8040c:~# echo c > /proc/sysrq-trigger
[ 2285.405357] sysrq: SysRq : Trigger a crash
[ 2285.409592] Kernel panic - not syncing: sysrq triggered crash
[
