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:panic (procfs)
BoxMatrix >> System >> panic (procfs) | @ 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 panic!
|
Procfs-Object
Procfs-Object: | panic (procfs) - type File | Wiki | Freetz | IPPF | whmf | AVM | Web |
Location: | System >> Proc-Filesystem - Origin: AVM | ||||||
Path: | /proc/avm/log_cr, /proc/avm/log_sd | ||||||
Properties: | Firmware: 6.55 - 7.90 - Kernel (perm): 2.6.32.61 (rw), 2.6.39.4 (r), 2.6.39.4 (rw), 3.10.107 (r), 3.10.107 (rw), 3.10.73 (rw), 4.1.38 (rw), 4.1.52 (rw), 4.19.183 (r), 4.4.271 (r), 4.4.60 (r), 4.4.60 (rw), 4.9.198 (rw), 4.9.218 (r), 4.9.250 (rw), 4.9.325 (r) | ||||||
Function: | Kernel crash logs for supportdata and crashreport mail (first Linux). |
Goto: Dependencies - Model-Matrix - Help Supportdata2 - SMW-Browser
Details
panic is part of the second solution of Kernel crash logs in procfs. It is the successor of avm_panic_sd / avm_panic_cr.
This file exists in 2 instances at 2 locations, depending on the purpose it's used for:
The first instance is located in /proc/avm/log_sd
. The trailing sd
means dedicated to supportdata.
root@fritz1:/var/mod/root# ls -l /proc/avm/log_sd -rw-rw-rw- 1 root root 0 Dec 1 08:49 crash -rw-rw-rw- 1 root root 0 Dec 1 08:49 crash2 -rw-rw-rw- 1 root root 0 Dec 1 08:49 panic -rw-rw-rw- 1 root root 0 Dec 1 08:49 panic2 -rw-rw-rw- 1 root root 0 Dec 1 08:49 user -rw-rw-rw- 1 root root 0 Dec 1 08:49 user2
The second instance is located in /proc/avm/log_cr
. The trailing cr
means for crashreport mail by libmailbuilder.so.
root@fritz1:/var/mod/root# ls -l /proc/avm/log_cr -rw-rw-rw- 1 root root 0 Dec 1 08:49 crash -rw-rw-rw- 1 root root 0 Dec 1 08:49 crash2 -rw-rw-rw- 1 root root 0 Dec 1 08:49 panic -rw-rw-rw- 1 root root 0 Dec 1 08:49 panic2 -rw-rw-rw- 1 root root 0 Dec 1 08:49 user -rw-rw-rw- 1 root root 0 Dec 1 08:49 user2
crash, panic and user are for the first Linux, the Linux this is running on.
crash2, panic2 and user2 are for the other / second Linux if Inter-CPU logging is used.
Reboot Info:
- procfs: info, reboot_status
- kernel: avm_reboot_status.ko, reboot_status.ko
Crash Logs: - user mode crashes
- bootenv: crash (bootenv)
- tffs: crash.log (tffs)
- procfs: crash.log (procfs), crash (procfs), crash2 (procfs)
- temp: crash.log (temp)
- pipes: crash.log (pipe)
Panic Logs: - kernel crashes
- tffs: panic (tffs)
- procfs: panic (procfs), panic2 (procfs), avm_panic_cr, avm_panic_sd
- temp: panic (temp)
- pstore: console-ramoops-0
User Logs: - user stuff
- procfs: user (procfs), user2
Module Logs: - kernel modules
- procfs: antfs_logger, capicodec
Debug Logs:
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-20 18:05 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/log_cr, /proc/avm/log_sd | 3.10.107 (rw) |
FRITZ!Box 4020 | 7.01 | /proc/avm/log_cr, /proc/avm/log_sd | 4.4.60 (rw) |
FRITZ!Box 4060 | 7.30 - 7.39 | /proc/avm/log_cr, /proc/avm/log_sd | 4.4.271 (r), 4.4.60 (rw) |
FRITZ!Box 5490 | 7.29 | /proc/avm/log_cr, /proc/avm/log_sd | 3.10.107 (rw) |
FRITZ!Box 5590 Fiber (main) | 7.29 | /proc/avm/log_cr, /proc/avm/log_sd | 4.4.60 (rw) |
FRITZ!Box 6430 Cable (arm) | 7.29 | /proc/avm/log_cr, /proc/avm/log_sd | 2.6.39.4 (rw) |
FRITZ!Box 6430 Cable (atom) | 7.29 | /proc/avm/log_cr, /proc/avm/log_sd | 2.6.39.4 (rw) |
FRITZ!Box 6490 Cable (arm) | 7.29 - 7.39 | /proc/avm/log_cr, /proc/avm/log_sd | 2.6.39.4 (r), 2.6.39.4 (rw) |
FRITZ!Box 6490 Cable (atom) | 7.29 - 7.39 | /proc/avm/log_cr, /proc/avm/log_sd | 2.6.39.4 (r), 2.6.39.4 (rw) |
FRITZ!Box 6660 Cable (atom) | 7.29 | /proc/avm/log_cr, /proc/avm/log_sd | 4.9.250 (rw) |
FRITZ!Box 6850 LTE | 7.39 | /proc/avm/log_cr, /proc/avm/log_sd | 4.4.60 (r) |
FRITZ!Box 6850 5G | 7.39 | /proc/avm/log_cr, /proc/avm/log_sd | 4.4.60 (r) |
FRITZ!Box 7272 | 6.88 | /proc/avm/log_cr, /proc/avm/log_sd | 2.6.32.61 (rw) |
FRITZ!Box Fon WLAN 7320 | 6.55 | /proc/avm/log_cr, /proc/avm/log_sd | 2.6.32.61 (rw) |
FRITZ!Box 7362 SL | 7.12 | /proc/avm/log_cr, /proc/avm/log_sd | 3.10.107 (rw) |
FRITZ!Box 7412 | 6.87 | /proc/avm/log_cr, /proc/avm/log_sd | 3.10.73 (rw) |
FRITZ!Box 7430 | 7.29 | /proc/avm/log_cr, /proc/avm/log_sd | 3.10.107 (rw) |
FRITZ!Box 7490 | 7.29 - 7.51 | /proc/avm/log_cr, /proc/avm/log_sd | 3.10.107 (r), 3.10.107 (rw) |
FRITZ!Box 7510 | 7.30 | /proc/avm/log_cr, /proc/avm/log_sd | 4.4.60 (rw) |
FRITZ!Box 7520 | 7.29 - 7.50 | /proc/avm/log_cr, /proc/avm/log_sd | 4.4.271 (r), 4.4.60 (rw) |
FRITZ!Box 7520 v2 | 7.31 | /proc/avm/log_cr, /proc/avm/log_sd | 4.4.60 (rw) |
FRITZ!Box 7530 | 7.39 | /proc/avm/log_cr, /proc/avm/log_sd | 4.4.271 (r) |
FRITZ!Box 7530 AX | 7.31 - 7.51 | /proc/avm/log_cr, /proc/avm/log_sd | 4.1.52 (rw), 4.19.183 (r) |
FRITZ!Box 7581 | 7.17 | /proc/avm/log_cr, /proc/avm/log_sd | 4.1.38 (rw) |
FRITZ!Box 7590 | 7.57 - 7.90 | /proc/avm/log_cr, /proc/avm/log_sd | 4.9.325 (r) |
FRITZ!Box 7590 AX | 7.31 - 7.39 | /proc/avm/log_cr, /proc/avm/log_sd | 4.9.198 (rw), 4.9.218 (r) |
FRITZ!Smart Gateway | 7.57 - 7.58 | /proc/avm/log_cr, /proc/avm/log_sd | 4.4.271 (r) |
FRITZ!Repeater 1200 AX | 7.30 - 7.39 | /proc/avm/log_cr, /proc/avm/log_sd | 4.4.60 (r), 4.4.60 (rw) |
FRITZ!WLAN Repeater 1750E | 7.29 | /proc/avm/log_cr, /proc/avm/log_sd | 4.4.60 (rw) |
FRITZ!Repeater 6000 | 7.29 - 7.39 | /proc/avm/log_cr, /proc/avm/log_sd | 4.4.60 (r), 4.4.60 (rw) |
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!