Hi folks,

Has anyone else had any issues with firmware 4.4.5.1/v23 on the Vigor 3912S which causes the router to freeze up every 18 - 20 hours without warning.
I'm connected to Zen internet FTTP and have for months had no issues but the past 4 days in a row the router has locked up forcing me to power cycle to get it to work again.

Setting a static IP on my laptop and plugging directly into the router when it locks up doesn't allow me to ping or connect to it so I'm unable to pull logs.

Any help would be great.

Thanks,

John

I upgraded to 4.4.5.1 just before I returned my 3912s due to hardware failure (not received it back yet) so I can’t say for sure but I didn’t see any issues, and I also use Zen.
When I get it back I’ll see how I get on and report back.

When you say it locks up, do you mean it’s totally unfunctional? You’ve said you cannot ping it; also not ssh to it? It’s not processing/routing?
Can you set up a syslog server and use that so when the 3912s dies you’ll be able to still access the syslog data?
I use a Synology NAS for my syslog server but the functionality of that is “limited” so it’s not a solution I’d recommend and indeed I intend to create a container to provide this functionality at some point.

Rgds

I encountered same issue with latest firmware, had to power off/on router to resolve, after reboot router was working again and able to login, then access export the debug logs. From debug logs found:
20251003_013042_5232_8190_QEMU_dies_Ping Fail
20251003_142600_5232_8190_dpdk_dies_Process Die
20251003_143052_5232_8190_dpdk_dies_Process Die
20251003_143445_5232_8190_dpdk_dies_Process Die
Above you can see further errors, below this was the time of total lockup, router not responsive:
20251003_163050_5232_8190_QEMU_dies_Ping Fail
Then followed by main log below:
2025-10-03_16:39:48.12451 v3912-r2: Pulling from vigor39xx/suricata
2025-10-03_16:39:48.12455 Digest: sha256:91f3ecdca246a2bf0d2034f11ac82d17aecb6a3d95e7a2149f3eda5494fe98fb
2025-10-03_16:39:48.12457 Status: Image is up to date for vigor39xx/suricata:v3912-r2
2025-10-03_16:39:48.12458 docker.io/vigor39xx/suricata:v3912-r2
2025-10-03_16:39:48.68887 touch: setting times of '/run/docker/netns/default': Operation not permitted
2025-10-03_16:42:42.25481 Drayos is alive and fw_upload is not running, start FW Backup ...
2025-10-03_16:42:42.25761 rc.99.fw_backup.sh: [FW Backup ...][2025-10-03(Fri) 16:42:42]
2025-10-03_16:42:46.20866 rc.99.fw_backup.sh: [FW Backup done][2025-10-03(Fri) 16:42:46]
2025-10-03_16:46:22.85365 Processing basic set...
Suspect it was stuck or hung, had to power off/on to recover.


 

@alpha1tec have you tried updating the Linux packages (ssh to 3912s)? Potentially a docker issue?

I have tried upgrading the Linux applications, but it is failing to upgrade due to error write (28: No space left on device)
W: Failed to fetch https://download.docker.com/linux/ubuntu/dists/jammy/InReleas                                          e  Error writing to file - write (28: No space left on device) [IP: 18.239.236.6                                          7 443]
W: Some index files failed to download. They have been ignored, or old ones used                                           instead.

emmc 0% - 10% device life time used
ssd percentage used is 3%, still healthy
[Core File]==================================================================
-rw

---

1 root root 49205248 Oct  3 14:34 /app/core/dray_dpdk.core.1218752
-rw

---

1 root root 49205248 Oct  3 14:30 /app/core/dray_dpdk.core.1205703
-rw

---

1 root root 49205248 Oct  3 14:25 /app/core/dray_dpdk.core.238457
-rw

---

1 root root 49205248 Aug 26 12:13 /app/core/dray_dpdk.core.1868805

admin@Vigor3912:~$ df
Filesystem     1K-blocks      Used Available Use% Mounted on
tmpfs            4072868         0   4072868   0% /oldroot/run
/dev/nvme0n1p1 245085796 245069412         0 100% /oldroot/mnt
overlay        245085796 245069412         0 100% /
tmpfs            1048576     15364   1033212   2% /dev/shm
tmpfs            1048576     27504   1021072   3% /run
tmpfs               5120         0      5120   0% /run/lock
tmpfs            1048576       192   1048384   1% /tmp
/dev/mmcblk0p2    499656    197160    265800  43% /image
/dev/mmcblk0p1     59365      8013     46766  15% /cfg
/dev/mmcblk0p5    499656     49924    413036  11% /data
/dev/mmcblk0p3    499656    197160    265800  43% /image2
/dev/mmcblk0p6   5836712    725372   4795132  14% /app
tmpfs             814572         0    814572   0% /run/user/1000


 

Thanks for your help, I think I have resolved it now, followed the solution https://www.draytek.com/support/knowledge-base/11698 option "Clean Linux Applications". 
Clean Linux Application: this will restore Linux OS and any applications installed to the default state.
After reboot was then able to run upgrade Linux Packages.