FreefileSync Suddenly Freezing & Crashing System

Posts: 22 · tippunmon 11 Jun 2021, 14:09

Freefilesync Arch Linux (also affects Manjaro which is Arch based).

Following recent Arch updates, Freefilesync suddenly doesn't work correctly (any version).

Set up and administered in normal manner, but as soon as the start button is pressed for the synchronisation the program freezes up and crashes the system meaning any button presses, key presses do not work; however the cursor still works fine! But only the cursor. Frustrating. Freefilesync works perfectly on any Debian based system (I've tried several) but will not work on any Arch based system so there appears to be 'something' in the latest batch of updates causing this problem.

Posts: 345 · bgstack15 11 Jun 2021, 19:28

Can you share all the packages with versio number on you system that have been updated since the time FreeFileSync started crashing? Chances are this is a problem with one of the dependency libraries like libgtk.

Posts: 22 · tippunmon 11 Jun 2021, 19:37

Thanks but as I rely on Freefilesync for aligning my backup I completely scrapped the Arch system I had installed and the Manjaro system I subsequently installed and am now using Mint XFCE which works fine. A person on the Arch forum also updated FFS to 11.11 and stated he had no problems with it, which is a little strange. Anyway many thanks for the offer of support I appreciate it.

Posts: 22 · tippunmon 13 Jun 2021, 11:34

Cannot get ffs to work correctly using Manjaro xfce. Have now installed a debian based xfce system (Mint) with no problems whatsoever. Whilst using Mint have loaded a USB live disk with Manjaro xfce and ffs exhibited exactly the same behaviour. Likewise pure Arch and Archman which I also tried. So my only conclusion is it’s something to do with Arch combined with AMD 4300ge as I never had any issues with my ryzen 1300x and nvidia gt710 before I upgraded.

Posts: 22 · tippunmon 14 Jun 2021, 09:20

Now here's proof for you. Downloaded Manjaro xfce 20.2 from the Manjaro archives, loaded and ran FreefileSync latest version whilst using the live usb and - everything works absolutely perfectly, so something or another in between latest Manjaro xfce and the older 20.2 has interfered with the running of FFS. I have to assume this is something within Arch as Arch is exhibiting the same behaviour.

Posts: 22 · tippunmon 22 Jun 2021, 13:22

Further info - believe this is something to do with 5.12 kernel and my Ryzen 4300ge. Tried Debian SID with 5.10 kernel (LTS?), no problems. When SID automatically upgraded to 5.12 kernel FFS exhibited exactly the same behaviour as Arch (with the same 5.12 kernel). So the obvious solution will be to roll back the kernel until such time as a more permanent solution presents itself.

Posts: 22 · tippunmon 22 Jun 2021, 16:57

Update - 5.10 works fine in any live usb environment whatsoever. Also works fine in debian based distros, such but SID, Arch, Manjaro, Elementary etc etc once updated to latest packages FFS freezes at the same point in the usage procedure irrespective of 5.10 or 5.12 kernel so SOMETHING within the large number of update packages after installation is causing the problem. Stress that, apart from Pure Arch (for obvious reasons) every other live usb FFS works absolutely fine then still works fine upon installation UNTIL the updates are installed, then it fails.

Posts: 3 · w0mpy 2 Jul 2021, 18:01

I have the same issue. How can we debug this?

I am using current XFCE Manjaro with a Ryzen 4800H (no additional GPU). Since it is a laptop, I cannot change the GPU and I do not have an eGPU.

Tippunmon, are you using the iGPU of your 4300ge?

I suspect this is related to the mesa drivers combined with AMD iGPUs for two reasons:

For me FFS freezes the screen completely for 5 seconds, screen goes black for one second and returns back with only the cursor being active. It is just a guess, but it seems related to graphics/rendering.
The mesa drivers released at about the same time also broke other graphics related software, for example FreeCAD, see here:
https://forum.manjaro.org/t/many-appimages-have-stopped-working-after-todays-update/69445

Posts: 22 · tippunmon 2 Jul 2021, 18:51

Believe you appear to be on the right track. I do use the graphics of the 4300ge via hdmi connection into my LG monitor. Currently using siduction which has 5.13 kernel. As a bit of a noob I worked around the issue by using a usb live Mint disk and adding ffs to it whilst live. This solution whilst crude is within the current boundaries of my knowledge. Sorry you are having same/similar problem but selfishly reassuring to know that "I'm not the only one".

Posts: 2 · v3rtex 4 Jul 2021, 18:35

I have the exact same behavior on the latest Manjaro release wit FFS 11.11
The UI works without problems until I hit the „Start“ Button to begin a sync process.
After that the screen turns black for a moment, comes back, but then all windows including ffs are black, but work when you know the positions of the buttons.
Background and taskbar are working, but also with graphic issues.
The ffs sync operation itself runs successfully, and it says „success“ in the result dialog header.

Maybe it’s related to the latest AMD drivers, because I am using a 4800H too.
But in my case I am using Manjaro with the KDE Environment.

Posts: 22 · tippunmon 4 Jul 2021, 20:34

Currently using Siduction (rolling Debian unstable) xfce which has received four kernel upgrades in the couple of weeks or so. In fairness I haven't tried FFS on the last 2 kernel upgrades, so not sure if amd driver related or whether missing/upgraded library file or what. Notice no updates since June 11th for FFS itself. May have to test again in case issue resolved.

Posts: 22 · tippunmon 5 Jul 2021, 14:11

Tested again and suddenly working all fine!! Haven't updated FFS, only the day-to-day Siduction updates but for the first time today after last kernel update and Siduction updates all is now working fine. Happy days!!

Posts: 2 · v3rtex 5 Jul 2021, 15:01

On Manjaro KDE still the same.
I tested this with Kernel 5.10.42-1 LTS and with the latest released 5.12.9-1.
Same problem with both of them.

But i got a dmesg log for the crash.

[  379.887287] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=29164, emitted seq=29166

[  379.887653] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 1130 thread Xorg:cs0 pid 1132

[  379.887949] amdgpu 0000:03:00.0: amdgpu: GPU reset begin!

[  379.965355] [drm] free PSP TMR buffer

[  379.991990] amdgpu 0000:03:00.0: amdgpu: MODE2 reset

[  379.992469] amdgpu 0000:03:00.0: amdgpu: GPU reset succeeded, trying to resume

[  379.992550] [drm] PCIE GART of 1024M enabled (table at 0x000000F400900000).

[  379.992683] [drm] PSP is resuming...

[  380.012701] [drm] reserve 0x400000 from 0xf41f800000 for PSP TMR

[  380.311320] amdgpu 0000:03:00.0: amdgpu: RAS: optional ras ta ucode is not available

[  380.319946] amdgpu 0000:03:00.0: amdgpu: RAP: optional rap ta ucode is not available

[  380.319950] amdgpu 0000:03:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available

[  380.319953] amdgpu 0000:03:00.0: amdgpu: SMU is resuming...

[  380.320577] amdgpu 0000:03:00.0: amdgpu: SMU is resumed successfully!

[  380.503699] [drm] kiq ring mec 2 pipe 1 q 0

[  380.504866] [drm] DMUB hardware initialized: version=0x01020008

[  380.696371] [drm] VCN decode and encode initialized successfully(under DPG Mode).

[  380.696780] [drm] JPEG decode initialized successfully.

[  380.696787] amdgpu 0000:03:00.0: amdgpu: ring gfx uses VM inv eng 0 on hub 0

[  380.696792] amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0

[  380.696795] amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0

[  380.696797] amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0

[  380.696800] amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0

[  380.696802] amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0

[  380.696804] amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0

[  380.696807] amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0

[  380.696809] amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0

[  380.696812] amdgpu 0000:03:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0

[  380.696815] amdgpu 0000:03:00.0: amdgpu: ring sdma0 uses VM inv eng 0 on hub 1

[  380.696817] amdgpu 0000:03:00.0: amdgpu: ring vcn_dec uses VM inv eng 1 on hub 1

[  380.696819] amdgpu 0000:03:00.0: amdgpu: ring vcn_enc0 uses VM inv eng 4 on hub 1

[  380.696821] amdgpu 0000:03:00.0: amdgpu: ring vcn_enc1 uses VM inv eng 5 on hub 1

[  380.696824] amdgpu 0000:03:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 on hub 1

[  380.702822] amdgpu 0000:03:00.0: amdgpu: recover vram bo from shadow start

[  380.702829] amdgpu 0000:03:00.0: amdgpu: recover vram bo from shadow done

[  380.702833] [drm] Skip scheduling IBs!

[  380.702964] amdgpu 0000:03:00.0: amdgpu: GPU reset(2) succeeded!

[  380.703465] [drm] Skip scheduling IBs!

[  380.703303] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!

[  380.706911] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!

[  380.709710] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!

[  380.717490] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!

[  380.719776] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!

[  380.730017] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!

[  380.735652] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!

[  380.759336] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!

[  380.763002] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!

[  380.770050] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!

[  390.724219] amdgpu_cs_ioctl: 79 callbacks suppressed

[  390.724226] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!

[  390.740449] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!

[  390.763467] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!

[  390.766012] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!

[  390.792740] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!

[  390.793275] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!

[  390.795152] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!

[  390.795702] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!

[  390.817889] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!

[  390.820322] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!

Posts: 3 · w0mpy 5 Jul 2021, 20:11

I can confirm the crash log of v3rtex, so it is a Mesa problem.

Mesa 21.1.4 was released a few days ago and the changelog mentions a bug fix fitting the crash log:
https://docs.mesa3d.org/relnotes/21.1.4.html

I assume that tippunmon got this update on Siduction, so this fix should be available soon on the stable Manjaro update channel.

@tippunmon
Does Siduction have a changelog or history for updates, like Manjaro? Would be nice to confirm that it is indeed the 21.1.4 Mesa update.

Posts: 22 · tippunmon 5 Jul 2021, 20:35

Thanks for the info. Not terribly advanced so don't know whether I can help you with your query, but I'll have a damn good try. I'll get back to you and update you on which current kernel Siduction is using. Do my best for you. Thanks for your help, appreciate it.

Posts: 22 · tippunmon 5 Jul 2021, 21:16

Here we go. The current kernel on Siduction is - 5.12.14-1.

APT History Log - as you can see it seems you are absolutely correct!!!

Start-Date: 2021-07-01 14:58:16
Commandline: apt upgrade
Requested-By: david (1000)
Install: linux-image-5.12.14-1-siduction-amd64:amd64 (5.12-14, automatic), linux-headers-5.12.14-1-siduction-amd64:amd64 (5.12-14, automatic)
Upgrade: linux-headers-siduction-amd64:amd64 (5.12-13.1, 5.12-14), linux-image-siduction-amd64:amd64 (5.12-13.1, 5.12-14), libicu67:amd64 (67.1-6, 67.1-7)
End-Date: 2021-07-01 14:58:30

Start-Date: 2021-07-02 14:46:30
Commandline: apt upgrade
Requested-By: david (1000)
Upgrade: kodi-data:amd64 (2:19.1+dfsg2-1, 2:19.1+dfsg2-2), libglx-mesa0:amd64 (21.1.3-0~siduction.1, 21.1.4-0~siduction.1), libgbm1:amd64 (21.1.3-0~siduction.1, 21.1.4-0~siduction.1), kodi:amd64 (2:19.1+dfsg2-1, 2:19.1+dfsg2-2), mesa-va-drivers:amd64 (21.1.3-0~siduction.1, 21.1.4-0~siduction.1), libgl1-mesa-dri:amd64 (21.1.3-0~siduction.1, 21.1.4-0~siduction.1), mesa-vulkan-drivers:amd64 (21.1.3-0~siduction.1, 21.1.4-0~siduction.1), kodi-bin:amd64 (2:19.1+dfsg2-1, 2:19.1+dfsg2-2), libglapi-mesa:amd64 (21.1.3-0~siduction.1, 21.1.4-0~siduction.1), kodi-repository-kodi:amd64 (2:19.1+dfsg2-1, 2:19.1+dfsg2-2), libegl-mesa0:amd64 (21.1.3-0~siduction.1, 21.1.4-0~siduction.1), mesa-vdpau-drivers:amd64 (21.1.3-0~siduction.1, 21.1.4-0~siduction.1)
End-Date: 2021-07-02 14:46:36

Start-Date: 2021-07-03 02:57:55
Requested-By: david (1000)
Install: gir1.2-cinnamondesktop-3.0:amd64 (4.8.1-2, automatic)
End-Date: 2021-07-03 02:57:56

Start-Date: 2021-07-03 03:24:45
Commandline: packagekit role='install-packages'
Requested-By: david (1000)
Install: redshift:amd64 (1.12-4.2, automatic), redshift-gtk:amd64 (1.12-4.2)
End-Date: 2021-07-03 03:24:47

Start-Date: 2021-07-03 03:25:41
Commandline: apt upgrade
Requested-By: david (1000)
Upgrade: libqt5core5a:amd64 (5.15.2+dfsg-8, 5.15.2+dfsg-9), qt5-gtk-platformtheme:amd64 (5.15.2+dfsg-8, 5.15.2+dfsg-9), libqt5network5:amd64 (5.15.2+dfsg-8, 5.15.2+dfsg-9), libqt5dbus5:amd64 (5.15.2+dfsg-8, 5.15.2+dfsg-9), libqt5widgets5:amd64 (5.15.2+dfsg-8, 5.15.2+dfsg-9), libqt5gui5:amd64 (5.15.2+dfsg-8, 5.15.2+dfsg-9), libqt5printsupport5:amd64 (5.15.2+dfsg-8, 5.15.2+dfsg-9), libqt5xml5:amd64 (5.15.2+dfsg-8, 5.15.2+dfsg-9), libqt5opengl5:amd64 (5.15.2+dfsg-8, 5.15.2+dfsg-9)
End-Date: 2021-07-03 03:25:43

Start-Date: 2021-07-03 03:32:58
Commandline: /usr/sbin/synaptic
Requested-By: david (1000)
Install: sct:amd64 (1.3-1+b1)
End-Date: 2021-07-03 03:32:59

Start-Date: 2021-07-04 09:37:07
Commandline: apt upgrade
Requested-By: david (1000)
Upgrade: libllvm12:amd64 (1:12.0.1~+rc3-1, 1:12.0.1~+rc4-1)
End-Date: 2021-07-04 09:37:08

Start-Date: 2021-07-05 14:39:34
Commandline: apt upgrade
Requested-By: david (1000)
Upgrade: python-apt-common:amd64 (2.2.0, 2.2.1), libgnome-desktop-3-19:amd64 (3.38.5-2, 3.38.5-3), gnome-desktop3-data:amd64 (3.38.5-2, 3.38.5-3), libnss3:amd64 (2:3.67-1, 2:3.67-2), python3-apt:amd64 (2.2.0, 2.2.1), libuv1:amd64 (1.40.0-1, 1.40.0-2)
End-Date: 2021-07-05 14:39:36

Posts: 3 · w0mpy 5 Jul 2021, 21:54

Thank you for your quick response, tippunmon. This pretty much confirms, that Mesa 21.1.4 fixes the issue.

So if anybody else with this bug needs it fixed ASAP, can get it here:
https://docs.mesa3d.org/download.html

Distros with AUR can also use "mesa-git".