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:log (event)
| BoxMatrix >> System >> log (event) | @ 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 |
 |
Name-Collision - multiple objects in this wiki use the name log!
|
AVM-Event
| AVM-Event: | log (event) - type | Wiki | Freetz | IPPF | whmf | AVM | Web |
| Location: | System >> AVM-Events - Origin: AVM | ||||||
| Event-Sources: | event_log | ||||||
| Properties: | Firmware: 6.24 - 7.61 | ||||||
| Function: | avm_event.ko remote logging | ||||||
Goto: Dependencies - Model-Matrix - Missing Supportdata - SMW-Browser
Details
The log event is used for Inter-CPU logging between avm_event.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.
avm_event.ko is the management kernel module for AVM-Events and runs on both Linux instances of these models.
For remote logging each instance creates an event_log event source to send log events from it. A matching event sink is not
registered since this is handled internally. log_remote_sink is from very old firmware before FRITZ!OS ran on ATOM.
// From include/uapi/avm/event/gen-types.h
struct avm_event_log {
enum _avm_logtype logtype;
unsigned int loglen;
unsigned int logpointer;
unsigned int checksum;
unsigned int rebootflag;
};
enum _avm_logtype {
local_panic = 0,
local_crash = 1,
remote_panic = 2,
remote_crash = 3,
};
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 | event_log | 11* | 6.24 - 7.61 | Event-Source of avm_event.ko | AVM |
| Sink | evsink | log_remote_sink | 1* | 6.24 - 6.66 | Event-Sink of avm_event.ko (obsolete) | 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) label in the Model column shows which CPU is meant for models with multiple Linux instances.
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 | event_log | |
| FRITZ!Box 6490 Cable (atom) | 6.24 - 7.24 | event_log | |
| FRITZ!Box 6590 Cable (atom) | 6.87 - 7.20 | event_log | |
| FRITZ!Box 6591 Cable (arm) | 7.01 - 7.29 | event_log | |
| FRITZ!Box 6591 Cable (atom) | 7.01 - 7.29 | event_log | |
| FRITZ!Box 6660 Cable (arm) | 7.13 - 7.29 | event_log | |
| FRITZ!Box 6660 Cable (atom) | 7.13 - 7.29 | event_log | |
| FRITZ!Box 6670 Cable (arm) | 7.59 - 7.61 | event_log | |
| FRITZ!Box 6670 Cable (atom) | 7.59 - 7.61 | event_log | |
| FRITZ!Box 6690 Cable (arm) | 7.29 - 7.57 | event_log | |
| FRITZ!Box 6690 Cable (atom) | 7.29 - 7.57 | event_log | |
| 11 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.
