All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 110574] System hang after screen power saving
Date: Wed, 01 May 2019 18:56:49 +0000	[thread overview]
Message-ID: <bug-110574-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 110574
           Summary: System hang after screen power saving
           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: number048@gmail.com

Created attachment 144122
  --> https://bugs.freedesktop.org/attachment.cgi?id=144122&action=edit
dmesg

After updating to Xubuntu 19.04 I started having problems with the screen saver
feature. After a request for the monitor to go into power saving mode I am
unable to recover the system. When the monitor turns on again I get the last
image shown but I cannot move the cursor, nothing on the screen is moving,
everything is frozen and I cannot use ssh to access the machine.

Later I discovered that I could access the computer using ssh before I let the
monitor enter power saving mode and I was then able to save a copy of dmesg.

As soon as the monitor is turned off by the system the crash happens:

[ 2674.166451] general protection fault: 0000 [#1] SMP NOPTI
...
[ 2674.166530] RIP: 0010:dce110_vblank_set+0x4f/0xa0 [amdgpu]

with the last 5 entries of the call trace:

[ 2674.166624]  dal_irq_service_set+0x4c/0x90 [amdgpu]
[ 2674.166687]  dc_interrupt_set+0x24/0x30 [amdgpu]
[ 2674.166753]  dm_enable_vblank+0x2a/0x40 [amdgpu]
[ 2674.166768]  drm_vblank_enable+0xe2/0x130 [drm]
[ 2674.166781]  drm_vblank_get+0x92/0xb0 [drm]

I was using the Oibaf PPA both before and after I updated to Xubuntu 19.04.
I tried to use the kernel v5.1-rc7 from the Ubuntu mainline:
https://kernel.ubuntu.com/~kernel-ppa/mainline/

My linux command line:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash radeon.cik_support=0
amdgpu.cik_support=1 amdgpu.dc=1"

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

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

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

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

             reply	other threads:[~2019-05-01 18:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-01 18:56 bugzilla-daemon [this message]
2019-05-01 19:03 ` [Bug 110574] System hang after screen power saving bugzilla-daemon
2019-05-01 19:11 ` bugzilla-daemon
2019-10-22 21:57 ` 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-110574-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.