[SOLVED] Screen goes off (xdg-screensaver) and can't resume

Cristhian · 2018-02-17 16:45:54

Hi, I can't understand why after screen blanks with:

xset s activate

or

xset dpms force off

The screen blanks correctly, but I can't resume pressing any key or moving mouse .
The keyboard is actually working, because I can use keys to write or to play and stop music.
The only way to resume i found, is to press Ctrl+Alt+F2 and then close it with Ctrl+Alt+F7.

Please can you help me? I don't want to install something else like xscreensaver that override X config.

I'm using i3wm as window manger
and Kernel : x86_64 Linux 4.15.1-2-ARCH

Thanks so much

EDIT:
I solved this problem deleting the two Options you can find here in my previous /etc/X11/xorg.conf.d/20-intel.conf file:
My config file was :

Section "Device"
       Identifier  "Intel Graphics"
       Driver       "intel"
       Option       "AccelMethod"   "uxa"
       Option       "TearFree"  "true"
EndSection

Last edited by Cristhian (2018-02-25 15:20:31)

lo1 · 2018-02-17 20:56:31

Hi and welcome to the forums.

You should provide some other info to troubleshoot this:

lspci | grep VGA
pacman -Qs xf86-video*  #or any driver you're using
cat /proc/cmdline

Also, post your journalctl and dmesg logs (if you think they're relevant) along with you xorg log. Don't forget code tags.

P.S. newest nvidia drivers are affected from performance issues and I don't know what other bugs, search for other nvidia threads if you're using nvidia 390*.

Last edited by lo1 (2018-02-17 20:59:44)

Cristhian · 2018-02-18 04:09:48

Thank you so much!

lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06)

pacman -Qs xf86-video-intel
local/xf86-video-intel 1:2.99.917+805+g26f54068-1 (xorg-drivers)
    X.org Intel i810/i830/i915/945G/G965+ video drivers

cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-linux root=UUID=2e730657-891d-48af-8b54-55d3325de50b rw

I'm not using nvidia drivers or bumblebee. I'm just using xf86-video-intel and I did not create any Monitor config file in /etc/X11/xorg.conf.d

xset q
Keyboard Control:
  auto repeat:  on    key click percent:  0    LED mask:  00000000
  XKB indicators:
    00: Caps Lock:   off    01: Num Lock:    off    02: Scroll Lock: off
    03: Compose:     off    04: Kana:        off    05: Sleep:       off
    06: Suspend:     off    07: Mute:        off    08: Misc:        off
    09: Mail:        off    10: Charging:    off    11: Shift Lock:  off
    12: Group 2:     off    13: Mouse Keys:  off
  auto repeat delay:  660    repeat rate:  25
  auto repeating keys:  00ffffffdffffbbf
                        fadfffefffedffff
                        9fffffffffffffff
                        fff7ffffffffffff
  bell percent:  50    bell pitch:  400    bell duration:  100
Pointer Control:
  acceleration:  2/1    threshold:  4
Screen Saver:
  prefer blanking:  yes    allow exposures:  yes
  timeout:  600    cycle:  600
Colors:
  default colormap:  0x20    BlackPixel:  0x0    WhitePixel:  0xffffff
Font Path:
  /usr/share/fonts/TTF/,built-ins
DPMS (Energy Star):
  Standby: 600    Suspend: 600    Off: 600
  DPMS is Enabled
  Monitor is On
xset q
Keyboard Control:
  auto repeat:  on    key click percent:  0    LED mask:  00000000
  XKB indicators:
    00: Caps Lock:   off    01: Num Lock:    off    02: Scroll Lock: off
    03: Compose:     off    04: Kana:        off    05: Sleep:       off
    06: Suspend:     off    07: Mute:        off    08: Misc:        off
    09: Mail:        off    10: Charging:    off    11: Shift Lock:  off
    12: Group 2:     off    13: Mouse Keys:  off
  auto repeat delay:  660    repeat rate:  25
  auto repeating keys:  00ffffffdffffbbf
                        fadfffefffedffff
                        9fffffffffffffff
                        fff7ffffffffffff
  bell percent:  50    bell pitch:  400    bell duration:  100
Pointer Control:
  acceleration:  2/1    threshold:  4
Screen Saver:
  prefer blanking:  yes    allow exposures:  yes
  timeout:  600    cycle:  600
Colors:
  default colormap:  0x20    BlackPixel:  0x0    WhitePixel:  0xffffff
Font Path:
  /usr/share/fonts/TTF/,built-ins
DPMS (Energy Star):
  Standby: 600    Suspend: 600    Off: 600
  DPMS is Enabled
  Monitor is On

The journalctl is too long , do you prefer me to link the .txt file in wich i redirect the output or can I post here the all entire output?
For dmesg los and xorg log I did not understand very well what to post here. I found xorg.0.log xorg.0.log.old and also the same files with the number 1 instead of 0 , in /var/log directory.

seth · 2018-02-18 08:09:13

xset dpms force off
sleep 5
xrandr -q
xset dpms force on

Notebook or desktop? Does the output have a status led/OSD?

Cristhian · 2018-02-18 09:27:50

It's a laptop. Acer VN7 592G

xrandr -q
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
eDP1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 345mm x 194mm
   1920x1080     60.02*+  59.96    59.93
   1680x1050     59.95    59.88
   1400x1050     59.98
   1600x900      59.95    59.82
   1280x1024     60.02
   1400x900      59.96    59.88
   1280x960      60.00
   1368x768      59.88    59.85
   1280x800      59.81    59.91
   1280x720      59.86    59.74
   1024x768      60.00
   1024x576      59.90    59.82
   960x540       59.63    59.82
   800x600       60.32    56.25
   864x486       59.92    59.57
   640x480       59.94
   720x405       59.51    58.99
   640x360       59.84    59.32
DP1 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
DP2 disconnected (normal left inverted right x axis y axis)
HDMI2 disconnected (normal left inverted right x axis y axis)

Also after

xset dpms force on

the screen was blank.
Also

xset s reset

after

xset s activate

// this command force the screensaver to activate , I think it's different form dpms commands, but the results are the same.
doesn't seem to work and the screen remain blank.

Last edited by Cristhian (2018-02-18 09:31:38)

Head_on_a_Stick · 2018-02-18 10:15:29

Cristhian wrote:

I'm just using xf86-video-intel

Try removing that, it can be buggy. Xorg's built-in modesetting driver might do better.

Cristhian · 2018-02-18 10:31:54

