[T-Mobile Samsung Galaxy Note 3] cun7:
Yes I got it.

Also, not sure what ROM you were really on, or if you didn't clear data, or what you did... but I'll tell you right now that halfway through this log I can tell that you are causing whatever issues you are having

Example, right here:

02-20 01:14:05.833 E/OCApplication(4251): cannot detect color type
02-20 01:14:05.833 E/OCApplication(4251): cannot detect vibration type!
02-20 01:14:05.833 E/OCApplication(4251): cannot detect sweep2wake type!
02-20 01:14:05.843 E/OCApplication(4251): cannot detect fastcharge type

And here...

02-20 01:14:05.993 E/OCApplication(4251): setup cpu!
02-20 01:14:05.993 E/OCApplication(4251): fix cpu permissions!

And here...

02-20 01:14:06.293 I/RootTools v2.6(4251): [rw, relatime] AND rw

So.... if you just flashed tweaked, and did a full data wipe, why is Root Tools app installed? Tweaked doesn't come with it.

02-20 01:14:07.763 E/OCApplication(4251): loaded gpu settings!
02-20 01:14:07.773 E/OCApplication(4251): setup voltage!
02-20 01:14:07.773 E/OCApplication(4251): fix voltage permissions!

There are errors all over this log... that indicate user related issues. Your reboot issue is not because of the kernel. Your logs even indicate that you didn't even pull this log from tweaked ROM after a fresh install... I'm just confused.

02-20 01:14:07.823 E/OCApplication(4251): setup iosched!
02-20 01:14:07.823 E/OCApplication(4251): fix iosched permissions!
02-20 01:14:07.853 D/WifiDirectBR(4709): WifiDirectBroadcastReceiver::onReceive() : android.net.wifi.p2p.STATE_CHANGED
02-20 01:14:07.853 E/SELinux (4740): selinux_android_seapp_context_reload: seapp_contexts file is loaded from /seapp_contexts
02-20 01:14:07.873 I/IOSchedulerFragment(4251): fix permissions...
02-20 01:14:07.873 E/OCApplication(4251): loaded ioscheduler settings!
02-20 01:14:07.873 E/OCApplication(4251): setup color!
02-20 01:14:07.873 E/OCApplication(4251): color is NULL!
02-20 01:14:07.873 E/OCApplication(4251): setup vibration!
02-20 01:14:07.873 E/OCApplication(4251): vibration is NULL!
02-20 01:14:07.873 E/OCApplication(4251): setup mdnie!
02-20 01:14:07.873 E/OCApplication(4251): fix mdnie permissions!

02-20 01:14:08.273 E/OCApplication(4251): loaded socPower settings!
02-20 01:14:08.273 E/OCApplication(4251): setup thermal!
02-20 01:14:08.273 E/OCApplication(4251): thermal is NULL!
02-20 01:14:08.273 E/OCApplication(4251): setup fastcharge!
02-20 01:14:08.273 E/OCApplication(4251): FastCharge is NULL!
02-20 01:14:08.273 E/OCApplication(4251): setup lowmemkill!
02-20 01:14:08.273 E/OCApplication(4251): fix LowMemKill permissions!
02-20 01:14:08.333 I/LowMemKillHelper(4251): fix permissions...
02-20 01:14:08.333 E/OCApplication(4251): setup misc!
02-20 01:14:08.333 E/OCApplication(4251): fix misc permissions
02-20 01:14:08.383 I/MiscHelpers(4251): fix permissions...
02-20 01:14:08.383 E/OCApplication(4251): setup governor!
02-20 01:14:08.383 E/OCApplication(4251): fix governor permissions
02-20 01:14:08.383 W/GGovHelper(4251): fixPermissions: governor name mismatch
02-20 01:14:08.383 E/OCApplication(4251): setup appcontrol!
02-20 01:14:08.383 E/OCApplication(4251): setup zcontrol!
02-20 01:14:08.383 E/OCApplication(4251): fix z-control permissions

There is also a line in there to disable the checkJNI... a popular useless build prop edit that I know dwitherell does not use...

I need you to not waste my valuable time. I don't know what your motive is here, or why you feel the need to pretend you did something when you clearly didn't, but I don't even see a reboot in the log.

You are on your own. I have yet to see one device have an issue with this kernel, and like I said, I've been on it for weeks now, so have others with zero issues... over clocked, undervolted, etc....