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:call
BoxMatrix >> System >> call | @ 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: | call - type File | Wiki | Freetz | IPPF | whmf | AVM | Web |
Location: | System >> Proc-Filesystem - Origin: AVM | ||||||
Path: | /proc/avm | ||||||
Properties: | Firmware: 6.87 - Kernel (perm): 3.10.73 (r) | ||||||
Function: | Low-level Kernel debugging (development Kernels only). |
Goto: Examples - Dependencies - Model-Matrix - Help Supportdata2 - SMW-Browser
Details
call is a low-level Kernel debugging helper, provided by avm_core_debug.ko, which is only built into development Kernels.
It is a commandline interface typically used with echo >
to trigger a set of testing functions.
Most of these functions are intentional bugs to test the Kernel crash handling. 7530ac fw 7.50:
waddr <addr> <val> # Write to address raddr <addr> <count> # Read from address oomslab <order> <limit> # OOM via slab allocation oomskb <count> # check skb-oom limit=<count> oom <order> <limit> # OOM via vmalloc bug_on # Trigger bug on event_ovr <trigger_msec> <count> # Remote event-overrun or stress kcrash # Trigger NULL-Pointer access hw_wdog [<cpu>] # Lock up all cpus/specific cpu timer <percent> <cpu> # Waste <percent> of time in sw-irq on <cpu> hang-mutex <timeout> # Hang a task on a mutex for <timeout> seconds alloc <kbyte> <order-mask> <age> <threads> [stop][GFP_KERNEL] # Alloc limit=<kbyte> order=0x<order-mask> # age=<age>(jiffies) num=<threads> [stop][GFP_KERNEL] faila # Check double-free, invalid kfree-pointer panic # Trigger kernel panic
Additional commands if CONFIG_AVM_FASTIRQ is enabled:
bug_on_firq # Trigger bug on in fiq mode kcrash_firq # NULL-Pointer access in fiq mode panic_firq # Trigger panic in fiq mode deadlock # Lock all fast and normal interrupts
Examples
echo panic > /proc/avm/call
Boom!
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-11-21 05:21 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 7412 | 6.87 | /proc/avm | 3.10.73 (r) |
1 model uses 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!