[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <trinity-e1d06dde-12e1-4e2a-8871-d6c5f4af9f51-1541766480902@msvc-mesg-gmx023>
Date: Fri, 9 Nov 2018 13:28:00 +0100
From: "Qian Cai" <cai@....us>
To: "Marc Zyngier" <marc.zyngier@....com>
Cc: linux-kernel@...r.kernel.org,
"Thomas Gleixner" <tglx@...utronix.de>,
"Ard Biesheuvel" <ard.biesheuvel@...aro.org>,
"Jason Cooper" <jason@...edaemon.net>
Subject: Re: WARNING: CPU: 0 PID: 0 at drivers/irqchip/irq-gic-v3-its.c
On 11/9/18 at 7:08 AM, Marc Zyngier wrote:
> [+Ard]
>
> 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) 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 the memory for your GIC
> redistributors. Pretty annoying. At the same time, you have reported
> other issues with the EFI reservation mechanism, such as:
>
> https://lore.kernel.org/patchwork/patch/1008413/
>
> for which you have given a "Tested-by:". Is that related?
No, I don’t think so. Those warnings are still there even after applied the patch above.
Powered by blists - more mailing lists