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:crash.log (tffs)
| BoxMatrix >> Configuration >> crash.log (tffs) | @ 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 |
| Static-Config | Bin-Files | Audio-Files | Crypto-Files | Vartar-Items | TFFS-Config | Temp-Files | Data-Dirs | Inet-Providers | VoIP-Providers | Firmware | Research |
 |
Name-Collision - multiple objects in this wiki use the name crash.log!
|
TFFS-Configfile
| Configfile: | crash.log (tffs) - type | Wiki | Freetz | IPPF | whmf | AVM | Web |
| Location: | Configuration >> TFFS-Configuration - Origin: AVM | ||||||
| Path: | /var/flash | ||||||
| Properties: | Firmware: 4.67 - 7.29 | ||||||
| Function: | Persistent user mode crash log / final dump. | ||||||
Goto: Dependencies - Model-Matrix - Missing Supportdata - SMW-Browser
Details
crash.log is the oldest solution of a user mode crash log, and the persistent storage of all later solutions.
In fact it is not really a log but a dump.
crash.log is stored in the TFFS-Configuration, which consists of character devices in the TFFS on most models.
Character devices are streams and don't behave like a file. Logs need to append a log entry at the end of a file,
which is not possible with streams. See crash.log (temp) for a workaround to append to a character device in TFFS.
Simplified from the MIPS kernel source at arch/mips/include/asm/r4cache.h:
dmesg > /var/flash/crash.log msgsend ctlmgr crashreport
This dumps the kernel ring buffer to crash.log and notifies ctlmgr about the crashreport.
In older firmware (ie 7272 fw 6.83) crash.log in TFFS is accessed by libavmcsock.so, libbacktrace.so and dsl_monitor
to dump a crash, by supportdata, and by libmailbuilder.so to compile the crashreport.
In recent firmware AVM implemented a procfs interface for crash handling which is directly maintained by tffs.ko.
See the crash.log (procfs) and crash (procfs) articles or the procfs lines below:
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 config file. Last update: 2024-04-19 06:38 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 |
|---|---|---|---|---|---|---|
| Config for | lib | libavmcppterminatehandler.so | - | 7.08 - 7.90 | Process termination handler for C++ programs | AVM |
| Config for | lib | libavmcsock.so | - | 1.120 - 7.90 | Networking, I/O and helper functions | AVM |
| Config for | lib | libbacktrace.so | - | 4.47 - 7.90 | Crash handler and logger | AVM |
| Config for | lib | libwlandcommon.so | - | 6.98 - 7.90 | TODO | Linux |
| Config for | cmd | mobiled (avmcmd) | - | 6.98 - 7.90 | Mobile modem daemon | AVM |
| 5 dependencies for this config file | ||||||
Model-Matrix
Daily updated index of the presence, path and size of this config file for each model. Last update: 2024-04-19 06:38 GMT.
Showing all models using this config file. 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 | Path | Maj/Min |
|---|---|---|---|
| FRITZ!Box WLAN 3270 | 5.54 | /var/flash | 249/95 |
| FRITZ!Box WLAN 3270 v3 | 5.21 - 5.54 | /var/flash | 240/95, 249/95 |
| FRITZ!Box 3272 | 5.50 - 6.85 | /var/flash | 244/95 |
| FRITZ!Box WLAN 3370 | 6.20 - 6.55 | /var/flash | 244/95 |
| FRITZ!Box 3390 | 6.20 - 6.55 | /var/flash | 243/95 |
| FRITZ!Box 4020 | 6.25 - 6.83 | /var/flash | 250/95 |
| FRITZ!Box Fon 5140 | 4.67 | /var/flash | 240/95 |
| FRITZ!Box 6320 Cable v1 | 6.21 | /var/flash | 249/95 |
| FRITZ!Box 6320 Cable v2 | 5.28 - 6.21 | /var/flash | 249/95 |
| FRITZ!Box 6340 Cable | 5.24 | /var/flash | 249/95 |
| FRITZ!Box 6360 Cable | 6.04 - 6.05 | /var/flash | 249/95 |
| FRITZ!Box 6490 Cable (arm) | 6.08 - 6.66 | /var/flash | 244/95 |
| FRITZ!Box 6490 Cable (atom) | 6.08 - 6.66 | /var/flash | 244/95, 245/95 |
| FRITZ!Box 6810 LTE | 6.04 | /var/flash | 250/95 |
| FRITZ!Box 6840 LTE | 6.04 - 6.10 | /var/flash | 243/95, 244/95 |
| FRITZ!Box 6842 LTE | 6.04 | /var/flash | 250/95 |
| FRITZ!Box Fon WLAN 7112 | 4.88 | /var/flash | 240/95 |
| FRITZ!Fon 7150 | 4.71 | /var/flash | 240/95 |
| FRITZ!Box Fon WLAN 7170 v1 | 4.87 - 4.88 | /var/flash | 240/95 |
| FRITZ!Box Fon WLAN 7170 v2 | 4.87 - 4.88 | /var/flash | 240/95 |
| FRITZ!Box Fon WLAN 7240 | 5.54 - 6.06 | /var/flash | 249/95 |
| FRITZ!Box Fon WLAN 7270 v1 | 4.89 | /var/flash | 240/95 |
| FRITZ!Box Fon WLAN 7270 v2 | 5.54 - 6.06 | /var/flash | 249/95 |
| FRITZ!Box Fon WLAN 7270 v3 | 5.53 - 6.06 | /var/flash | 249/95 |
| FRITZ!Box 7272 | 6.03 - 6.87 | /var/flash | 244/95 |
| FRITZ!Box 7312 | 5.20 - 6.54 | /var/flash | 240/95, 243/95 |
| FRITZ!Box Fon WLAN 7320 | 5.51 - 6.34 | /var/flash | 243/95 |
| FRITZ!Box 7330 | 5.20 - 6.03 | /var/flash | 240/95, 243/95 |
| FRITZ!Box 7330 SL | 5.20 - 6.54 | /var/flash | 240/95, 243/95 |
| FRITZ!Box Fon WLAN 7340 | 5.05 - 6.06 | /var/flash | 250/95 |
| FRITZ!Box Fon WLAN 7360 SL | 5.04 - 6.33 | /var/flash | 242/95, 243/95 |
| FRITZ!Box Fon WLAN 7360 v1 | 5.51 - 6.33 | /var/flash | 243/95, 244/95 |
| FRITZ!Box Fon WLAN 7360 v2 | 5.22 - 5.51 | /var/flash | 240/95, 242/95 |
| FRITZ!Box 7362 SL | 6.03 - 7.12 | /var/flash | 243/95 |
| FRITZ!Box 7369 | 6.31 | /var/flash | 250/95 |
| FRITZ!Box Fon WLAN 7390 | 5.50 - 6.86 | /var/flash | 250/95 |
| FRITZ!Box 7412 | 6.30 | /var/flash | 243/95 |
| FRITZ!Box 7430 | 6.30 | /var/flash | 243/95 |
| FRITZ!Box 7490 | 6.05 | /var/flash | 243/95 |
| FRITZ!Box 7490 (main) | 6.30 - 7.19 | /var/flash | 243/95 |
| FRITZ!Box 7490 (scrpn) | 7.01 - 7.29 | /var/flash | 243/95 |
| FRITZ!Box Fon WLAN 7570 vDSL | 4.91 - 4.92 | /var/flash | 240/95 |
| FRITZ!WLAN Repeater 300E | 5.09 - 6.04 | /var/flash | 240/95, 250/95 |
| FRITZ!WLAN Repeater 310 A | 5.24 - 6.92 | /var/flash | 240/95, 250/95 |
| FRITZ!WLAN Repeater 450E | 6.04 - 6.92 | /var/flash | 250/95 |
| FRITZ!WLAN Repeater 1160 | 6.92 | /var/flash | 250/95 |
| FRITZ!WLAN Repeater 1750E | 6.23 - 6.93 | /var/flash | 250/95 |
| FRITZ!WLAN Repeater DVB-C | 6.20 - 6.92 | /var/flash | 250/95 |
| FRITZ!Powerline 540E | 6.92 | /var/flash | 250/95 |
| FRITZ!Powerline 546E | 5.50 | /var/flash | 250/95 |
| Multibox 7270 NGN | 5.05 | /var/flash | 240/95 |
| FRITZ!Box Fon WLAN 7360 EWE | 5.09 - 5.51 | /var/flash | 240/95, 242/95 |
| 52 models use this config file | |||
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.