Wait a moment, I found the problem!! It was compton!!
Do you know how I can fix this bug in compton? ( I'll try to google it in a few seconds)
Or maybe do you recommend another compositor? I'm using i3wm .
PS: If you prefer me to close this topic as Solved I will open another topic for this new problem.
Thank you so much to everyone!!

lo1 · 2018-02-18 11:08:11

Do you mind posting an explanation/logs/your reasoning/whatever made you understand that it was compton in the first place?

Anyway, if the issue is the same (which is, the display stays black after the screensaver steps in) don't create a new thread but edit the title and your first post so that it describes accurately which application is not working properly, what is the deviation from the normal behaviour and how to reproduce the issue.

EDIT: Don't forget any relevant configuration files for compton.

Last edited by lo1 (2018-02-18 11:10:42)

seth · 2018-02-18 11:13:42

He probably killed compton and it also makes sense, because comment #5 rules out pretty much everything dpms related.

@Cristhian
This is probably a GL/driver related issue, maybe vsync related.
First try compton w/ the xrender backend and then go for comment #6. If that "fixes" it and you still want to use the intel driver for other reasons, we need to sort out what exactly causes this. DRI3 would be a contender: https://wiki.archlinux.org/index.php/In … RI3_issues

Cristhian · 2018-02-18 11:43:45

lo1 wrote:

Do you mind posting an explanation/logs/your reasoning/whatever made you understand that it was compton in the first place?
Anyway, if the issue is the same (which is, the display stays black after the screensaver steps in) don't create a new thread but edit the title and your first post so that it describes accurately which application is not working properly, what is the deviation from the normal behaviour and how to reproduce the issue.
EDIT: Don't forget any relevant configuration files for compton.

Yes of course, thank you so much to be patient , I will edit my first post as soon as possible.

Last edited by Cristhian (2018-02-18 11:45:03)

Cristhian · 2018-02-18 11:51:15

seth wrote:

He probably killed compton and it also makes sense, because comment #5 rules out pretty much everything dpms related.
@Cristhian
This is probably a GL/driver related issue, maybe vsync related.
First try compton w/ the xrender backend and then go for comment #6. If that "fixes" it and you still want to use the intel driver for other reasons, we need to sort out what exactly causes this. DRI3 would be a contender: https://wiki.archlinux.org/index.php/In … RI3_issues

@seth

compton --backend xrender

solve the problem !!
I just don't know why the output of this command is :

vsync_opengl_swc_init(): I'm afraid glXSwapIntervalSGI wouldn't help if you are not using GLX backend. You could try, nonetheless.

Ps: I don't have DRI2 or DRI3 installed.

seth · 2018-02-18 12:35:57

This isn't a solution, you've merely figured that it's a problem with OpenGL or comptons use thereof.
DRI is not something you have "installed" but https://en.wikipedia.org/wiki/Direct_Re … astructure - read the previously linked intel article.

The warning is expectable - you've configured compton to vsync (afair the default) but the xrender protocol doesn't know the concept of syncing to an output (so it doesn't work)

Cristhian · 2018-02-18 14:53:45

@seth
I tried to add

Option "DRI" "2"

to my 20-intel.conf and reboot. But nothing change .

I tried also

compton --backend xrender --vsync opengl

and

 compton --backend xrender --vsync opengl-swc

The first one seems to work, the output is clear . No errors.
With the latter the output is

 vsync_opengl_swc_init(): I'm afraid glXSwapIntervalSGI wouldn't help if you are not using GLX backend. You could try, nonetheless.

As I have already stated, both of this commands don't give any problem with screen blanking or screensaver.

Do you think I can think my problem is solved or maybe also adding

--vsync opengl

it just cover a problem that it's not really solved?

If it can helps , this is my compton config file. I never set it , it's everything set by default.

cat /etc/xdg/compton.conf
# Thank you code_nomad: http://9m.no/ꪯ鵞

#################################
#
# Backend
#
#################################

# Backend to use: "xrender" or "glx".
# GLX backend is typically much faster but depends on a sane driver.
backend = "glx";

#################################
#
# GLX backend
#
#################################

glx-no-stencil = true;

# GLX backend: Copy unmodified regions from front buffer instead of redrawing them all.
# My tests with nvidia-drivers show a 10% decrease in performance when the whole screen is modified,
# but a 20% increase when only 1/4 is.
# My tests on nouveau show terrible slowdown.
# Useful with --glx-swap-method, as well.
glx-copy-from-front = false;

# GLX backend: Use MESA_copy_sub_buffer to do partial screen update.
# My tests on nouveau shows a 200% performance boost when only 1/4 of the screen is updated.
# May break VSync and is not available on some drivers.
# Overrides --glx-copy-from-front.
# glx-use-copysubbuffermesa = true;

# GLX backend: Avoid rebinding pixmap on window damage.
# Probably could improve performance on rapid window content changes, but is known to break things on some drivers (LLVMpipe).
# Recommended if it works.
# glx-no-rebind-pixmap = true;


# GLX backend: GLX buffer swap method we assume.
# Could be undefined (0), copy (1), exchange (2), 3-6, or buffer-age (-1).
# undefined is the slowest and the safest, and the default value.
# copy is fastest, but may fail on some drivers,
# 2-6 are gradually slower but safer (6 is still faster than 0).
# Usually, double buffer means 2, triple buffer means 3.
# buffer-age means auto-detect using GLX_EXT_buffer_age, supported by some drivers.
# Useless with --glx-use-copysubbuffermesa.
# Partially breaks --resize-damage.
# Defaults to undefined.
glx-swap-method = "undefined";

#################################
#
# Shadows
#
#################################

# Enabled client-side shadows on windows.
shadow = true;
# Don't draw shadows on DND windows.
no-dnd-shadow = true;
# Avoid drawing shadows on dock/panel windows.
no-dock-shadow = true;
# Zero the part of the shadow's mask behind the window. Fix some weirdness with ARGB windows.
clear-shadow = true;
# The blur radius for shadows. (default 12)
shadow-radius = 5;
# The left offset for shadows. (default -15)
shadow-offset-x = -5;
# The top offset for shadows. (default -15)
shadow-offset-y = -5;
# The translucency for shadows. (default .75)
shadow-opacity = 0.5;

# Set if you want different colour shadows
# shadow-red = 0.0;
# shadow-green = 0.0;
# shadow-blue = 0.0;

# The shadow exclude options are helpful if you have shadows enabled. Due to the way compton draws its shadows, certain applications will have visual glitches
# (most applications are fine, only apps that do weird things with xshapes or argb are affected).
# This list includes all the affected apps I found in my testing. The "! name~=''" part excludes shadows on any "Unknown" windows, this prevents a visual glitch with the XFWM alt tab switcher.
shadow-exclude = [
    "! name~=''",
    "name = 'Notification'",
    "name = 'Plank'",
    "name = 'Docky'",
    "name = 'Kupfer'",
    "name = 'xfce4-notifyd'",
    "name *= 'VLC'",
    "name *= 'compton'",
    "name *= 'Chromium'",
    "name *= 'Chrome'",
    "class_g = 'Conky'",
    "class_g = 'Kupfer'",
    "class_g = 'Synapse'",
    "class_g ?= 'Notify-osd'",
    "class_g ?= 'Cairo-dock'",
    "class_g ?= 'Xfce4-notifyd'",
    "class_g ?= 'Xfce4-power-manager'",
    "_GTK_FRAME_EXTENTS@:c"
];
# Avoid drawing shadow on all shaped windows (see also: --detect-rounded-corners)
shadow-ignore-shaped = false;

#################################
#
# Opacity
#
#################################

menu-opacity = 1;
inactive-opacity = 1;
active-opacity = 1;
frame-opacity = 1;
inactive-opacity-override = false;
alpha-step = 0.06;

# Dim inactive windows. (0.0 - 1.0)
# inactive-dim = 0.2;
# Do not let dimness adjust based on window opacity.
# inactive-dim-fixed = true;
# Blur background of transparent windows. Bad performance with X Render backend. GLX backend is preferred.
# blur-background = true;
# Blur background of opaque windows with transparent frames as well.
# blur-background-frame = true;
# Do not let blur radius adjust based on window opacity.
blur-background-fixed = false;
blur-background-exclude = [
    "window_type = 'dock'",
    "window_type = 'desktop'"
];

#################################
#
# Fading
#
#################################

# Fade windows during opacity changes.
fading = true;
# The time between steps in a fade in milliseconds. (default 10).
fade-delta = 4;
# Opacity change between steps while fading in. (default 0.028).
fade-in-step = 0.03;
# Opacity change between steps while fading out. (default 0.03).
fade-out-step = 0.03;
# Fade windows in/out when opening/closing
# no-fading-openclose = true;

# Specify a list of conditions of windows that should not be faded.
fade-exclude = [ ];

#################################
#
# Other
#
#################################

# Try to detect WM windows and mark them as active.
mark-wmwin-focused = true;
# Mark all non-WM but override-redirect windows active (e.g. menus).
mark-ovredir-focused = true;
# Use EWMH _NET_WM_ACTIVE_WINDOW to determine which window is focused instead of using FocusIn/Out events.
# Usually more reliable but depends on a EWMH-compliant WM.
use-ewmh-active-win = true;
# Detect rounded corners and treat them as rectangular when --shadow-ignore-shaped is on.
detect-rounded-corners = true;

# Detect _NET_WM_OPACITY on client windows, useful for window managers not passing _NET_WM_OPACITY of client windows to frame windows.
# This prevents opacity being ignored for some apps.
# For example without this enabled my xfce4-notifyd is 100% opacity no matter what.
detect-client-opacity = true;

# Specify refresh rate of the screen.
# If not specified or 0, compton will try detecting this with X RandR extension.
refresh-rate = 0;

# Set VSync method. VSync methods currently available:
# none: No VSync
# drm: VSync with DRM_IOCTL_WAIT_VBLANK. May only work on some drivers.
# opengl: Try to VSync with SGI_video_sync OpenGL extension. Only work on some drivers.
# opengl-oml: Try to VSync with OML_sync_control OpenGL extension. Only work on some drivers.
# opengl-swc: Try to VSync with SGI_swap_control OpenGL extension. Only work on some drivers. Works only with GLX backend. Known to be most effective on many drivers. Does not actually control paint timing, only buffer swap is affected, so it doesn’t have the effect of --sw-opti unlike other methods. Experimental.
# opengl-mswc: Try to VSync with MESA_swap_control OpenGL extension. Basically the same as opengl-swc above, except the extension we use.
# (Note some VSync methods may not be enabled at compile time.)
vsync = "opengl-swc";

# Enable DBE painting mode, intended to use with VSync to (hopefully) eliminate tearing.
# Reported to have no effect, though.
dbe = false;
# Painting on X Composite overlay window. Recommended.
paint-on-overlay = true;

# Limit compton to repaint at most once every 1 / refresh_rate second to boost performance.
# This should not be used with --vsync drm/opengl/opengl-oml as they essentially does --sw-opti's job already,
# unless you wish to specify a lower refresh rate than the actual value.
sw-opti = true;

# Unredirect all windows if a full-screen opaque window is detected, to maximize performance for full-screen windows, like games.
# Known to cause flickering when redirecting/unredirecting windows.
# paint-on-overlay may make the flickering less obvious.
unredir-if-possible = true;

# Specify a list of conditions of windows that should always be considered focused.
focus-exclude = [ ];

# Use WM_TRANSIENT_FOR to group windows, and consider windows in the same group focused at the same time.
detect-transient = true;
# Use WM_CLIENT_LEADER to group windows, and consider windows in the same group focused at the same time.
# WM_TRANSIENT_FOR has higher priority if --detect-transient is enabled, too.
detect-client-leader = true;

#################################
#
# Window type settings
#
#################################

wintypes:
{
    tooltip =
    {
        # fade: Fade the particular type of windows.
        fade = true;
        # shadow: Give those windows shadow
        shadow = false;
        # opacity: Default opacity for the type of windows.
        opacity = 0.85;
        # focus: Whether to always consider windows of this type focused.
        focus = true;
    };
};

seth · 2018-02-18 15:11:38

xrender is much different from opengl and especially does not provide a non-orthogonal frustum (ie. "depth")
If you require such features of the opengl backend you should try to use the modesetting driver as suggested in comment #6

Cristhian · 2018-02-18 17:16:07

I don't know so much about this staff, I'm tryng to read a lot of guides.
In the mean while I tried to remove xf86-video-intel .
With

compton --backend xrender --vsync opengl-swc

there is always the same error in the output

V1del · 2018-02-18 19:04:38

We know, the question is if you can use your original compton line (without the xrender backend) now and if the wakeup from the screensaver works, now that you've removed xf86-video-intel (and the corresponding 20-intel.conf I hope)

Cristhian · 2018-02-18 20:10:21

Yes of course I deleted the 20-intel.conf , now I can use compton without adding any option and I can resume correctly after screensaver or DPMS functions.
But I noticed I'm not able to set brightness any more.

xbacklight
No outputs have backlight property

seth · 2018-02-18 20:24:35

So it's related to the intel ddx driver.
See https://wiki.archlinux.org/index.php/Backlight and esp. whether you've entries in /sys/class/backlight - you might not be able to use xbacklight but still be able to control the latter more directly.

Cristhian · 2018-02-19 10:22:23

Sorry, do you mind to explain what does it means "esp."? Sorry, english it's not my mother tongue. Anyway I've one entry in /sys/class/blacklight and it is " intel_blacklight".
But the most important problem I found after I removed xf86-video-intel is that I can't resume after reboot or suspend. My screen is black. Not blank or off, just black with no possibility to open tty and go back. I'm forced to long press on my power button to shutdown everything.
I 've red this topic where you @seth tried to answer to something similar (or equal, I don't know) . https://bbs.archlinux.org/viewtopic.php?id=228814
This is a part of my journactl at the time of suspend request , I don't know how to use grep to find when it's resuming.

Feb 19 10:02:20 arch systemd[1]: Reached target Sleep.
Feb 19 10:02:20 arch systemd[1]: Starting Suspend...
Feb 19 10:02:20 arch dhcpcd[444]: wlp7s0: new hardware address: 22:9f:1c:ff:d6:0e
Feb 19 10:02:20 arch dhcpcd[444]: wlp7s0: new hardware address: c8:ff:28:09:1d:2d
Feb 19 10:02:20 arch systemd-sleep[2190]: Suspending system...
Feb 19 10:02:20 arch kernel: PM: suspend entry (deep)
Feb 19 10:02:20 arch wpa_supplicant[497]: nl80211: deinit ifname=wlp7s0 disabled_11b_rates=0
-- Reboot --
Feb 19 10:03:54 arch kernel: Linux version 4.15.3-2-ARCH (builduser@heftig-19445) (gcc version 7.3.0 (GCC)) #1 SMP PREEMPT Thu Feb 15 00:13:49 UTC 2018
Feb 19 10:03:54 arch kernel: Command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=2e730657-891d-48af-8b54-55d3325de50b rw
Feb 19 10:03:54 arch kernel: KERNEL supported cpus:
Feb 19 10:03:54 arch kernel:   Intel GenuineIntel
Feb 19 10:03:54 arch kernel:   AMD AuthenticAMD
Feb 19 10:03:54 arch kernel:   Centaur CentaurHauls
Feb 19 10:03:54 arch kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Feb 19 10:03:54 arch kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Feb 19 10:03:54 arch kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Feb 19 10:03:54 arch kernel: x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers'
Feb 19 10:03:54 arch kernel: x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
Feb 19 10:03:54 arch kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
Feb 19 10:03:54 arch kernel: x86/fpu: xstate_offset[3]:  832, xstate_sizes[3]:   64
Feb 19 10:03:54 arch kernel: x86/fpu: xstate_offset[4]:  896, xstate_sizes[4]:   64
Feb 19 10:03:54 arch kernel: x86/fpu: Enabled xstate features 0x1f, context size is 960 bytes, using 'compacted' format.
Feb 19 10:03:54 arch kernel: e820: BIOS-provided physical RAM map:
Feb 19 10:03:54 arch kernel: BIOS-e820: [mem 0x0000000000000000-0x0000000000057fff] usable
Feb 19 10:03:54 arch kernel: BIOS-e820: [mem 0x0000000000058000-0x0000000000058fff] reserved
Feb 19 10:03:54 arch kernel: BIOS-e820: [mem 0x0000000000059000-0x0000000000085fff] usable
Feb 19 10:03:54 arch kernel: BIOS-e820: [mem 0x0000000000086000-0x00000000000fffff] reserved
Feb 19 10:03:54 arch kernel: BIOS-e820: [mem 0x0000000000100000-0x000000001877afff] usable
Feb 19 10:03:54 arch kernel: BIOS-e820: [mem 0x000000001877b000-0x000000001877bfff] ACPI NVS
Feb 19 10:03:54 arch kernel: BIOS-e820: [mem 0x000000001877c000-0x00000000187c5fff] reserved
Feb 19 10:03:54 arch kernel: BIOS-e820: [mem 0x00000000187c6000-0x0000000018878fff] usable
Feb 19 10:03:54 arch kernel: BIOS-e820: [mem 0x0000000018879000-0x0000000019178fff] reserved
Feb 19 10:03:54 arch kernel: BIOS-e820: [mem 0x0000000019179000-0x000000002f38dfff] usable
Feb 19 10:03:54 arch kernel: BIOS-e820: [mem 0x000000002f38e000-0x000000002f58dfff] type 20
Feb 19 10:03:54 arch kernel: BIOS-e820: [mem 0x000000002f58e000-0x000000002fd7dfff] reserved
Feb 19 10:03:54 arch kernel: BIOS-e820: [mem 0x000000002fd7e000-0x000000002ff7dfff] ACPI NVS
Feb 19 10:03:54 arch kernel: BIOS-e820: [mem 0x000000002ff7e000-0x000000002fffdfff] ACPI data
Feb 19 10:03:54 arch kernel: BIOS-e820: [mem 0x000000002fffe000-0x000000002fffefff] usable
Feb 19 10:03:54 arch kernel: BIOS-e820: [mem 0x000000002ffff000-0x000000003affffff] reserved
Feb 19 10:03:54 arch kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
Feb 19 10:03:54 arch kernel: BIOS-e820: [mem 0x00000000fd000000-0x00000000fe7fffff] reserved
Feb 19 10:03:54 arch kernel: BIOS-e820: [mem 0x00000000feb00000-0x00000000feb03fff] reserved
Feb 19 10:03:54 arch kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
Feb 19 10:03:54 arch kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] reserved
Feb 19 10:03:54 arch kernel: BIOS-e820: [mem 0x00000000fed10000-0x00000000fed19fff] reserved
Feb 19 10:03:54 arch kernel: BIOS-e820: [mem 0x00000000fed84000-0x00000000fed84fff] reserved
Feb 19 10:03:54 arch kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Feb 19 10:03:54 arch kernel: BIOS-e820: [mem 0x00000000ffa00000-0x00000000ffffffff] reserved
Feb 19 10:03:54 arch kernel: BIOS-e820: [mem 0x0000000100000000-0x00000002c3ffffff] usable
Feb 19 10:03:54 arch kernel: NX (Execute Disable) protection: active
Feb 19 10:03:54 arch kernel: efi: EFI v2.40 by INSYDE Corp.
Feb 19 10:03:54 arch kernel: efi:  SMBIOS=0x2f5fe000  ESRT=0x2f5ffd18  ACPI 2.0=0x2fffd014
Feb 19 10:03:54 arch kernel: random: fast init done
Feb 19 10:03:54 arch kernel: SMBIOS 2.8 present.
Feb 19 10:03:54 arch kernel: DMI: Acer Aspire VN7-592G/Aspire VN7-592G, BIOS V1.03 09/25/2015
Feb 19 10:03:54 arch kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Feb 19 10:03:54 arch kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
Feb 19 10:03:54 arch kernel: e820: last_pfn = 0x2c4000 max_arch_pfn = 0x400000000
Feb 19 10:03:54 arch kernel: MTRR default type: uncachable
Feb 19 10:03:54 arch kernel: MTRR fixed ranges enabled:
Feb 19 10:03:54 arch kernel:   00000-9FFFF write-back
Feb 19 10:03:54 arch kernel:   A0000-BFFFF uncachable
Feb 19 10:03:54 arch kernel:   C0000-FFFFF write-protect
Feb 19 10:03:54 arch kernel: MTRR variable ranges enabled:
Feb 19 10:03:54 arch kernel:   0 base 0000000000 mask 7C00000000 write-back
Feb 19 10:03:54 arch kernel:   1 base 002FFFF000 mask 7FFFFFF000 uncachable
Feb 19 10:03:54 arch kernel:   2 base 0030000000 mask 7FF0000000 uncachable
Feb 19 10:03:54 arch kernel:   3 base 0040000000 mask 7FC0000000 uncachable
Feb 19 10:03:54 arch kernel:   4 base 0080000000 mask 7F80000000 uncachable
Feb 19 10:03:54 arch kernel:   5 disabled
Feb 19 10:03:54 arch kernel:   6 disabled
Feb 19 10:03:54 arch kernel:   7 disabled
Feb 19 10:03:54 arch kernel:   8 disabled
Feb 19 10:03:54 arch kernel:   9 disabled
Feb 19 10:03:54 arch kernel: x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT
Feb 19 10:03:54 arch kernel: total RAM covered: 13055M
Feb 19 10:03:54 arch kernel:  gran_size: 64K         chunk_size: 64K         num_reg: 10          lose cover RAM: 12583420K
Feb 19 10:03:54 arch kernel:  gran_size: 64K         chunk_size: 128K         num_reg: 5          lose cover RAM: 60K
Feb 19 10:03:54 arch kernel:  gran_size: 64K         chunk_size: 256K         num_reg: 5          lose cover RAM: 60K
Feb 19 10:03:54 arch kernel:  gran_size: 64K         chunk_size: 512K         num_reg: 5          lose cover RAM: 60K
Feb 19 10:03:54 arch kernel:  gran_size: 64K         chunk_size: 1M         num_reg: 5          lose cover RAM: 60K
Feb 19 10:03:54 arch kernel:  gran_size: 64K         chunk_size: 2M         num_reg: 5          lose cover RAM: 60K
Feb 19 10:03:54 arch kernel:  gran_size: 64K         chunk_size: 4M         num_reg: 5          lose cover RAM: 60K
Feb 19 10:03:54 arch kernel:  gran_size: 64K         chunk_size: 8M         num_reg: 5          lose cover RAM: 60K
Feb 19 10:03:54 arch kernel:  gran_size: 64K         chunk_size: 16M         num_reg: 5          lose cover RAM: 60K
Feb 19 10:03:54 arch kernel:  gran_size: 64K         chunk_size: 32M         num_reg: 5          lose cover RAM: 60K
Feb 19 10:03:54 arch kernel:  gran_size: 64K         chunk_size: 64M         num_reg: 5          lose cover RAM: 60K
Feb 19 10:03:54 arch kernel:  gran_size: 64K         chunk_size: 128M         num_reg: 5          lose cover RAM: 60K
Feb 19 10:03:54 arch kernel:  gran_size: 64K         chunk_size: 256M         num_reg: 5          lose cover RAM: 60K
Feb 19 10:03:54 arch kernel:  gran_size: 64K         chunk_size: 512M         num_reg: 5          lose cover RAM: 60K
Feb 19 10:03:54 arch kernel:  gran_size: 64K         chunk_size: 1G         num_reg: 5          lose cover RAM: 60K
Feb 19 10:03:54 arch kernel:  gran_size: 64K         chunk_size: 2G         num_reg: 10          lose cover RAM: 12583420K
Feb 19 10:03:54 arch kernel:  gran_size: 128K         chunk_size: 128K         num_reg: 10          lose cover RAM: 12583420K
Feb 19 10:03:54 arch kernel:  gran_size: 128K         chunk_size: 256K         num_reg: 5          lose cover RAM: 124K
Feb 19 10:03:54 arch kernel:  gran_size: 128K         chunk_size: 512K         num_reg: 5          lose cover RAM: 124K
Feb 19 10:03:54 arch kernel:  gran_size: 128K         chunk_size: 1M         num_reg: 5          lose cover RAM: 124K
Feb 19 10:03:54 arch kernel:  gran_size: 128K         chunk_size: 2M         num_reg: 5          lose cover RAM: 124K
Feb 19 10:03:54 arch kernel:  gran_size: 128K         chunk_size: 4M         num_reg: 5          lose cover RAM: 124K
Feb 19 10:03:54 arch kernel:  gran_size: 128K         chunk_size: 8M         num_reg: 5          lose cover RAM: 124K
Feb 19 10:03:54 arch kernel:  gran_size: 128K         chunk_size: 16M         num_reg: 5          lose cover RAM: 124K
Feb 19 10:03:54 arch kernel:  gran_size: 128K         chunk_size: 32M         num_reg: 5          lose cover RAM: 124K
Feb 19 10:03:54 arch kernel:  gran_size: 128K         chunk_size: 64M         num_reg: 5          lose cover RAM: 124K
Feb 19 10:03:54 arch kernel:  gran_size: 128K         chunk_size: 128M         num_reg: 5          lose cover RAM: 124K
Feb 19 10:03:54 arch kernel:  gran_size: 128K         chunk_size: 256M         num_reg: 5          lose cover RAM: 124K
Feb 19 10:03:54 arch kernel:  gran_size: 128K         chunk_size: 512M         num_reg: 5          lose cover RAM: 124K
Feb 19 10:03:54 arch kernel:  gran_size: 128K         chunk_size: 1G         num_reg: 5          lose cover RAM: 124K
Feb 19 10:03:54 arch kernel:  gran_size: 128K         chunk_size: 2G         num_reg: 10          lose cover RAM: 12583420K
Feb 19 10:03:54 arch kernel:  gran_size: 256K         chunk_size: 256K         num_reg: 10          lose cover RAM: 12583420K
Feb 19 10:03:54 arch kernel:  gran_size: 256K         chunk_size: 512K         num_reg: 5          lose cover RAM: 252K
Feb 19 10:03:54 arch kernel:  gran_size: 256K         chunk_size: 1M         num_reg: 5          lose cover RAM: 252K
Feb 19 10:03:54 arch kernel:  gran_size: 256K         chunk_size: 2M         num_reg: 5          lose cover RAM: 252K
Feb 19 10:03:54 arch kernel:  gran_size: 256K         chunk_size: 4M         num_reg: 5          lose cover RAM: 252K
Feb 19 10:03:54 arch kernel:  gran_size: 256K         chunk_size: 8M         num_reg: 5          lose cover RAM: 252K
Feb 19 10:03:54 arch kernel:  gran_size: 256K         chunk_size: 16M         num_reg: 5          lose cover RAM: 252K
Feb 19 10:03:54 arch kernel:  gran_size: 256K         chunk_size: 32M         num_reg: 5          lose cover RAM: 252K
Feb 19 10:03:54 arch kernel:  gran_size: 256K         chunk_size: 64M         num_reg: 5          lose cover RAM: 252K
Feb 19 10:03:54 arch kernel:  gran_size: 256K         chunk_size: 128M         num_reg: 5          lose cover RAM: 252K
Feb 19 10:03:54 arch kernel:  gran_size: 256K         chunk_size: 256M         num_reg: 5          lose cover RAM: 252K
Feb 19 10:03:54 arch kernel:  gran_size: 256K         chunk_size: 512M         num_reg: 5          lose cover RAM: 252K
Feb 19 10:03:54 arch kernel:  gran_size: 256K         chunk_size: 1G         num_reg: 5          lose cover RAM: 252K
Feb 19 10:03:54 arch kernel:  gran_size: 256K         chunk_size: 2G         num_reg: 10          lose cover RAM: 12583420K
Feb 19 10:03:54 arch kernel:  gran_size: 512K         chunk_size: 512K         num_reg: 10          lose cover RAM: 12583420K
Feb 19 10:03:54 arch kernel:  gran_size: 512K         chunk_size: 1M         num_reg: 5          lose cover RAM: 508K
Feb 19 10:03:54 arch kernel:  gran_size: 512K         chunk_size: 2M         num_reg: 5          lose cover RAM: 508K
Feb 19 10:03:54 arch kernel:  gran_size: 512K         chunk_size: 4M         num_reg: 5          lose cover RAM: 508K
Feb 19 10:03:54 arch kernel:  gran_size: 512K         chunk_size: 8M         num_reg: 5          lose cover RAM: 508K
Feb 19 10:03:54 arch kernel:  gran_size: 512K         chunk_size: 16M         num_reg: 5          lose cover RAM: 508K
Feb 19 10:03:54 arch kernel:  gran_size: 512K         chunk_size: 32M         num_reg: 5          lose cover RAM: 508K
Feb 19 10:03:54 arch kernel:  gran_size: 512K         chunk_size: 64M         num_reg: 5          lose cover RAM: 508K
Feb 19 10:03:54 arch kernel:  gran_size: 512K         chunk_size: 128M         num_reg: 5          lose cover RAM: 508K
Feb 19 10:03:54 arch kernel:  gran_size: 512K         chunk_size: 256M         num_reg: 5          lose cover RAM: 508K
Feb 19 10:03:54 arch kernel:  gran_size: 512K         chunk_size: 512M         num_reg: 5          lose cover RAM: 508K
Feb 19 10:03:54 arch kernel:  gran_size: 512K         chunk_size: 1G         num_reg: 5          lose cover RAM: 508K
Feb 19 10:03:54 arch kernel:  gran_size: 512K         chunk_size: 2G         num_reg: 10          lose cover RAM: 12583420K
Feb 19 10:03:54 arch kernel:  gran_size: 1M         chunk_size: 1M         num_reg: 10          lose cover RAM: 8389628K
Feb 19 10:03:54 arch kernel:  gran_size: 1M         chunk_size: 2M         num_reg: 5          lose cover RAM: 1020K
Feb 19 10:03:54 arch kernel:  gran_size: 1M         chunk_size: 4M         num_reg: 5          lose cover RAM: 1020K
Feb 19 10:03:54 arch kernel:  gran_size: 1M         chunk_size: 8M         num_reg: 5          lose cover RAM: 1020K
Feb 19 10:03:54 arch kernel:  gran_size: 1M         chunk_size: 16M         num_reg: 5          lose cover RAM: 1020K
Feb 19 10:03:54 arch kernel:  gran_size: 1M         chunk_size: 32M         num_reg: 5          lose cover RAM: 1020K
Feb 19 10:03:54 arch kernel:  gran_size: 1M         chunk_size: 64M         num_reg: 5          lose cover RAM: 1020K
Feb 19 10:03:54 arch kernel:  gran_size: 1M         chunk_size: 128M         num_reg: 5          lose cover RAM: 1020K
Feb 19 10:03:54 arch kernel:  gran_size: 1M         chunk_size: 256M         num_reg: 5          lose cover RAM: 1020K
Feb 19 10:03:54 arch kernel:  gran_size: 1M         chunk_size: 512M         num_reg: 5          lose cover RAM: 1020K
Feb 19 10:03:54 arch kernel:  gran_size: 1M         chunk_size: 1G         num_reg: 5          lose cover RAM: 1020K
Feb 19 10:03:54 arch kernel:  gran_size: 1M         chunk_size: 2G         num_reg: 10          lose cover RAM: 8389628K
Feb 19 10:03:54 arch kernel:  gran_size: 2M         chunk_size: 2M         num_reg: 10          lose cover RAM: 2044K
Feb 19 10:03:54 arch kernel:  gran_size: 2M         chunk_size: 4M         num_reg: 5          lose cover RAM: 2044K
Feb 19 10:03:54 arch kernel:  gran_size: 2M         chunk_size: 8M         num_reg: 5          lose cover RAM: 2044K
Feb 19 10:03:54 arch kernel:  gran_size: 2M         chunk_size: 16M         num_reg: 5          lose cover RAM: 2044K
Feb 19 10:03:54 arch kernel:  gran_size: 2M         chunk_size: 32M         num_reg: 5          lose cover RAM: 2044K
Feb 19 10:03:54 arch kernel:  gran_size: 2M         chunk_size: 64M         num_reg: 5          lose cover RAM: 2044K
Feb 19 10:03:54 arch kernel:  gran_size: 2M         chunk_size: 128M         num_reg: 5          lose cover RAM: 2044K
Feb 19 10:03:54 arch kernel:  gran_size: 2M         chunk_size: 256M         num_reg: 5          lose cover RAM: 2044K
Feb 19 10:03:54 arch kernel:  gran_size: 2M         chunk_size: 512M         num_reg: 5          lose cover RAM: 2044K
Feb 19 10:03:54 arch kernel:  gran_size: 2M         chunk_size: 1G         num_reg: 5          lose cover RAM: 2044K
Feb 19 10:03:54 arch kernel:  gran_size: 2M         chunk_size: 2G         num_reg: 10          lose cover RAM: 2044K
Feb 19 10:03:54 arch kernel:  gran_size: 4M         chunk_size: 4M         num_reg: 9          lose cover RAM: 4092K
Feb 19 10:03:54 arch kernel:  gran_size: 4M         chunk_size: 8M         num_reg: 5          lose cover RAM: 4092K
Feb 19 10:03:54 arch kernel:  gran_size: 4M         chunk_size: 16M         num_reg: 5          lose cover RAM: 4092K
Feb 19 10:03:54 arch kernel:  gran_size: 4M         chunk_size: 32M         num_reg: 5          lose cover RAM: 4092K
Feb 19 10:03:54 arch kernel:  gran_size: 4M         chunk_size: 64M         num_reg: 5          lose cover RAM: 4092K
Feb 19 10:03:54 arch kernel:  gran_size: 4M         chunk_size: 128M         num_reg: 5          lose cover RAM: 4092K
Feb 19 10:03:54 arch kernel:  gran_size: 4M         chunk_size: 256M         num_reg: 5          lose cover RAM: 4092K
Feb 19 10:03:54 arch kernel:  gran_size: 4M         chunk_size: 512M         num_reg: 5          lose cover RAM: 4092K
Feb 19 10:03:54 arch kernel:  gran_size: 4M         chunk_size: 1G         num_reg: 5          lose cover RAM: 4092K
Feb 19 10:03:54 arch kernel:  gran_size: 4M         chunk_size: 2G         num_reg: 9          lose cover RAM: 4092K
Feb 19 10:03:54 arch kernel:  gran_size: 8M         chunk_size: 8M         num_reg: 8          lose cover RAM: 8188K
Feb 19 10:03:54 arch kernel:  gran_size: 8M         chunk_size: 16M         num_reg: 5          lose cover RAM: 8188K
Feb 19 10:03:54 arch kernel:  gran_size: 8M         chunk_size: 32M         num_reg: 5          lose cover RAM: 8188K
Feb 19 10:03:54 arch kernel:  gran_size: 8M         chunk_size: 64M         num_reg: 5          lose cover RAM: 8188K
Feb 19 10:03:54 arch kernel:  gran_size: 8M         chunk_size: 128M         num_reg: 5          lose cover RAM: 8188K
Feb 19 10:03:54 arch kernel:  gran_size: 8M         chunk_size: 256M         num_reg: 5          lose cover RAM: 8188K
Feb 19 10:03:54 arch kernel:  gran_size: 8M         chunk_size: 512M         num_reg: 5          lose cover RAM: 8188K
Feb 19 10:03:54 arch kernel:  gran_size: 8M         chunk_size: 1G         num_reg: 5          lose cover RAM: 8188K
Feb 19 10:03:54 arch kernel:  gran_size: 8M         chunk_size: 2G         num_reg: 8          lose cover RAM: 8188K
Feb 19 10:03:54 arch kernel:  gran_size: 16M         chunk_size: 16M         num_reg: 7          lose cover RAM: 16380K
Feb 19 10:03:54 arch kernel:  gran_size: 16M         chunk_size: 32M         num_reg: 5          lose cover RAM: 16380K
Feb 19 10:03:54 arch kernel:  gran_size: 16M         chunk_size: 64M         num_reg: 5          lose cover RAM: 16380K
Feb 19 10:03:54 arch kernel:  gran_size: 16M         chunk_size: 128M         num_reg: 5          lose cover RAM: 16380K
Feb 19 10:03:54 arch kernel:  gran_size: 16M         chunk_size: 256M         num_reg: 5          lose cover RAM: 16380K
Feb 19 10:03:54 arch kernel:  gran_size: 16M         chunk_size: 512M         num_reg: 5          lose cover RAM: 16380K
Feb 19 10:03:54 arch kernel:  gran_size: 16M         chunk_size: 1G         num_reg: 5          lose cover RAM: 16380K
Feb 19 10:03:54 arch kernel:  gran_size: 16M         chunk_size: 2G         num_reg: 7          lose cover RAM: 16380K
Feb 19 10:03:54 arch kernel:  gran_size: 32M         chunk_size: 32M         num_reg: 6          lose cover RAM: 32764K
Feb 19 10:03:54 arch kernel:  gran_size: 32M         chunk_size: 64M         num_reg: 5          lose cover RAM: 32764K
Feb 19 10:03:54 arch kernel:  gran_size: 32M         chunk_size: 128M         num_reg: 5          lose cover RAM: 32764K
Feb 19 10:03:54 arch kernel:  gran_size: 32M         chunk_size: 256M         num_reg: 5          lose cover RAM: 32764K
Feb 19 10:03:54 arch kernel:  gran_size: 32M         chunk_size: 512M         num_reg: 5          lose cover RAM: 32764K
Feb 19 10:03:54 arch kernel:  gran_size: 32M         chunk_size: 1G         num_reg: 5          lose cover RAM: 32764K
Feb 19 10:03:54 arch kernel:  gran_size: 32M         chunk_size: 2G         num_reg: 6          lose cover RAM: 32764K
Feb 19 10:03:54 arch kernel:  gran_size: 64M         chunk_size: 64M         num_reg: 5          lose cover RAM: 65532K
Feb 19 10:03:54 arch kernel:  gran_size: 64M         chunk_size: 128M         num_reg: 5          lose cover RAM: 65532K
Feb 19 10:03:54 arch kernel:  gran_size: 64M         chunk_size: 256M         num_reg: 5          lose cover RAM: 65532K
Feb 19 10:03:54 arch kernel:  gran_size: 64M         chunk_size: 512M         num_reg: 5          lose cover RAM: 65532K
Feb 19 10:03:54 arch kernel:  gran_size: 64M         chunk_size: 1G         num_reg: 5          lose cover RAM: 65532K
Feb 19 10:03:54 arch kernel:  gran_size: 64M         chunk_size: 2G         num_reg: 5          lose cover RAM: 65532K
Feb 19 10:03:54 arch kernel:  gran_size: 128M         chunk_size: 128M         num_reg: 4          lose cover RAM: 131068K
Feb 19 10:03:54 arch kernel:  gran_size: 128M         chunk_size: 256M         num_reg: 5          lose cover RAM: 131068K
Feb 19 10:03:54 arch kernel:  gran_size: 128M         chunk_size: 512M         num_reg: 5          lose cover RAM: 131068K
Feb 19 10:03:54 arch kernel:  gran_size: 128M         chunk_size: 1G         num_reg: 5          lose cover RAM: 131068K
Feb 19 10:03:54 arch kernel:  gran_size: 128M         chunk_size: 2G         num_reg: 4          lose cover RAM: 131068K
Feb 19 10:03:54 arch kernel:  gran_size: 256M         chunk_size: 256M         num_reg: 3          lose cover RAM: 262140K
Feb 19 10:03:54 arch kernel:  gran_size: 256M         chunk_size: 512M         num_reg: 3          lose cover RAM: 262140K
Feb 19 10:03:54 arch kernel:  gran_size: 256M         chunk_size: 1G         num_reg: 3          lose cover RAM: 262140K
Feb 19 10:03:54 arch kernel:  gran_size: 256M         chunk_size: 2G         num_reg: 3          lose cover RAM: 262140K
Feb 19 10:03:54 arch kernel:  gran_size: 512M         chunk_size: 512M         num_reg: 3          lose cover RAM: 262140K
Feb 19 10:03:54 arch kernel:  gran_size: 512M         chunk_size: 1G         num_reg: 3          lose cover RAM: 262140K
Feb 19 10:03:54 arch kernel:  gran_size: 512M         chunk_size: 2G         num_reg: 3          lose cover RAM: 262140K
Feb 19 10:03:54 arch kernel:  gran_size: 1G         chunk_size: 1G         num_reg: 2          lose cover RAM: 786428K
Feb 19 10:03:54 arch kernel:  gran_size: 1G         chunk_size: 2G         num_reg: 2          lose cover RAM: 786428K
Feb 19 10:03:54 arch kernel:  gran_size: 2G         chunk_size: 2G         num_reg: 2          lose cover RAM: 786428K
Feb 19 10:03:54 arch kernel: mtrr_cleanup: can not find optimal value
Feb 19 10:03:54 arch kernel: please specify mtrr_gran_size/mtrr_chunk_size
Feb 19 10:03:54 arch kernel: e820: update [mem 0x2ffff000-0xffffffff] usable ==> reserved
Feb 19 10:03:54 arch kernel: e820: last_pfn = 0x2ffff max_arch_pfn = 0x400000000
Feb 19 10:03:54 arch kernel: esrt: Reserving ESRT space from 0x000000002f5ffd18 to 0x000000002f5ffd50.
Feb 19 10:03:54 arch kernel: Scanning 1 areas for low memory corruption
Feb 19 10:03:54 arch kernel: Base memory trampoline at [        (ptrval)] 7c000 size 24576
Feb 19 10:03:54 arch kernel: Using GB pages for direct mapping
Feb 19 10:03:54 arch kernel: BRK [0x249638000, 0x249638fff] PGTABLE
Feb 19 10:03:54 arch kernel: BRK [0x249639000, 0x249639fff] PGTABLE
Feb 19 10:03:54 arch kernel: BRK [0x24963a000, 0x24963afff] PGTABLE
Feb 19 10:03:54 arch kernel: BRK [0x24963b000, 0x24963bfff] PGTABLE
Feb 19 10:03:54 arch kernel: BRK [0x24963c000, 0x24963cfff] PGTABLE
Feb 19 10:03:54 arch kernel: BRK [0x24963d000, 0x24963dfff] PGTABLE
Feb 19 10:03:54 arch kernel: BRK [0x24963e000, 0x24963efff] PGTABLE
Feb 19 10:03:54 arch kernel: BRK [0x24963f000, 0x24963ffff] PGTABLE
Feb 19 10:03:54 arch kernel: BRK [0x249640000, 0x249640fff] PGTABLE
Feb 19 10:03:54 arch kernel: BRK [0x249641000, 0x249641fff] PGTABLE
Feb 19 10:03:54 arch kernel: Secure boot could not be determined
Feb 19 10:03:54 arch kernel: RAMDISK: [mem 0x2e238000-0x2eeb1fff]
Feb 19 10:03:54 arch kernel: ACPI: Early table checksum verification disabled
Feb 19 10:03:54 arch kernel: ACPI: RSDP 0x000000002FFFD014 000024 (v02 ACRSYS)
Feb 19 10:03:54 arch kernel: ACPI: XSDT 0x000000002FFFD170 000114 (v01 ACRSYS ACRPRDCT 00000000      01000013)
Feb 19 10:03:54 arch kernel: ACPI: FACP 0x000000002FFE4000 0000F4 (v05 ACRSYS ACRPRDCT 00000000 1025 00040000)
Feb 19 10:03:54 arch kernel: ACPI: DSDT 0x000000002FFC3000 01B761 (v02 ACRSYS ACRPRDCT 00000000 1025 00040000)
Feb 19 10:03:54 arch kernel: ACPI: FACS 0x000000002FF78000 000040
Feb 19 10:03:54 arch kernel: ACPI: TCPA 0x000000002FFFC000 000032 (v02 ACRSYS ACRPRDCT 00000000 1025 00040000)
Feb 19 10:03:54 arch kernel: ACPI: UEFI 0x000000002FFFA000 000042 (v01 ACRSYS ACRPRDCT 00000002 1025 00040000)
Feb 19 10:03:54 arch kernel: ACPI: SSDT 0x000000002FFF8000 00004B (v02 ACRSYS ACRPRDCT 00003000 1025 00040000)
Feb 19 10:03:54 arch kernel: ACPI: SSDT 0x000000002FFF2000 004128 (v01 ACRSYS ACRPRDCT 00001000 1025 00040000)
Feb 19 10:03:54 arch kernel: ACPI: SSDT 0x000000002FFEB000 005030 (v02 ACRSYS ACRPRDCT 00003000 1025 00040000)
Feb 19 10:03:54 arch kernel: ACPI: DBG2 0x000000002FFE9000 000054 (v00 ACRSYS ACRPRDCT 00000000 1025 00040000)
Feb 19 10:03:54 arch kernel: ACPI: ASPT 0x000000002FFE7000 000034 (v07 ACRSYS ACRPRDCT 00000001 1025 00040000)
Feb 19 10:03:54 arch kernel: ACPI: DBGP 0x000000002FFE5000 000034 (v01 ACRSYS ACRPRDCT 00000001 1025 00040000)
Feb 19 10:03:54 arch kernel: ACPI: LPIT 0x000000002FFE2000 000094 (v01 ACRSYS ACRPRDCT 00000000 1025 00040000)
Feb 19 10:03:54 arch kernel: ACPI: MCFG 0x000000002FFE0000 00003C (v01 ACRSYS ACRPRDCT 00000001 1025 00040000)
Feb 19 10:03:54 arch kernel: ACPI: SSDT 0x000000002FFC1000 000ECB (v02 ACRSYS ACRPRDCT 00001000 1025 00040000)
Feb 19 10:03:54 arch kernel: ACPI: SSDT 0x000000002FFBF000 00021A (v02 ACRSYS ACRPRDCT 00001000 1025 00040000)
Feb 19 10:03:54 arch kernel: ACPI: SSDT 0x000000002FFBE000 000E58 (v02 ACRSYS ACRPRDCT 00003000 1025 00040000)
Feb 19 10:03:54 arch kernel: ACPI: DMAR 0x000000002FFB8000 0000F0 (v01 ACRSYS ACRPRDCT 00000001 1025 00040000)
Feb 19 10:03:54 arch kernel: ACPI: FPDT 0x000000002FFDF000 000044 (v01 ACRSYS ACRPRDCT 00000002 1025 00040000)
Feb 19 10:03:54 arch kernel: ACPI: UEFI 0x000000002FFFB000 000236 (v01 ACRSYS ACRPRDCT 00000001 1025 00040000)
Feb 19 10:03:54 arch kernel: ACPI: TPM2 0x000000002FFF7000 000034 (v03 ACRSYS ACRPRDCT 00000000 1025 00040000)
Feb 19 10:03:54 arch kernel: ACPI: DBGP 0x000000002FFEA000 000034 (v01 ACRSYS ACRPRDCT 00000001 1025 00040000)
Feb 19 10:03:54 arch kernel: ACPI: BOOT 0x000000002FFE6000 000028 (v01 ACRSYS ACRPRDCT 00000001 1025 00040000)
Feb 19 10:03:54 arch kernel: ACPI: APIC 0x000000002FFE1000 0000BC (v03 ACRSYS ACRPRDCT 00000001 1025 00040000)
Feb 19 10:03:54 arch kernel: ACPI: SSDT 0x000000002FFC0000 00019A (v02 ACRSYS ACRPRDCT 00001000 1025 00040000)
Feb 19 10:03:54 arch kernel: ACPI: SSDT 0x000000002FFB9000 004352 (v01 ACRSYS ACRPRDCT 00001000 1025 00040000)
Feb 19 10:03:54 arch kernel: ACPI: SSDT 0x000000002FFF9000 0004B7 (v02 ACRSYS ACRPRDCT 00001000 1025 00040000)
Feb 19 10:03:54 arch kernel: ACPI: ASF! 0x000000002FFE8000 0000A5 (v32 ACRSYS ACRPRDCT 00000001 1025 00040000)
Feb 19 10:03:54 arch kernel: ACPI: SSDT 0x000000002FFC2000 0002D4 (v01 ACRSYS ACRPRDCT 00000000 1025 00040000)
Feb 19 10:03:54 arch kernel: ACPI: NHLT 0x000000002FFB6000 0017F0 (v00 ACRSYS ACRPRDCT 00000002 1025 00040000)
Feb 19 10:03:54 arch kernel: ACPI: MSDM 0x000000002FFF1000 000055 (v03 ACRSYS ACRPRDCT 00000001 1025 00040000)
Feb 19 10:03:54 arch kernel: ACPI: HPET 0x000000002FFE3000 000038 (v01 ACRSYS ACRPRDCT 00000001 1025 00040000)
Feb 19 10:03:54 arch kernel: ACPI: BGRT 0x000000002FFB5000 000038 (v01 ACRSYS ACRPRDCT 00000001 1025 00040000)
Feb 19 10:03:54 arch kernel: ACPI: Local APIC address 0xfee00000
Feb 19 10:03:54 arch kernel: No NUMA configuration found
Feb 19 10:03:54 arch kernel: Faking a node at [mem 0x0000000000000000-0x00000002c3ffffff]
Feb 19 10:03:54 arch kernel: NODE_DATA(0) allocated [mem 0x2c3ffd000-0x2c3ffffff]
Feb 19 10:03:54 arch kernel: Zone ranges:
Feb 19 10:03:54 arch kernel:   DMA      [mem 0x0000000000001000-0x0000000000ffffff]
Feb 19 10:03:54 arch kernel:   DMA32    [mem 0x0000000001000000-0x00000000ffffffff]
Feb 19 10:03:54 arch kernel:   Normal   [mem 0x0000000100000000-0x00000002c3ffffff]
Feb 19 10:03:54 arch kernel:   Device   empty
Feb 19 10:03:54 arch kernel: Movable zone start for each node
Feb 19 10:03:54 arch kernel: Early memory node ranges
Feb 19 10:03:54 arch kernel:   node   0: [mem 0x0000000000001000-0x0000000000057fff]
Feb 19 10:03:54 arch kernel:   node   0: [mem 0x0000000000059000-0x0000000000085fff]
Feb 19 10:03:54 arch kernel:   node   0: [mem 0x0000000000100000-0x000000001877afff]
Feb 19 10:03:54 arch kernel:   node   0: [mem 0x00000000187c6000-0x0000000018878fff]
Feb 19 10:03:54 arch kernel:   node   0: [mem 0x0000000019179000-0x000000002f38dfff]
Feb 19 10:03:54 arch kernel:   node   0: [mem 0x000000002fffe000-0x000000002fffefff]
Feb 19 10:03:54 arch kernel:   node   0: [mem 0x0000000100000000-0x00000002c3ffffff]
Feb 19 10:03:54 arch kernel: Initmem setup node 0 [mem 0x0000000000001000-0x00000002c3ffffff]
Feb 19 10:03:54 arch kernel: On node 0 totalpages: 2042312
Feb 19 10:03:54 arch kernel:   DMA zone: 64 pages used for memmap
Feb 19 10:03:54 arch kernel:   DMA zone: 22 pages reserved
Feb 19 10:03:54 arch kernel:   DMA zone: 3972 pages, LIFO batch:0
Feb 19 10:03:54 arch kernel:   DMA32 zone: 2922 pages used for memmap
Feb 19 10:03:54 arch kernel:   DMA32 zone: 186948 pages, LIFO batch:31
Feb 19 10:03:54 arch kernel:   Normal zone: 28928 pages used for memmap
Feb 19 10:03:54 arch kernel:   Normal zone: 1851392 pages, LIFO batch:31
Feb 19 10:03:54 arch kernel: Reserved but unavailable: 99 pages
Feb 19 10:03:54 arch kernel: Reserving Intel graphics memory at 0x0000000039000000-0x000000003affffff
Feb 19 10:03:54 arch kernel: ACPI: PM-Timer IO Port: 0x1808
Feb 19 10:03:54 arch kernel: ACPI: Local APIC address 0xfee00000
Feb 19 10:03:54 arch kernel: ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Feb 19 10:03:54 arch kernel: ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Feb 19 10:03:54 arch kernel: ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Feb 19 10:03:54 arch kernel: ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1])
Feb 19 10:03:54 arch kernel: ACPI: LAPIC_NMI (acpi_id[0x05] high edge lint[0x1])
Feb 19 10:03:54 arch kernel: ACPI: LAPIC_NMI (acpi_id[0x06] high edge lint[0x1])
Feb 19 10:03:54 arch kernel: ACPI: LAPIC_NMI (acpi_id[0x07] high edge lint[0x1])
Feb 19 10:03:54 arch kernel: ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Feb 19 10:03:54 arch kernel: IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-119
Feb 19 10:03:54 arch kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Feb 19 10:03:54 arch kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Feb 19 10:03:54 arch kernel: ACPI: IRQ0 used by override.
Feb 19 10:03:54 arch kernel: ACPI: IRQ9 used by override.
Feb 19 10:03:54 arch kernel: Using ACPI (MADT) for SMP configuration information
Feb 19 10:03:54 arch kernel: ACPI: HPET id: 0x8086a201 base: 0xfed00000
Feb 19 10:03:54 arch kernel: [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0xb2 (or later)
Feb 19 10:03:54 arch kernel: smpboot: Allowing 8 CPUs, 0 hotplug CPUs
Feb 19 10:03:54 arch kernel: PM: Registered nosave memory: [mem 0x00000000-0x00000fff]
Feb 19 10:03:54 arch kernel: PM: Registered nosave memory: [mem 0x00058000-0x00058fff]
Feb 19 10:03:54 arch kernel: PM: Registered nosave memory: [mem 0x00086000-0x000fffff]
Feb 19 10:03:54 arch kernel: PM: Registered nosave memory: [mem 0x1877b000-0x1877bfff]
Feb 19 10:03:54 arch kernel: PM: Registered nosave memory: [mem 0x1877c000-0x187c5fff]
Feb 19 10:03:54 arch kernel: PM: Registered nosave memory: [mem 0x18879000-0x19178fff]
Feb 19 10:03:54 arch kernel: PM: Registered nosave memory: [mem 0x2f38e000-0x2f58dfff]
Feb 19 10:03:54 arch kernel: PM: Registered nosave memory: [mem 0x2f58e000-0x2fd7dfff]
Feb 19 10:03:54 arch kernel: PM: Registered nosave memory: [mem 0x2fd7e000-0x2ff7dfff]
Feb 19 10:03:54 arch kernel: PM: Registered nosave memory: [mem 0x2ff7e000-0x2fffdfff]
Feb 19 10:03:54 arch kernel: PM: Registered nosave memory: [mem 0x2ffff000-0x3affffff]
Feb 19 10:03:54 arch kernel: PM: Registered nosave memory: [mem 0x3b000000-0xdfffffff]
Feb 19 10:03:54 arch kernel: PM: Registered nosave memory: [mem 0xe0000000-0xefffffff]
Feb 19 10:03:54 arch kernel: PM: Registered nosave memory: [mem 0xf0000000-0xfcffffff]
Feb 19 10:03:54 arch kernel: PM: Registered nosave memory: [mem 0xfd000000-0xfe7fffff]
Feb 19 10:03:54 arch kernel: PM: Registered nosave memory: [mem 0xfe800000-0xfeafffff]
Feb 19 10:03:54 arch kernel: PM: Registered nosave memory: [mem 0xfeb00000-0xfeb03fff]
Feb 19 10:03:54 arch kernel: PM: Registered nosave memory: [mem 0xfeb04000-0xfebfffff]
Feb 19 10:03:54 arch kernel: PM: Registered nosave memory: [mem 0xfec00000-0xfec00fff]
Feb 19 10:03:54 arch kernel: PM: Registered nosave memory: [mem 0xfec01000-0xfecfffff]
Feb 19 10:03:54 arch kernel: PM: Registered nosave memory: [mem 0xfed00000-0xfed00fff]
Feb 19 10:03:54 arch kernel: PM: Registered nosave memory: [mem 0xfed01000-0xfed0ffff]
Feb 19 10:03:54 arch kernel: PM: Registered nosave memory: [mem 0xfed10000-0xfed19fff]
Feb 19 10:03:54 arch kernel: PM: Registered nosave memory: [mem 0xfed1a000-0xfed83fff]
Feb 19 10:03:54 arch kernel: PM: Registered nosave memory: [mem 0xfed84000-0xfed84fff]
Feb 19 10:03:54 arch kernel: PM: Registered nosave memory: [mem 0xfed85000-0xfedfffff]
Feb 19 10:03:54 arch kernel: PM: Registered nosave memory: [mem 0xfee00000-0xfee00fff]
Feb 19 10:03:54 arch kernel: PM: Registered nosave memory: [mem 0xfee01000-0xff9fffff]
Feb 19 10:03:54 arch kernel: PM: Registered nosave memory: [mem 0xffa00000-0xffffffff]
Feb 19 10:03:54 arch kernel: e820: [mem 0x3b000000-0xdfffffff] available for PCI devices
Feb 19 10:03:54 arch kernel: Booting paravirtualized kernel on bare hardware
Feb 19 10:03:54 arch kernel: clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1910969940391419 ns
Feb 19 10:03:54 arch kernel: setup_percpu: NR_CPUS:320 nr_cpumask_bits:320 nr_cpu_ids:8 nr_node_ids:1
Feb 19 10:03:54 arch kernel: percpu: Embedded 45 pages/cpu @        (ptrval) s147456 r8192 d28672 u262144
Feb 19 10:03:54 arch kernel: pcpu-alloc: s147456 r8192 d28672 u262144 alloc=1*2097152
Feb 19 10:03:54 arch kernel: pcpu-alloc: [0] 0 1 2 3 4 5 6 7
Feb 19 10:03:54 arch kernel: Built 1 zonelists, mobility grouping on.  Total pages: 2010376
Feb 19 10:03:54 arch kernel: Policy zone: Normal
Feb 19 10:03:54 arch kernel: Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=2e730657-891d-48af-8b54-55d3325de50b rw
Feb 19 10:03:54 arch kernel: Calgary: detecting Calgary via BIOS EBDA area
Feb 19 10:03:54 arch kernel: Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Feb 19 10:03:54 arch kernel: Memory: 7889748K/8169248K available (10252K kernel code, 1250K rwdata, 3224K rodata, 1428K init, 632K bss, 279500K reserved, 0K cma-reserved)
Feb 19 10:03:54 arch kernel: SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1
Feb 19 10:03:54 arch kernel: Kernel/User page tables isolation: enabled
Feb 19 10:03:54 arch kernel: ftrace: allocating 31409 entries in 123 pages
Feb 19 10:03:54 arch kernel: Preemptible hierarchical RCU implementation.
Feb 19 10:03:54 arch kernel:         CONFIG_RCU_FANOUT set to non-default value of 32
Feb 19 10:03:54 arch kernel:         RCU dyntick-idle grace-period acceleration is enabled.
Feb 19 10:03:54 arch kernel:         RCU restricting CPUs from NR_CPUS=320 to nr_cpu_ids=8.
Feb 19 10:03:54 arch kernel:         RCU priority boosting: priority 1 delay 500 ms.
Feb 19 10:03:54 arch kernel:         Tasks RCU enabled.
Feb 19 10:03:54 arch kernel: RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=8
Feb 19 10:03:54 arch kernel: NR_IRQS: 20736, nr_irqs: 2048, preallocated irqs: 16
Feb 19 10:03:54 arch kernel:         Offload RCU callbacks from CPUs: .
Feb 19 10:03:54 arch kernel: Console: colour dummy device 80x25
Feb 19 10:03:54 arch kernel: console [tty0] enabled
Feb 19 10:03:54 arch kernel: ACPI: Core revision 20170831
Feb 19 10:03:54 arch kernel: ACPI: 11 ACPI AML tables successfully acquired and loaded
Feb 19 10:03:54 arch kernel: clocksource: hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 79635855245 ns
Feb 19 10:03:54 arch kernel: hpet clockevent registered
Feb 19 10:03:54 arch kernel: APIC: Switch to symmetric I/O mode setup
Feb 19 10:03:54 arch kernel: DMAR: Host address width 39
Feb 19 10:03:54 arch kernel: DMAR: DRHD base: 0x000000fed90000 flags: 0x0
Feb 19 10:03:54 arch kernel: DMAR: dmar0: reg_base_addr fed90000 ver 1:0 cap 1c0000c40660462 ecap 7e3ff0501e
Feb 19 10:03:54 arch kernel: DMAR: DRHD base: 0x000000fed91000 flags: 0x1
Feb 19 10:03:54 arch kernel: DMAR: dmar1: reg_base_addr fed91000 ver 1:0 cap d2008c40660462 ecap f050da
Feb 19 10:03:54 arch kernel: DMAR: RMRR base: 0x0000002fc59000 end: 0x0000002fc78fff
Feb 19 10:03:54 arch kernel: DMAR: RMRR base: 0x00000038800000 end: 0x0000003affffff
Feb 19 10:03:54 arch kernel: DMAR: ANDD device: 1 name: \_SB.PCI0.I2C0
Feb 19 10:03:54 arch kernel: DMAR: ANDD device: 2 name: \_SB.PCI0.I2C1
Feb 19 10:03:54 arch kernel: DMAR-IR: IOAPIC id 2 under DRHD base  0xfed91000 IOMMU 1
Feb 19 10:03:54 arch kernel: DMAR-IR: HPET id 0 under DRHD base 0xfed91000
Feb 19 10:03:54 arch kernel: DMAR-IR: x2apic is disabled because BIOS sets x2apic opt out bit.
Feb 19 10:03:54 arch kernel: DMAR-IR: Use 'intremap=no_x2apic_optout' to override the BIOS setting.
Feb 19 10:03:54 arch kernel: DMAR-IR: Enabled IRQ remapping in xapic mode
Feb 19 10:03:54 arch kernel: x2apic: IRQ remapping doesn't support X2APIC mode
Feb 19 10:03:54 arch kernel: ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Feb 19 10:03:54 arch kernel: tsc: Detected 2600.000 MHz processor
Feb 19 10:03:54 arch kernel: tsc: Detected 2592.000 MHz TSC
Feb 19 10:03:54 arch kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 5184.00 BogoMIPS (lpj=2592000)
Feb 19 10:03:54 arch kernel: pid_max: default: 32768 minimum: 301
Feb 19 10:03:54 arch kernel: Security Framework initialized
Feb 19 10:03:54 arch kernel: Yama: becoming mindful.
Feb 19 10:03:54 arch kernel: Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes)
Feb 19 10:03:54 arch kernel: Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes)
Feb 19 10:03:54 arch kernel: Mount-cache hash table entries: 16384 (order: 5, 131072 bytes)
Feb 19 10:03:54 arch kernel: Mountpoint-cache hash table entries: 16384 (order: 5, 131072 bytes)
Feb 19 10:03:54 arch kernel: CPU: Physical Processor ID: 0
Feb 19 10:03:54 arch kernel: CPU: Processor Core ID: 0
Feb 19 10:03:54 arch kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Feb 19 10:03:54 arch kernel: ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Feb 19 10:03:54 arch kernel: mce: CPU supports 10 MCE banks
Feb 19 10:03:54 arch kernel: CPU0: Thermal monitoring enabled (TM1)
Feb 19 10:03:54 arch kernel: process: using mwait in idle threads
Feb 19 10:03:54 arch kernel: Last level iTLB entries: 4KB 64, 2MB 8, 4MB 8
Feb 19 10:03:54 arch kernel: Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0, 1GB 4
Feb 19 10:03:54 arch kernel: Spectre V2 : Mitigation: Full generic retpoline

