You are not logged in.

#1 2017-01-07 10:19:15

uhuu
Member
From: Estonia
Registered: 2010-11-22
Posts: 23

System freeze

Once for oa while I get complete system freeze for a few minutes, sometimes even mouse is not moving.
Laptop Lenovo T410 and kernel Arch4.4.39-1-lts

dmesg shows me

 447.610228] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  447.611772] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  447.612422] nouveau 0000:01:00.0: DRM: suspending console...
[  447.612431] nouveau 0000:01:00.0: DRM: suspending display...
[  447.612448] nouveau 0000:01:00.0: DRM: evicting buffers...
[  447.612452] nouveau 0000:01:00.0: DRM: waiting for kernel channels to go idle...
[  447.612487] nouveau 0000:01:00.0: DRM: suspending client object trees...
[  447.612899] nouveau 0000:01:00.0: DRM: suspending kernel object tree...
[  449.668667] thinkpad_acpi: EC reports that Thermal Table has changed
[  569.135423] nouveau 0000:01:00.0: DRM: resuming kernel object tree...
[  569.428469] thinkpad_acpi: EC reports that Thermal Table has changed
[  569.429921] nouveau 0000:01:00.0: DRM: resuming client object trees...
[  569.430079] nouveau 0000:01:00.0: DRM: resuming display...
[  569.430105] nouveau 0000:01:00.0: DRM: resuming console...
[  574.542878] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  574.544253] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  574.544911] nouveau 0000:01:00.0: DRM: suspending console...
[  574.544920] nouveau 0000:01:00.0: DRM: suspending display...
[  574.544937] nouveau 0000:01:00.0: DRM: evicting buffers...
[  574.544941] nouveau 0000:01:00.0: DRM: waiting for kernel channels to go idle...
[  574.544977] nouveau 0000:01:00.0: DRM: suspending client object trees...
[  574.545387] nouveau 0000:01:00.0: DRM: suspending kernel object tree...

Journalctl:

plasmashell[1155]: QXcbConnection: XCB error: 2 (BadValue), sequence: 20358, resource id: 104857605, major code: 142 (Unknown), minor code: 3
jaan  07 12:04:55 home plasmashell[1155]: QXcbConnection: XCB error: 2 (BadValue), sequence: 20477, resource id: 92274760, major code: 142 (Unknown), minor code: 3
jaan  07 12:04:56 home plasmashell[1155]: QXcbConnection: XCB error: 2 (BadValue), sequence: 20572, resource id: 92274690, major code: 142 (Unknown), minor code: 3
jaan  07 12:05:01 home crond[3175]: pam_unix(crond:session): session opened for user root by (uid=0)
jaan  07 12:05:01 home CROND[3176]: (root) CMD (/usr/local/bin/autonfs_kodu)
jaan  07 12:05:01 home CROND[3175]: (root) CMDOUT (/bin/sh: /usr/local/bin/autonfs_kodu: No such file or directory)
jaan  07 12:05:01 home CROND[3175]: pam_unix(crond:session): session closed for user root
jaan  07 12:05:34 home plasmashell[1155]: QXcbConnection: XCB error: 2 (BadValue), sequence: 20960, resource id: 92274760, major code: 142 (Unknown), minor code: 3
jaan  07 12:05:34 home plasmashell[1155]: QXcbConnection: XCB error: 2 (BadValue), sequence: 21031, resource id: 92274690, major code: 142 (Unknown), minor code: 3
jaan  07 12:05:35 home plasmashell[1155]: QXcbConnection: XCB error: 2 (BadValue), sequence: 21102, resource id: 92274760, major code: 142 (Unknown), minor code: 3
jaan  07 12:05:36 home plasmashell[1155]: QXcbConnection: XCB error: 2 (BadValue), sequence: 21173, resource id: 92274690, major code: 142 (Unknown), minor code: 3

these messages repeat all the time.
Very annoying. sometimes these freezes occur several times an hour, sometimes i don't gen any for a whole day.


Windows is not a virus, virus does something...

Offline

#2 2017-01-07 10:32:18

ooo
Member
Registered: 2013-04-10
Posts: 1,638

Re: System freeze

Did you try if the problem persists with latest (non-lts) kernel?

Offline

#3 2017-01-07 11:06:10

uhuu
Member
From: Estonia
Registered: 2010-11-22
Posts: 23

Re: System freeze

