[Awesome] Screen temporarily freezing on a regular basis

sylv3r · 2017-09-14 21:27:44

Hello everyone,

Since I installed my new laptop with Arch and Awesome, I notice a strange behavior. The screen stop refreshing its content on a regular basis (every few minutes or so). Everything else is working (sound, mouse, keyboard,...) and a single action like switching tab on Chrome, switching desktop or even a right-click trigger a refresh and everything is back to normal and smooth.
This is especially happening when in Chrome or viewing videos. Never noticed the problem while on a terminal or an IDE. This seems related when heavy content refresh is needed (scrolling the web, videos, etc), but I can't be sure, there's nothing special in the logs/journal about it when this is happening.

Does anyone has any clue about what could do that and how to fix it ?

A few informations about my config :

Laptop: Razer Blade Stealth late 2016
Distro: "Arch Linux" x86_64
Kernel: 4.12.6-1-ARCH
WindowManager: awesome
DesktopEnvironment: None
CPU: Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz
GPU: Intel Corporation HD Graphics 620 (rev 02)

This is very annoying and I didn't find an answer anywhere yet.
Any help would be much appreciated

Thanks !

Last edited by sylv3r (2017-09-15 01:39:48)

seth · 2017-09-15 07:15:52

Are you also using a compositor (compton etc.)?

sylv3r · 2017-09-16 00:09:51

No, nothing special, only this good old X11 out of the box and awesome. I can provide my X11 configuration, but nothing really exotic in here.

seth · 2017-09-16 06:36:15

xf86-video-intel or modesetting driver? Does it happen with the other one?

