Bug 90935

Summary: [BYT-M] connection to x server lost when resuming from S4
Product: DRI Reporter: cprigent <christophe.prigent>
Component: DRM/IntelAssignee: Intel GFX Bugs mailing list <intel-gfx-bugs>
Status: CLOSED WORKSFORME QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: major    
Priority: medium CC: intel-gfx-bugs
Version: unspecified   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: BYT i915 features: power/suspend-resume
Attachments:
Description Flags
Kernel configuration
none
kern.log none

Description cprigent 2015-06-11 14:55:12 UTC 
Created attachment 116437 [details]
Kernel configuration

Setup
-----
BAY TRAIL M /Notebook ACER Aspire ES1-512
Hardware
Platform: Aspire ES1-512 (ACER) - Notebook
Processor Family : ATOM
CPU Type: Intel(R) Celeron(R) CPU N2840 @ 2.16GHz
Signature : Type , Family: 6, Model: 55, stepping: 8
(SoC : VLV2 C0)
Software
Linux distribution: Ubuntu 14.04 LTS 64 bits ( Window 8.1 dual Boot)
Kernel: 4.1.0-rc4 drm-intel-testing-2015-05-22
BIOS : v1.09 
Mesa: mesa-10.6.0-rc3
Xf86_video_intel: 2.99.917
Libdrm: libdrm-2.4.60
Cairo: 1.14.2
Xserver: xorg-server-1.17.1

Reproduce steps:
----------------
1. Boot in text mode
2. Login as user (not root) and execute command: sudo startx
3. Launch Terminal with Ctrl  + Alt + T
4. Suspend to DISK with command: echo disk > /sys/power/state
6. Wait a moment and resume with keyboard
7. Wait a moment

Actual result:
---------------
7. Image is restored. Terminal is displayed without new prompt.
After several seconds we go back to 1st virtual terminal.
Message indicates that connection to x server is lost

Expected result:
----------------
7. DUT successfully resume from S4

Info:
------
Tested for the first time on Notebook ACER Aspire ES1-512

Similar to https://bugs.freedesktop.org/show_bug.cgi?id=90468

Also reproduced with following steps:
1. Boot in text mode with HDMI screen connected
2. Login as user (not root) and execute command: sudo startx
3. Launch Terminal with Ctrl  + Alt + T
4. Execute command: xrandr --output HDMI1 --rotation left
4. Unplug-plug HDMI cable
5. Suspend to RAM with command: echo mem > /sys/power/state
6. Resume with keyboard
7. Unplug-plug HDMI cable
8. Execute command: xrandr --output HDMI1 --rotation right
9. Unplug-plug HDMI cable
10. Suspend to RAM with command: echo mem > /sys/power/state
Comment 1 cprigent 2015-06-11 14:55:35 UTC 
Created attachment 116438 [details]
kern.log
Comment 2 cprigent 2015-06-11 15:05:41 UTC 
Please ignore the section "Also reproduced with following steps:". This is a wrong copy/paste. Sorry!
Comment 3 Ander Conselvan de Oliveira 2015-06-12 08:44:10 UTC 
Jun 11 16:28:31 BYTM kernel: [  186.879813] [drm] GPU HANG: ecode 7:0:0x75d65370, in compiz [2815], reason: Ring hung, action: reset
Jun 11 16:28:31 BYTM kernel: [  186.880089] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
Jun 11 16:28:31 BYTM kernel: [  186.880093] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
Jun 11 16:28:31 BYTM kernel: [  186.880097] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
Jun 11 16:28:31 BYTM kernel: [  186.880100] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
Jun 11 16:28:31 BYTM kernel: [  186.880103] [drm] GPU crash dump saved to /sys/class/drm/card0/error

Please attach the GPU crash dump.
Comment 4 Elio 2016-01-06 17:28:53 UTC 
The mentioned test is working without problems
BYT environment:
Baytrail-M
Hardware
Platform: Toshiba Satellite C55t
Processor Intel(R) Celeron(R) CPU  N2820  @ 2.13GHz
Software
Linux distribution: Ubuntu 15.10 LTS 64Bits
BIOS: 1.10
kernel: 4.4.0-rc6-drm-intel-nightly-2015-10-10
commit 0417da5e6f56078d87d366d5f959f8290ae9d16d
IGT= intel-gpu-tools-1.13
Cairo=1.15.2
Intel-Driver= 1.6.2.pre2
xf86= 2.99.917-524-g8e98751
libva=libva-1.6.2.pre3
xorg-server=xorg-server-1.18.0
drm=libdrm-2.4.65
mesa=mesa-11.1.0

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.