Today I had Kernel Crash. After it it rejected trying to power up. Wise by previous experience I removed the battery (and put in after 30 seconds) at it booted properly at first time after reset. After booting it showed info about kernel crash (blah blah not properly blah blah custom settings reseted) and message looking like "batterry almost empty". So I checked it by bnf and it was at 33% (nokian batterry meter showed small red stripe) and restored my custom settings ("kernel-config load MAJC89" and "kernel-config default" from root console). Then I restored my date and time over internet by some "ntpd -s". Used it a much for 30 minutes without a problem and it shutdowned itself again (but now because of real batterry discharge). I'm now recharging and boot was clean (booted properly at first time, no settings-reset message, and guess what - it didn't bugged boot up, despite charger beeing present and connected - no wallcharger bug this time at first boot trial). I'll check if any charging bug will occur or if my N900 piece is cured for at least a day (all the kernel-power power-maintenance bugs seems to have some trigger without which, they don't seem to occur at all).

PS: I noticed that during my kernel crash I had mediabox (which is audio/video player) running and playing and headphones on my head. It were playing with stutterring for 3 seconds after screen went off. It may be related because mediabox during switching tracks with shuffle (which lasts between 50ms to 750ms) seems to be on 100% processor which triggers my overclocking settings temporary for the fragment of second to 900 mhz (and after it returns safely to 500 mhz which is my minimum in my kernel-config profile - I checked it with freq-watch.sh which i noted from the quote when I wanted to know why "kernel-config show" show the 900mhz and then it was obvious that kernel-power-config fails to measure the current frequency because it use too much processor resources, so I found the script very helpful for the task that "kernel-config show" fails to do). I remind that I previously late time ago (when latest VDD2 patch came in) I tested it can stand 900mhz for 15 minutes without single problem, so kp51 was partially the reason (either my kernel-config profile is valid or beacame invalid after update to kp51 and my profile didn't changed since then).