From: Borislav Petkov <bp@alien8.de>
To: Johnathan Smithinovic <johnathan.smithinovic@gmx.at>
Cc: tglx@linutronix.de, mingo@redhat.com, x86@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: CPU hotplug leads to NULL pointer dereference with RAPL enabled on AMD 2990WX
Date: Mon, 4 Jan 2021 10:50:10 +0100 [thread overview]
Message-ID: <20210104095010.GA32151@zn.tnic> (raw)
In-Reply-To: <151f54e9-5b45-5624-681c-754224b6c263@gmx.at>
On Mon, Jan 04, 2021 at 12:02:44AM +0100, Johnathan Smithinovic wrote:
> CPU hotplug leads to NULL pointer dereference with RAPL enabled on AMD 2990WX
>
>
> When hot-plugging CPUs (e.g. manually or on suspend) I get a NULL
> pointer dereference in rapl_cpu_offline() for CPUs 16 and 24.
> It *seems* to me that this has to do with commit
> 700d098acec5271161606f3c0086b71695ea2ef8
> ("x86/CPU/AMD: Save AMD NodeId as cpu_die_id").
> When reverting said commit hotplug works again.
Yeah, known issue and I'm working on it.
Thx for reporting.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2021-01-04 9:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-03 23:02 Johnathan Smithinovic
2021-01-04 9:50 ` Borislav Petkov [this message]
2021-01-04 10:49 ` Borislav Petkov
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=20210104095010.GA32151@zn.tnic \
--to=bp@alien8.de \
--cc=johnathan.smithinovic@gmx.at \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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®