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.

0
U

Property:panic2 (procfs)

From BoxMatrix


BoxMatrix >> System >> panic2 (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

Info
  
Name-Collision - multiple objects in this wiki use the name panic2!
panic2 (procfs) Kernel crash logs for supportdata and crashreport mail (second Linux).
panic2 (temp) log_server Inter-CPU log from Scorpion panic (x490).

Procfs-Object

Goto:   Dependencies   -   Model-Matrix   -   Help Supportdata2   -   SMW-Browser

Details

panic2 is part of the second solution of Kernel crash logs in procfs. It is the panic (procfs) for the second Linux.
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:

Crash Logs: - user mode crashes

Panic Logs: - kernel crashes

User Logs: - user stuff

Module Logs: - kernel modules

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.

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!

SMW-Browser

Information is currently being retrieved from the backend.