On 11/12/18 3:39 AM, Marc Zyngier wrote:
> On Fri, 09 Nov 2018 18:41:03 +,
> Qian Cai wrote:
>>
>>
>>
>>> On Nov 9, 2018, at 12:41 PM, Marc Zyngier wrote:
>>>
>>> On 09/11/18 17:28, Sudeep Holla wrote:
On Fri, Nov 9, 2018 at 4:10 PM Marc Zyngier wrote:
>
[...]
>
>>>
On Fri, 09 Nov 2018 18:41:03 +,
Qian Cai wrote:
>
>
>
> > On Nov 9, 2018, at 12:41 PM, Marc Zyngier wrote:
> >
> > On 09/11/18 17:28, Sudeep Holla wrote:
> >> On Fri, Nov 9, 2018 at 4:10 PM Marc Zyngier wrote:
> >>>
> >> [...]
> >>
> >>>
> >>> See bb42ca474010 and d003d029cea8 for det
> On Nov 9, 2018, at 12:41 PM, Marc Zyngier wrote:
>
> On 09/11/18 17:28, Sudeep Holla wrote:
>> On Fri, Nov 9, 2018 at 4:10 PM Marc Zyngier wrote:
>>>
>> [...]
>>
>>>
>>> See bb42ca474010 and d003d029cea8 for details.
>>>
>>> Now, activating this workaround leads to lockdep being really
On 09/11/18 17:28, Sudeep Holla wrote:
> On Fri, Nov 9, 2018 at 4:10 PM Marc Zyngier wrote:
>>
> [...]
>
>>
>> See bb42ca474010 and d003d029cea8 for details.
>>
>> Now, activating this workaround leads to lockdep being really angry,
>> most likely because the cpus_read_lock is not taken, which is
On Fri, Nov 9, 2018 at 4:10 PM Marc Zyngier wrote:
>
[...]
>
> See bb42ca474010 and d003d029cea8 for details.
>
> Now, activating this workaround leads to lockdep being really angry,
> most likely because the cpus_read_lock is not taken, which is a change
> in behaviour...
>
> I'm trying to dig i
t git master (b00d209) on an aarch64 server
>>>>>>> and saw
>>>>>>> this. Not sure about the third warning (at kernel/cpu.c:315
>>>>>>> lockdep_assert_cpus_held+0x50/0x60) relates to irqchip or not, but
>>>>>>> ap
gt;> this. Not sure about the third warning (at kernel/cpu.c:315
>>>>>> lockdep_assert_cpus_held+0x50/0x60) relates to irqchip or not, but
>>>>>> appended it
>>>>>> to here anyway just in case.
>>>>>>
>>>>>&
On 08/11/18 20:59, Qian Cai wrote:
>>>>> Just booting up the latest git master (b00d209) on an aarch64 server and
>>>>> saw
>>>>> this. Not sure about the third warning (at kernel/cpu.c:315
>>>>> lockdep_assert_cpus_held+0x50/0x60) relat
the latest git master (b00d209) on an aarch64 server and
>>>> saw
>>>> this. Not sure about the third warning (at kernel/cpu.c:315
>>>> lockdep_assert_cpus_held+0x50/0x60) relates to irqchip or not, but
>>>> appended it
>>>> to here anyway jus
about the third warning (at kernel/cpu.c:315
>>> lockdep_assert_cpus_held+0x50/0x60) relates to irqchip or not, but appended
>>> it
>>> to here anyway just in case.
>>>
>>> [0.00] WARNING: CPU: 0 PID: 0 at
>>> drivers/irqchip/irq-gic-v3-its.c:169
50/0x60) relates to irqchip or not, but appended
> > it
> > to here anyway just in case.
> >
> > [ 0.000000] WARNING: CPU: 0 PID: 0 at
> > drivers/irqchip/irq-gic-v3-its.c:1696
> > its_init+0x588/0xb54
>
> It looks like EFI cannot manage to reserve t
just in case.
>
> [ 0.000000] WARNING: CPU: 0 PID: 0 at drivers/irqchip/irq-gic-v3-its.c:1696
> its_init+0x588/0xb54
It looks like EFI cannot manage to reserve the memory for your GIC
redistributors. Pretty annoying. At the same time, you have reported
other issues with the EFI reservati
Just booting up the latest git master (b00d209) on an aarch64 server and saw
this. Not sure about the third warning (at kernel/cpu.c:315
lockdep_assert_cpus_held+0x50/0x60) relates to irqchip or not, but appended it
to here anyway just in case.
[0.00] WARNING: CPU: 0 PID: 0 at drivers
13 matches
Mail list logo