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 (tffs)
| BoxMatrix >> Configuration >> panic (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 panic!
|
TFFS-Configfile
| Configfile: | panic (tffs) - type | Wiki | Freetz | IPPF | whmf | AVM | Web |
| Location: | Configuration >> TFFS-Configuration - Origin: AVM | ||||||
| Path: | /var/flash | ||||||
| Properties: | Firmware: 4.67 - 7.12 | ||||||
| Function: | Persistent Kernel crash log / final dump. | ||||||
Goto: Dependencies - Model-Matrix - Missing Supportdata - SMW-Browser
Details
panic is the oldest solution of a kernel crash log, and the persistent storage of all later solutions.
In fact it is not really a log but a dump. This is also accessed as /dev/tffs_panic.
panic 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 panic (temp) for a workaround to append to a character device in TFFS.
In older firmware (ie 7272 fw 6.83) panic in TFFS is only accessed by libmailbuilder.so to compile the crashreport.
supportdata already accesses the first generation procfs interface avm_panic_sd.
In recent firmware AVM implemented a procfs interface for crash handling which is directly maintained by tffs.ko.
See the panic (procfs) and panic (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-18 06:30 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 |
|---|---|---|---|---|---|---|
| 0 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-18 06:30 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 v3 | 5.54 | /var/flash | 249/96 |
| FRITZ!Box WLAN 3370 | 6.54 | /var/flash | 244/96 |
| FRITZ!Box 3390 | 6.20 | /var/flash | 243/96 |
| FRITZ!Box Fon 5140 | 4.67 | /var/flash | 240/96 |
| FRITZ!Box 6320 Cable v2 | 5.28 - 5.51 | /var/flash | 249/96 |
| FRITZ!Box 6340 Cable | 5.24 | /var/flash | 249/96 |
| FRITZ!Box 6360 Cable | 6.04 | /var/flash | 249/96 |
| FRITZ!Box 6840 LTE | 6.04 | /var/flash | 243/96 |
| FRITZ!Box Fon WLAN 7112 | 4.88 | /var/flash | 240/96 |
| FRITZ!Fon 7150 | 4.71 | /var/flash | 240/96 |
| FRITZ!Box Fon WLAN 7270 v1 | 4.89 | /var/flash | 240/96 |
| FRITZ!Box Fon WLAN 7270 v3 | 6.06 | /var/flash | 249/96 |
| FRITZ!Box 7272 | 6.03 - 6.84 | /var/flash | 244/96 |
| FRITZ!Box Fon WLAN 7320 | 5.51 | /var/flash | 243/96 |
| FRITZ!Box 7330 | 5.20 | /var/flash | 240/96 |
| FRITZ!Box Fon WLAN 7340 | 5.51 | /var/flash | 250/96 |
| FRITZ!Box Fon WLAN 7360 v2 | 5.22 | /var/flash | 240/96 |
| FRITZ!Box 7362 SL | 6.83 - 7.12 | /var/flash | 243/96 |
| FRITZ!Box Fon WLAN 7390 | 5.50 | /var/flash | 250/96 |
| FRITZ!Box 7490 | 6.05 | /var/flash | 243/96 |
| FRITZ!Box 7490 (main) | 6.30 | /var/flash | 243/96 |
| FRITZ!Box 7490 (scrpn) | 7.01 | /var/flash | 243/96 |
| FRITZ!WLAN Repeater 310 A | 5.24 | /var/flash | 240/96 |
| FRITZ!Powerline 546E | 5.50 | /var/flash | 250/96 |
| FRITZ!Box Fon WLAN 7360 EWE | 5.09 - 5.50 | /var/flash | 240/96, 242/96 |
| 25 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.
