All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 218696] DYTC frequency scaling deterioration and event spam
Date: Tue, 09 Apr 2024 14:30:58 +0000	[thread overview]
Message-ID: <bug-218696-215701-xKBD64573G@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218696-215701@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=218696

--- Comment #4 from Mark Pearson (mpearson-lenovo@squebb.ca) ---
Thanks! (for my reference - L14 G3 AMD)

I've created internal ticket LO-2964 and we'll see if we can reproduce and get
insight from the FW team as to what is happening.

If you have some of the ACPI events recorded (I assume you're running
acpi_listen?) that might be useful - just so we can show the FW team what
events are being sent. Hopefully we can reproduce the issue in the lab though.

Mark

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2024-04-09 14:30 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-08 19:32 [Bug 218696] New: DYTC frequency scaling deterioration bugzilla-daemon
2024-04-08 20:58 ` [Bug 218696] DYTC frequency scaling deterioration and event spam bugzilla-daemon
2024-04-09  9:14 ` bugzilla-daemon
2024-04-09  9:51 ` bugzilla-daemon
2024-04-09 13:26 ` bugzilla-daemon
2024-04-09 14:30 ` bugzilla-daemon [this message]
2024-04-10  0:34 ` bugzilla-daemon
2024-04-10 17:08 ` bugzilla-daemon
2024-04-13  5:23 ` bugzilla-daemon
2024-05-08  4:20 ` bugzilla-daemon
2024-05-14  0:58 ` bugzilla-daemon
2024-05-27 13:25 ` bugzilla-daemon
2024-05-27 17:20 ` bugzilla-daemon
2024-06-07 13:49 ` bugzilla-daemon
2024-06-08  7:02 ` bugzilla-daemon
2024-07-31 13:36 ` bugzilla-daemon
2024-08-04 16:03 ` bugzilla-daemon
2024-09-17 21:56 ` bugzilla-daemon
2024-10-10  2:45 ` bugzilla-daemon

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=bug-218696-215701-xKBD64573G@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=platform-driver-x86@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.