[Galaxy Note 3 Android Development] ocujos:
Had a spontaneous reboot on 1.2b2 kernel. last_kmsg.log attached. Phone would boot but after lock screen came up i t would just die.

log file was taken during one of the attempts to boot the phone. I then deleted 99fast_charge script from /etc/system/init.d directory after which phone booted ok! That script was originally copied from /res folder. I only changed AC charge level to 1800mAh and USB charge level to 1000mAh. Please note that charger was not connected during this ordeal.

I've noticed the following error:

[ 4.623411] F2FS-fs (mmcblk0p23): Can't find valid F2FS filesystem in 1th superblock

[ 4.623889] F2FS-fs (mmcblk0p23): Can't find valid F2FS filesystem in 2th superblock

[ 4.623999] F2FS-fs (mmcblk0p23): Can't find valid F2FS filesystem in 1th superblock

[ 4.624176] F2FS-fs (mmcblk0p23): Can't find valid F2FS filesystem in 2th superblock

[ 4.632516] fs_mgr: mount_with_alternatives(): Mounted /dev/block/platform/msm_sdcc.1/by-name/system on /system with fs_type=ext4 instead of f2fs

[ 4.633432] F2FS-fs (mmcblk0p26): Can't find valid F2FS filesystem in 1th superblock

[ 4.633926] F2FS-fs (mmcblk0p26): Can't find valid F2FS filesystem in 2th superblock

[ 4.634032] F2FS-fs (mmcblk0p26): Can't find valid F2FS filesystem in 1th superblock

[ 4.634211] F2FS-fs (mmcblk0p26): Can't find valid F2FS filesystem in 2th superblock

[ 5.465877] fs_mgr: Cannot set clusters for super-user: open /sys/fs/ext4/mmcblk0p26/r_blocks_count failed

[ 5.465969] fs_mgr: mount_with_alternatives(): Mounted /dev/block/platform/msm_sdcc.1/by-name/userdata on /data with fs_type=ext4 instead of f2fs

[ 5.467222] F2FS-fs (mmcblk0p24): Can't find valid F2FS filesystem in 1th superblock

[ 5.467516] F2FS-fs (mmcblk0p24): Can't find valid F2FS filesystem in 2th superblock

[ 5.467662] F2FS-fs (mmcblk0p24): Can't find valid F2FS filesystem in 1th superblock

[ 5.467804] F2FS-fs (mmcblk0p24): Can't find valid F2FS filesystem in 2th superblock

[ 5.514525] fs_mgr: mount_with_alternatives(): Mounted /dev/block/platform/msm_sdcc.1/by-name/cache on /cache with fs_type=ext4 instead of f2fs

It appears that kernel is looking for F2FS file system instead of ext4 by default. Shouldn't that be the other way around?

edit: I the following kernel settings applied via Kernel Auduitor:

Apply on boot

1. cpu: #{"path":"\/sys\/devices\/system\/cpu\/cpu%d\/cpufreq\/scaling_min_freq","value":"300000","min":0,"max":3}

2. battery: echo '1' > /sys/kernel/fast_charge/force_fast_charge

3. io: echo '1' > /sys/block/mmcblk0/queue/iostats

4. io: echo '1' > /sys/block/mmcblk1/queue/iostats

5. io: echo '2048' > /sys/block/mmcblk1/queue/read_ahead_kb

6. entropy: echo '4096' > /proc/sys/kernel/random/read_wakeup_threshold

7. entropy: echo '4096' > /proc/sys/kernel/random/write_wakeup_threshold

8. cpu: #{"path":"\/sys\/devices\/system\/cpu\/cpu%d\/cpufreq\/scaling_governor","value":"conservative","min":0,"max":3}

9. cpu: #{"path":"\/sys\/devices\/system\/cpu\/cpu%d\/cpufreq\/scaling_max_freq","value":"2035200","min":0,"max":3}

10. thermal: echo 'Y' > /sys/module/msm_thermal/parameters/enabled

11. cpu: echo '100' > /sys/module/cpu_boost/parameters/boost_ms