All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 219556] New: AMDGPU monitoring is broken
Date: Wed, 04 Dec 2024 07:39:04 +0000	[thread overview]
Message-ID: <bug-219556-2300@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 219556
           Summary: AMDGPU monitoring is broken
           Product: Drivers
           Version: 2.5
    Kernel Version: 6.13-rc1
          Hardware: AMD
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: i.r.e.c.c.a.k.u.n+bugzilla.kernel.org@gmail.com
        Regression: Yes
           Bisected 831c1926ee728c3e747255f7c0f434762e8e863d
         commit-id:

In 6.13-rc1, AMDGPU monitoring is broken. Many sysfs knobs simply output
nothing. For example:

# cd /sys/class/drm/card1/device
# <gpu_busy_percent
# <pp_dpm_sclk
# <pp_od_clk_voltage
# <hwmon/hwmon6/temp1_input

Otherwise the kernel log seems to be totally fine and GPU itself appears to
work normally.

I tried AMD GPUs of different generations, so it doesn't appear to be
series/model specific.

I have done a bisection though.

first bad commit: [831c1926ee728c3e747255f7c0f434762e8e863d] Merge tag
'uml-for-linus-6.13-rc1' of
git://git.kernel.org/pub/scm/linux/kernel/git/uml/linux

-- 
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:[~2024-12-04  7:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-04  7:39 bugzilla-daemon [this message]
2024-12-04 10:20 ` [Bug 219556] AMDGPU monitoring is broken bugzilla-daemon
2024-12-04 10:39 ` 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-219556-2300@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@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.