All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 101714] Complete System Freeze (displaycore staging 4.11)
Date: Fri, 07 Jul 2017 10:07:04 +0000	[thread overview]
Message-ID: <bug-101714-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 101714
           Summary: Complete System Freeze (displaycore staging 4.11)
           Product: DRI
           Version: unspecified
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/AMDgpu
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: m.mcnutt@gmail.com

Created attachment 132490
  --> https://bugs.freedesktop.org/attachment.cgi?id=132490&action=edit
backtrace generated by Fedora Problem reporting

Using Mystro256's DC Staging Kerenel for Fedora 26. When I have compositing
turned on I get a complete system freeze, machine can not even be ssh'd into
while frozen.

WARNING: CPU: 2 PID: 1504 at
drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_surface.c:158
dc_surface_retain+0x34/0x50 [amdgpu]

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

[-- Attachment #1.2: Type: text/html, Size: 2488 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:[~2017-07-07 10:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-07 10:07 bugzilla-daemon [this message]
2017-07-07 10:08 ` [Bug 101714] Complete System Freeze (displaycore staging 4.11) bugzilla-daemon
2017-12-23  1:37 ` 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-101714-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.