mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: srinivas pandruvada <srinivas.pandruvada@linux.intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
Cc: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	the arch/x86 maintainers <x86@kernel.org>
Subject: Re: thermal throttling on xps13: unchecked MSR access error
Date: Tue, 13 Dec 2022 18:12:51 -0800	[thread overview]
Message-ID: <34d950e1e11dc91281adf3d2e8bb52645b4a7d6e.camel@linux.intel.com> (raw)
In-Reply-To: <CAHk-=wgDEq2LYW6rnfQXmEOSfF8ECPkuwjJ3CR7aC4N2zuRLWQ@mail.gmail.com>

Hi Linus,

Sorry about the issue.

On Tue, 2022-12-13 at 16:35 -0800, Linus Torvalds wrote:
> Hmm.
> 
> I don't think I've seen this before on my trusty old x86 laptop (XPS
> 13 9380 - it's a few years old)
> 
>     unchecked MSR access error: WRMSR to 0x1b1
>       (tried to write 0x0000000004000aa8)
>       at rIP: 0xffffffff8b8559fe (throttle_active_work+0xbe/0x1b0)
> 
You got a (PROCHOT#) throttling event.
 
> I'm blaming one of
> 
>   930d06bf071a ("thermal: intel: Protect clearing of thermal status
> bits")
>   6fe1e64b6026 ("thermal: intel: Prevent accidental clearing of HFI
> status")
> 
This is to blame. I am able to reproduce on an old system.

I sent a patch " thermal: intel: Don't set HFI status bit to 1"

Please check.

Thanks,
Srinivas

> with no real reason apart from being the last commit to touch that
> function, but also when it started happening.
> 
> The first kernel I see this for is 6.1.0-03225-g764822972d64, but
> honestly, it's possible that it has happened before too, and the real
> issue is that the machine just happened to be hot and throttling at
> bootup and/or I just didn't notice.
> 
> The CPU in this thing is a
> 
>   Intel(R) Core(TM) i7-8565U CPU @ 1.80GHz
> 
> which hopefully makes somebody go "Ahh, yes, I missed that case".
> 
> I don't *think* the MSR access checking has changed, but maybe it
> did,
> and I'm barking up the wrong tree.
> 
> Anybody?
> 
>                  Linus


  reply	other threads:[~2022-12-14  2:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-14  0:35 Linus Torvalds
2022-12-14  2:12 ` srinivas pandruvada [this message]
2022-12-14  3:17   ` Linus Torvalds

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=34d950e1e11dc91281adf3d2e8bb52645b4a7d6e.camel@linux.intel.com \
    --to=srinivas.pandruvada@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael.j.wysocki@intel.com \
    --cc=ricardo.neri-calderon@linux.intel.com \
    --cc=torvalds@linux-foundation.org \
    --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®