mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Marc Zyngier <maz@kernel.org>
Cc: Marek Szyprowski <m.szyprowski@samsung.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	'Linux Samsung SOC' <linux-samsung-soc@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	John Garry <john.garry@huawei.com>,
	Xiongfeng Wang <wangxiongfeng2@huawei.com>,
	David Decotigny <ddecotig@google.com>
Subject: Re: [PATCH v3 2/3] genirq: Always limit the affinity to online CPUs
Date: Wed, 20 Apr 2022 11:42:36 +0200	[thread overview]
Message-ID: <1c3cb265-2497-537d-3c7b-ca4766775b46@linaro.org> (raw)
In-Reply-To: <87mtgg9jok.wl-maz@kernel.org>

On 20/04/2022 11:40, Marc Zyngier wrote:
> It was picked up by Thomas and pushed out into tip, which is pulled by
> -next:
> 
> maz@hot-poop:~/arm-platforms$ git describe --contains c48c8b829d2b966a6649827426bcdba082ccf922
> next-20220420~51^2~3^2
> 
> So it definitely is in today's -next.
> 
>> Instead of silent fail there is now "Unable to handle kernel paging
>> request at virtual address f0836644", so it is slightly different.
>>
>> See the dmesg:
>> https://krzk.eu/#/builders/21/builds/3542/steps/15/logs/serial0
> 
> This looks completely unrelated:
> 
> [   10.382010] Unable to handle kernel paging request at virtual address f0836644
> [   10.388597] [f0836644] *pgd=41c83811, *pte=00000000, *ppte=00000000
> [   10.394482] Internal error: Oops: 807 [#1] PREEMPT SMP ARM
> [   10.399567] Modules linked in:
> [   10.402583] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 5.18.0-rc3-next-20220420 #2
> [   10.410060] Hardware name: Samsung Exynos (Flattened Device Tree)
> [   10.416106] PC is at cpu_ca15_set_pte_ext+0x4c/0x58
> [   10.420952] LR is at handle_pte_fault+0x218/0x260
> [   10.425631] pc : [<c011d588>]    lr : [<c02ab188>]    psr: 40000113
> [   10.431874] sp : f0835df0  ip : f0835e5c  fp : 00000081
> [   10.437069] r10: c0f2eafc  r9 : c1d31000  r8 : 00000000
> [   10.442268] r7 : c1d58000  r6 : 00000081  r5 : befffff6  r4 : f0835e24
> [   10.448773] r3 : 00000000  r2 : 00000000  r1 : 00000040  r0 : f0835e44
> [   10.455273] Flags: nZcv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment none
> [   10.462381] Control: 10c5387d  Table: 4000406a  DAC: 00000051
> 
> This is a crash in cpu_ca15_set_pte_ext() when populating the
> userspace page tables, which seems unrelated to interrupt affinity.
> 
> I suggest you bisect this to find the actual problem.

Thanks for checking.


Best regards,
Krzysztof

  reply	other threads:[~2022-04-20  9:42 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-05 18:50 [PATCH v3 0/3] genirq: Managed affinity fixes Marc Zyngier
2022-04-05 18:50 ` [PATCH v3 1/3] genirq/msi: Shutdown managed interrupts with unsatifiable affinities Marc Zyngier
2022-04-10 19:13   ` [tip: irq/core] " tip-bot2 for Marc Zyngier
2022-04-05 18:50 ` [PATCH v3 2/3] genirq: Always limit the affinity to online CPUs Marc Zyngier
2022-04-10 19:12   ` [tip: irq/core] " tip-bot2 for Marc Zyngier
     [not found]   ` <CGME20220413145922eucas1p2dc46908354f4d2b48db79978d086a838@eucas1p2.samsung.com>
2022-04-13 14:59     ` [PATCH v3 2/3] " Marek Szyprowski
2022-04-13 17:26       ` Marc Zyngier
2022-04-14  9:09         ` Marek Szyprowski
2022-04-14 10:35           ` Marc Zyngier
2022-04-14 11:08             ` Marek Szyprowski
2022-04-20  9:13               ` Krzysztof Kozlowski
2022-04-20  9:40                 ` Marc Zyngier
2022-04-20  9:42                   ` Krzysztof Kozlowski [this message]
2022-04-20  9:47                 ` Marek Szyprowski
2022-04-20  9:50                   ` Krzysztof Kozlowski
2022-04-14 10:49         ` Thomas Gleixner
2022-04-14 14:14       ` [tip: irq/core] genirq: Take the proposed affinity at face value if force==true tip-bot2 for Marc Zyngier
2022-04-05 18:50 ` [PATCH v3 3/3] irqchip/gic-v3: Always trust the managed affinity provided by the core code Marc Zyngier
2022-04-10 19:12   ` [tip: irq/core] " tip-bot2 for Marc Zyngier
2022-04-07 17:29 ` [PATCH v3 0/3] genirq: Managed affinity fixes John Garry
2022-04-08  1:02   ` Xiongfeng Wang

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=1c3cb265-2497-537d-3c7b-ca4766775b46@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=ddecotig@google.com \
    --cc=john.garry@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=maz@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=wangxiongfeng2@huawei.com \
    /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®