Property:wdt

---

BoxMatrix >> System >> wdt

@ BoxMatrix   -   IRC-Chat   -   Translate: de es fr it nl pl

News

Selectors

Models

Accessories

Components

Environment

Config

Commands

System

Webif

Software

Develop

Lexicon

Community

Project

Media

---

Devices

Filesystems

Partitions

Sockets

Netlink

Pipes

Interfaces

Bridges

Ports

Events

Sources

Sinks

AVMIPC

Processes

Watchdogs

Memory

Slab

Vmalloc

ProcFS

SysFS

Research

---

Procfs-Object

Procfs-Object:	wdt   -   type File	Wiki	Freetz	IPPF	whmf	AVM	Web
Location:	System >> Proc-Filesystem   -   Origin: AVM
Path:	/proc/avm
Properties:	Firmware: 6.55 - 7.90   -   Kernel (perm): 2.6.32.61 (r), 2.6.39.4 (r), 3.10.107 (r), 3.10.73 (r), 4.1.38 (r), 4.1.52 (r), 4.19.183 (r), 4.4.271 (r), 4.4.60 (r), 4.9.198 (r), 4.9.218 (r), 4.9.250 (r), 4.9.325 (r)
Function:	Currently active AVM-Watchdogs.

Goto:   Examples  -  Dependencies   -   Model-Matrix   -   Help Supportdata2   -   SMW-Browser

Details

wdt provides statistics about the currently running AVM-Watchdogs.
It is used in supportdata.basis like this:

# Watchdog-Statistic

cat /proc/avm/wdt

wdt is provided by ar7wdt_main.ko.

AVM-Watchdogs:

• Commands: avm_watchdog, watchdog (initscr)
• Startup: S05-watchdog, rc.tail.sh, watchdog.service
• Devices: watchdog (device)
• Procfs: wdt
• Sources: avm_event_remotewatchdog
• Sinks: avm_event_remotewatchdog_sink
• Events: remotewatchdog
• Libraries: libwdt.so
• Bundles: ar7wdt.ko, avmwdt.ko, avm_sammel.ko, avm.ko
• Drivers: ar7wdt_main.ko, ar7wdt_file.ko
• Special: ar7wdt_hw_wdtremote.ko, ar7wdt_hw_shim.ko
• Hardware: wdtimer.ko, ar7wdt_hw.ko, ar7wdt_hw_26.ko
• Hardware: ifxmips_wdt.ko, ar7wdt_hw_puma.ko, davinci_watchdog_hw.ko
• Hardware: ikan_wdt.ko, brcm_wdt.ko, ath_wdt.ko, qcom_wdt.ko
• Hardware: grx_wdt.ko, grx500_wdt.ko, tep-wdt.ko

Examples

fw 7.29 example:

fritz3:/var/mod/root $ cat /proc/avm/wdt

hdl= 2 supervisor    pid  976 triggered before:  15.570 s(avg  50.010 s) state: S cpu1 pgfault      0 oom_score 1
hdl= 3 untrustedd    pid 1178 triggered before:  68.690 s(avg  80.090 s) state: S cpu0 pgfault      4 oom_score 1
hdl= 4 boxnotifyd    pid 3089 triggered before:  41.490 s(avg  80.090 s) state: S cpu1 pgfault      0 oom_score 1
hdl= 5 run_clock     pid 3092 triggered before: 1200.950 s(avg 1680.000 s) state: S cpu0 pgfault      0 oom_score 1
hdl= 6 avmnexusd     pid 3159 triggered before:   5.960 s(avg   9.940 s) state: S cpu1 pgfault      7 oom_score 1
hdl= 7 l2tpv3d       pid 3220 triggered before:   8.670 s(avg   9.940 s) state: S cpu1 pgfault      1 oom_score 1
hdl= 8 dsl_monitor   pid 3252 triggered before:  15.570 s(avg  19.970 s) state: S cpu0 pgfault      1 oom_score 1
hdl= 9 ctlmgr        pid 3259 triggered before:   2.740 s(avg   9.020 s) state: S cpu0 pgfault     48 oom_score 1
hdl=10 vpnd          pid 3266 triggered before:   5.880 s(avg   9.940 s) state: S cpu0 pgfault      0 oom_score 1
hdl=18 upnpd         pid 3272 triggered before:   1.160 s(avg   9.940 s) state: S cpu1 pgfault     45 oom_score 1
hdl=11 multid        pid 3368 triggered before:   7.230 s(avg   9.940 s) state: S cpu0 pgfault      4 oom_score 1
hdl=12 pcpd          pid 3469 triggered before:   4.750 s(avg   9.930 s) state: S cpu0 pgfault      0 oom_score 1
hdl=13 wland         pid 3488 triggered before:   8.350 s(avg   9.960 s) state: S cpu0 pgfault      1 oom_score 1
hdl=14 dsld          pid 3531 triggered before:   2.100 s(avg   9.940 s) state: S cpu0 pgfault      0 oom_score 1
hdl=15 deviceinfod   pid 3554 triggered before:   0.820 s(avg   9.930 s) state: S cpu0 pgfault      0 oom_score 1
hdl=17 aha           pid 3556 triggered before:   4.600 s(avg  30.000 s) state: S cpu1 pgfault     11 oom_score 1
hdl=16 pbd           pid 3644 triggered before:  16.530 s(avg  80.090 s) state: S cpu1 pgfault      0 oom_score 1
hdl=19 meshd         pid 4648 triggered before:   8.690 s(avg   9.930 s) state: S cpu1 pgfault      6 oom_score 1
hdl=21 telefon       pid 4890 triggered before:  15.730 s(avg  90.170 s) state: S cpu1 pgfault      2 oom_score 1
hdl=22 log_server[4995] pid 5000 triggered before:   9.390 s(avg   9.950 s) state: S cpu0 pgfault      0 oom_score 1
hdl=23 log_server[5001] pid 5002 triggered before:   9.390 s(avg  10.020 s) state: S cpu1 pgfault      0 oom_score 1
hdl=24 log_server[5003] pid 5004 triggered before:   9.350 s(avg   9.960 s) state: S cpu0 pgfault      0 oom_score 1
hdl=25 log_server[5005] pid 5007 triggered before:   9.330 s(avg   9.950 s) state: S cpu1 pgfault      0 oom_score 1
hdl=26 log_server[5008] pid 5011 triggered before:   9.330 s(avg  10.020 s) state: S cpu0 pgfault      0 oom_score 1
hdl=27 log_server[5012] pid 5013 triggered before:   9.290 s(avg  10.020 s) state: S cpu1 pgfault      0 oom_score 1
hdl=28 log_server[5014] pid 5015 triggered before:   9.290 s(avg   9.950 s) state: S cpu0 pgfault      0 oom_score 1
hdl=29 voipd         pid 5093 triggered before:   2.720 s(avg  10.000 s) state: S cpu1 pgfault      6 oom_score 1

