From: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
To: "Naveen N. Rao" <naveen.n.rao@linux.ibm.com>,
Thadeu Lima de Souza Cascardo <cascardo@canonical.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: coherency issue observed after hotplug on POWER8
Date: Thu, 21 Oct 2021 17:01:42 +0200 [thread overview]
Message-ID: <42491f5a-593b-535c-b28c-41fbdbb43f99@canonical.com> (raw)
In-Reply-To: <1632500323.sp1p885nv8.naveen@linux.ibm.com>
On 24/09/2021 19:17, Naveen N. Rao wrote:
> Hi Cascardo,
> Thanks for reporting this.
>
>
> Thadeu Lima de Souza Cascardo wrote:
>> Hi, there.
>>
>> We have been investigating an issue we have observed on POWER8 POWERNV systems.
>> When running the kernel selftests reuseport_bpf_cpu after a CPU hotplug, we see
>> crashes, in different forms. [1]
>
> Just to re-confirm: you are only seeing this on P8 powernv, and not in a
> P8 guest/LPAR? I haven't been able to reproduce this on a firestone --
> can you share more details about your power8 machine?
>
> Also, do you only see this with ubuntu kernels, or are you also able to
> reproduce this with the upstream tree?
Let me just covert this part of your email:
Upstream trees (5.11, 5.13, 5.14). See also:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1927076/comments/28
I could not reproduce it on Power8 LPAR. Neither on Power9 QEMU guest.
Reproduced on few machines:
IBM, POWER8NVL, 8335-GTB
POWER8, 8001-22C and 8335-GTA
lspcpu for the last one:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1927076/comments/15
Best regards,
Krzysztof
prev parent reply other threads:[~2021-10-21 15:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-21 21:03 coherency issue observed after hotplug on POWER8 Thadeu Lima de Souza Cascardo
2021-09-24 17:17 ` Naveen N. Rao
2021-10-21 15:01 ` Krzysztof Kozlowski [this message]
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=42491f5a-593b-535c-b28c-41fbdbb43f99@canonical.com \
--to=krzysztof.kozlowski@canonical.com \
--cc=cascardo@canonical.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=naveen.n.rao@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).