mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Marc Zyngier <marc.zyngier@arm.com>
To: Qian Cai <cai@gmx.us>
Cc: linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	Jason Cooper <jason@lakedaemon.net>
Subject: Re: WARNING: CPU: 0 PID: 0 at drivers/irqchip/irq-gic-v3-its.c
Date: Fri, 9 Nov 2018 13:50:40 +0000	[thread overview]
Message-ID: <b23b62b4-9ecb-8b76-57e5-d323cc9926ce@arm.com> (raw)
In-Reply-To: <trinity-e1d06dde-12e1-4e2a-8871-d6c5f4af9f51-1541766480902@msvc-mesg-gmx023>

On 09/11/18 12:28, Qian Cai wrote:
> 
> 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.

Do you also have this series[1] applied? I'd otherwise need your
configuration to try and reproduce it, as I can't manage to trigger it
on my own setup.

Thanks,

	M.

[1] https://www.spinics.net/lists/arm-kernel/msg685751.html
-- 
Jazz is not dead. It just smells funny...

  reply	other threads:[~2018-11-09 13:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-08 20:59 Qian Cai
2018-11-09 12:08 ` Marc Zyngier
2018-11-09 12:28   ` Qian Cai
2018-11-09 13:50     ` Marc Zyngier [this message]
2018-11-09 15:28       ` Qian Cai
2018-11-09 15:38         ` Marc Zyngier
2018-11-09 15:52           ` Qian Cai
2018-11-09 16:06             ` Marc Zyngier
2018-11-09 17:28               ` Sudeep Holla
2018-11-09 17:41                 ` Marc Zyngier
2018-11-09 18:41                   ` Qian Cai
2018-11-12  8:39                     ` Marc Zyngier
2018-12-02  4:16                       ` Qian Cai

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b23b62b4-9ecb-8b76-57e5-d323cc9926ce@arm.com \
    --to=marc.zyngier@arm.com \
    --cc=ard.biesheuvel@linaro.org \
    --cc=cai@gmx.us \
    --cc=jason@lakedaemon.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®