Arch Linux

vlogswawa

Member

Registered: 2017-09-29

Posts: 26

awesome WM freezes each min!!!

i have macbook pro late 2016 with touch bar, i do use awesome WM, and i'm really addicted to it. the problem i just can't work on my mbp, awesome wm freezes each minute.
i only have this problem with awesome wm, if i'm on gnome or kde ..., my mbp works fine!!!

here is what causes this:
Jan 12 11:42:32 oden kernel: INFO: task kworker/0:11:1502 blocked for more than 120 seconds.

journalctl:

Jan 12 11:37:10 oden systemd[3297]: Started Virtual filesystem service.
Jan 12 11:37:18 oden systemd[3297]: Starting Sound Service...
Jan 12 11:37:18 oden rtkit-daemon[896]: Successfully made thread 3437 of process 3437 (/usr/bin/pulseaudio) owned by '1001' high priority at nice level -11.
Jan 12 11:37:18 oden rtkit-daemon[896]: Supervising 1 threads of 1 processes of 1 users.
Jan 12 11:37:19 oden rtkit-daemon[896]: Supervising 1 threads of 1 processes of 1 users.
Jan 12 11:37:19 oden rtkit-daemon[896]: Successfully made thread 3438 of process 3437 (/usr/bin/pulseaudio) owned by '1001' RT at priority 5.
Jan 12 11:37:19 oden rtkit-daemon[896]: Supervising 2 threads of 1 processes of 1 users.
Jan 12 11:37:19 oden rtkit-daemon[896]: Supervising 2 threads of 1 processes of 1 users.
Jan 12 11:37:19 oden rtkit-daemon[896]: Successfully made thread 3439 of process 3437 (/usr/bin/pulseaudio) owned by '1001' RT at priority 5.
Jan 12 11:37:19 oden rtkit-daemon[896]: Supervising 3 threads of 1 processes of 1 users.
Jan 12 11:37:19 oden dbus-daemon[424]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.209' (uid=1001 pid=3437 comm="/usr/bin/pulseaudio --daemonize=no ")
Jan 12 11:37:19 oden dbus-daemon[424]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service not found.
Jan 12 11:37:19 oden systemd[3297]: Started Sound Service.
Jan 12 11:37:19 oden pulseaudio[3437]: E: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.systemd1.NoSuchUnit: Unit dbus-org.bluez.service not found.
Jan 12 11:37:29 oden dbus-daemon[3377]: [session uid=1001 pid=3377] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.13' (uid=1001 pid=3560 comm="/usr/lib/chromium/chromium --force-device-scale-fa")
Jan 12 11:37:29 oden systemd[3297]: Starting Accessibility services bus...
Jan 12 11:37:29 oden dbus-daemon[3377]: [session uid=1001 pid=3377] Successfully activated service 'org.a11y.Bus'
Jan 12 11:37:29 oden systemd[3297]: Started Accessibility services bus.
Jan 12 11:37:29 oden at-spi-bus-launcher[3574]: dbus-daemon[3579]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=1001 pid=3560 comm="/usr/lib/chromium/chromium --force-device-scale-fa")
Jan 12 11:37:29 oden at-spi-bus-launcher[3574]: dbus-daemon[3579]: Successfully activated service 'org.a11y.atspi.Registry'
Jan 12 11:37:29 oden at-spi-bus-launcher[3574]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Jan 12 11:37:29 oden dbus-daemon[424]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.210' (uid=1001 pid=3560 comm="/usr/lib/chromium/chromium --force-device-scale-fa")
Jan 12 11:37:29 oden dbus-daemon[424]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service not found.
Jan 12 11:39:21 oden dbus-daemon[424]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.241' (uid=1001 pid=5301 comm="/usr/lib/chromium/chromium --force-device-scale-fa")
Jan 12 11:39:21 oden dbus-daemon[424]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service not found.
Jan 12 11:42:32 oden kernel: INFO: task kworker/0:11:1502 blocked for more than 120 seconds.
Jan 12 11:42:32 oden kernel:       Tainted: G           O    4.14.4-1-ARCH #1
Jan 12 11:42:32 oden kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jan 12 11:42:32 oden kernel: kworker/0:11    D    0  1502      2 0x80000000
Jan 12 11:42:32 oden kernel: Workqueue: kec_query acpi_ec_event_processor
Jan 12 11:42:32 oden kernel: Call Trace:
Jan 12 11:42:32 oden kernel:  ? __schedule+0x239/0x870
Jan 12 11:42:32 oden kernel:  schedule+0x2f/0x90
Jan 12 11:42:32 oden kernel:  schedule_preempt_disabled+0x11/0x20
Jan 12 11:42:32 oden kernel:  __mutex_lock.isra.2+0x288/0x510
Jan 12 11:42:32 oden kernel:  ? smbus_alarm+0x73/0x110 [sbshc]
Jan 12 11:42:32 oden kernel:  smbus_alarm+0x73/0x110 [sbshc]
Jan 12 11:42:32 oden kernel:  acpi_ec_event_processor+0x23/0x90
Jan 12 11:42:32 oden kernel:  process_one_work+0x1db/0x410
Jan 12 11:42:32 oden kernel:  worker_thread+0x2b/0x3d0
Jan 12 11:42:32 oden kernel:  ? process_one_work+0x410/0x410
Jan 12 11:42:32 oden kernel:  kthread+0x118/0x130
Jan 12 11:42:32 oden kernel:  ? kthread_create_on_node+0x70/0x70
Jan 12 11:42:32 oden kernel:  ret_from_fork+0x25/0x30
Jan 12 11:42:32 oden kernel: INFO: task kworker/0:13:1504 blocked for more than 120 seconds.
Jan 12 11:42:32 oden kernel:       Tainted: G           O    4.14.4-1-ARCH #1
Jan 12 11:42:32 oden kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jan 12 11:42:32 oden kernel: kworker/0:13    D    0  1504      2 0x80000000
Jan 12 11:42:32 oden kernel: Workqueue: kec_query acpi_ec_event_processor
Jan 12 11:42:32 oden kernel: Call Trace:
Jan 12 11:42:32 oden kernel:  ? __schedule+0x239/0x870
Jan 12 11:42:32 oden kernel:  schedule+0x2f/0x90
Jan 12 11:42:32 oden kernel:  schedule_preempt_disabled+0x11/0x20
Jan 12 11:42:32 oden kernel:  __mutex_lock.isra.2+0x288/0x510
Jan 12 11:42:32 oden kernel:  ? smbus_alarm+0x73/0x110 [sbshc]
Jan 12 11:42:32 oden kernel:  smbus_alarm+0x73/0x110 [sbshc]
Jan 12 11:42:32 oden kernel:  acpi_ec_event_processor+0x23/0x90
Jan 12 11:42:32 oden kernel:  process_one_work+0x1db/0x410
Jan 12 11:42:32 oden kernel:  worker_thread+0x2b/0x3d0
Jan 12 11:42:32 oden kernel:  ? process_one_work+0x410/0x410
Jan 12 11:42:32 oden kernel:  kthread+0x118/0x130
Jan 12 11:42:32 oden kernel:  ? kthread_create_on_node+0x70/0x70
Jan 12 11:42:32 oden kernel:  ret_from_fork+0x25/0x30
Jan 12 11:42:32 oden kernel: INFO: task kworker/0:15:1517 blocked for more than 120 seconds.
Jan 12 11:42:32 oden kernel:       Tainted: G           O    4.14.4-1-ARCH #1
Jan 12 11:42:32 oden kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jan 12 11:42:32 oden kernel: kworker/0:15    D    0  1517      2 0x80000000
Jan 12 11:42:32 oden kernel: Workqueue: kec_query acpi_ec_event_processor
Jan 12 11:42:32 oden kernel: Call Trace:
Jan 12 11:42:32 oden kernel:  ? __schedule+0x239/0x870
Jan 12 11:42:32 oden kernel:  schedule+0x2f/0x90
Jan 12 11:42:32 oden kernel:  schedule_preempt_disabled+0x11/0x20
Jan 12 11:42:32 oden kernel:  __mutex_lock.isra.2+0x288/0x510
Jan 12 11:42:32 oden kernel:  ? smbus_alarm+0x73/0x110 [sbshc]
Jan 12 11:42:32 oden kernel:  smbus_alarm+0x73/0x110 [sbshc]
Jan 12 11:42:32 oden kernel:  acpi_ec_event_processor+0x23/0x90
Jan 12 11:42:32 oden kernel:  process_one_work+0x1db/0x410
Jan 12 11:42:32 oden kernel:  worker_thread+0x2b/0x3d0
Jan 12 11:42:32 oden kernel:  ? process_one_work+0x410/0x410
Jan 12 11:42:32 oden kernel:  kthread+0x118/0x130
Jan 12 11:42:32 oden kernel:  ? kthread_create_on_node+0x70/0x70
Jan 12 11:42:32 oden kernel:  ? do_group_exit+0x3a/0xa0
Jan 12 11:42:32 oden kernel:  ret_from_fork+0x25/0x30
Jan 12 11:42:32 oden kernel: INFO: task kworker/0:16:1518 blocked for more than 120 seconds.
Jan 12 11:42:32 oden kernel:       Tainted: G           O    4.14.4-1-ARCH #1
Jan 12 11:42:32 oden kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jan 12 11:42:32 oden kernel: kworker/0:16    D    0  1518      2 0x80000000
Jan 12 11:42:32 oden kernel: Workqueue: kec_query acpi_ec_event_processor
Jan 12 11:42:32 oden kernel: Call Trace:
Jan 12 11:42:32 oden kernel:  ? __schedule+0x239/0x870
Jan 12 11:42:32 oden kernel:  schedule+0x2f/0x90
Jan 12 11:42:32 oden kernel:  schedule_preempt_disabled+0x11/0x20
Jan 12 11:42:32 oden kernel:  __mutex_lock.isra.2+0x288/0x510
Jan 12 11:42:32 oden kernel:  ? smbus_alarm+0x73/0x110 [sbshc]
Jan 12 11:42:32 oden kernel:  smbus_alarm+0x73/0x110 [sbshc]
Jan 12 11:42:32 oden kernel:  acpi_ec_event_processor+0x23/0x90
Jan 12 11:42:32 oden kernel:  process_one_work+0x1db/0x410
Jan 12 11:42:32 oden kernel:  worker_thread+0x2b/0x3d0
Jan 12 11:42:32 oden kernel:  ? process_one_work+0x410/0x410
Jan 12 11:42:32 oden kernel:  kthread+0x118/0x130
Jan 12 11:42:32 oden kernel:  ? kthread_create_on_node+0x70/0x70
Jan 12 11:42:32 oden kernel:  ret_from_fork+0x25/0x30
Jan 12 11:42:32 oden kernel: INFO: task kworker/1:0:1606 blocked for more than 120 seconds.
Jan 12 11:42:32 oden kernel:       Tainted: G           O    4.14.4-1-ARCH #1
Jan 12 11:42:32 oden kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jan 12 11:42:32 oden kernel: kworker/1:0     D    0  1606      2 0x80000000
Jan 12 11:42:32 oden kernel: Workqueue: kec_query acpi_ec_event_processor
Jan 12 11:42:32 oden kernel: Call Trace:
Jan 12 11:42:32 oden kernel:  ? __schedule+0x239/0x870
Jan 12 11:42:32 oden kernel:  schedule+0x2f/0x90
Jan 12 11:42:32 oden kernel:  schedule_preempt_disabled+0x11/0x20
Jan 12 11:42:32 oden kernel:  __mutex_lock.isra.2+0x288/0x510
Jan 12 11:42:32 oden kernel:  ? smbus_alarm+0x73/0x110 [sbshc]
Jan 12 11:42:32 oden kernel:  smbus_alarm+0x73/0x110 [sbshc]
Jan 12 11:42:32 oden kernel:  acpi_ec_event_processor+0x23/0x90
Jan 12 11:42:32 oden kernel:  process_one_work+0x1db/0x410
Jan 12 11:42:32 oden kernel:  worker_thread+0x2b/0x3d0
Jan 12 11:42:32 oden kernel:  ? process_one_work+0x410/0x410
Jan 12 11:42:32 oden kernel:  kthread+0x118/0x130
Jan 12 11:42:32 oden kernel:  ? kthread_create_on_node+0x70/0x70
Jan 12 11:42:32 oden kernel:  ? exit_to_usermode_loop+0x69/0xa0
Jan 12 11:42:32 oden kernel:  ret_from_fork+0x25/0x30
Jan 12 11:42:32 oden kernel: INFO: task kworker/0:0:2034 blocked for more than 120 seconds.
Jan 12 11:42:32 oden kernel:       Tainted: G           O    4.14.4-1-ARCH #1
Jan 12 11:42:32 oden kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jan 12 11:42:32 oden kernel: kworker/0:0     D    0  2034      2 0x80000000
Jan 12 11:42:32 oden kernel: Workqueue: kec_query acpi_ec_event_processor
Jan 12 11:42:32 oden kernel: Call Trace:
Jan 12 11:42:32 oden kernel:  ? __schedule+0x239/0x870
Jan 12 11:42:32 oden kernel:  schedule+0x2f/0x90
Jan 12 11:42:32 oden kernel:  schedule_preempt_disabled+0x11/0x20
Jan 12 11:42:32 oden kernel:  __mutex_lock.isra.2+0x288/0x510
Jan 12 11:42:32 oden kernel:  ? smbus_alarm+0x73/0x110 [sbshc]
Jan 12 11:42:32 oden kernel:  smbus_alarm+0x73/0x110 [sbshc]
Jan 12 11:42:32 oden kernel:  acpi_ec_event_processor+0x23/0x90
Jan 12 11:42:32 oden kernel:  process_one_work+0x1db/0x410
Jan 12 11:42:32 oden kernel:  worker_thread+0x2b/0x3d0
Jan 12 11:42:32 oden kernel:  ? process_one_work+0x410/0x410
Jan 12 11:42:32 oden kernel:  kthread+0x118/0x130
Jan 12 11:42:32 oden kernel:  ? kthread_create_on_node+0x70/0x70
Jan 12 11:42:32 oden kernel:  ? exit_to_usermode_loop+0x69/0xa0
Jan 12 11:42:32 oden kernel:  ret_from_fork+0x25/0x30
Jan 12 11:42:32 oden kernel: INFO: task kworker/0:1:2035 blocked for more than 120 seconds.
Jan 12 11:42:32 oden kernel:       Tainted: G           O    4.14.4-1-ARCH #1
Jan 12 11:42:32 oden kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jan 12 11:42:32 oden kernel: kworker/0:1     D    0  2035      2 0x80000000
Jan 12 11:42:32 oden kernel: Workqueue: kec_query acpi_ec_event_processor
Jan 12 11:42:32 oden kernel: Call Trace:
Jan 12 11:42:32 oden kernel:  ? __schedule+0x239/0x870
Jan 12 11:42:32 oden kernel:  schedule+0x2f/0x90
Jan 12 11:42:32 oden kernel:  schedule_preempt_disabled+0x11/0x20
Jan 12 11:42:32 oden kernel:  __mutex_lock.isra.2+0x288/0x510
Jan 12 11:42:32 oden kernel:  ? smbus_alarm+0x73/0x110 [sbshc]
Jan 12 11:42:32 oden kernel:  smbus_alarm+0x73/0x110 [sbshc]
Jan 12 11:42:32 oden kernel:  acpi_ec_event_processor+0x23/0x90
Jan 12 11:42:32 oden kernel:  process_one_work+0x1db/0x410
Jan 12 11:42:32 oden kernel:  worker_thread+0x2b/0x3d0
Jan 12 11:42:32 oden kernel:  ? process_one_work+0x410/0x410
Jan 12 11:42:32 oden kernel:  kthread+0x118/0x130
Jan 12 11:42:32 oden kernel:  ? kthread_create_on_node+0x70/0x70
Jan 12 11:42:32 oden kernel:  ? exit_to_usermode_loop+0x69/0xa0
Jan 12 11:42:32 oden kernel:  ret_from_fork+0x25/0x30
Jan 12 11:42:32 oden kernel: INFO: task kworker/0:2:2036 blocked for more than 120 seconds.
Jan 12 11:42:32 oden kernel:       Tainted: G           O    4.14.4-1-ARCH #1
Jan 12 11:42:32 oden kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jan 12 11:42:32 oden kernel: kworker/0:2     D    0  2036      2 0x80000000
Jan 12 11:42:32 oden kernel: Workqueue: kec_query acpi_ec_event_processor
Jan 12 11:42:32 oden kernel: Call Trace:
Jan 12 11:42:32 oden kernel:  ? __schedule+0x239/0x870
Jan 12 11:42:32 oden kernel:  schedule+0x2f/0x90
Jan 12 11:42:32 oden kernel:  schedule_preempt_disabled+0x11/0x20
Jan 12 11:42:32 oden kernel:  __mutex_lock.isra.2+0x288/0x510
Jan 12 11:42:32 oden kernel:  ? smbus_alarm+0x73/0x110 [sbshc]
Jan 12 11:42:32 oden kernel:  smbus_alarm+0x73/0x110 [sbshc]
Jan 12 11:42:32 oden kernel:  acpi_ec_event_processor+0x23/0x90
Jan 12 11:42:32 oden kernel:  process_one_work+0x1db/0x410
Jan 12 11:42:32 oden kernel:  worker_thread+0x2b/0x3d0
Jan 12 11:42:32 oden kernel:  ? process_one_work+0x410/0x410
Jan 12 11:42:32 oden kernel:  kthread+0x118/0x130
Jan 12 11:42:32 oden kernel:  ? kthread_create_on_node+0x70/0x70
Jan 12 11:42:32 oden kernel:  ret_from_fork+0x25/0x30
Jan 12 11:42:32 oden kernel: INFO: task kworker/0:4:2037 blocked for more than 120 seconds.
Jan 12 11:42:32 oden kernel:       Tainted: G           O    4.14.4-1-ARCH #1
Jan 12 11:42:32 oden kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jan 12 11:42:32 oden kernel: kworker/0:4     D    0  2037      2 0x80000000
Jan 12 11:42:32 oden kernel: Workqueue: kec_query acpi_ec_event_processor
Jan 12 11:42:32 oden kernel: Call Trace:
Jan 12 11:42:32 oden kernel:  ? __schedule+0x239/0x870
Jan 12 11:42:32 oden kernel:  schedule+0x2f/0x90
Jan 12 11:42:32 oden kernel:  schedule_preempt_disabled+0x11/0x20
Jan 12 11:42:32 oden kernel:  __mutex_lock.isra.2+0x288/0x510
Jan 12 11:42:32 oden kernel:  ? smbus_alarm+0x73/0x110 [sbshc]
Jan 12 11:42:32 oden kernel:  smbus_alarm+0x73/0x110 [sbshc]
Jan 12 11:42:32 oden kernel:  acpi_ec_event_processor+0x23/0x90
Jan 12 11:42:32 oden kernel:  process_one_work+0x1db/0x410
Jan 12 11:42:32 oden kernel:  worker_thread+0x2b/0x3d0
Jan 12 11:42:32 oden kernel:  ? process_one_work+0x410/0x410
Jan 12 11:42:32 oden kernel:  kthread+0x118/0x130
Jan 12 11:42:32 oden kernel:  ? kthread_create_on_node+0x70/0x70
Jan 12 11:42:32 oden kernel:  ret_from_fork+0x25/0x30
Jan 12 11:42:32 oden kernel: INFO: task kworker/0:5:2038 blocked for more than 120 seconds.
Jan 12 11:42:32 oden kernel:       Tainted: G           O    4.14.4-1-ARCH #1
Jan 12 11:42:32 oden kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jan 12 11:42:32 oden kernel: kworker/0:5     D    0  2038      2 0x80000000
Jan 12 11:42:32 oden kernel: Workqueue: kec_query acpi_ec_event_processor
Jan 12 11:42:32 oden kernel: Call Trace:
Jan 12 11:42:32 oden kernel:  ? __schedule+0x239/0x870
Jan 12 11:42:32 oden kernel:  schedule+0x2f/0x90
Jan 12 11:42:32 oden kernel:  schedule_preempt_disabled+0x11/0x20
Jan 12 11:42:32 oden kernel:  __mutex_lock.isra.2+0x288/0x510
Jan 12 11:42:32 oden kernel:  ? smbus_alarm+0x73/0x110 [sbshc]
Jan 12 11:42:32 oden kernel:  smbus_alarm+0x73/0x110 [sbshc]
Jan 12 11:42:32 oden kernel:  acpi_ec_event_processor+0x23/0x90
Jan 12 11:42:32 oden kernel:  process_one_work+0x1db/0x410
Jan 12 11:42:32 oden kernel:  worker_thread+0x2b/0x3d0
Jan 12 11:42:32 oden kernel:  ? process_one_work+0x410/0x410
Jan 12 11:42:32 oden kernel:  kthread+0x118/0x130
Jan 12 11:42:32 oden kernel:  ? kthread_create_on_node+0x70/0x70
Jan 12 11:42:32 oden kernel:  ret_from_fork+0x25/0x30

