Scribe Help Tweaking crash.log parameters

[CaptnDanLKW]

The default crash.log doesn't capture all the events, I'm looking for ideas to enhance it but not pull in stuff it shouldn't.

Example - with the occasional asd faults, I end up with the entries below...

Ideally the 5 entries that went to the system log should go to crash.log.

I was thinking of adding a number of additional 'OR' statements to the crash configuration file, like

'translation fault'
'fatal signal 11'

these would catch more than just asd
'asd' would catch the asd specific ones...

the 2nd entry is the tricky one, I was thinking a pattern like 'pud=0000000'

Thoughts?


(In Default System Messages)
Nov 23 07:55:29 RTAC86U kernel: asd[1173]: unhandled level 3 translation fault (11) at 0x00000168, esr 0x92000007
Nov 23 07:55:29 RTAC86U kernel: [00000168] *pgd=00000000164a7003, *pud=00000000164a7003, *pmd=0000000016df2003, *pte=0000000000000000
Nov 23 07:55:29 RTAC86U kernel: CPU: 1 PID: 1173 Comm: asd Tainted: P O 4.1.27 #2
Nov 23 07:55:29 RTAC86U kernel: potentially unexpected fatal signal 11.
Nov 23 07:55:29 RTAC86U kernel: CPU: 1 PID: 1173 Comm: asd Tainted: P O 4.1.27 #2

(In crash.log)
Nov 23 07:55:29 RTAC86U kernel: pgd = ffffffc016550000
Nov 23 07:55:29 RTAC86U kernel: Hardware name: Broadcom-v8A (DT)
Nov 23 07:55:29 RTAC86U kernel: task: ffffffc019192a40 ti: ffffffc016598000 task.ti: ffffffc016598000
Nov 23 07:55:29 RTAC86U kernel: PC is at 0xf6f9816e
Nov 23 07:55:29 RTAC86U kernel: LR is at 0xf6f637fc
Nov 23 07:55:29 RTAC86U kernel: pc : [<00000000f6f9816e>] lr : [<00000000f6f637fc>] pstate: 200f0030
Nov 23 07:55:29 RTAC86U kernel: sp : 00000000ff8b4278
Nov 23 07:55:29 RTAC86U kernel: x12: 00000000ffffffff
Nov 23 07:55:29 RTAC86U kernel: x11: 00000000ff8b4774 x10: 000000000000001c
Nov 23 07:55:29 RTAC86U kernel: x9 : 00000000ffffffff x8 : 000000000000016d
Nov 23 07:55:29 RTAC86U kernel: x7 : 0000000000000000 x6 : 00000000ff8b4780
Nov 23 07:55:29 RTAC86U kernel: x5 : 0000000000000073 x4 : 0000000000000005
Nov 23 07:55:29 RTAC86U kernel: x3 : 0000000000000000 x2 : 0000000000000001
Nov 23 07:55:29 RTAC86U kernel: x1 : 0000000000000168 x0 : 000000000000016d
Nov 23 07:55:29 RTAC86U kernel: Hardware name: Broadcom-v8A (DT)
Nov 23 07:55:29 RTAC86U kernel: task: ffffffc019192a40 ti: ffffffc016598000 task.ti: ffffffc016598000
Nov 23 07:55:29 RTAC86U kernel: PC is at 0xf6f9816e
Nov 23 07:55:29 RTAC86U kernel: LR is at 0xf6f637fc
Nov 23 07:55:29 RTAC86U kernel: pc : [<00000000f6f9816e>] lr : [<00000000f6f637fc>] pstate: 200f0030
Nov 23 07:55:29 RTAC86U kernel: sp : 00000000ff8b4278
Nov 23 07:55:29 RTAC86U kernel: x12: 00000000ffffffff
Nov 23 07:55:29 RTAC86U kernel: x11: 00000000ff8b4774 x10: 000000000000001c
Nov 23 07:55:29 RTAC86U kernel: x9 : 00000000ffffffff x8 : 000000000000016d
Nov 23 07:55:29 RTAC86U kernel: x7 : 0000000000000000 x6 : 00000000ff8b4780
Nov 23 07:55:29 RTAC86U kernel: x5 : 0000000000000073 x4 : 0000000000000005
Nov 23 07:55:29 RTAC86U kernel: x3 : 0000000000000000 x2 : 0000000000000001
Nov 23 07:55:29 RTAC86U kernel: x1 : 0000000000000168 x0 : 000000000000016d