If you like BoxMatrix then please contribute Supportdata, Supportdata2, Firmware and/or Hardware (get in touch).
My metamonk@yahoo.com is not reachable by me since years. Please use hippie2000@webnmail.de instead.
Property:remotewatchdog
| BoxMatrix >> System >> remotewatchdog | @ 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 |
AVM-Event
| AVM-Event: | remotewatchdog - type | Wiki | Freetz | IPPF | whmf | AVM | Web |
| Location: | System >> AVM-Events - Origin: AVM | ||||||
| Event-Sources: | avm_event_remotewatchdog | ||||||
| Properties: | Firmware: 6.24 - 7.61 | ||||||
| Function: | ar7wdt_hw_wdtremote.ko remote watchdog control | ||||||
Goto: Dependencies - Model-Matrix - Missing Supportdata - SMW-Browser
Details
The remotewatchdog event is used for Inter-CPU communication of ar7wdt.ko instances on Puma6/7 models.
On Puma6 and Puma7 models FRITZ!OS is running on the ATOM CPU, while the cable modem frontend runs on the ARM CPU.
ar7wdt.ko is the management kernel module for AVM-Watchdogs, running on both Linux indtances on these models.
To connect both the ATOM side runs the avm_event_remotewatchdog source sending remotewatchdog events to the
avm_event_remotewatchdog_sink on the ARM side. The real watchdog which can reboot the system runs on the ARM side.
remotewatchdog events can register a watchdog and its timeout, release it, or perform the trigger to avoid a reboot.
// From include/uapi/avm/event/gen-types.h
struct _avm_event_remotewatchdog {
struct _avm_event_header event_header;
enum _avm_remote_wdt_cmd cmd;
char name[16];
unsigned int param;
};
enum _avm_remote_wdt_cmd {
wdt_register = 0, /*--- RemoteCPU: param1: time to trigger ---*/
wdt_release = 1, /*--- RemoteCPU ---*/
wdt_trigger = 2, /*--- RemoteCPU: trigger ---*/
};
- 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
Dependencies
Daily updated index of all dependencies of this event. Last update: GMT.
A * in the Mod column marks info from Supportdata-Probes, which will always stay incomplete.
A ** in the Mod column marks info from Supportdata2 probes, which by their nature will stay way more incomplete.
A - in the Mod column marks manual research, the Firmware then shows where the item occurs, not the Relation.
| Relation | Typ | Object | Mod | Firmware | Info | Origin |
|---|---|---|---|---|---|---|
| Source | evsrc | avm_event_remotewatchdog | 3* | 6.24 - 7.29 | Event-Source of ar7wdt_hw_wdtremote.ko / extswitch_watch | AVM |
| Sink | evsink | avm_event_remotewatchdog_sink | 7* | 6.24 - 7.61 | Event-Sink of ar7wdt_main.ko | AVM |
| 2 dependencies for this event | ||||||
Model-Matrix
Daily updated index of the presence, path and size of this event for each model. Last update: GMT.
Showing all models using this event. 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 Supportdata-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 supportdata file or just a disabled feature.
| Model | Firmware | Event-Sources | Event-Sinks |
|---|---|---|---|
| FRITZ!Box 6430 Cable (atom) | 6.87 - 7.29 | avm_event_remotewatchdog | |
| FRITZ!Box 6490 Cable (atom) | 6.24 - 7.24 | avm_event_remotewatchdog | |
| FRITZ!Box 6590 Cable (atom) | 6.87 - 7.20 | avm_event_remotewatchdog | |
| 3 models use this event | |||
Missing Supportdata
The data in this article is incomplete due to missing Supportdata-Probes for the models listed below.
If you own any of these models and would like to help then please get in touch.
| Model | Method | Info |
|---|---|---|
| Eumex 300 IP | telnet | |
| FRITZ!Box Fon 5010 | html | http://fritz.box/html/support.html |
| FRITZ!Box Fon 5012 | html | http://fritz.box/html/support.html |
| FRITZ!Box Fon ata | html | http://fritz.box/html/support.html |
| FRITZ!Box Fon ata 1020 | html | http://fritz.box/html/support.html |
| FRITZ!Box Fon WLAN 7113 INT | html | http://fritz.box/html/support.html |
| FRITZ!Box WLAN 3270 IT | lua | http://fritz.box/support.lua |
| Speedport W 501V | telnet | |
| Speedport W 722V | console | |
| 9 models without supportdata probes | ||