I tried to install xf86-video-intel but the problem is already there . Maybe beacuse I must add kernel parameters like nomodset. But to be sure i removed the driver again and I wrote here

seth · 2018-02-19 15:26:32

"especially"

"nomodeset" is certainly not going to work and I don't think this is related to having used the modesetting ddx driver once (and then getting it after a reboot despite now using the intel driver)
Did you try the lts kernel in this regard (itr ;-) and can you still ping the machine after a failed resume? (Preferably over a wired ethernet connection)
Also try to suspend the system from the multi-user.target, https://wiki.archlinux.org/index.php/Sy … ent_target

Cristhian · 2018-02-19 15:54:17

I tried this one and the problem is already there.

systemctl set-default multi-user.target

After this command now I noticed that the X server does not start automatically. After boot I have to login in the tty and launch

startx

And everything goes fine. How can I come back to the configuration before

systemctl set-default multi-user.target

?

What does it means ping the machine? I tried the command

ping

followed by my ip and nothing wrong happend.
When I install Arch I always choose Vanilla kernel because simply I don't know anything about kernel .
Anyway I don't want to do an installation of Arch right now , how can I solve this problems that was not there before doing all this things?

Last edited by Cristhian (2018-02-19 15:57:32)

seth · 2018-02-19 15:57:33

