All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 216163] New: cstates: intel_idle.max_cstate=4 required to eliminate flickering of the display on the laptop model 3Logic Group Graviton N15i-K2
Date: Wed, 22 Jun 2022 08:28:39 +0000	[thread overview]
Message-ID: <bug-216163-215701@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 216163
           Summary: cstates: intel_idle.max_cstate=4 required to eliminate
                    flickering of the display on the laptop model 3Logic
                    Group Graviton N15i-K2
           Product: Drivers
           Version: 2.5
    Kernel Version: v5.18
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Platform_x86
          Assignee: drivers_platform_x86@kernel-bugs.osdl.org
          Reporter: kovalev@altlinux.org
        Regression: No

Created attachment 301249
  --> https://bugzilla.kernel.org/attachment.cgi?id=301249&action=edit
Limiting the list of states for the model processor INTEL_FAM6_KABYLAKE_L

After booting the system almost immediately (it takes less than 1 minute),
there are short-term shutdowns of the display (up to 3 seconds). The problem
disappears if I load the kernel with the parameter intel_idle.max_cstate=4.

While debugging the kernel, I determined that the processor model ID is 0x8E,
defined a macro in the header file /arch/x86/include/asm/intel-family.h :

...
#define INTEL_FAM6_KABYLAKE_L           0x8E    /* Sky Lake             */
/*                 AMBERLAKE_L          0x8E       Sky Lake -- s: 9     */
/*                 COFFEELAKE_L         0x8E       Sky Lake -- s: 10    */
/*                 WHISKEYLAKE_L        0x8E       Sky Lake -- s: 11,12 */
...

And I created a patch with a reduced number of states (4 states) of downtime
for this model, which works successfully.

I am attaching a patch and asking you to consider the feasibility of such a
solution.

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

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

             reply	other threads:[~2022-06-22  8:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-22  8:28 bugzilla-daemon [this message]
2022-06-22  8:31 ` [Bug 216163] cstates: intel_idle.max_cstate=4 required to eliminate flickering of the display on the laptop model 3Logic Group Graviton N15i-K2 bugzilla-daemon
2022-06-22  8:32 ` bugzilla-daemon
2022-06-22  8:33 ` bugzilla-daemon
2022-06-22  8:36 ` bugzilla-daemon
2022-06-22  9:00 ` 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-216163-215701@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.