linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 209069] New: CPU stuck at 800 MHz at any load
Date: Sat, 29 Aug 2020 14:51:11 +0000	[thread overview]
Message-ID: <bug-209069-137361@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 209069
           Summary: CPU stuck at 800 MHz at any load
           Product: Power Management
           Version: 2.5
    Kernel Version: 5.8.5
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: cpufreq
          Assignee: linux-pm@vger.kernel.org
          Reporter: tg@gmplib.org
        Regression: No

Environment 1:
  OS:     GNU/Linux/Xen Gentoo 17.1 (ker=5.8.5 xen=4.12.3)
  mbd:    Supermicro X10SLH-F-O S1150 µATX (BIOS 3.3 2020-06-13)
  cpu:    Intel HWL X4 3600MHz (Xeon E3-1271v3, ECC)
  memory: 8192MB SDRAM DDR3L-1600 ECC (Samsung M391B1G73QH0-YK0Q)
  memory: 8192MB SDRAM DDR3L-1600 ECC (Samsung M391B1G73QH0-YK0Q)
  memory: 8192MB SDRAM DDR3L-1600 ECC (Samsung M391B1G73QH0-YK0Q)
  memory: 8192MB SDRAM DDR3L-1600 ECC (Samsung M391B1G73QH0-YK0Q)
  disk:   SATA SSD 2.5" 120GB Samsung SM863
  case:   Supermicro CSE-510T-203B

Environment 2. Almost identical, but with this cpu:
  cpu:    Intel BWL X4 3400MHz LLC=6M+128M (Xeon E3-1285Lv4)

I upgraded from 5.4.48 to 5.8.x for various versions of x to finally reach x =
5. Now, the systems get stuck at what is displayed as 800 MHz in /proc/cpuinfo.

When booted to run Xen, the problem goes away. When booting the (Xen
Dom0-capable) kernel without Xen, the clock gets stuck at 800 MHz at any load.

It's certainly not just a problem with /proc/cpuinfo's displayed frequency; the
systems are really, really sluggish.

A similarly configured Skylake system does NOT exhibit the same problem. (The
motherboard of that system is Supermicro X11SSM.) Similarly configured Sandy
Bridge and Westmere systems also do not exhibit this problem.

-- 
You are receiving this mail because:
You are the assignee for the bug.

             reply	other threads:[~2020-08-29 14:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-29 14:51 bugzilla-daemon [this message]
2020-08-29 15:00 ` [Bug 209069] CPU stuck at 800 MHz at any load bugzilla-daemon
2020-08-29 15:23 ` bugzilla-daemon
2020-08-29 17:25 ` bugzilla-daemon
2020-08-29 18:07 ` bugzilla-daemon
2020-09-02 18:36 ` bugzilla-daemon
2020-09-05 14:33 ` bugzilla-daemon
2020-09-05 16:01 ` bugzilla-daemon
2020-09-06 18:37 ` bugzilla-daemon
2021-03-21 15:48 ` bugzilla-daemon
2021-04-21  2:16 ` [Bug 209069] CPU stuck at 800 MHz at any load - Xeon E3-1271v3 HSW bugzilla-daemon
2021-04-21  2:16 ` 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-209069-137361@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-pm@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).