All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 106597] [vga_switcheroo] commit 07f4f97d7b4bf325d9f558c5b58230387e4e57e0 breaks dpm on Alienware 15R3
Date: Mon, 21 May 2018 20:36:17 +0000	[thread overview]
Message-ID: <bug-106597-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1951 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=106597

            Bug ID: 106597
           Summary: [vga_switcheroo] commit
                    07f4f97d7b4bf325d9f558c5b58230387e4e57e0 breaks dpm on
                    Alienware 15R3
           Product: DRI
           Version: DRI git
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/other
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: taijian@posteo.de

Over on Bug 104064 Alex Deucher and Harry Wentland had heroically assisted me
in finally fixing dGPU auto-suspend on my HG laptop (Intel iGPU + AMD dGPU). I
was really looking forward to their work going mainline in 4.16 and me being
able to enjoy my newly working system. Unfortunately, some other commit into
4.16 broke things again. After overcoming my initial frustration and doing some
research, I was now able to track this down to the work by Lukas Wunner on
vga_switcheroo.

I am doing my debugging with drm-next-4.18-wip over at
https://cgit.freedesktop.org/~agd5f/linux because 4.16 & 4.17 have one other
bug that 4.18 doesn't (Bug 105760) that prevent me from using those. Simply
compiling drm-next-4.18-wip will result in a kernel that cannot dynamically
power down the dGPU. It remains up regardless of use status and draws power.

Now if I revert commits 07f4f97d7b4bf325d9f558c5b58230387e4e57e0,
b67ae78efae0d5be5d9c7a507e67cd02971b32e1 and
2b4f44eec2be2688511c2b617d0e1b4f94c45ba4 and recompile, then the resulting
kernel will once again fully power down my dGPU when it is not in use. 

Now, if I can assist in any way with further debugging or testing patches to
figure out what specifically went wrong with those patches, I'd be happy to do
so, just let me know!

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

[-- Attachment #1.2: Type: text/html, Size: 3757 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2018-05-21 20:36 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-21 20:36 bugzilla-daemon [this message]
2018-05-21 20:59 ` [Bug 106597] [vga_switcheroo] commit 07f4f97d7b4bf325d9f558c5b58230387e4e57e0 breaks dpm on Alienware 15R3 bugzilla-daemon
2018-05-21 21:17 ` bugzilla-daemon
2018-05-21 21:26 ` bugzilla-daemon
2018-05-21 21:34 ` bugzilla-daemon
2018-05-21 21:47 ` bugzilla-daemon
2018-05-21 22:03 ` bugzilla-daemon
2018-05-21 22:43 ` bugzilla-daemon
2018-05-22  8:16 ` bugzilla-daemon
2018-05-22  8:18 ` bugzilla-daemon
2018-05-22  8:19 ` bugzilla-daemon
2018-05-22  8:22 ` bugzilla-daemon
2018-05-22  9:03 ` bugzilla-daemon
2018-05-22 20:40 ` bugzilla-daemon
2018-05-22 21:18 ` bugzilla-daemon
2018-05-22 21:49 ` bugzilla-daemon
2018-05-23  6:54 ` bugzilla-daemon
2018-05-23  9:59 ` bugzilla-daemon
2018-05-23 10:21 ` bugzilla-daemon
2018-05-23 12:19 ` bugzilla-daemon
2018-05-23 23:12 ` bugzilla-daemon
2018-05-24  8:56 ` bugzilla-daemon
2018-05-24 10:01 ` bugzilla-daemon
2018-05-24 10:04 ` bugzilla-daemon
2018-05-24 10:13 ` bugzilla-daemon
2018-05-24 10:28 ` bugzilla-daemon
2018-05-24 13:07 ` bugzilla-daemon
2018-05-24 15:34 ` bugzilla-daemon
2018-05-24 15:43 ` bugzilla-daemon
2018-05-24 16:15 ` bugzilla-daemon
2018-05-24 16:40 ` bugzilla-daemon
2018-05-24 16:40 ` bugzilla-daemon
2018-05-24 17:18 ` bugzilla-daemon
2018-05-24 17:42 ` bugzilla-daemon
2018-05-24 21:08 ` 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-106597-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.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.