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 120561] powernow_k8 causes kernel panic during block device write access
Date: Tue, 02 Jul 2019 22:21:56 +0000	[thread overview]
Message-ID: <bug-120561-137361-0AcZvXB5la@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-120561-137361@https.bugzilla.kernel.org/>

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

kr@sognnes.no changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |CODE_FIX

--- Comment #3 from kr@sognnes.no ---
It seems this bug was caused by the kernel misidentifying the number of
available PowerNow states on certain AMD CPUs, and was thus very CPU-specific. 

As of right now, none of the currently supported kernels (4.4.184, 4.9.184,
4.14.131, 4.19.56, and 5.1.15) have any issues with the particular AMD CPU on
the system that originally exhibited the problem.

The newer kernels all report significantly fewer power states, and the ondemand
governor can now be enabled without issue.

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

      parent reply	other threads:[~2019-07-03  0:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-120561-137361@https.bugzilla.kernel.org/>
2016-06-20  3:35 ` [Bug 120561] powernow_k8 causes kernel panic during block device write access bugzilla-daemon
2019-07-02 22:21 ` bugzilla-daemon [this message]

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-120561-137361-0AcZvXB5la@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).