All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 106194] AMD Fury X system freeze on kernel 4.17rc2
Date: Mon, 23 Apr 2018 17:18:13 +0000	[thread overview]
Message-ID: <bug-106194-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 106194
           Summary: AMD Fury X system freeze on kernel 4.17rc2
           Product: DRI
           Version: unspecified
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/AMDgpu
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: harlemsquirrel@gmail.com

Created attachment 139018
  --> https://bugs.freedesktop.org/attachment.cgi?id=139018&action=edit
dmesg output running kernel 4.17-rc2

I left my computer on over night. After I noticed the system was frozen just
now, I rebooted to found these log entries.

5:06:46 AM
RIP: dm_update_crtcs_state+0x347/0x3c0 [amdgpu] RSP: ffffb2560bc37b10

5:06:46 AM
kernel BUG at drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:4700!

Software versions:
  OpenGL version string: 3.0 Mesa 18.0.1


CPU hardware:
  x86_64
  AMD Ryzen 7 1800X Eight-Core Processor
        Max Speed: 4100 MHz
        Current Speed: 3600 MHz


Memory:
        Speed: 3200 MT/s
              total        used        free      shared  buff/cache   available
Mem:           15Gi       3.0Gi        11Gi        67Mi       1.5Gi        12Gi
Swap:         7.8Gi          0B       7.8Gi


GPU hardware:
  OpenGL renderer string: AMD Radeon (TM) R9 Fury Series (FIJI / DRM 3.23.0 /
4.15.15-1-ARCH, LLVM 6.0.0)
  0b:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc.
[AMD/ATI] Fiji [Radeon R9 FURY / NANO Series] [1002:7300] (rev c8)
0c:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc.
[AMD/ATI] Ellesmere [Radeon RX 470/480/570/580] [1002:67df] (rev e7)


Motherboard:
  ASUSTeK COMPUTER INC.
  CROSSHAIR VI HERO
  BIOS Version: 3008


Storage:
Smart Log for NVME device:nvme0 namespace-id:ffffffff

I've attached the relevent dmesg output.

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

[-- Attachment #1.2: Type: text/html, Size: 3499 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-04-23 17:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-23 17:18 bugzilla-daemon [this message]
2018-04-23 17:21 ` [Bug 106194] AMDGPU RIP: dm_update_crtcs_state on kernel 4.17rc2 bugzilla-daemon
2018-04-25  6:34 ` bugzilla-daemon
2018-04-28 15:13 ` bugzilla-daemon
2018-04-28 15:15 ` bugzilla-daemon
2018-04-28 15:19 ` bugzilla-daemon
2018-04-28 17:24 ` bugzilla-daemon
2018-04-28 20:14 ` bugzilla-daemon
2018-04-28 21:12 ` bugzilla-daemon
2018-04-29  5:05 ` bugzilla-daemon
2018-05-02 16:49 ` bugzilla-daemon
2018-05-07  0:41 ` bugzilla-daemon
2018-05-08  5:26 ` bugzilla-daemon
2018-05-09 15:41 ` bugzilla-daemon
2018-05-16 20:42 ` 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-106194-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.