synce4l will not restart after some number of runs

Version: 1.1.0
Hardware: Raspberry Pi CM4 with LAN743x based NIC on the PCIe bus.
OS: Raspberry Pi OS 2024-11-19 (891df1e21ed2b6099a2e6a13e26c91dea44b34d4)

I compiled synce4l from source. I had to modify SYNCE_THREAD_STACK_SIZE to 0x100000 to fix a segfault, see here: https://github.com/intel/synce4l/issues/59

Initially synce4l works without issue a few times, but eventually it stops working. Output looks like this:

```
sudo synce4l -f /home/pi/synce4l.conf -m
synce4l[2992.821]: [synce4l] created synce1
synce4l[2992.821]: [synce4l] device init synce1 addr 0x559215b8b0
synce4l[2992.821]: [synce4l] config item (null).smc_socket_path is '/tmp/synce4l_socket'
synce4l[2992.822]: [synce4l] created num_devices: 1
synce4l[2992.822]: [synce4l] config item synce1.extended_tlv is 1 (0x1)
synce4l[2992.822]: [synce4l] synce_manager_server_thread Bind failed
synce4l[2992.822]: [synce4l] config item synce1.network_option is 1 (0x1)
synce4l[2992.822]: [synce4l] config item synce1.recover_time is 60 (0x3c)
synce4l[2992.822]: [synce4l] config item synce1.eec_get_state_cmd is '/home/pi/synce_poll/bin/synce_poll'
synce4l[2992.822]: [synce4l] config item synce1.eec_get_state_cmd is '/home/pi/synce_poll/bin/synce_poll'
synce4l[2992.822]: [synce4l] config item synce1.eec_holdover_value is 'holdover1'
synce4l[2992.822]: [synce4l] config item synce1.eec_locked_ho_value is 'holdover'
synce4l[2992.822]: [synce4l] config item synce1.eec_locked_value is 'locked'
synce4l[2992.822]: [synce4l] config item synce1.eec_freerun_value is 'freerun'
synce4l[2992.822]: [synce4l] config item synce1.eec_invalid_value is 'invalid'
synce4l[2992.822]: [synce4l] config item synce1.module_name is '(null)'
valid'
synce4l[2992.822]: [synce4l] config item synce1.module_name is '(null)'
```

Presumably `synce_manager_server_thread Bind failed` is the issue. From that point onwards, until a reboot, synce4l will not start.

I have tried removing the LAN743x driver and reinstalling it with `modprobe`, and taking the interface down and then up again. The only thing that fixes it is a reboot.