That's the point of the multi-user.target and the idea was to try whether the suspend/resume issues also occur *without* a graphical session (ie. suspend from the TTY login)
From the linked section of the linked wiki:

The standard target is default.target, which is aliased by default to graphical.target

You should ping that machine from another one (in the same network) when it's not coming up after a suspend to check whether this is a graphical/output thing "only".

Edit: copied too few tokens from the article ;-)

Last edited by seth (2018-02-19 15:58:43)

Cristhian · 2018-02-19 16:15:16

Also without a graphical

systemctl suspend

give me a black screen when resuming.
But I tried also

reboot

and this work perfectly.
So I think there is something dealing with systemctl, because

systemctl reboot

does not work.

To ping , can I use ssh and ping form my tablet with JuiceSsh ?

Cristhian · 2018-02-19 16:23:41

Sorry I have to be more specific
Without a graphic both commands for reboot , works. The only one that is problematic is the one used to suspend.
While starting X , reboot is the only one that works.

Last edited by Cristhian (2018-02-19 16:26:44)

Cristhian · 2018-02-19 17:20:11

@seth Maybe this can solve. https://bbs.archlinux.org/viewtopic.php … 8#p1310958
What do you think?

Arch Linux

#1 2018-02-17 16:45:54

[SOLVED] Screen goes off (xdg-screensaver) and can't resume