Dependencies

Daily updated index of all dependencies of this object. Last update: GMT.
A ** in the Mod column marks info from Supportdata2 probes, which will always stay incomplete.
A - in the Mod column marks manual research, the Firmware then shows where the Object occurs, not the Relation.

Relation	Typ	Object	Mod	Firmware	Info	Origin
0 dependencies for this object

Model-Matrix

Daily updated index of the presence, path and size of this object for each model. Last update: 2024-12-22 05:13 GMT.
Showing all models using this object. Click any column header (click-wait-click) to sort the list by the respective data.
The (main/scrpn/boot/arm/prx/atom/rtl) label in the Model column shows which CPU is meant for Multi-Linux models.
Note that this list comes from Supportdata2 probes, which can have arbitrary settings and come from different firmware versions.
It doesn't say much if a model is not listed here. It may be a missing supportdata2 file or just a disabled feature.

Model	Firmware	Path	Kernel (perm)
FRITZ!Box 3490	7.30	/proc/avm	3.10.107 (r)
FRITZ!Box 4020	7.01	/proc/avm	4.4.60 (r)
FRITZ!Box 4060	7.30 - 7.39	/proc/avm	4.4.271 (r), 4.4.60 (r)
FRITZ!Box 5490	7.29	/proc/avm	3.10.107 (r)
FRITZ!Box 5590 Fiber (main)	7.29	/proc/avm	4.4.60 (r)
FRITZ!Box 6430 Cable (arm)	7.29	/proc/avm	2.6.39.4 (r)
FRITZ!Box 6430 Cable (atom)	7.29	/proc/avm	2.6.39.4 (r)
FRITZ!Box 6490 Cable (arm)	7.29 - 7.39	/proc/avm	2.6.39.4 (r)
FRITZ!Box 6490 Cable (atom)	7.29 - 7.39	/proc/avm	2.6.39.4 (r)
FRITZ!Box 6660 Cable (atom)	7.29	/proc/avm	4.9.250 (r)
FRITZ!Box 6850 LTE	7.39	/proc/avm	4.4.60 (r)
FRITZ!Box 6850 5G	7.39	/proc/avm	4.4.60 (r)
FRITZ!Box 7272	6.88	/proc/avm	2.6.32.61 (r)
FRITZ!Box Fon WLAN 7320	6.55	/proc/avm	2.6.32.61 (r)
FRITZ!Box 7362 SL	7.12	/proc/avm	3.10.107 (r)
FRITZ!Box 7412	6.87	/proc/avm	3.10.73 (r)
FRITZ!Box 7430	7.29	/proc/avm	3.10.107 (r)
FRITZ!Box 7490	7.29 - 7.51	/proc/avm	3.10.107 (r)
FRITZ!Box 7510	7.30	/proc/avm	4.4.60 (r)
FRITZ!Box 7520	7.29 - 7.50	/proc/avm	4.4.271 (r), 4.4.60 (r)
FRITZ!Box 7520 v2	7.31	/proc/avm	4.4.60 (r)
FRITZ!Box 7530	7.39	/proc/avm	4.4.271 (r)
FRITZ!Box 7530 AX	7.31 - 7.51	/proc/avm	4.1.52 (r), 4.19.183 (r)
FRITZ!Box 7581	7.17	/proc/avm	4.1.38 (r)
FRITZ!Box 7590	7.57 - 7.90	/proc/avm	4.9.325 (r)
FRITZ!Box 7590 AX	7.31 - 7.39	/proc/avm	4.9.198 (r), 4.9.218 (r)
FRITZ!Smart Gateway	7.57 - 7.58	/proc/avm	4.4.271 (r)
FRITZ!Repeater 1200 AX	7.30 - 7.39	/proc/avm	4.4.60 (r)
FRITZ!WLAN Repeater 1750E	7.29	/proc/avm	4.4.60 (r)
FRITZ!Repeater 6000	7.29 - 7.39	/proc/avm	4.4.60 (r)
30 models use this object

Help Supportdata2

The data in this article is incomplete since it was manually collected using the Supportdata2 project.

Unlike the Supportdata-Probes which have been collected for years Supportdata2 is brand new and only has a few probes.
If you have access to a shell then please help to extend the Supportdata2 collection to improve this data.

It's easy and it's done in minutes. Please send created data as an Email attachment to the address listed here. Thanks!

SMW-Browser

Property:wdt

Information is currently being retrieved from the backend.