All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 92836] amdgpu does not resume properly from suspend
Date: Thu, 05 Nov 2015 21:27:43 +0000	[thread overview]
Message-ID: <bug-92836-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 92836
           Summary: amdgpu does not resume properly from suspend
           Product: DRI
           Version: XOrg git
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/AMDgpu
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: David@WalkerStreet.info

My laptop does not resume properly after a suspend.  The problem seems to be
with the amdgpu kernel module; it's often accompanied by a long stream of dmesg
errors reported.  Here's a sampling:

 [ 1494.980561] amdgpu 0000:00:01.0: GPU fault detected: 146 0x0b020504
 [ 1494.980561] amdgpu 0000:00:01.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
0x00000000
 [ 1494.980561] amdgpu 0000:00:01.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x00000000
 [ 1494.980561] VM fault (0x00, vmid 0) at page 0, read from '' (0x00000000)
(0)
 [ 1494.995478] systemd-journald[498]: /dev/kmsg buffer overrun, some messages
lost.
 [ 1494.980561] amdgpu 0000:00:01.0: GPU fault detected: 146 0x0b0a4004
 [ 1494.980561] amdgpu 0000:00:01.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
0x00000000
 [ 1494.980561] amdgpu 0000:00:01.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x00000000
 [ 1494.980561] VM fault (0x00, vmid 0) at page 0, read from '' (0x00000000)
(0)
 [ 1494.995486] systemd-journald[498]: /dev/kmsg buffer overrun, some messages
lost.

Any ideas?  I'm running the 4.2.4-1-default under openSUSE Tumbleweed.  Here's
some hwinfo data:

 09: PCI 01.0: 0300 VGA compatible controller (VGA)              
  [Created at pci.366]
  Unique ID: vSkL.bMI5Iw7ysWD
  SysFS ID: /devices/pci0000:00/0000:00:01.0
  SysFS BusID: 0000:00:01.0
  Hardware Class: graphics card
  Model: "ATI Carrizo"
  Vendor: pci 0x1002 "ATI Technologies Inc"
  Device: pci 0x9874 "Carrizo"
  SubVendor: pci 0x103c "Hewlett-Packard Company"
  SubDevice: pci 0x80af 
  Revision: 0xc5
  Driver: "amdgpu"
  Driver Modules: "drm"
  Memory Range: 0xe0000000-0xefffffff (ro,non-prefetchable)
  Memory Range: 0xf0000000-0xf07fffff (ro,non-prefetchable)
  I/O Ports: 0xf000-0xf0ff (rw)
  Memory Range: 0xff700000-0xff73ffff (rw,non-prefetchable)
  Memory Range: 0xff740000-0xff75ffff (ro,non-prefetchable,disabled)
  IRQ: 47 (129945 events)
  Module Alias: "pci:v00001002d00009874sv0000103Csd000080AFbc03sc00i00"
  Driver Info #0:
    Driver Status: amdgpu is active
    Driver Activation Cmd: "modprobe amdgpu"
  Config Status: cfg=new, avail=yes, need=no, active=unknown

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

[-- Attachment #1.2: Type: text/html, Size: 3959 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-05 21:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-05 21:27 bugzilla-daemon [this message]
2015-11-05 22:34 ` [Bug 92836] amdgpu does not resume properly from suspend bugzilla-daemon
2015-11-05 22:35 ` bugzilla-daemon
2015-11-06 19:27 ` bugzilla-daemon
2015-11-06 19:27 ` bugzilla-daemon
2015-11-06 19:32 ` bugzilla-daemon
2015-11-06 20:09 ` bugzilla-daemon
2015-11-07 23:57 ` bugzilla-daemon
2015-11-20  3:03 ` bugzilla-daemon
2015-11-20  3:04 ` bugzilla-daemon
2015-11-20  3:04 ` bugzilla-daemon
2015-11-20  3:05 ` bugzilla-daemon
2015-11-20  3:13 ` bugzilla-daemon
2016-05-22 16:53 ` bugzilla-daemon
2016-05-22 19:06 ` bugzilla-daemon
2017-10-20 17:22 ` 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-92836-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.