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:sysrq-trigger
BoxMatrix >> System >> sysrq-trigger | @ 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: | sysrq-trigger - type File | Wiki | Freetz | IPPF | whmf | AVM | Web |
Location: | System >> Proc-Filesystem - Origin: Linux | ||||||
Path: | /proc | ||||||
Properties: | Firmware: 4.33 - 7.90 - Kernel (perm): 2.6.13.1 (w), 2.6.28.10 (w), 2.6.32.21 (w), 2.6.32.60 (w), 2.6.32.61 (w), 2.6.39.4 (w), 3.10.107 (w), 3.10.73 (w), 4.1.38 (w), 4.1.52 (w), 4.19.183 (w), 4.4.271 (w), 4.4.60 (w), 4.9.198 (w), 4.9.218 (w), 4.9.250 (w), 4.9.325 (w) | ||||||
Function: | Write-only trigger to fire up a SysRq event. |
Goto: Examples - Dependencies - Model-Matrix - Help Supportdata2 - SMW-Browser
Details
sysrq-trigger is a write-only trigger to fire up a SysRq event.
A SysRq event is typically triggered by pressing the key combination ALT-SysRq-<character>
.
The SysRq
key is the key often labled Print Scrn
.
Writing a <character>
to sysrq-trigger
performs exactly the same action as pressing the key combination.
See also sysrq.rst and sysrq.txt and the Wikipedia page.
Excerpt from the proc(5) man page:
/proc/sysrq-trigger (since Linux 2.4.21) Writing a character to this file triggers the same SysRq function as typing ALT-SysRq-<character> (see the description of /proc/sys/kernel/sysrq). This file is normally writable only by root. For further details see the Linux kernel source file Documentation/admin-guide/sysrq.rst (or Documentation/sysrq.txt before Linux 4.10).
Examples
Assumed from libwlandcommon.so fw 7.29 - immediate reboot without unmounting or syncing:
echo "b" > /proc/sysrq-trigger
Symbolic from mobiled fw 7.29 - performs a crash and creates a crashdump:
echo "c" > /proc/sysrq-trigger
From rc.net fw 7.29 - commented out - sets the loglevel to debug - see klogd explaining the loglevels:
# echo STD_PRINTK >/dev/debug ; echo 9 >/proc/sysrq-trigger
From tail (initscr) fw 7.29 - sets the loglevel to warn - see klogd explaining the loglevels:
echo "4" > /proc/sysrq-trigger
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-03 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 | 3.10.107 (w) |
FRITZ!Box 4020 | 7.01 | /proc | 4.4.60 (w) |
FRITZ!Box 4060 | 7.30 - 7.39 | /proc | 4.4.271 (w), 4.4.60 (w) |
FRITZ!Box 5490 | 7.29 | /proc | 3.10.107 (w) |
FRITZ!Box 5590 Fiber (main) | 7.29 | /proc | 4.4.60 (w) |
FRITZ!Box 6360 Cable | 5.20 | /proc | 2.6.28.10 (w) |
FRITZ!Box 6430 Cable (arm) | 7.29 | /proc | 2.6.39.4 (w) |
FRITZ!Box 6430 Cable (atom) | 7.29 | /proc | 2.6.39.4 (w) |
FRITZ!Box 6490 Cable (arm) | 7.29 - 7.39 | /proc | 2.6.39.4 (w) |
FRITZ!Box 6490 Cable (atom) | 7.29 - 7.39 | /proc | 2.6.39.4 (w) |
FRITZ!Box 6660 Cable (atom) | 7.29 | /proc | 4.9.250 (w) |
FRITZ!Box 6850 LTE | 7.39 | /proc | 4.4.60 (w) |
FRITZ!Box 6850 5G | 7.39 | /proc | 4.4.60 (w) |
FRITZ!Box Fon WLAN 7140 | 4.33 | /proc | 2.6.13.1 (w) |
FRITZ!Fon 7150 | 4.72 | /proc | 2.6.13.1 (w) |
FRITZ!Box Fon WLAN 7240 | 6.06 | /proc | 2.6.32.60 (w) |
FRITZ!Box 7272 | 6.88 | /proc | 2.6.32.61 (w) |
FRITZ!Box Fon WLAN 7320 | 6.55 | /proc | 2.6.32.61 (w) |
FRITZ!Box 7362 SL | 7.12 | /proc | 3.10.107 (w) |
FRITZ!Box Fon WLAN 7390 | 6.04 | /proc | 2.6.28.10 (w) |
FRITZ!Box 7412 | 6.87 | /proc | 3.10.73 (w) |
FRITZ!Box 7430 | 7.29 | /proc | 3.10.107 (w) |
FRITZ!Box 7490 | 7.29 - 7.51 | /proc | 3.10.107 (w) |
FRITZ!Box 7510 | 7.30 | /proc | 4.4.60 (w) |
FRITZ!Box 7520 | 7.29 - 7.50 | /proc | 4.4.271 (w), 4.4.60 (w) |
FRITZ!Box 7520 v2 | 7.31 | /proc | 4.4.60 (w) |
FRITZ!Box 7530 | 7.39 | /proc | 4.4.271 (w) |
FRITZ!Box 7530 AX | 7.31 - 7.51 | /proc | 4.1.52 (w), 4.19.183 (w) |
FRITZ!Box 7581 | 7.17 | /proc | 4.1.38 (w) |
FRITZ!Box 7590 | 7.57 - 7.90 | /proc | 4.9.325 (w) |
FRITZ!Box 7590 AX | 7.31 - 7.39 | /proc | 4.9.198 (w), 4.9.218 (w) |
FRITZ!Smart Gateway | 7.57 - 7.58 | /proc | 4.4.271 (w) |
FRITZ!Repeater 1200 AX | 7.30 - 7.39 | /proc | 4.4.60 (w) |
FRITZ!WLAN Repeater 1750E | 7.29 | /proc | 4.4.60 (w) |
FRITZ!Repeater 6000 | 7.29 - 7.39 | /proc | 4.4.60 (w) |
Speedport W 504V MK | 5.04 | /proc | 2.6.32.21 (w) |
36 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!