FS#54847 - [linux-hardened] system freeze on copy and rsync

Attached to Project: Community Packages
Opened by tom (archtom) - Monday, 17 July 2017, 09:52 GMT
Last edited by Daniel Micay (thestinger) - Friday, 21 July 2017, 10:05 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Daniel Micay (thestinger)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

The complete system freezes when copying (cp or rsync via samba) a bigger amount of data or a bigger file from or to the system running 4.12.e-1 and earlier. Don`t know about later versions as 4.12.2.a-1 does not start for me (see separate bug report).

Same operations work fine with the "regular" linux kernel in its current version 4.11.9-1.

I´m sorry I don`t know how to provide more needed information.

Just let me know the exact command to issue for getting further details you will probably need.

Thanks in advance for fixing.
This task depends upon

Closed by  Daniel Micay (thestinger)
Friday, 21 July 2017, 10:05 GMT
Reason for closing:  Fixed
Additional comments about closing:  I think this might have been a short-lived FORTIFY_SOURCE incompatibility that was fixed.
Comment by loqs (loqs) - Monday, 17 July 2017, 20:56 GMT
This is on bare metal? Does the same issue occur if you use linux 4.12.2-1 from testing? Have you checked the journal for output from the time of the hang?
https://bbs.archlinux.org/viewtopic.php?id=228210 option is enabled for linux-hardened.
Comment by tom (archtom) - Tuesday, 18 July 2017, 08:43 GMT
The issue also happens with all hardened kernels before 4.12 (I only tried the 4.11 versions). It always worked without issues on the "normal" linux kernel.
Comment by Daniel Micay (thestinger) - Tuesday, 18 July 2017, 08:58 GMT
You'll need to confirm that it still happens on 4.12.2.a where a bug was fixed, so you need to resolve the other issue before anything can be done about this one. The issue may not be present anymore.
Comment by tom (archtom) - Tuesday, 18 July 2017, 10:12 GMT
Ok, but I cannot try with 4.12.2.a as it doesn`t boot for me.
see this bug report
https://bugs.archlinux.org/task/54846

So perhaps the other bug has to be solved first.
Comment by tom (archtom) - Tuesday, 18 July 2017, 10:26 GMT
deleted comment
Comment by tom (archtom) - Tuesday, 18 July 2017, 13:58 GMT
As the other issue
https://bugs.archlinux.org/task/54846
is resolved I´ll upgrade my server system to the latest kernel and test if this issue is gone with 4.12.2.a.

Please leave the bug open. I will report back in a few days if it is stable because our routines where the freezing happens doesn`t run every day. Thanks.
Comment by tom (archtom) - Friday, 21 July 2017, 10:02 GMT
I can not say for sure yet, but our routines went through without issues the last three days. I think this one can be closed, too. I will open another issue if it happens again. Thanks for maintaining the kernel and thanks for all the help.

Loading...