From: Borislav Petkov <bp@alien8.de>
To: Dominik Brodowski <linux@dominikbrodowski.net>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
Tony Luck <tony.luck@intel.com>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org
Subject: Re: unchecked MSR access error in throttle_active_work()
Date: Thu, 28 Nov 2019 10:44:19 +0100 [thread overview]
Message-ID: <20191128094419.GB17745@zn.tnic> (raw)
In-Reply-To: <20191128085447.GA3682@owl.dominikbrodowski.net>
On Thu, Nov 28, 2019 at 09:54:47AM +0100, Dominik Brodowski wrote:
> On most recent mainline kernels (such as 5.5-rc0 up to a6ed68d6468b), I see
> the following output in dmesg during startup:
>
> [ 78.016676] unchecked MSR access error: WRMSR to 0x19c (tried to write 0x00000000880f3a80) at rIP: 0xffffffff84ab5742 (throttle_active_work+0xf2/0x230)
> [ 78.016686] Call Trace:
> [ 78.016694] process_one_work+0x247/0x590
> [ 78.016703] worker_thread+0x50/0x3b0
> [ 78.016710] kthread+0x10a/0x140
> [ 78.016715] ? process_one_work+0x590/0x590
> [ 78.016735] ? kthread_park+0x90/0x90
> [ 78.016740] ret_from_fork+0x3a/0x50
>
> Any clues?
Most likely
f6656208f04e ("x86/mce/therm_throt: Optimize notifications of thermal throttle")
I guess we're missing some X86_FEATURE_ check for that MSR to exist.
Adding more people to Cc.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2019-11-28 9:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-28 8:54 unchecked MSR access error in throttle_active_work() Dominik Brodowski
2019-11-28 9:44 ` Borislav Petkov [this message]
2019-11-28 10:29 ` Dominik Brodowski
2019-11-28 14:51 ` Srinivas Pandruvada
2019-11-28 18:56 ` Dominik Brodowski
2019-11-28 19:12 ` Borislav Petkov
2019-11-28 19:47 ` Dominik Brodowski
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=20191128094419.GB17745@zn.tnic \
--to=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=tony.luck@intel.com \
--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