All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 92865] MSI R7 370 Armor 2X dpm issues and errors
Date: Mon, 09 Nov 2015 07:23:15 +0000	[thread overview]
Message-ID: <bug-92865-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 92865
           Summary: MSI R7 370 Armor 2X dpm issues and errors
           Product: DRI
           Version: unspecified
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: major
          Priority: medium
         Component: DRM/Radeon
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: mrader3940@gmail.com

Long story short: sent a patch to Alex Deucher, the patch got submitted and
it's in 4.3 kernel now. However, I get a black screen after system startup, or
it can happen randomly, especially after bug screen updates. I'm on freshly
installed Arch Linux 64-bit UEFI. I think the issue is connected with the
recent commit to the si_dpm.c, maybe there are ID conflicts. Here's a link to
that new patch:
https://github.com/torvalds/linux/commit/2b02ec79004388a8c65e227bc289ed891b5ac8c6

And link to my patch:
https://github.com/torvalds/linux/commit/e78654799135a788a941bacad3452fbd7083e518

Maybe we should make some identification code in that file? Oh, I'll also try
to compile the 4.3 kernel with that Asus line removed. Any ideas other than
those above?

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

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

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

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

             reply	other threads:[~2015-11-09  7:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-09  7:23 bugzilla-daemon [this message]
2015-11-09  7:26 ` [Bug 92865] MSI R7 370 Armor 2X dpm issues and errors bugzilla-daemon
2015-11-09  8:31 ` bugzilla-daemon
2015-11-09  8:31 ` bugzilla-daemon
2015-11-09  8:32 ` bugzilla-daemon
2015-11-09 10:36 ` bugzilla-daemon
2015-11-09 10:39 ` bugzilla-daemon
2015-11-09 10:39 ` bugzilla-daemon
2015-11-09 18:04 ` bugzilla-daemon
2015-11-09 18:04 ` [Bug 92865] MSI R7 370 Armor 2X dpm issues bugzilla-daemon
2015-11-09 19:34 ` bugzilla-daemon
2015-11-09 19:39 ` bugzilla-daemon
2015-11-09 19:40 ` bugzilla-daemon
2015-11-10 15:01 ` bugzilla-daemon
2015-11-22  9:36 ` bugzilla-daemon
2015-11-27  8:12 ` 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-92865-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.