#2 2018-02-17 20:56:31

Re: [SOLVED] Screen goes off (xdg-screensaver) and can't resume

#3 2018-02-18 04:09:48

Re: [SOLVED] Screen goes off (xdg-screensaver) and can't resume

#4 2018-02-18 08:09:13

Re: [SOLVED] Screen goes off (xdg-screensaver) and can't resume

#5 2018-02-18 09:27:50

Re: [SOLVED] Screen goes off (xdg-screensaver) and can't resume

#6 2018-02-18 10:15:29

Re: [SOLVED] Screen goes off (xdg-screensaver) and can't resume

#7 2018-02-18 10:31:54

Re: [SOLVED] Screen goes off (xdg-screensaver) and can't resume

#8 2018-02-18 11:08:11

Re: [SOLVED] Screen goes off (xdg-screensaver) and can't resume

#9 2018-02-18 11:13:42

Re: [SOLVED] Screen goes off (xdg-screensaver) and can't resume

#10 2018-02-18 11:43:45

Re: [SOLVED] Screen goes off (xdg-screensaver) and can't resume

#11 2018-02-18 11:51:15

Re: [SOLVED] Screen goes off (xdg-screensaver) and can't resume

#12 2018-02-18 12:35:57

Re: [SOLVED] Screen goes off (xdg-screensaver) and can't resume

