How is Crashlog.log supposed to work?

CaptnDanLKW

Senior Member
I have only an occasional (dare I say rare) crash but when I do, I can never find /jffs/crashlog.log - as I would expect to find.

I see this...
May 5 01:05:06 kernel: [JFFS2 DBG] (1) jffs2_sum_write_data: Not enough space for summary, padsize = -427
May 5 01:05:06 kernel: proc_dostring_crashlogsave: crash log filename is /jffs/crashlog.log
May 5 01:05:06 kernel: crashFileSet: log signature invalid !


Then, later in the log I also see this:
May 5 01:05:06 kernel: proc_dostring_crashlogsave: crash log filename is /jffs/crashlog.log
May 5 01:05:06 kernel: crashLogErase: write 1 blocks data_offset 131072

It seems like the crash detection process creates it (does it)? Does anyone know what invalid signature means?

What seems clear is the delete - it happens before anyone can get to it, hence the confusion.

So how is it supposed to work?
 
Last edited:

Similar threads

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top