Bug 367759 - System occasionally unable to suspend if Dolphin left running with sshfs folder open
Summary: System occasionally unable to suspend if Dolphin left running with sshfs fold...
Status: RESOLVED DUPLICATE of bug 374228
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.2
Platform: Arch Linux Linux
: NOR critical
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-08-24 13:18 UTC by Nicolas F.
Modified: 2017-01-14 11:21 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Nicolas F. 2016-08-24 13:18:06 UTC 
Occasionally, if a user attempts to suspend the system, the entire system will hang and cannot be recovered. This appears to be related to having Dolphin open viewing a SSHFS mounted folder. Journal messages indicate that the file.so component does not wish to be suspended, and its call trace shows references to fuse.

Reproducible: Sometimes

Steps to Reproduce:
1. Mount an SSHFS
2. Open a folder on it in dolphin and watch some videos or something
3. Suspend the system while dolphin is still open

Actual Results:  
The system hangs on a black screen with only the mouse cursor showing and no longer accepts mouse or keyboard inputs. A while later, the sddm lock screen pops up, but does not react to any inputs. Switching VTs is impossible. The only way to get the system running again is to do a hard reset.

Expected Results:  
The system actually suspends properly.

The journal logs the following information:

Aug 24 03:48:49 archbook kernel: Freezing user space processes ... 
Aug 24 03:48:49 archbook kernel: Freezing of tasks failed after 20.007 seconds (5 tasks refusing to freeze, wq_busy=0):
Aug 24 03:48:49 archbook kernel: file.so         D ffff88021ca8bbb8     0  5791    641 0x00000004
Aug 24 03:48:49 archbook kernel:  ffff88021ca8bbb8 00ff8800a2fe1838 ffffffff8180d500 ffff8801aeade3c0
Aug 24 03:48:49 archbook kernel:  ffff88021ca8bbc0 ffff88021ca8c000 ffff88021ca8bbe8 ffff880064c89520
Aug 24 03:48:49 archbook kernel:  ffff8800a2fe1840 fffffffffffffe00 ffff88021ca8bbd0 ffffffff815d9aac
Aug 24 03:48:49 archbook kernel: Call Trace:
Aug 24 03:48:49 archbook kernel:  [<ffffffff815d9aac>] schedule+0x3c/0x90
Aug 24 03:48:49 archbook kernel:  [<ffffffffa078788a>] request_wait_answer+0x11a/0x270 [fuse]
Aug 24 03:48:49 archbook kernel:  [<ffffffff810bcc80>] ? wake_atomic_t_function+0x60/0x60
Aug 24 03:48:49 archbook kernel:  [<ffffffffa0788547>] __fuse_request_send+0x67/0x90 [fuse]
Aug 24 03:48:49 archbook kernel:  [<ffffffffa0788597>] fuse_request_send+0x27/0x30 [fuse]
Aug 24 03:48:49 archbook kernel:  [<ffffffffa078aebf>] fuse_simple_request+0xcf/0x1a0 [fuse]
Aug 24 03:48:49 archbook kernel:  [<ffffffffa078c450>] fuse_do_getattr+0x120/0x330 [fuse]
Aug 24 03:48:49 archbook kernel:  [<ffffffffa078df08>] fuse_update_attributes+0x68/0x70 [fuse]
Aug 24 03:48:49 archbook kernel:  [<ffffffffa078df53>] fuse_getattr+0x43/0x50 [fuse]
Aug 24 03:48:49 archbook kernel:  [<ffffffff811ff169>] vfs_getattr_nosec+0x29/0x40
Aug 24 03:48:49 archbook kernel:  [<ffffffff811ff386>] vfs_getattr+0x26/0x30
Aug 24 03:48:49 archbook kernel:  [<ffffffff811ff468>] vfs_fstatat+0x78/0xc0
Aug 24 03:48:49 archbook kernel:  [<ffffffff811ff913>] SyS_newstat+0x33/0x60
Aug 24 03:48:49 archbook kernel:  [<ffffffff8100360e>] ? exit_to_usermode_loop+0x5e/0xc0
Aug 24 03:48:49 archbook kernel:  [<ffffffff81003b9e>] ? syscall_return_slowpath+0x4e/0x60
Aug 24 03:48:49 archbook kernel:  [<ffffffff815dd772>] entry_SYSCALL_64_fastpath+0x1a/0xa4
Aug 24 03:48:49 archbook kernel: file.so         D ffff880219263bb8     0  6439    641 0x00000004
Aug 24 03:48:49 archbook kernel:  ffff880219263bb8 00ff8800a2fe1838 ffff880225ecc740 ffff880221d18e40
Aug 24 03:48:49 archbook kernel:  ffff880219263bc0 ffff880219264000 ffff880219263be8 ffff880064d30580
Aug 24 03:48:49 archbook kernel:  ffff8800a2fe1840 fffffffffffffe00 ffff880219263bd0 ffffffff815d9aac
Aug 24 03:48:49 archbook kernel: Call Trace:
Aug 24 03:48:49 archbook kernel:  [<ffffffff815d9aac>] schedule+0x3c/0x90
Aug 24 03:48:49 archbook kernel:  [<ffffffffa078788a>] request_wait_answer+0x11a/0x270 [fuse]
Aug 24 03:48:49 archbook kernel:  [<ffffffff810bcc80>] ? wake_atomic_t_function+0x60/0x60
Aug 24 03:48:49 archbook kernel:  [<ffffffffa0788547>] __fuse_request_send+0x67/0x90 [fuse]
Aug 24 03:48:49 archbook kernel:  [<ffffffffa0788597>] fuse_request_send+0x27/0x30 [fuse]
Aug 24 03:48:49 archbook kernel:  [<ffffffffa078aebf>] fuse_simple_request+0xcf/0x1a0 [fuse]
Aug 24 03:48:49 archbook kernel:  [<ffffffffa078c450>] fuse_do_getattr+0x120/0x330 [fuse]
Aug 24 03:48:49 archbook kernel:  [<ffffffffa078df08>] fuse_update_attributes+0x68/0x70 [fuse]
Aug 24 03:48:49 archbook kernel:  [<ffffffffa078df53>] fuse_getattr+0x43/0x50 [fuse]
Aug 24 03:48:49 archbook kernel:  [<ffffffff811ff169>] vfs_getattr_nosec+0x29/0x40
Aug 24 03:48:49 archbook kernel:  [<ffffffff811ff386>] vfs_getattr+0x26/0x30
Aug 24 03:48:49 archbook kernel:  [<ffffffff811ff468>] vfs_fstatat+0x78/0xc0
Aug 24 03:48:49 archbook kernel:  [<ffffffff811ff913>] SyS_newstat+0x33/0x60
Aug 24 03:48:49 archbook kernel:  [<ffffffff8100360e>] ? exit_to_usermode_loop+0x5e/0xc0
Aug 24 03:48:49 archbook kernel:  [<ffffffff81003b9e>] ? syscall_return_slowpath+0x4e/0x60
Aug 24 03:48:49 archbook kernel:  [<ffffffff815dd772>] entry_SYSCALL_64_fastpath+0x1a/0xa4
Aug 24 03:48:49 archbook kernel: file.so         D ffff880215733bb8     0  6447    641 0x00000004
Aug 24 03:48:49 archbook kernel:  ffff880215733bb8 00ff8800a2fe1838 ffff88021cab9c80 ffff880220d463c0
Aug 24 03:48:49 archbook kernel:  ffff880215733bc0 ffff880215734000 ffff880215733be8 ffff880220e783f0
Aug 24 03:48:49 archbook kernel:  ffff8800a2fe1840 fffffffffffffe00 ffff880215733bd0 ffffffff815d9aac
Aug 24 03:48:49 archbook kernel: Call Trace:
Aug 24 03:48:49 archbook kernel:  [<ffffffff815d9aac>] schedule+0x3c/0x90
Aug 24 03:48:49 archbook kernel:  [<ffffffffa078788a>] request_wait_answer+0x11a/0x270 [fuse]
Aug 24 03:48:49 archbook kernel:  [<ffffffff810bcc80>] ? wake_atomic_t_function+0x60/0x60
Aug 24 03:48:49 archbook kernel:  [<ffffffffa0788547>] __fuse_request_send+0x67/0x90 [fuse]
Aug 24 03:48:49 archbook kernel:  [<ffffffffa0788597>] fuse_request_send+0x27/0x30 [fuse]
Aug 24 03:48:49 archbook kernel:  [<ffffffffa078aebf>] fuse_simple_request+0xcf/0x1a0 [fuse]
Aug 24 03:48:49 archbook kernel:  [<ffffffffa078c450>] fuse_do_getattr+0x120/0x330 [fuse]
Aug 24 03:48:49 archbook kernel:  [<ffffffffa078df08>] fuse_update_attributes+0x68/0x70 [fuse]
Aug 24 03:48:49 archbook kernel:  [<ffffffffa078df53>] fuse_getattr+0x43/0x50 [fuse]
Aug 24 03:48:49 archbook kernel:  [<ffffffff811ff169>] vfs_getattr_nosec+0x29/0x40
Aug 24 03:48:49 archbook kernel:  [<ffffffff811ff386>] vfs_getattr+0x26/0x30
Aug 24 03:48:49 archbook kernel:  [<ffffffff811ff468>] vfs_fstatat+0x78/0xc0
Aug 24 03:48:49 archbook kernel:  [<ffffffff811ff913>] SyS_newstat+0x33/0x60
Aug 24 03:48:49 archbook kernel:  [<ffffffff8100360e>] ? exit_to_usermode_loop+0x5e/0xc0
Aug 24 03:48:49 archbook kernel:  [<ffffffff81003b9e>] ? syscall_return_slowpath+0x4e/0x60
Aug 24 03:48:49 archbook kernel:  [<ffffffff815dd772>] entry_SYSCALL_64_fastpath+0x1a/0xa4
Aug 24 03:48:49 archbook kernel: file.so         D ffff88021920bbb8     0  6448    641 0x00000004
Aug 24 03:48:49 archbook kernel:  ffff88021920bbb8 00ff8800a2fe1838 ffff880225ecd580 ffff88021cab9c80
Aug 24 03:48:49 archbook kernel:  ffff88021920bbc0 ffff88021920c000 ffff88021920bbe8 ffff880220e79520
Aug 24 03:48:49 archbook kernel:  ffff8800a2fe1840 fffffffffffffe00 ffff88021920bbd0 ffffffff815d9aac
Aug 24 03:48:49 archbook kernel: Call Trace:
Aug 24 03:48:49 archbook kernel:  [<ffffffff815d9aac>] schedule+0x3c/0x90
Aug 24 03:48:49 archbook kernel:  [<ffffffffa078788a>] request_wait_answer+0x11a/0x270 [fuse]
Aug 24 03:48:49 archbook kernel:  [<ffffffff810bcc80>] ? wake_atomic_t_function+0x60/0x60
Aug 24 03:48:49 archbook kernel:  [<ffffffffa0788547>] __fuse_request_send+0x67/0x90 [fuse]
Aug 24 03:48:49 archbook kernel:  [<ffffffffa0788597>] fuse_request_send+0x27/0x30 [fuse]
Aug 24 03:48:49 archbook kernel:  [<ffffffffa078aebf>] fuse_simple_request+0xcf/0x1a0 [fuse]
Aug 24 03:48:49 archbook kernel:  [<ffffffffa078c450>] fuse_do_getattr+0x120/0x330 [fuse]
Aug 24 03:48:49 archbook kernel:  [<ffffffffa078df08>] fuse_update_attributes+0x68/0x70 [fuse
Aug 24 03:48:49 archbook kernel:  [<ffffffffa078df53>] fuse_getattr+0x43/0x50 [fuse]
Aug 24 03:48:49 archbook kernel:  [<ffffffff811ff169>] vfs_getattr_nosec+0x29/0x40
Aug 24 03:48:49 archbook kernel:  [<ffffffff811ff386>] vfs_getattr+0x26/0x30
Aug 24 03:48:49 archbook kernel:  [<ffffffff811ff468>] vfs_fstatat+0x78/0xc0
Aug 24 03:48:49 archbook kernel:  [<ffffffff811ff913>] SyS_newstat+0x33/0x60
Aug 24 03:48:49 archbook kernel:  [<ffffffff8100360e>] ? exit_to_usermode_loop+0x5e/0xc0
Aug 24 03:48:49 archbook kernel:  [<ffffffff81003b9e>] ? syscall_return_slowpath+0x4e/0x60
Aug 24 03:48:49 archbook kernel:  [<ffffffff815dd772>] entry_SYSCALL_64_fastpath+0x1a/0xa4
Aug 24 03:48:49 archbook kernel: file.so         D ffff8800abb3bbb8     0  6449    641 0x0000
Aug 24 03:48:49 archbook kernel:  ffff8800abb3bbb8 00ff8800a2fe1838 ffffffff8180d500 ffff8802
Aug 24 03:48:49 archbook kernel:  ffff8800abb3bbc0 ffff8800abb3c000 ffff8800abb3bbe8 ffff8802
Aug 24 03:48:49 archbook kernel:  ffff8800a2fe1840 fffffffffffffe00 ffff8800abb3bbd0 ffffffff
Aug 24 03:48:49 archbook kernel: Call Trace:
Aug 24 03:48:49 archbook kernel:  [<ffffffff815d9aac>] schedule+0x3c/0x90
Aug 24 03:48:49 archbook kernel:  [<ffffffffa078788a>] request_wait_answer+0x11a/0x270 [fuse]
Aug 24 03:48:49 archbook kernel:  [<ffffffff810bcc80>] ? wake_atomic_t_function+0x60/0x60
Aug 24 03:48:49 archbook kernel:  [<ffffffffa0788547>] __fuse_request_send+0x67/0x90 [fuse]
Aug 24 03:48:49 archbook kernel:  [<ffffffffa0788597>] fuse_request_send+0x27/0x30 [fuse]
Aug 24 03:48:49 archbook kernel:  [<ffffffffa078aebf>] fuse_simple_request+0xcf/0x1a0 [fuse]
Aug 24 03:48:49 archbook kernel:  [<ffffffffa078c450>] fuse_do_getattr+0x120/0x330 [fuse]
Aug 24 03:48:49 archbook kernel:  [<ffffffffa078df08>] fuse_update_attributes+0x68/0x70 [fuse
Aug 24 03:48:49 archbook kernel:  [<ffffffffa078df53>] fuse_getattr+0x43/0x50 [fuse]
Aug 24 03:48:49 archbook kernel:  [<ffffffff811ff169>] vfs_getattr_nosec+0x29/0x40
Aug 24 03:48:49 archbook kernel:  [<ffffffff811ff386>] vfs_getattr+0x26/0x30
Aug 24 03:48:49 archbook kernel:  [<ffffffff811ff468>] vfs_fstatat+0x78/0xc0
Aug 24 03:48:49 archbook kernel:  [<ffffffff811ff913>] SyS_newstat+0x33/0x60
Aug 24 03:48:49 archbook kernel:  [<ffffffff8100360e>] ? exit_to_usermode_loop+0x5e/0xc0
Aug 24 03:48:49 archbook kernel:  [<ffffffff81003b9e>] ? syscall_return_slowpath+0x4e/0x60
Aug 24 03:48:49 archbook kernel:  [<ffffffff815dd772>] entry_SYSCALL_64_fastpath+0x1a/0xa4
Aug 24 03:48:49 archbook kernel:
Comment 1 Nicolas F. 2016-08-24 13:24:14 UTC 
Note that this is on the Arch Linux stock kernel 4.7.1 on x86_64, for all I know this could be a kernel bug making fuse hang which makes file.so hang which makes Dolphin hang which makes suspend hang which makes my system hang.
Comment 2 Bob Wya 2016-10-02 20:55:16 UTC 
I've got a systemd sleep script to stop and then restart my sshfs mount unit.
This used to work more cleanly - but I believe a few months ago systemd was made atomic during a critical stage of the suspend process (not sure what version that was now). NFS mountpoints are similarly affected.
Comment 3 Elvis Angelaccio 2017-01-14 11:21:20 UTC 
This is a known issue with sshfs, unfortunately there is nothing we can do from the Dolphin side.
See the duplicate report for more details.

*** This bug has been marked as a duplicate of bug 374228 ***