#13 2018-02-18 14:53:45

Re: [SOLVED] Screen goes off (xdg-screensaver) and can't resume

#14 2018-02-18 15:11:38

Re: [SOLVED] Screen goes off (xdg-screensaver) and can't resume

#15 2018-02-18 17:16:07

Re: [SOLVED] Screen goes off (xdg-screensaver) and can't resume

#16 2018-02-18 19:04:38

Re: [SOLVED] Screen goes off (xdg-screensaver) and can't resume

#17 2018-02-18 20:10:21

Re: [SOLVED] Screen goes off (xdg-screensaver) and can't resume

#18 2018-02-18 20:24:35

Re: [SOLVED] Screen goes off (xdg-screensaver) and can't resume

#19 2018-02-19 10:22:23

Re: [SOLVED] Screen goes off (xdg-screensaver) and can't resume

#20 2018-02-19 15:26:32

Re: [SOLVED] Screen goes off (xdg-screensaver) and can't resume

#21 2018-02-19 15:54:17

Re: [SOLVED] Screen goes off (xdg-screensaver) and can't resume

#22 2018-02-19 15:57:33

Re: [SOLVED] Screen goes off (xdg-screensaver) and can't resume

#23 2018-02-19 16:15:16

Re: [SOLVED] Screen goes off (xdg-screensaver) and can't resume

#24 2018-02-19 16:23:41

Re: [SOLVED] Screen goes off (xdg-screensaver) and can't resume

#25 2018-02-19 17:20:11

Re: [SOLVED] Screen goes off (xdg-screensaver) and can't resume

Board footer