I don't think it's a stalled I/O (because input breaks it ;-) but something™ could grab the server and forget to release it. Since predominantly the WM is prone to this, try openbox. (But I will say that this doesn't fit the "playing video" context)

Ultimately please provide your xorg log - you should btw. not have/use a static xorg.conf nowadays.

vlogswawa · 2017-09-29 10:03:12

I have the same issue. macbook pro late 2016/ amd radeon rx 460. i tried gnome and xfce4 both have no problem!
any idea how to fix this?

vlogswawa · 2017-09-29 10:17:44

this is from journalctl you can see awesome is blocked for more than 2 min:

Aug 16 20:58:28 oden kernel: INFO: task awesome:1218 blocked for more than 120 seconds.
Aug 16 20:58:28 oden kernel:       Tainted: G           O    4.12.6-1-ARCH #1
Aug 16 20:58:28 oden kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Aug 16 20:58:28 oden kernel: awesome         D    0  1218   1208 0x00000000
Aug 16 20:58:28 oden kernel: Call Trace:
Aug 16 20:58:28 oden kernel:  __schedule+0x236/0x870
Aug 16 20:58:28 oden kernel:  schedule+0x3d/0x90
Aug 16 20:58:28 oden kernel:  schedule_preempt_disabled+0x15/0x20
Aug 16 20:58:28 oden kernel:  __mutex_lock.isra.5+0x295/0x530
Aug 16 20:58:28 oden kernel:  ? __d_lookup+0x86/0x150
Aug 16 20:58:28 oden kernel:  __mutex_lock_slowpath+0x13/0x20
Aug 16 20:58:28 oden kernel:  ? __mutex_lock_slowpath+0x13/0x20
Aug 16 20:58:28 oden kernel:  mutex_lock+0x25/0x30
Aug 16 20:58:28 oden kernel:  acpi_smbus_transaction+0x51/0x300 [sbshc]
Aug 16 20:58:28 oden kernel:  ? kernfs_fop_open+0x9b/0x390
Aug 16 20:58:28 oden kernel:  acpi_smbus_read+0x1b/0x20 [sbshc]
Aug 16 20:58:28 oden kernel:  acpi_battery_get_state+0x78/0xa0 [sbs]
Aug 16 20:58:28 oden kernel:  acpi_sbs_battery_get_property+0x56/0x3e0 [sbs]
Aug 16 20:58:28 oden kernel:  power_supply_read_temp+0x45/0x80
Aug 16 20:58:28 oden kernel:  ? path_openat+0x2a8/0x13a0
Aug 16 20:58:28 oden kernel:  thermal_zone_get_temp+0x54/0x70
Aug 16 20:58:28 oden kernel:  temp_show+0x2d/0x60
Aug 16 20:58:28 oden kernel:  dev_attr_show+0x20/0x50
Aug 16 20:58:28 oden kernel:  sysfs_kf_seq_show+0xb8/0x120
Aug 16 20:58:28 oden kernel:  kernfs_seq_show+0x21/0x30
Aug 16 20:58:28 oden kernel:  seq_read+0xc9/0x3f0
Aug 16 20:58:28 oden kernel:  kernfs_fop_read+0x134/0x180
Aug 16 20:58:28 oden kernel:  __vfs_read+0x37/0x130
Aug 16 20:58:28 oden kernel:  ? security_file_permission+0x9b/0xc0
Aug 16 20:58:28 oden kernel:  vfs_read+0x8e/0x130
Aug 16 20:58:28 oden kernel:  SyS_read+0x55/0xc0
Aug 16 20:58:28 oden kernel:  entry_SYSCALL_64_fastpath+0x1a/0xa5
Aug 16 20:58:28 oden kernel: RIP: 0033:0x7f644102abad
Aug 16 20:58:28 oden kernel: RSP: 002b:00007ffd66c597c0 EFLAGS: 00000293 ORIG_RAX: 0000000000000000
Aug 16 20:58:28 oden kernel: RAX: ffffffffffffffda RBX: 00007f64412ebad8 RCX: 00007f644102abad
Aug 16 20:58:28 oden kernel: RDX: 0000000000002000 RSI: 00007ffd66c59870 RDI: 000000000000000a
Aug 16 20:58:28 oden kernel: RBP: 0000000000002710 R08: 0000000000000670 R09: 000000000000007c
Aug 16 20:58:28 oden kernel: R10: 00007f64412ebad8 R11: 0000000000000293 R12: 00007f64412ebad8
Aug 16 20:58:28 oden kernel: R13: 0000000000000270 R14: 000000f4315e41a0 R15: 00007f64412eba80
Aug 16 20:58:28 oden kernel: INFO: task kworker/0:9:2019 blocked for more than 120 seconds.
Aug 16 20:58:28 oden kernel:       Tainted: G           O    4.12.6-1-ARCH #1

Last edited by vlogswawa (2017-10-05 09:16:51)

asusu · 2017-10-04 13:17:41

I have the exact same problem.

VGA: Intel Corporation HD Graphics 5500 (rev 09)
CPU: Intel(R) Core(TM) i7-5600U

Suspicous log in dmesg:

Wed Oct 4 13:13:41 2017] DMAR: DRHD: handling fault status reg 3
[Wed Oct 4 13:13:41 2017] DMAR: [DMA Write] Request device [00:02.0] fault addr 9f5000 [fault reason 23] Unknown
[Wed Oct 4 13:13:50 2017] drm/i915: Resetting chip after gpu hang
[Wed Oct 4 13:13:51 2017] asynchronous wait on fence i915:Xorg[12480]/0:1d31 timed out
[Wed Oct 4 13:14:04 2017] drm/i915: Resetting chip after gpu hang
[Wed Oct 4 13:20:01 2017] DMAR: DRHD: handling fault status reg 3
[Wed Oct 4 13:20:01 2017] DMAR: [DMA Write] Request device [00:02.0] fault addr bbf000 [fault reason 23] Unknown
[Wed Oct 4 13:20:11 2017] drm/i915: Resetting chip after gpu hang
[Wed Oct 4 13:20:24 2017] drm/i915: Resetting chip after gpu hang
[Wed Oct 4 15:03:31 2017] DMAR: DRHD: handling fault status reg 2
[Wed Oct 4 15:03:31 2017] DMAR: [DMA Write] Request device [00:02.0] fault addr 1f36000 [fault reason 23] Unknown
[Wed Oct 4 15:03:41 2017] drm/i915: Resetting chip after gpu hang
[Wed Oct 4 15:03:41 2017] DMAR: DRHD: handling fault status reg 2
[Wed Oct 4 15:03:41 2017] DMAR: [DMA Write] Request device [00:02.0] fault addr 1f37000 [fault reason 23] Unknown
[Wed Oct 4 15:03:42 2017] asynchronous wait on fence i915:Xorg[22361]/0:beb1 timed out
[Wed Oct 4 15:03:49 2017] drm/i915: Resetting chip after gpu hang
[Wed Oct 4 15:04:36 2017] DMAR: DRHD: handling fault status reg 3
[Wed Oct 4 15:04:36 2017] DMAR: [DMA Write] Request device [00:02.0] fault addr 81000 [fault reason 23] Unknown
[Wed Oct 4 15:04:45 2017] drm/i915: Resetting chip after gpu hang
[Wed Oct 4 15:04:54 2017] DMAR: DRHD: handling fault status reg 3
[Wed Oct 4 15:04:54 2017] DMAR: [DMA Write] Request device [00:02.0] fault addr 81000 [fault reason 23] Unknown
[Wed Oct 4 15:05:03 2017] drm/i915: Resetting chip after gpu hang
[Wed Oct 4 15:10:10 2017] DMAR: DRHD: handling fault status reg 3
[Wed Oct 4 15:10:10 2017] DMAR: [DMA Write] Request device [00:02.0] fault addr 1f36000 [fault reason 23] Unknown
[Wed Oct 4 15:10:20 2017] drm/i915: Resetting chip after gpu hang
[Wed Oct 4 15:10:22 2017] DMAR: DRHD: handling fault status reg 3
[Wed Oct 4 15:10:22 2017] DMAR: [DMA Write] Request device [00:02.0] fault addr 1c43000 [fault reason 23] Unknown
[Wed Oct 4 15:10:30 2017] drm/i915: Resetting chip after gpu hang
[Wed Oct 4 15:11:33 2017] DMAR: DRHD: handling fault status reg 3
[Wed Oct 4 15:11:33 2017] DMAR: [DMA Write] Request device [00:02.0] fault addr 1efb000 [fault reason 23] Unknown
[Wed Oct 4 15:11:42 2017] drm/i915: Resetting chip after gpu hang
[Wed Oct 4 15:11:51 2017] DMAR: DRHD: handling fault status reg 3
[Wed Oct 4 15:11:51 2017] DMAR: [DMA Write] Request device [00:02.0] fault addr 1c46000 [fault reason 23] Unknown
[Wed Oct 4 15:12:00 2017] drm/i915: Resetting chip after gpu hang

seth · 2017-10-04 14:14:13

vlogswawa & asusu, please edit your posts and wrap them into "code" tags.

@asusu, your problem is unrelated, see https://bbs.archlinux.org/viewtopic.php?id=230362
@vlogswawa, looks like https://bbs.archlinux.org/viewtopic.php?id=205186 where it hit i3. Smells related to a battery and/or temperature indicator in awesome - does that ring a bell?

Arch Linux

#1 2017-09-14 21:27:44

[Awesome] Screen temporarily freezing on a regular basis

#2 2017-09-15 07:15:52

Re: [Awesome] Screen temporarily freezing on a regular basis

#3 2017-09-16 00:09:51

Re: [Awesome] Screen temporarily freezing on a regular basis

#4 2017-09-16 06:36:15

Re: [Awesome] Screen temporarily freezing on a regular basis

#5 2017-09-29 10:03:12

Re: [Awesome] Screen temporarily freezing on a regular basis

#6 2017-09-29 10:17:44

Re: [Awesome] Screen temporarily freezing on a regular basis

#7 2017-10-04 13:17:41

Re: [Awesome] Screen temporarily freezing on a regular basis

#8 2017-10-04 14:14:13

Re: [Awesome] Screen temporarily freezing on a regular basis

Board footer