can anyone explain to me what's this  Workqueue: kec_query acpi_ec_event_processor??
thanks

Last edited by vlogswawa (2018-01-12 11:08:49)

Trilby

Inspector Parrot

Registered: 2011-11-29

Posts: 30,525

Website

Re: awesome WM freezes each min!!!

If this only happens in AwesomeWM post your awesome configs and anything else that is unique to your AwesomeWM sessions.  Specifically, do you have some system monitoring script running in a loop on a 1 minute interval making an ACPI call?

---

"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman

vlogswawa

Member

Registered: 2017-09-29

Posts: 26

Re: awesome WM freezes each min!!!

I forgot to mention that I use the same awesome configuration for my two other computers with no problems.
it's kinda hard to post my awesome configs, I do use multi files and folders.
I don't have any system monitoring script running in a loop.

I'll start Awesome with its normal config "/etc/xdg/awesome/rc.lua" and see if anything happen. i'll keep you updates.
Thank you

Last edited by vlogswawa (2018-01-12 13:46:48)

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 78,066

Re: awesome WM freezes each min!!!

conky?

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

vlogswawa

Member

Registered: 2017-09-29

Posts: 26

Re: awesome WM freezes each min!!!

back to you guys, i did as i said, i tried it with its normal configs and nothing happen for more than hour! which mean you were right it's something in my config.
as this problem is related to ACPI, i started my config but this time i deleted all lain widgets related to CPU MEM POWER... and my awesome wm is no longer freezing.

IDK but obviously one of these lain functions is causing this.

i forgot to tell you that i'm using linux in mbp without "Suspend & Hibernation". all macbook late 2016 and 2017 can't use it https://github.com/Dunedan/mbp-2016-linux
so my question here is: does "Suspend & Hibernation" has to do anything with those widgets?
i would like to have my widgets back

thank you all

Trilby

Inspector Parrot

Registered: 2011-11-29

Posts: 30,525

Website

Re: awesome WM freezes each min!!!

If this only happens in AwesomeWM post your awesome configs

We are not mind readers.  Show us what you're working with or there's nothing that could possibly be done.

---

"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 78,066

Re: awesome WM freezes each min!!!

You're using "what"?? That page looks more like a system support status collection?

There're likely general ACPI issues causing this indirectly, please paste your *entire* dmesg output somewhere - ideally including a bit of the problems (ie. enable the widgets, endure the freezes for some minutes and pull dmesg afterwards. You can oc. re-disable the widgets again)

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc