All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 204609] amdgpu: powerplay failed send message
Date: Mon, 16 Dec 2019 23:22:37 +0000	[thread overview]
Message-ID: <bug-204609-2300-3CO3VEjS6q@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-204609-2300@https.bugzilla.kernel.org/>

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

Błażej Szczygieł (spaz16@wp.pl) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |spaz16@wp.pl

--- Comment #5 from Błażej Szczygieł (spaz16@wp.pl) ---
Created attachment 286329
  --> https://bugzilla.kernel.org/attachment.cgi?id=286329&action=edit
kernel5.4 powerplay add mutex

Also the same as: https://gitlab.freedesktop.org/drm/amd/issues/900

In kernel 5.4.3 run a few times `watch -n 0.1 cat
/sys/class/drm/card0/device/hwmon/hwmon*/fan1_input` in parallel and you'll
have a lot of warning and finally system freeze.

In kernel 5.5-rc2 powerplay warnings and finally system freeze can happen when
sensors are read and screen mode is changed (like screen resolution change,
etc).

In my opinion a lot of powerplay issues are caused by missing mutexes between
kernel and user space. I prepared a very simple kernel 5.4 patch which allows
me to use fan monitor, but probably there are still some missing mutexes there.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2019-12-16 23:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-18  7:15 [Bug 204609] New: amdgpu: powerplay failed send message bugzilla-daemon
2019-10-13 10:38 ` [Bug 204609] " bugzilla-daemon
2019-11-12  0:07 ` bugzilla-daemon
2019-11-12  0:08 ` bugzilla-daemon
2019-12-02 14:39 ` bugzilla-daemon
2019-12-16 23:22 ` bugzilla-daemon [this message]
2020-04-11  5:40 ` bugzilla-daemon
2020-07-03  8:59 ` bugzilla-daemon
2020-07-03  8:59 ` bugzilla-daemon
2020-08-15 16:16 ` bugzilla-daemon
2020-08-15 16:17 ` 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-204609-2300-3CO3VEjS6q@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.freedesktop.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.