It seems to me that the reboots could likely be cause by the person's personal phone and not the kernel itself. Perhaps the gremlins are on the prowl?
[KERNEL] (BETA) bhundven's SMS KJ6 v0.2.0 [Apr 11]
- Thread starter FBis251
- Start date
-
- Tags
- development
- Status
I just noticed on miui at least, I got a soft reboot and I checked in status and it says its been on for 54 hrs 0_o anyone else getting soft reboots on miui?
if you ain't first you're last
if you ain't first you're last
I haven't that's why I'm asking if anyone else is having them, if they are not then it could be a bad flash.
if you ain't first you're last
Once or twice. Just saw google cogs spinning than right back to homescreen. Didn't affect my up time either.
Can't help you without these files and the files in these directories.
/proc/last_kmsg
/data/tombstones/
/data/system/dropbox/
I don't know about "random reboots," but my wife's phone will sometimes be completely unresponsive, and I have to either pull the battery or hold the power button for ten seconds to reboot it... Anyone else have this occur?
Best regards,
M.A.
Best regards,
M.A.
Have you tried any other kernels yet? Flash another kernel and make sure that it IS indeed the kernel causing the problem.
I'm currently trying the old beta 02d, but if that doesn't work... What other kennels are there? I'm sure where to get a rooted stock kernel outside of flashing an entire ROM, which wouldn't make for the most valid apples-to-apples test...
I think I may have found what could be the cause of the random reboots. I was out of town for a week and my phone did not reboot a single time. Upon my return the phone went back to it's pattern of rebooting every few hours while sitting on my desk. Here's my findings. The phone works fine when it is in 4G, 3G or E service area. But when it's in a service area that has only 1G service the phone acts up. So perhaps it could be the way the modem is handling the different service type reacting weird with the kernel. I also have found wi-fi calling does not remedy this.
I've had it reboot when I'm at work in a 4G area. I will admit I didn't see what service it was reporting at the time, though. I'll try and keep an eye on it. What modem are you using? I'm on KJ6.
Mine silently rebooted today on the way to work. I think it's first time with this kernel.
Nothing interesting in the logs. logcat is overwritten after reboot. last_kmsg doesn't have anything suspicious that would cause a reboot, it ends with line "No Errors Detected". Last tombstone is dated a week ago. So - nothing to work with.
What is interesting that on the way to work I had mobile data disabled, which I normally don't do.
Probably not related to the crash, but last_kmesg has a lot of lines saying that wm8994 doesn't power down, like this:
[170980.858246] [ wm8994_samsung.c (wm8994_resume,3925) ] ------WM8994 Revision = [3]-------
[170982.107538] Freezing of user space aborted
[170986.866932] binder: release proc 22175, transaction 2084119, not freed
[170989.907401] [ wm8994_samsung.c (wm8994_resume,3925) ] ------WM8994 Revision = [3]-------
[170991.587031] [ wm8994_samsung.c (wm8994_resume,3925) ] ------WM8994 Revision = [3]-------
[170992.450684] pm_noirq_op(): platform_pm_suspend_noirq+0x0/0x40 returns -11
[170992.455623] PM: Device power.0 failed to suspend late: error -11
[170992.464376] PM: Some devices failed to power down
[170992.716984] [ wm8994_samsung.c (wm8994_resume,3925) ] ------WM8994 Revision = [3]-------
[170993.916744] [ wm8994_samsung.c (wm8994_resume,3925) ] ------WM8994 Revision = [3]-------
[171012.094788] binder: release proc 22257, transaction 2087245, not freed
[171024.900397] binder: release proc 22329, transaction 2088212, not freed
[171264.134776] binder: release proc 22589, transaction 2103042, not freed
[171563.962075] binder: release proc 22851, transaction 2118855, not freed
[171621.119278] Freezing of user space aborted
[171622.145995] [ wm8994_samsung.c (wm8994_resume,3925) ] ------WM8994 Revision = [3]
...and this goes on for a quite a while. Not sure if it's of any importance.
Nothing interesting in the logs. logcat is overwritten after reboot. last_kmsg doesn't have anything suspicious that would cause a reboot, it ends with line "No Errors Detected". Last tombstone is dated a week ago. So - nothing to work with.
What is interesting that on the way to work I had mobile data disabled, which I normally don't do.
Probably not related to the crash, but last_kmesg has a lot of lines saying that wm8994 doesn't power down, like this:
[170980.858246] [ wm8994_samsung.c (wm8994_resume,3925) ] ------WM8994 Revision = [3]-------
[170982.107538] Freezing of user space aborted
[170986.866932] binder: release proc 22175, transaction 2084119, not freed
[170989.907401] [ wm8994_samsung.c (wm8994_resume,3925) ] ------WM8994 Revision = [3]-------
[170991.587031] [ wm8994_samsung.c (wm8994_resume,3925) ] ------WM8994 Revision = [3]-------
[170992.450684] pm_noirq_op(): platform_pm_suspend_noirq+0x0/0x40 returns -11
[170992.455623] PM: Device power.0 failed to suspend late: error -11
[170992.464376] PM: Some devices failed to power down
[170992.716984] [ wm8994_samsung.c (wm8994_resume,3925) ] ------WM8994 Revision = [3]-------
[170993.916744] [ wm8994_samsung.c (wm8994_resume,3925) ] ------WM8994 Revision = [3]-------
[171012.094788] binder: release proc 22257, transaction 2087245, not freed
[171024.900397] binder: release proc 22329, transaction 2088212, not freed
[171264.134776] binder: release proc 22589, transaction 2103042, not freed
[171563.962075] binder: release proc 22851, transaction 2118855, not freed
[171621.119278] Freezing of user space aborted
[171622.145995] [ wm8994_samsung.c (wm8994_resume,3925) ] ------WM8994 Revision = [3]
...and this goes on for a quite a while. Not sure if it's of any importance.
bhundven
Inactive Recognized Developer
here is mine:
[13628.804853] [ wm8994_samsung.c (wm8994_resume,3925) ] ------WM8994 Revision = [3]-------
[13630.118568] [ wm8994_samsung.c (wm8994_resume,3925) ] ------WM8994 Revision = [3]-------
[13631.414162] [ wm8994_samsung.c (wm8994_resume,3925) ] ------WM8994 Revision = [3]-------
[13632.224097] pm_noirq_op(): platform_pm_suspend_noirq+0x0/0x40 returns -11
[13632.229036] PM: Device power.0 failed to suspend late: error -11
[13632.237789] PM: Some devices failed to power down
[13632.721267] [ wm8994_samsung.c (wm8994_resume,3925) ] ------WM8994 Revision = [3]-------
No errors detected
Entire log attached
[13628.804853] [ wm8994_samsung.c (wm8994_resume,3925) ] ------WM8994 Revision = [3]-------
[13630.118568] [ wm8994_samsung.c (wm8994_resume,3925) ] ------WM8994 Revision = [3]-------
[13631.414162] [ wm8994_samsung.c (wm8994_resume,3925) ] ------WM8994 Revision = [3]-------
[13632.224097] pm_noirq_op(): platform_pm_suspend_noirq+0x0/0x40 returns -11
[13632.229036] PM: Device power.0 failed to suspend late: error -11
[13632.237789] PM: Some devices failed to power down
[13632.721267] [ wm8994_samsung.c (wm8994_resume,3925) ] ------WM8994 Revision = [3]-------
No errors detected
Entire log attached
Last edited:
bhundven
Inactive Recognized Developer
yes, that is the same thing. I don't really need any more logs.
I know where to look now I just need time to debug it.
I know where to look now I just need time to debug it.
By any chance do you guys have media/ringer volume set all the way down when it reboots. Just a crazy thought
Sent from my SGH-T959V using xda premium
Sent from my SGH-T959V using xda premium
Sound Off vibration on but volume is never down all the way.
Sent from my SGH-T959V using xda premium
- Status
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
42THIS KERNEL HAS BEEN DEPRECATED. USE BHUNDVEN'S BLASTOFF KERNEL INSTEAD.
Presents
bhundven's
Subtly Modified Stock CWM 5 KJ6 Kernel
http://xdaforums.com/showthread.php?t=1828171
NOTES
- Need help with BLN? Check here: BLN Support
- This kernel is still in beta! Please help us test for stability. Logs are always welcome
- This is still Bryan's kernel, the only changes I have made were to the initramfs and a few changes here and there to the kernel itself.
- Bryan is developing again! This thread will continue to be open to discuss the new releases here unless he decides to open his other kernel thread for XDA.
FEATURES
In addition to the changes bhundven has made:
- SuperSU instead of Superuser (adds root support using the kernel alone, regardless of which ROM you install this on)
- BLN support added (thanks to neldar and our newest Team Acid member m4xm4n) MARKET LINK
- Includes a Team Acid boot splash and recovery image (courtesy of theexel and Tablador)
- Cleaned up voodoo extensions directory to remove zipalign for TW launcher
- Forcing an ext4 conversion by default regardless of lagfix option
- Enabled cifs, fuse and tun kernel modules
NOTES
- Want to change your boot splash image? Here's a git repo that helps you do just that:
https://github.com/morfic/Samsung-logo
(Thanks to tablador who linked me to this!)
INSTRUCTIONS
- Download the kernel zip file
- Flash it using CWM
- Wipe the Dalvik Cache before you reboot! (CWM > Advanced > Wipe Dalvik Cache)
DOWNLOADS
kernel-sms-kj6-v0.2.0-bml.zip (MD5: 9cc2278d0d00c61210e1311181de0b67)
Older Versions: Sourceforge
SOURCE CODE
Android SGS4G Kernel at GitHub
Android SGS4G Initramfs at GitHub You might want to use the voodoo branch, not master!
Want to learn how to build the kernel from source? Look at these instructions:
Building From Source
CHANGELOG
Here is Bryan's OP, at the link below
http://xdaforums.com/showthread.php?t=138033115
The mmc_rescan mess is some stupid comments samsung left in.
Reading your log helped me to understand that the change that I made DID NOT fix the reboot issue, but causes it to not happen.
Think about the observer effect to understand what I'm saying. We made a change that adds some noise to stop the wakelock timeout to reboot the system, but the wakelock issue still exists.
The solution to the problem may take me longer to solve with the current source base then it would if I started to port us to the aosp samsung source.
With that... I am going to disappear for a while and concentrate on that task.
I will continue to work with teamacid to move cm7 forward, but it is obvious that the kernel source that samsung produced has too many problems.
As usual, no ETAs, askers will be punished.10February 24, 2012
v0.1.1-rc2
Now using Team Acid's changes to voodoo initramfs
Removed a lot of unneeded checks and their included files since we're only dealing with the sgs4g
Added battery capacity check before voodoo lagfix
Modified the ext4 conversion process to use the bonsai defaults
Forcing an ext4 conversion by default regardless of lagfix option
Removed check for froyo anti_boot_glitch since this is a GB kernel
Enabled cifs, fuse and tun kernel modules9Hey guys! Got another update ready for you. Huge thanks to bhundven for setting up a new kernel source tree for me to work from. He even included the patches he and Max have been working on in the CM7 kernel, so this build should be more stable.
Also included is the BLN binary that got pushed out with the v0.1.1-rc3 CWM package, but now you can flash the kernel using whatever method you want. The kernel will make sure it adds BLN support to whatever GB rom you flash it to.
Apr 11, 2012
Enable SVNET_WHITELIST to fix wakelock reboot problemsCode:9cc2278d0d00c61210e1311181de0b67 kernel-sms-kj6-v0.2.0-bml.zip
Bump version to '-sms-kj6-v0.2.0-bml'
Integrated lights.s5pc110.so into the initramfs to add BLN support
-- The kernel itself now copies the file to the rom instead of doing it via CWM
The CWM zip should no longer cause your phone to reboot after the kernel flashes9FBis251,
I updated the source for gingerbread-bml, but I might have broke compatibility with fsr/rfs with tinyrcu changes and config changes.
Let me know if I did and I'll revert those changes. Otherwise the new v0.3.0-bml has the fix I put in cm7 for random reboot madness and some other wakelock fixes backported from the ics 3.0 kernel for better wakelock behavior.