I do get this with the latest kernel.
I have Optimus enabled from the bios.
bbswitch is installed and no bumblebee or primus.
in addition I get even longer errors and in addition btrfs problems and journal dies with the latest kernel:

491.331737] systemd-journal D ffff880230027cf8     0   218      1 0x00000104
[  491.331743]  ffff880230027cf8 00ff880230027ce0 ffff88023221e800 ffff88022f234100
[  491.331745]  0000000000008000 ffff880230028000 ffff88022fb501f0 ffff88022fb50000
[  491.331747]  ffff88022fb501f0 0000000000000001 ffff880230027d10 ffffffff815f40ec
[  491.331749] Call Trace:
[  491.331757]  [<ffffffff815f40ec>] schedule+0x3c/0x90
[  491.331782]  [<ffffffffa039311a>] wait_current_trans.isra.8+0xca/0x110 [btrfs]
[  491.331786]  [<ffffffff810c0450>] ? wake_atomic_t_function+0x60/0x60
[  491.331796]  [<ffffffffa0395941>] start_transaction+0x2c1/0x4c0 [btrfs]
[  491.331808]  [<ffffffffa0395b58>] btrfs_start_transaction+0x18/0x20 [btrfs]
[  491.331819]  [<ffffffffa03a1d83>] btrfs_setattr+0x1e3/0x360 [btrfs]
[  491.331822]  [<ffffffff81226974>] notify_change+0x2e4/0x440
[  491.331825]  [<ffffffff81206f03>] do_truncate+0x73/0xc0
[  491.331827]  [<ffffffff81207267>] do_sys_ftruncate.constprop.2+0x117/0x120
[  491.331828]  [<ffffffff812072ae>] SyS_ftruncate+0xe/0x10
[  491.331830]  [<ffffffff81003b97>] do_syscall_64+0x57/0xb0
[  491.331832]  [<ffffffff815f80e1>] entry_SYSCALL64_slow_path+0x25/0x25
[  491.331842] INFO: task systemd-timesyn:1354 blocked for more than 120 seconds.
[  491.331844]       Tainted: G           O    4.8.13-1-ARCH #1
[  491.331845] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[  491.331846] systemd-timesyn D ffff880225cf3c50     0  1354      1 0x00000104
[  491.331848]  ffff880225cf3c50 0001000000010000 ffffffff81a0d500 ffff8802311f2700
[  491.331850]  00000000b632054d ffff880225cf4000 ffff88022fb501f0 ffff88022fb50000
[  491.331852]  ffff88022fb501f0 0000000000000001 ffff880225cf3c68 ffffffff815f40ec
[  491.331853] Call Trace:
[  491.331855]  [<ffffffff815f40ec>] schedule+0x3c/0x90
[  491.331864]  [<ffffffffa039311a>] wait_current_trans.isra.8+0xca/0x110 [btrfs]
[  491.331865]  [<ffffffff810c0450>] ? wake_atomic_t_function+0x60/0x60
[  491.331874]  [<ffffffffa03958f2>] start_transaction+0x272/0x4c0 [btrfs]
[  491.331882]  [<ffffffffa0395b97>] btrfs_join_transaction+0x17/0x20 [btrfs]
[  491.331891]  [<ffffffffa039c00c>] btrfs_dirty_inode+0x3c/0xd0 [btrfs]
[  491.331900]  [<ffffffffa03a1c3c>] btrfs_setattr+0x9c/0x360 [btrfs]
[  491.331901]  [<ffffffff81226974>] notify_change+0x2e4/0x440
[  491.331903]  [<ffffffff8123dbc1>] utimes_common+0xd1/0x1b0
[  491.331904]  [<ffffffff8123dd7e>] do_utimes+0xde/0x160
[  491.331905]  [<ffffffff8123def7>] SyS_utimensat+0x67/0xa0
[  491.331906]  [<ffffffff81003b97>] do_syscall_64+0x57/0xb0
[  491.331907]  [<ffffffff815f80e1>] entry_SYSCALL64_slow_path+0x25/0x25
[  491.331927] INFO: task plasmashell:2054 blocked for more than 120 seconds.
[  491.331928]       Tainted: G           O    4.8.13-1-ARCH #1
[  491.331929] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[  491.331930] plasmashell     D ffff880207ae3c18     0  2054   2018 0x00000000
[  491.331932]  ffff880207ae3c18 00ff880207ae3c50 ffff88023221e800 ffff88020793c100
[  491.331934]  0000000000000000 ffff880207ae4000 ffff8802297009f0 ffff880229700800
[  491.331935]  ffff8802297009f0 0000000000000001 ffff880207ae3c30 ffffffff815f40ec
[  491.331937] Call Trace:
[  491.331938]  [<ffffffff815f40ec>] schedule+0x3c/0x90
[  491.331947]  [<ffffffffa039311a>] wait_current_trans.isra.8+0xca/0x110 [btrfs]
[  491.331948]  [<ffffffff810c0450>] ? wake_atomic_t_function+0x60/0x60
[  491.331957]  [<ffffffffa03958f2>] start_transaction+0x272/0x4c0 [btrfs]
[  491.331965]  [<ffffffffa0395b97>] btrfs_join_transaction+0x17/0x20 [btrfs]
[  491.331974]  [<ffffffffa039c00c>] btrfs_dirty_inode+0x3c/0xd0 [btrfs]
[  491.331983]  [<ffffffffa039c11f>] btrfs_update_time+0x7f/0xb0 [btrfs]
[  491.331984]  [<ffffffff81226548>] touch_atime+0xa8/0xd0
[  491.331993]  [<ffffffffa03a8d7e>] btrfs_file_mmap+0x3e/0x60 [btrfs]
[  491.331995]  [<ffffffff811baa4d>] mmap_region+0x39d/0x630
[  491.331996]  [<ffffffff811bb0cb>] do_mmap+0x3eb/0x4a0
[  491.331999]  [<ffffffff8119c00a>] vm_mmap_pgoff+0xba/0xf0
[  491.332000]  [<ffffffff811b8d5c>] SyS_mmap_pgoff+0x19c/0x240
[  491.332002]  [<ffffffff81032f2b>] SyS_mmap+0x1b/0x30
[  491.332003]  [<ffffffff815f8032>] entry_SYSCALL_64_fastpath+0x1a/0xa4
[  502.042330] systemd[1]: systemd-timesyncd.service: Main process exited, code=killed, status=6/ABRT
[  502.043600] systemd[1]: systemd-timesyncd.service: Unit entered failed state.
[  502.043615] systemd[1]: systemd-timesyncd.service: Failed with result 'watchdog'.
[  502.052335] systemd[1]: systemd-timesyncd.service: Service has no hold-off time, scheduling restart.
[  502.052459] systemd[1]: Stopped Network Time Synchronization.
[  502.065486] systemd[1]: Starting Network Time Synchronization...
[  502.381927] systemd[1]: Started Network Time Synchronization.
[  502.408251] systemd[1]: systemd-journald.service: Main process exited, code=dumped, status=6/ABRT
[  502.409136] systemd[1]: systemd-journald.service: Unit entered failed state.
[  502.409179] systemd[1]: systemd-journald.service: Failed with result 'watchdog'.
[  503.601729] systemd-coredump[3266]: Detected coredump of the journal daemon or PID 1, diverted to /var/lib/systemd/coredump/core.systemd-journal.0.66348627e4544d79a7ccfbecba80e036.218.1483786969000000.
[  503.795112] systemd-journald[3418]: File /var/log/journal/2a510bbc8a3be82923fb94a600000322/system.journal corrupted or uncleanly shut down, renaming and replacing.
[  503.883994] systemd-journald[3418]: File /var/log/journal/2a510bbc8a3be82923fb94a600000322/user-1000.journal corrupted or uncleanly shut down, renaming and replacing.
scrub status for dc42fefb-ad17-4cab-ab3a-61d816e04aa5
        scrub started at Sat Jan  7 13:05:37 2017, running for 00:01:55
        total bytes scrubbed: 26.35GiB with 0 errors

Last edited by uhuu (2017-01-07 11:18:29)


Windows is not a virus, virus does something...

Offline

#4 2017-01-07 15:04:34

ooo
Member
Registered: 2013-04-10
Posts: 1,638

Re: System freeze

I guess it could also be plasmashell freezing up, as per your journalctl output. Have you tried if the issue persists with another desktop environment? Also, can you switch to another tty with Alt+Ctrl+F# when the freeze occurs?

If that doesn't help, next thing I'd try would be switching up video drivers to isolate the issue, e.g. disabling optimus if possible etc.

Offline

#5 2017-01-11 18:00:19

uhuu
Member
From: Estonia
Registered: 2010-11-22
Posts: 23

Re: System freeze

It seems that switching off the vsync resolved the problem.


Windows is not a virus, virus does something...

Offline

Board footer

Powered by FluxBB