Related
Github:
I now consider this Release Candidate quality. Please do report issues (with logcats and dmesgs). Check the known bugs, etc, etc.
https://github.com/s0be/cm-kernel
the -amonra zip is for recoveries that don't take the FS type as the first argument of mount(...) If the regular zip fails complaining about missing files, try the -amonra version.
Latest official version:
no debug
http://heroc.s0be.com/HERC-2.6.35-AP-5.zip
http://heroc.s0be.com/HERC-2.6.35-AP-5-amonra.zip
Headset detection less broken. Now it always thinks there's a mic connected to anything plugged in.
http://heroc.s0be.com/HERC-2.6.35-AP-4.zip
http://heroc.s0be.com/HERC-2.6.35-AP-4-amonra.zip
If that download doesn't work for you, your OS likely has a broken ipv6 stack. Please check that you have ipv6 disabled if you don't actually have an ipv6 connection.
What works:
Ram console
Keypad
Screen
Touchscreen
GPS
Compass
G-Sensor
nand
Early Suspend
Bluetooth
Headset Detection
Camera
What Doesn't work or hasn't been tested:
Thanks to:
Elemag for the initial Hero 2.6.35 port, with Erasmux as a major contributor, Decadence for the 2.6.34/35 heroc board files, and riemervdzee for his pointers at fixes needed to get it working and his continued drive to get this kernel full featured and stable, and everyone they pulled from (Darch, Toast, Cyanogen, etc, etc). If I've forgotten anyone, please let me know the names to add.
See first post for current. This is just historic releases.
Headset detection fixed. Mic detection not working yet.
Weird audio program related crashes fixed
http://heroc.s0be.com/HERC-2.6.35-AP-3.zip
http://heroc.s0be.com/HERC-2.6.35-AP-3-amonra.zip
Rebased on Pershoot's G1 2.6.35.11 Kernel Tree
New base .config
BFS Disabled
Headset detection re-broken. Will be reviewing this currently.
http://heroc.s0be.com/HERC-2.6.35-AP-2.zip
http://heroc.s0be.com/HERC-2.6.35-AP-2-amonra.zip
Camera fix from JayBob via decad3nce
http://heroc.s0be.com/HERC-2.6.35-AP-1.zip
http://heroc.s0be.com/HERC-2.6.35-AP-1-amonra.zip
Pulls some changes from Decad3nce for the camera (still doesn't work) and some i2c speedups from riemervdzee
http://heroc.s0be.com/HERC-2.6.35-sl0ppy_s0be-114.zip
http://heroc.s0be.com/HERC-2.6.35-sl0ppy_s0be-114-amonra.zip
Fixes most of what I broke in 106
http://heroc.s0be.com/HERC-2.6.35-sl0ppy_s0be-109.zip
http://heroc.s0be.com/HERC-2.6.35-sl0ppy_s0be-109-amonra.zip
Disabled some ****
Changed some ****
This is an attempt to fix the power issues through voodoo
http://heroc.s0be.com/HERC-2.6.35-sl0ppy_s0be-106.zip
http://heroc.s0be.com/HERC-2.6.35-sl0ppy_s0be-106-amonra.zip
Fixed headset detection. Haven't figured out if the button works.
http://heroc.s0be.com/HERC-2.6.35-sl0ppy_s0be-101.zip
http://heroc.s0be.com/HERC-2.6.35-sl0ppy_s0be-101-amonra.zip
Went back to #55(never released) config
Disabled Debug
All updates from #56 still apply
http://heroc.s0be.com/HERC-2.6.35-sl0ppy_s0be-57.zip
http://heroc.s0be.com/HERC-2.6.35-sl0ppy_s0be-57-amonra.zip
Merged with upstream
Updated msm-camera
Updated msm-i2c
Ripped out a bunch of stuff, disabled debugging
This probably isn't going to be completely happy
This is definitely not happy...
http://heroc.s0be.com/HERC-2.6.35-sl0ppy_s0be-56.zip
http://heroc.s0be.com/HERC-2.6.35-sl0ppy_s0be-56-amonra.zip
Restored device mapper with crypt support. This may fix missing app issues
http://heroc.s0be.com/HERC-2.6.35-sl0ppy_s0be-47.zip
http://heroc.s0be.com/HERC-2.6.35-sl0ppy_s0be-47-amonra.zip
tun.ko Enabled - NOT TESTED AT ALL, PLEASE REPORT IF I GOT IT RIGHT
http://heroc.s0be.com/HERC-2.6.35-sl0ppy_s0be-45.zip
http://heroc.s0be.com/HERC-2.6.35-sl0ppy_s0be-45-amonra.zip
Enabled > 6912000 CPU speeds. Boots capped at 691 though
http://heroc.s0be.com/HERC-2.6.35-sl0ppy_s0be-44.zip
Fix ramzswap/compcache
http://heroc.s0be.com/HERC-2.6.35-sl0ppy_s0be-42-2.zip
h2w still broken
Camera almost works
Bluetooth is fixed
Touchscreen may not be problematic now.
http://heroc.s0be.com/HERC-2.6.35-sl0ppy_s0be-42.zip
Merged MDP changes from upstream
Fixed h2w (I think) someone with a headset, try plugging it
Camera almost works on occasion. Can catch a preview frame now and then.
http://heroc.s0be.com/HERC-2.6.35-sl0ppy_s0be-30.zip
Re-enabled netfilter modules
http://heroc.s0be.com/HERC-2.6.35-sl0ppy_s0be-23.zip
changed the early_suspend.level value of the synaptics_i2c_rmi driver to match 2.6.29.
Last attempt til next week
still capped at 691200
http://heroc.s0be.com/HERC-2.6.35-sl0ppy_s0be-18.zip
Clamped to 691200 max freq
http://heroc.s0be.com/HERC-2.6.35-sl0ppy_s0be-17.zip
Maybe solved TS issues??? Testing now.
Fixed USB Mass Storage
Enabled PerfLock
CURRENT MAX IS AT 768000, throwing together a #14 with a 691200 cap.
http://heroc.s0be.com/HERC-2.6.35-sl0ppy_s0be-13.zip
First alpha
http://heroc.s0be.com/HERC-2.6.35-sl0ppy_s0be-5.zip
what kind of performance increase will this bring? and will it be nice to have when we get a fully working GB rom?
Unfortunally the current .35 build for the Hero GSM version is slower than any .29 kernel.
But yeah, seems we have to reimplement a lot of optimalisations.
It is nice that we actually get something out of the HeroC though
riemervdzee said:
Unfortunally the current .35 build for the Hero GSM version is slower than any .29 kernel.
But yeah, seems we have to reimplement a lot of optimalisations.
It is nice that we actually get something out of the HeroC though
Click to expand...
Click to collapse
There are other advantages of course, we have to remember. Performance is king, but features are definitely queen. Getting to a recent kernel (2.6.29 is coming up on 2 years old), makes future updates to Heroc a lot easier. Going to up-to-date drivers may allow us to eliminate some of the binary cruft from the Heroc tree, etc, etc.
Two things I've tried:
1. In the xda "hero" dev forum, there was a post that there was a problem with the newer (>.34) yaffs2 code, and you needed to boot and wipe using a 1.7 RA recovery. So, I copied the yaffs2 code from deca's .29 kernel. It then oopsed at 1017 in msm_fb, which was the ifdef'd line for HERO.
2. So, I added "&& !defined(CONFIG_MACH_HEROC)" to line 1016. It then still rebooted, but last_kmsg was different after "vsync on gpio 97 now 0":
[ 3.626831] vsync on gpio 97 now 0
[ 3.632263] msmfb_probe() installing 320 x 480 panel
[ 3.640106] Registered led device: lcd-backlight
[ 3.650085] msm_serial: driver initialized
[ 3.654052] msm_serial_hs module loaded
[ 3.697570] loop: module loaded
[ 3.698760] pmem: 1 init
[ 3.702514] pmem_adsp: 0 init
[ 3.706420] pmem_camera: 0 init
[ 3.711578] Android kernel panic handler initialized (bind=kpanic)
[ 3.712524] AKM8973 compass driver: init
[ 3.718566] input: compass as /devices/virtual/input/input0
[ 3.731079] msm_nand: allocated dma buffer at ffa0a000, dma_addr 256fb000
[ 3.732696] msm_nand: read CFG0 = aa5400c0 CFG1 = 8744a
[ 3.733245] msm_nand: CFG0 cw/page=3 ud_sz=512 ecc_sz=10 spare_sz=4
[ 3.734069] msm_nand: NAND_READ_ID = 5501bcec
[ 3.735229] msn_nand: nandid 5501bcec status c03120
[ 3.735595] msm_nand: manuf Samsung (0xec) device 0xbc blocksz 20000 pagesz 800 size 20000000
[ 3.736114] msm_nand: save CFG0 = e85408c0 CFG1 = 4745e
[ 3.736419] msm_nand: CFG0: cw/page=3 ud_sz=516 ecc_sz=10 spare_sz=0 num_addr_cycles=5
[ 3.737121] msm_nand: DEV_CMD1: f00f3000
[ 3.737609] msm_nand: NAND_EBI2_ECC_BUF_CFG: 1ff
[ 3.738372] 6 cmdlinepart partitions found on MTD device msm_nand
[ 3.738708] Creating 6 MTD partitions on "msm_nand":
[ 3.739257] 0x00001ff60000-0x000020000000 : "misc"
[ 3.753509] 0x000002c60000-0x000003160000 : "recovery"
[ 3.776397] 0x000003160000-0x0000033e0000 : "boot"
[ 3.794219] 0x0000033e0000-0x000009be0000 : "system"
[ 4.070312] 0x000009be0000-0x000009fe0000 : "cache"
[ 4.098876] 0x000009fe0000-0x000020000000 : "userdata"
No errors detected
Don't know if this helps or not. BTW, I'm using Firerats's custom MTD partitions, so I modified the boot parameters.
dbayub said:
Two things I've tried:
1. In the xda "hero" dev forum, there was a post that there was a problem with the newer (>.34) yaffs2 code, and you needed to boot and wipe using a 1.7 RA recovery. So, I copied the yaffs2 code from deca's .29 kernel. It then oopsed at 1017 in msm_fb, which was the ifdef'd line for HERO.
2. So, I added "&& !defined(CONFIG_MACH_HEROC)" to line 1016. It then still rebooted, but last_kmsg was different after "vsync on gpio 97 now 0":
<SNIP>
Don't know if this helps or not. BTW, I'm using Firerats's custom MTD partitions, so I modified the boot parameters.
Click to expand...
Click to collapse
yeah, I had that fixed in my tree, forgot to commit the || -> && change I didn't do that yaffs2 change, but I just tested it with identical results.
Sweet. I'll spend more time on it this weekend. Swamped with homework atm.
Hopefully we'll have something super stable!
Decad3nce said:
Sweet. I'll spend more time on it this weekend. Swamped with homework atm.
Hopefully we'll have something super stable!
Click to expand...
Click to collapse
Made some more progress:
http://android.pastebin.com/AWysQDNk
s0be, i think you're going to blow up the hero scene again. with deca and you working together there's been a lot of progress recently and i want to thank both of you. i really love my hero and you guys keep it feeling young.
AND HOW!!!!!
Sent from my HERO200 using XDA App
jmkarnai01 said:
AND HOW!!!!!
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
More commits
More Progress
http://android.pastebin.com/rqm0Vn1p
You guys are pure AWESOME!
S0be, i was wondering your opinion, once this kernel is completed and we get GB running smoothly, will the supposed 2.4 GB update break everything that is already working or just maybe the new stuff will have to be worked in properly?
Pocker09 said:
S0be, i was wondering your opinion, once this kernel is completed and we get GB running smoothly, will the supposed 2.4 GB update break everything that is already working or just maybe the new stuff will have to be worked in properly?
Click to expand...
Click to collapse
no clue
http://android.pastebin.com/SSRM5MKB
Dang sobe making progress good work man. Thanks!!!!!!!!!!!"!
Sent from my HTC Hero CDMA using XDA App
oostah said:
Dang sobe making progress good work man. Thanks!!!!!!!!!!!"!
Sent from my HTC Hero CDMA using XDA App
Click to expand...
Click to collapse
http://android.pastebin.com/qKr6wEtY
Some more progress, looks like just the smd and i2c errors are left to fix
Looking forward to this. And wow you work like super man lol but thank for the time and hard work.
Root-Hack-Mod-Always™
Just curious, will you guys be running AOSP's GB or will this kernel allow for a less tweaked version of GB? Thanks! Great Job!
The smd stuff is because it used to call both v1 and v2 alloc, and as long as one succeeded, it was OK. Now it's ifdef'd to use different code depending on if CONFIG_MSM_SMD_PKG3 is set or not. Looks like the package 4 code is what works on heroc. With that change, the smd code works.
[ 3.684967] smd_alloc_channel() cid=01 size=08192 'SMD_DIAG'
[ 3.686340] smd_alloc_channel() cid=02 size=08192 'SMD_RPCCALL'
etc. Then it's the i2c failures:
[ 3.841674] msm_i2c msm_i2c.0: Error during data xfer 1e (-5)
[ 3.852203] msm_i2c msm_i2c.0: error, status 63c8
and oops:
[ 4.861785] Internal error: Oops: 80000005 [#1] PREEMPT
[ 4.863433] last sysfs file:
[ 4.864318] Modules linked in:
[ 4.866058] CPU: 0 Not tainted (2.6.35.10-cyanogenmod #11)
[ 4.867706] PC is at 0x0
[ 4.868682] LR is at microp_i2c_probe+0xb70/0x1438
[ 4.869598] pc : [<00000000>] lr : [<c0217e64>] psr: 60000013
[ 4.869659] sp : cc219e10 ip : cc219d10 fp : cc219e74
[ 4.872100] r10: c040eef4 r9 : 00000000 r8 : 00000005
[ 4.873748] r7 : cc255da0 r6 : c040ea10 r5 : cc255d80 r4 : cc48a760
[ 4.874694] r3 : c040ea2c r2 : 00000002 r1 : cc219ce0 r0 : cc219e3c
[ 4.876342] Flags: nZCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment kernel
My Desire S broke a few days ago. At first, it didn't boot - it vibrates seven times on the HTC logo, and stops there. Nothing works at that point, not even holding power and volume buttons to reset. As far as I can tell, there's nothing to do except pull the battery, which I know is a bad idea... but there's no other choice.
Other times, it ends up on the Android boot animation, and stays there forever.
Other times, it actually boots up, usually with the date set to Jan 6th 1980. When it does, it's partially usable - browsing, playing music, playing games all mostly works.
It ran stability test for 1.5 hours without "errors", but a ton of background apps crashed during that run (especially the keyboard, which of course wasn't actually used at all). Max temp ~37 C.
Now, here comes the weird stuff... No changes are saved between reboots, none at all. I get absolutely no errors about write protection, write errors etc. - but if I change a text file, complete a level in a game (that always saves automatically), etc. - and reboot - I'm back where I was.
On every boot, the GPS is on, and it asks about allowing Google location tracking. Every time.
However, that's not even the most bizarre thing... I figured I would try a full wipe and new ROM, just in case it actually IS a software problem/FS corruption (which I've doubted all along, but still). So, I backed it up with nandroid - first backup failed... Weird. I tried again after a reboot, and it worked.
I then wiped /data and /cache manually - no errors, installed the ROM which wiped /system as well - no errors here, either!
I boot it up... and I'm STILL BACK ON THE OLD ROM! What the hell?!?! Everything is EXACTLY as it was before, with the GPS question, the icons, my notes, my game progress... Not ONE difference, despite an apparently successful wipe. I kid you not.
Now, obviously, the wipe failed on some level, but why would it report success when it clearly didn't actually write the changes to flash?!
S-OFF via Revolutionary. HBOOT-6.98.1002, RADIO-38.03.02.11_M - both of which I've flashed exactly once, when rooting, back when I got the phone.
CWM Touch 5.8.1.5 - I've had that since at least 2-3 months, no problems.
Any ideas? I'm out of warranty (second-hand phone), and I assume I'll need to buy a replacement... Even then, I'd prefer an explanation of what the heck is going on here!
Edit: Yep... I opened a shell (via adb), created a file in /data, sync'ed and rebooted. It's gone.
BTW, I get "permission denied" to even ls in /data when I'm not root... Is that normal? I expect the answer is no...?
RUU is the best solution for me.
Sent from my HTC Desire S using xda app-developers app
Your description of the problem sounds like a broken chip. Well I can't be 100% sure but the same problems occur when a hard drive is failing. Maybe /proc/last_kmsg can report these kind of errors.
Sent from my Desire S using xda app-developers app
[ 6.944305] EXT4-fs (mmcblk0p27): warning: mounting fs with errors, running e2fsck is recommended
[ 6.950500] EXT4-fs (mmcblk0p27): recovery complete
Hmm, I wonder if that's a one-off. How do you even fsck the internal partitions? I'd have no problems doing that on a computer, but...
Also, there's this (repeated a few times):
[ 605.030731] INFO: task krmt_storagecln:467 blocked for more than 120 seconds.
[ 605.031433] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 605.032135] krmt_storagecln D c0444614 0 467 2 0x00000000
[ 605.033203] Backtrace:
[ 605.033966] [<c0444218>] (schedule+0x0/0x490) from [<c0040e50>] (rpc_clients_cb_thread+0x98/0x1b0)
[ 605.034729] [<c0040db8>] (rpc_clients_cb_thread+0x0/0x1b0) from [<c00a2bf0>] (kthread+0x84/0x8c)
[ 605.035461] [<c00a2b6c>] (kthread+0x0/0x8c) from [<c008f4e4>] (do_exit+0x0/0x69c)
[ 605.036193] r7:00000013 r6:c008f4e4 r5:c00a2b6c r4:e5c27df0
[ 605.037963] INFO: task voice:750 blocked for more than 120 seconds.
[ 605.038665] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 605.039062] voice D c0444614 0 750 2 0x00000000
[ 605.040527] Backtrace:
[ 605.041259] [<c0444218>] (schedule+0x0/0x490) from [<c0444d60>] (schedule_timeout+0x24/0x23c)
[ 605.041992] [<c0444d3c>] (schedule_timeout+0x0/0x23c) from [<c0444b70>] (wait_for_common+0x11c/0x1dc)
[ 605.042694] r7:e4920000 r6:00000002 r5:c061a6f0 r4:7fffffff
[ 605.044464] [<c0444a54>] (wait_for_common+0x0/0x1dc) from [<c0444d10>] (wait_for_completion+0x1c/0x20)
[ 605.045196] [<c0444cf4>] (wait_for_completion+0x0/0x20) from [<c0051118>] (voice_thread+0x6c/0x574)
[ 605.045928] [<c00510ac>] (voice_thread+0x0/0x574) from [<c00a2bf0>] (kthread+0x84/0x8c)
[ 605.046661] [<c00a2b6c>] (kthread+0x0/0x8c) from [<c008f4e4>] (do_exit+0x0/0x69c)
[ 605.047058] r7:00000013 r6:c008f4e4 r5:c00a2b6c r4:e5c27f28
Click to expand...
Click to collapse
Not good...
... I ran fsck, and it didn't look good. Tons of errors on /system, even though I ran it multiple times. (e2fsck -fyv)
Something's pretty effed up.
Doesn't seem encouraging ! I'm not a kernel hacker so I can't provide much help for the messages. I would not recommend formatting either as if you have a chip hardware problem you will end up with a bricked phone.
Sent from my Desire S using xda app-developers app
This probably belongs in Dev forum, but can't post there yet - How do I get MY custom kernel to "stick"?
I have a new kernel compiled for TF300T and repackaged it into a new boot.img - I am banging my head against the wall to get it reflashed.
fastboot does not work (per other users - it says it writes, but on reboot if reverts to orig and "fastboot boot <new boot img>" also fails):
fastboot flash boot newbootTF300.img
sending 'boot' (5196 KB)...
OKAY [ 1.699s]
writing 'boot'...
OKAY [ 2.174s]
tried - building a CWM update.zip - says it updates, but on reboot - back to other kernel.
even tried directly dding to boot partition when in CWM but - yet again - boots back to previous kernel:
~ # dd if=/data/media/newbootTF300.img of=/dev/block/mmcblk0p4
10392+0 records in
10392+0 records out
5320704 bytes (5.1MB) copied, 2.677940 seconds, 1.9MB/s
Perhaps my answer in the below thread can be helpful ?
http://forum.xda-developers.com/showthread.php?t=1931202
Original thread by hashcode for RAZR http://forum.xda-developers.com/showthread.php?t=2181971
Here is a copy paste.
Hashcode said:
** WARNING: THIS THREAD SHOULD BE FOR KERNEL DEVELOPERS OR ROM DEVS.
Users please post questions in your ROM's support threads. **
** DEVS: If you choose to use a kexec kernel in your ROM add a "KERNEL CREDIT" for the first 4 people in the "WHO HAS WORKED ON THIS?" section below. This has been spectacular development and credit is due. **
TESTING ROMS FOR KEXEC KERNEL PROGRESS:
Droid RAZR:
[2013-03-12] cm-10.1 on v3.0.8 JB kernel:link removed for safety
GSM RAZR:
cm-10.1 on v3.0.8: link removed for safety
MAPPHONE 3.0.x KEXEC KERNEL:
For use on Motorola devices; Droid RAZR, GSM RAZR, RAZR MAXX, Bionic and Droid 4. (1 GB OMAP4 devices for now, 512MB support coming).
WHAT IS A KERNEL?
Also from Wikipedia: http://en.wikipedia.org/wiki/Kernel_%28computing%29
Summary: If you had to choose 1 binary file which connects the hardware components of your device to the OS layer whether it be Android or some other software, it would be the kernel.
WHAT IS KEXEC?
The best description is found here on Wikipedia: http://en.wikipedia.org/wiki/Kexec
Summary: kexec is a process for hot reloading a new kernel while a device is running.
WHERE DID THIS KERNEL COME FROM?
Initially the source came from Motorola. All GPL components of Android are posted on Sourceforge.net for Motorola devices:
http://sourceforge.net/motorola/
After that it's been worked on (see below) to support kexec function and work for our needs.
WHO HAS WORKED ON THIS?
Several people played a large role in making this happen:
Kholk & [MBM]: Initial development work done on the RAZR/Bionic under Gingerbread to setup kexec modules + booting kexec kernel (no 2nd cpu)
jonpry: Ported and improved Kholk/MBM's work for use on the Droid 3. Brought up 2nd CPU, fixes for audio and more.
Hashcode (myself): On going development of this kernel for flawless function on our devices.
A full kernel source history on github starting with omapzoom sources and migrating Motorola source in commit by commit
Fixes for clocks, local timers, GPMC setup, race conditions in irq's due to kexec and more.
On going development towards full support for current Android / Ubuntu Phone OS requirements (including 512MB and Droid 3 support).
Other's have also contributed code (and hopefully more will as well): kfazz(D4), jarveson(D3) and more.
WHERE IS THE SOURCE?
KERNEL SOURCES (ALL DEVICES):
https://github.com/STS-Dev-Team/kernel_mapphone_kexec
BRANCH: stock-ics-kexec
DESCRIPTION: This is a perfect copy of the ICS kernel running as kexec. For use with stock-based ROM's etc.
STATUS: Ready for use
BRANCH: jb-mr1
DESCRIPTION: Ongoing kernel branch for support of newer Android OS (Jellybean MR1 currently).
STATUS: Work-in-progress. Heavy development
KEXEC KERNEL-MODULE SOURCES FOR ICS/JB BASED DEVICES:
https://github.com/STS-Dev-Team/kernel_kexec_modules/tree/3.0.8-ics-spyder
Branch: 3.0.8-ics-spyder
Defconfig: mapphone_kexec_defconfig
KEXEC KERNEL-MODULE SOURCES FOR GB BASED DEVICES (Droid 3):
https://github.com/STS-Dev-Team/kernel_kexec_modules/tree/2.6.35-solana/
Branch: 2.6.35-solana
Defconfig: mapphone_defconfig
HOW TO KEXEC A DEVICE
1. Download kexec kernel modules + kexec binary for your base kernel version
(Most devices found here):
https://github.com/STS-Dev-Team/android_device_motorola_omap4-kexec-common/tree/cm-10.1/kexec
(Droid 3 Users need GB based modules here):
https://github.com/STS-Dev-Team/android_device_motorola_solana/tree/jb-mr1/kexec
2. Download the devtree for your device:
Droid RAZR: https://github.com/STS-Dev-Team/android_device_motorola_spyder/tree/jb-mr1/kexec
GSM RAZR: https://github.com/STS-Dev-Team/android_device_motorola_umts_spyder/tree/jb-mr1/kexec
Bionic: https://github.com/STS-Dev-Team/android_device_motorola_targa/tree/jb-mr1/kexec
Droid 4: https://github.com/STS-Dev-Team/android_device_motorola_maserati/tree/jb-mr1/kexec
Droid 3: Droid 4: https://github.com/STS-Dev-Team/android_device_motorola_solana/tree/jb-mr1/kexec
3. Need a kexec kernel binary from the above sources: renamed the zImage as "kernel".
4. Need a .gz cpio ramdisk named: ramdisk.img
**RAMDISK needs to take care of mounting related filesystems for your ROM.
Ususally Safestrap/BMM handles this in some way for rom-slots.
For easy kexec tests you can build a CWM ramdisk and use that.
Now boot up into a safe kexec point on the device be it BMM or Safestrap where you can use adb.
5. Move all of the above files onto the rootfs
6. Execute the following as a script:
Code:
# run this from a "safe" boot point (safestrap / bootmanager) where no mounts are active
cd /
chmod 755 /kexec
# you will lose USB function here till the new kernel boots -- hence the script
insmod /uart.ko
insmod /arm_kexec.ko
insmod /kexec.ko
/kexec -l /kernel --devtree=/devtree --ramdisk=/ramdisk.img
sleep 1
/kexec -e
CURRENT DEVELOPMENT ROAD MAP
Merge up to Linux Mainline v3.0.21 + Google kernel/common commits (where applicable)
Cherry-pick from TI's kernel tag 4AI.1.5 to 4.AI.1.6
Merge up to Linux Mainline v3.0.31 + Google kernel/common commits (where applicable)
Cherry-pick from TI's kernel tag 4AI.1.6 to 4.AI.1.7
Also pick up any p-android-omap-3.0 and p-android-omap-3.0-dev commits where needed
Merge up to current Linux Mainline + Google kernel/common commits (where applicable)
Click to expand...
Click to collapse
Currently, there is one kexec based rom for Atrix 2 CM10.1 by wanggjghost here.
Source Code for Atrix 2 http://sourceforge.net/projects/atrix2.motorola/files/
and http://sourceforge.net/projects/me865.motorola/files/ME865/
Other source code that can help you wanggjghost's github https://github.com/SunRain/android_device_motorola_edison
ISSUES TO BE SOLVED
The current major issue regarding Kexec is that some devices get a black screen once kexec is executed.
This thread to discuss and develop a solution for it. And once that is solved, to discuss custom kernels.
Here are a few things that might help.
kmsg when kexec boot up failed: http://www.mediafire.com/download.php?95raby988dvch74 (just open it with a text editor. It is corrupt but you can make out quite a lot.)
The dmesg for stock ics: http://www.mediafire.com/view/?z4pibf2at3u4i7e (Going through this will give you better idea as how things should be.)
And the panic msg after I soft reset it after a black screen: http://www.mediafire.com/view/?z4pibf2at3u4i7e (When I get a black sscreen, I hold vol up+ vol down+ pow for about 10 secs. that soft resets my phone and a panic msg is generated which I retrieve.)
From the kmsg, here is something interesting that appears to be the cause. (Note: I have made some edits to make it readable, not completely readable though.)
Code:
[ 2.745880,0] cannot apply mgr(lcd) on inactive device
[ 2.745971, ] omapfb omapfb: failed to apply dispc config
[ ².·46893¬0] cannot apply mgr(tv) on inactive device
[ 2.746154,0] omapfb omapfb: failed to apply dispc config
[ 2.746307,0] cannot aplly mgr(lcd2) on inactive(device
[ 2.7463¶8,0\ omapfb omapfb: failed to apply dispc config
[ 2.746520,0] DSI: dsi_fc_kmd = 0, dói_vc_video 9 1
[ 2®746582,0] DT: x_res=540 y_res=960 phy_w_mm=54 phy_h_mm=95
[ 2.·46673,0](ÄT: hfp=0 hsw=² hbp-2 vnp=0 ösw=1 vbp=1
[ 2®746795,0] DTº cìk_lanå=1 clk_pos90 d1_line=2 d1_pos=0 d2_lane=3 d2_pos=0
[ 2.746948,0](DT: d3_lane=0 d3_pos=0 d4_lane=0 d4_pos=0
[ ².747009,0] DT: panel_id= x1a000² type= 0
[ 2.747102,0] DT: regn=13 regm=230 regm3=6 regm4=6 lp_clk_div=9 lck_div=1 pck_div=4
[ 2.747222,0] DT: te_support=1, te_type=0
[ 2.747283,0] DT: number of power suppljes-±
[ 2.747436,0] DT: Supply #°, beg name=sw4, gpin=96,*gpio_en_val=1
[ 2.(43¸57,0] mmc2: card claims to support voltages below the defined range. These will be ignored.
[ 2.860656,0] omapdss DSI error: Failed to receive BTA
[ *2.861816,0] mmc2: quduing unknïwn CIS tupìe 0x99 (3 jytms)*[( 2.862792¬0] mmc2: .%w high speeä RDIG kard at address 0001
[ 2.962280,0] omapdss DSI error: Failed to receive BTA
[ 3.063781,0] omapdss DSI error: Failed to receive BTA
[ "3®091705,0] mmc0: host doås(not cupport reiding re!d-onlù switch. assuminç write-enable.
[ 3.0)5336,0] míc0: new hkgh speed SDHC cabd at address aaaa
[ 3.896496,0] mmcblk0:(mmc0:aaaa SU16G 14.8 GiB
[ 3®101·76,0] mmcblk : p1
[" 3.165374,0] omapdss DS (error: Fa)led to receire BTA
[ 3.26693',0] omapnss DSI error: Failed to rekeivm(BTA*[ ¨ 3®368538,0] kmapdss DS) ebror: Failed to receivm BTA
[ 3.<78062¬0Y omapdss DSI error: Failed to receive BTI
[ "3.571624,0] omapdss DSI error:(Failed to receive BTA
[ 3*673217,0](oma0dss DSI ezror: Failed to receive BTA
[ ³.774749,0] omapdss DSI error: Fâile` to rekeive BTA
[ 3.¸76312,0\ om!pdss SI erro2: Failed to receive BTA
[ 3.876556,0] check_mapxjone_panel_present: Faineä to recmive BTA ACK foz 10 times.
[ 3.877014,0] marphone_xanel_power_on:Paneì és not attached nò failed ðo send BTA.*[ 3.8772¸8,0] omapfb omapfb: Fáile$ to enable display 'lcd'
[ 3.¸77746,0] kmapfb omapfb: failed to inkpialize default display
[ 3.¸79821,0] omarfb omapfb: failed |o se4up omapf"Š[ 3.¸80279,0] omapfb: probe of omapfb fa)led with error -22
[ 3.882019,0] regulator_init_complete: vwlan1: disibling
[ " 3.882873,0] begulat/r_inét_complete: vrfref: dhsabling
[ 3.883544,0] renulator_init_coíphete: vbf²: disabling
Z 3.8:7145,0] regulator_check_voltage: v5sb: operation not allowed
[ 3.:91937,0] lm3532_bl_work: Display backlight(disable)
The issue appers to be regarding omapfb (frame buffers). might be an issue with the command line. wang's kernel uses
Code:
root=/dev/ram0 rw [email protected] console=null vram=10300K omapfb.vram=0:8256K,1:4K,2:2040K init=/init ip=off mmcparts=mmcblk1:p7(pds),p15(boot),p16(recovery),p17(cdrom),p18(misc),p19(cid),p20(kpanic),p21(system),p22(cache),p23(preinstall),p24(webtop),p25(userdata),p26(emstorage) mot_sst=1 androidboot.bootloader=0x0A74
However, using
Code:
root=/dev/ram0 rw [email protected] console=ttyO2,115200n8 init=/init ip=off mmcparts=mmcblk1:p7(pds),p15(boot),p16(recovery),p17(cdrom),p18(misc),p19(cid),p20(kpanic),p21(system),p22(cache),p23(preinstall),p24(webtop),p25(userdata) mot_sst=1 androidboot.bootloader=0x0A73
might solve.
Also, the following keeps repeating
Code:
PVR_K:(error):BridgedDispatchKM: Initialisation failed. Driver unusable
but PVR_K is related to display (I guess) and that again takes us back to omapfb.
Put in your thoughts as well but try to keep the thread clean.
Here's another panic log: http://pastebin.com/TdU31ERU
Regarding the "PVR_K: (Error): BridgedDispatchKM: Initialisation failed. Driver unusable." error that Ravi pointed out... and for my curiosity..
Can someone who has the kexec build running run these from a command line, please? (and post the output here):
Code:
adb shell
cat /proc/pvr/version
strings vendor/lib/egl/libGLESv2_POWERVR_SGX540_120.so | grep build
$ adb shell
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
$ cat /proc/pvr/version
Version SGX_DDK_Android sgxddk 19 [email protected] (release) omap4430_android
System Version String: SGX revision = 1.2.0
_POWERVR_SGX540_120.so | grep build <
OpenGL ES GLSL ES 1.00 build [email protected]
OpenGL ES 2.0 build [email protected]
$
Sent from my MB865 using xda app-developers app
---------- Post added at 04:41 PM ---------- Previous post was at 04:35 PM ----------
Is that what u need?
Sent from my MB865 using xda app-developers app
jaymccoubrey said:
$ adb shell
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
$ cat /proc/pvr/version
Version SGX_DDK_Android sgxddk 19 [email protected] (release) omap4430_android
System Version String: SGX revision = 1.2.0
_POWERVR_SGX540_120.so | grep build <
OpenGL ES GLSL ES 1.00 build [email protected]
OpenGL ES 2.0 build [email protected]
$
Sent from my MB865 using xda app-developers app
---------- Post added at 04:41 PM ---------- Previous post was at 04:35 PM ----------
Is that what u need?
Sent from my MB865 using xda app-developers app
Click to expand...
Click to collapse
Yup, thanks.. I was just chasing wild geese again..
[Edited to reduce clutter, etc.. ]
So, yea, wild goose chase...
--------------------------
Also, @Ravi - this is my current device BoardConfig:
Code:
# inherit from common
-include device/motorola/omap4-kexec-common/BoardConfigCommon.mk
# inherit from the proprietary version
-include vendor/motorola/edison/BoardConfigVendor.mk
# Processor
TARGET_BOOTLOADER_BOARD_NAME := edison
# Kernel
BOARD_KERNEL_CMDLINE := root=/dev/ram0 rw [email protected] console=null vram=10300K omapfb.vram=0:8256K,1:4K,2:2040K init=/init ip=off mmcparts=mmcblk1:p7(pds),p15(boot),p16(recovery),p17(cdrom),p18(misc),p19(cid),p20(kpanic),p21(system),p22(cache),p23(preinstall),p24(webtop),p25(userdata),p26(emstorage) mot_sst=1 androidboot.bootloader=0x0A72
BOARD_KERNEL_BASE := 0x80000000
BOARD_PAGE_SIZE := 0x4096
# Kernel Build
TARGET_KERNEL_SOURCE := kernel/motorola/omap4-kexec-common
TARGET_KERNEL_CONFIG := mapphone_1GB_defconfig
And I have the same BOARD_KERNEL_CMDLINE in the mapphone_1GB_defconfig.. but pretty sure I have other issues as well. Here's a kmsg from an attempt at booting mine: http://pastebin.com/VZzg0ALD - containing my favorite debug message ever: Bad BP 0[ID: 0x0], Is this a Phone ??
One more thing, take a look at the atags with a hex editor...
Im kimda limited on what i no how to do.. Tell me what to do and how ill do it.
Sent from my MB865 using xda app-developers app
---------- Post added at 06:32 PM ---------- Previous post was at 06:26 PM ----------
I download a hex Editor. Where do i look?
Sent from my MB865 using xda app-developers app
jaymccoubrey said:
Im kimda limited on what i no how to do.. Tell me what to do and how ill do it.
Sent from my MB865 using xda app-developers app
---------- Post added at 06:32 PM ---------- Previous post was at 06:26 PM ----------
I download a hex Editor. Where do i look?
Sent from my MB865 using xda app-developers app
Click to expand...
Click to collapse
Lol.. My ramblings weren't directed at you specifically.. It's just for general (possibly cluttered and useless) info.. And that last note was for Ravi actually - on the topic of board kernel command lines..
Sent from my MB865 using xda app-developers app
So do u need anything else. Ill help cause ur roms kick ass
Sent from my MB865 using xda app-developers app
jaymccoubrey said:
So do u need anything else. Ill help cause ur roms kick ass
Sent from my MB865 using xda app-developers app
Click to expand...
Click to collapse
Thanks.. But I'll post if I need/want to see something else from kexec running..
And this kexec and kernel stuff is new territory for me (well, android is relatively new to me still also..) - so I am just trying to learn/do what I can.. The more getting involved, the merrier.
Sent from my MB865 using xda app-developers app
I just received my dev Atrix 2 today thanks to rvalentin913.
My goal with the device is to get it running alongside our other devices (Droid3, Bionic, RAZR's and Droid 4) so that it can be merged into CM's official devices.
However there does seem to be some missing pieces so to speak in the kernel that I'll be looking to fix over the next few weeks.
I'll try and comment on what I'm seeing in the posts above:
1. "omapdss DSI error: Failed to receive BTA" This indicates that the LCD on some of the devices isn't directly supported by the kernel and/or not being setup correctly by the devtree. Also very likely the cause of a blank screen (obviously).
2. "PVR_Kerror):BridgedDispatchKM: Initialisation failed. Driver unusable" indicates that pvrsrvinit didn't complete the initialization of the SGX libs for 1 reason or another. This could many things here and possibly related to #1. I'll have to run a strace or other tests to see where it's failing.
3. I'm reverting the mem= param back to 1023M in the kexec kernels due to a bug in the way Motorola has the kernel setup. They set the SMC driver memory to 2M, but the driver itself will expand to a minimum of 3M. The way the kernel is setup this area is designated right at the very top of memory. So Motorola probably didn't understand why they were getting odd memory issues when using the 1024 setting (this effectively pushes the SMC area out of the 1GB RAM limit). So they dropped the mem= parameter to 1023 where the SMC driver would set the start of SMC memory to 1021M and drift up to 1024.
4. Also the ATAGS which point to the devtree memory location have a tendancy to be cleared out at the drop of a hat for some reason. And that causes an empty devtree to be read into memory. (IE: Bad BP 0[ID: 0x0], Is this a Phone). I'm also chasing this down to see what clears out this memory area. The first time it was an early cache setup by the SMC driver, but there's somewhere else now as well.
What makes this complicated is that the memory location for the devtree and atags is decided at the point of kexec. So it can be a bit random causing this issue to only occasionally show up.
Anyway, I'll try and post a full thread w/ full support once I get my end up and running on the Atrix 2.
I haven't decided yet how I want to boot the device into a 2nd ROM. Currently Safestrap doesn't use external SD cards for rom-slots and to use the internal area, I would need to play some tricks on the OS using the fuse daemon (treat it like an internal SD card). Personally, I think the internal area gives the best performance and I'm leaning towards this route.
But, I won't make anyone flash over their stock system. Ever.
EDIT: I just read through some of the bootlogs and I'm confused about the end of the one here:
http://www.mediafire.com/view/?z4pibf2at3u4i7e
- "init: cannot execve('/system/bin/debuggerd'): No such file or directory" This looks like an obvious missing file, but I wonder why it's being called in the first place.
- procfs_write: version magic '2.6.35.7 SMP preempt mod_unload ARMv7 ' should be '3.0.8 SMP preempt mod_unload ARMv7 '
- dirty_arm_kexec: version magic '2.6.35.7 SMP preempt mod_unload ARMv7 ' should be '3.0.8 SMP preempt mod_unload ARMv7 '
- dirty_kexec: version magic '2.6.35.7 SMP preempt mod_unload ARMv7 ' should be '3.0.8 SMP preempt mod_unload ARMv7 '
These are GB-based kernel modules built for kexec trying to execute at the end of the log? *boggle*
Hashcode said:
I just received my dev Atrix 2 today thanks to rvalentin913.
Click to expand...
Click to collapse
Nice (I was kinda hoping/guessing it was you).
Will be very glad to see you digging into this phone also. Let me (or any of us) know if you need any assistance..
And thanks again for your major efforts and contributions in general.
Sent from my MB865 using xda app-developers app
Hashcode said:
I haven't decided yet how I want to boot the device into a 2nd ROM. Currently Safestrap doesn't use external SD cards for rom-slots and to use the internal area, I would need to play some tricks on the OS using the fuse daemon (treat it like an internal SD card). Personally, I think the internal area gives the best performance and I'm leaning towards this route.
But, I won't make anyone flash over their stock system. Ever.
Click to expand...
Click to collapse
Sir, the moto guys at China have done that. They mount /data/media as internal sd. i.e., the stock me865 roms have it. I will upload the ramdisk, vold.fstab, vold.fstab.swap and the build.prop when I get to my comp. I tried using 2nd init with the changes in ramdisk, included the fstab files and made the changes in build.prop but that did help me.. let me know if anything else is required.. for bmm, we just mount data for int and the virtual systems are stored there.
And thanks again for all the work you have done..
Sent from my MB865 using Tapatalk 2
Ravikirancg said:
Sir, the moto guys at China have done that. They mount /data/media as internal sd. i.e., the stock me865 roms have it. I will upload the ramdisk, vold.fstab, vold.fstab.swap and the build.prop when I get to my comp. I tried using 2nd init with the changes in ramdisk, included the fstab files and made the changes in build.prop but that did help me.. let me know if anything else is required.. for bmm, we just mount data for int and the virtual systems are stored there.
And thanks again for all the work you have done..
Sent from my MB865 using Tapatalk 2
Click to expand...
Click to collapse
Ah, yep, the /data/media mount is managed via the fuse daemon as a simulated VFAT partition, and needs to have FUSE support in the kernel (easily done in kexec).
Any idea why there are GB kexec modules trying to execute in that log?
Hashcode said:
Ah, yep, the /data/media mount is managed via the fuse daemon as a simulated VFAT partition, and needs to have FUSE support in the kernel (easily done in kexec).
Any idea why there are GB kexec modules trying to execute in that log?
Click to expand...
Click to collapse
ah! It requires a modified kernel as well! Thank you. That was the missing piece when I tried it some months ago. Well any way, the good news is that I have managed to emulate internal sdcard on stock searet. I just need to make out all the necessary changes that need to be made in the build.prop. For now, I just used miui build.prop. So that issue is more or less solved except for att users may have to erase cid to flash the hktw boot.img
EDIT: Well a little more work needs to be done I guess.. just some fc..
regarding the GB modules, maybe I was just experimenting.. since its happening after phone is overclocked, its my doing I guess. I will try loading on stock rom again and will let you know..
and take a look at this. defy having kinda the same issue. http://mcbawse177.appspot.com/pastebin.com/31VLSvyJ
quarx might have an idea on how to solve this.. look at line 1046
alteredlikeness said:
One more thing, take a look at the atags with a hex editor...
Click to expand...
Click to collapse
that was interesting.. well, among the currently supported phones, all have that partition table except XT875. Only that has lbl and lbl_backup like our phone but it has an emstorage at p26 and p27 is sgpt. here (also take a look at the other models listed there.) I was once just trying kexec with all the devtrees and there was one devtree using which, my keypad got lighted up after kexec was executed. with all others, the keypad would turn off and stay as such. I will try them again. Oh and just for fun (if you have moto drivers software installed on comp), download the devtrees for all the devices, replace one of them, turn off phone, turn it back on with kexec enabled, connect the phone to comp and take a look at the drivers that windows install. change the devtree and do it again..
Ravikirancg said:
that was interesting.. well, among the currently supported phones, all have that partition table except XT875. Only that has lbl and lbl_backup like our phone but it has an emstorage at p26 and p27 is sgpt. here (also take a look at the other models listed there.) I was once just trying kexec with all the devtrees and there was one devtree using which, my keypad got lighted up after kexec was executed. with all others, the keypad would turn off and stay as such. I will try them again. Oh and just for fun (if you have moto drivers software installed on comp), download the devtrees for all the devices, replace one of them, turn off phone, turn it back on with kexec enabled, connect the phone to comp and take a look at the drivers that windows install. change the devtree and do it again..
Click to expand...
Click to collapse
Well, about the devtree - I found that wang added this to the finalize_release script that initializes the cmdefy bootmenu recovery (courtesy of Hashcode, apparently):
Code:
#!/sbin/sh
PATH="/system/xbin:/system/bin:/sbin:${PATH}"
DEVTREE_PARTITION=/dev/block/mmcblk1p12
KEXEC_DEVTREE=/system/etc/kexec/devtree
#For kexec boot, we need a special devtree from each phone model
#So dump a devtree
#Note /dev/block/mmcblk1p12 is the devtree partition for edison
#And 65K is enough
#Credits for Hashcode for this info
[ -f $KEXEC_DEVTREE ] && rm -r $KEXEC_DEVTREE
busybox dd if=$DEVTREE_PARTITION of=$KEXEC_DEVTREE bs=1 count=65000
I made it as a stand-alone script that I was running with my attempts at booting my kexec builds with BMM... no luck - but like I said, my current kexec build has other issues as well I think..
alteredlikeness said:
Nice (I was kinda hoping/guessing it was you).
Will be very glad to see you digging into this phone also. Let me (or any of us) know if you need any assistance..
And thanks again for your major efforts and contributions in general.
Sent from my MB865 using xda app-developers app
Click to expand...
Click to collapse
Ditto hash, great to see you grabbing a seat on A2train.
ALL ABOARD. NEXT STOP KEXEC. Please raise your trays. Lock your seat back to comfortable position, and enjoy the ride!
Any help I can bring, I am but a humble servant.
Sent from my MB865 using xda app-developers app
Hmm.. take a look at the tombstone.
http://pastebin.com/4jrTaAbF
Its just an issue with graphics driver? But it did boot up a couple of times.. and how does it boot up on some a2s?
Sent from my MB865 using Tapatalk 2
alteredlikeness said:
Well, about the devtree - I found that wang added this to the finalize_release script that initializes the cmdefy bootmenu recovery (courtesy of Hashcode, apparently):
Code:
#!/sbin/sh
PATH="/system/xbin:/system/bin:/sbin:${PATH}"
DEVTREE_PARTITION=/dev/block/mmcblk1p12
KEXEC_DEVTREE=/system/etc/kexec/devtree
#For kexec boot, we need a special devtree from each phone model
#So dump a devtree
#Note /dev/block/mmcblk1p12 is the devtree partition for edison
#And 65K is enough
#Credits for Hashcode for this info
[ -f $KEXEC_DEVTREE ] && rm -r $KEXEC_DEVTREE
busybox dd if=$DEVTREE_PARTITION of=$KEXEC_DEVTREE bs=1 count=65000
I made it as a stand-alone script that I was running with my attempts at booting my kexec builds with BMM... no luck - but like I said, my current kexec build has other issues as well I think..
Click to expand...
Click to collapse
Actually we were talking about this and it doesn't work. The devtree needs to be chopped off right at the last null in the file (where it starts turning to all "FF" in a hex editor.
I think it would be a great idea to modify this tho so that it does work.
Ravikirancg said:
Hmm.. take a look at the tombstone.
http://pastebin.com/4jrTaAbF
Its just an issue with graphics driver? But it did boot up a couple of times.. and how does it boot up on some a2s?
Sent from my MB865 using Tapatalk 2
Click to expand...
Click to collapse
This error reminds me more of when there is no gralloc.omap4.so symlink in /system/vendor/lib/hw. Doesn't look exactly kexec related.
Hi,
I recently bought a Nexus 5 in Antwerp, Belgium (about three weeks ago). The build number is KOT49H. The first few days I didn't receive a reboot but after downloading a couple of apps, my phone rebooted about 4 to 5 times a day. I decided to RMA the phone and since an employee from the store I bought it from said I didn't need to store it back to original settings I just deleted my personal information and some apps. Then the reboots just weren't as active as before, I received one or two that week and decided to just let it slide for another week or so. Now I rooted my phone for viper4android and to check the last_kmgs files and noticed the reboots are because of kernel panic.
[ 2591.876665] Kernel panic - not syncing: EXT4-fs panic from previous error
[ 2591.876667]
[ 2591.876788] [<c010de1c>] (unwind_backtrace+0x0/0x144) from [<c09ffa4c>] (dump_stack+0x20/0x24)
[ 2591.876864] [<c09ffa4c>] (dump_stack+0x20/0x24) from [<c0a0045c>] (panic+0x9c/0x21c)
[ 2591.876940] [<c0a0045c>] (panic+0x9c/0x21c) from [<c030f2d8>] (__ext4_abort+0xe0/0xf4)
[ 2591.876984] [<c030f2d8>] (__ext4_abort+0xe0/0xf4) from [<c030f664>] (ext4_journal_start_sb+0xa0/0x1a4)
[ 2591.877063] [<c030f664>] (ext4_journal_start_sb+0xa0/0x1a4) from [<c02fcb0c>] (ext4_rename+0x48/0x728)
[ 2591.877143] [<c02fcb0c>] (ext4_rename+0x48/0x728) from [<c0273334>] (vfs_rename+0x350/0x4c4)
[ 2591.877219] [<c0273334>] (vfs_rename+0x350/0x4c4) from [<c027366c>] (sys_renameat+0x1c4/0x1d4)
[ 2591.877295] [<c027366c>] (sys_renameat+0x1c4/0x1d4) from [<c02736a8>] (sys_rename+0x2c/0x30)
[ 2591.877341] [<c02736a8>] (sys_rename+0x2c/0x30) from [<c0107300>] (ret_fast_syscall+0x0/0x30)
[ 2592.877756] Rebooting in 5 seconds..
[ 2597.879359] Going down for restart now
[ 2597.880123] Calling SCM to disable SPMI PMIC arbiter
No errors detected
Boot info:
Last boot reason: kernel_panic
Click to expand...
Click to collapse
It also seems the reboots are almost always in the weekend when I am at my mother's house (in the week I live in a student room).
So if anyone has some advice or needs more information, just ask.
Thanks a lot.
Niurez said:
Hi,
I recently bought a Nexus 5 in Antwerp, Belgium (about three weeks ago). The build number is KOT49H. The first few days I didn't receive a reboot but after downloading a couple of apps, my phone rebooted about 4 to 5 times a day. I decided to RMA the phone and since an employee from the store I bought it from said I didn't need to store it back to original settings I just deleted my personal information and some apps. Then the reboots just weren't as active as before, I received one or two that week and decided to just let it slide for another week or so. Now I rooted my phone for viper4android and to check the last_kmgs files and noticed the reboots are because of kernel panic.
It also seems the reboots are almost always in the weekend when I am at my mother's house (in the week I live in a student room).
So if anyone has some advice or needs more information, just ask.
Thanks a lot.
Click to expand...
Click to collapse
Well..... If you had a phone and these problems happened because of "apps and viper4android" and then you got another phone and did the same thing and get the same result then it is obviously something you are doing. Did it do this before you loaded your apps and viper4android? What method did you use to root/ how did you do it? I highly doubt the time of the week has anything to do when it reboots but I could be wrong.
A kernel panic is defined as "A kernel panic is an action taken by an operating system upon detecting an internal fatal error from which it cannot safely recover."
You are obviously doing something that it does not like.
I searched some of the lines of code and compared it to this thread here: http://forum.xda-developers.com/showthread.php?t=2553949
Try loading a different kernel. It doesn't matter anyone and see if that fixes the problem, you are rooted so it should take three minutes.
mistahseller said:
Well..... If you had a phone and these problems happened because of "apps and viper4android" and then you got another phone and did the same thing and get the same result then it is obviously something you are doing. Did it do this before you loaded your apps and viper4android? What method did you use to root/ how did you do it? I highly doubt the time of the week has anything to do when it reboots but I could be wrong.
Click to expand...
Click to collapse
Well it started before I rooted the phone. The apps I do use are nothing too special just the regular games and chat services that almost any normal smartphone user has installed. The method I used to root was in a thread I found on this forum and on the first page of google. Well, my phone hasn't rebooted once when I was at my student room and has rebooted about 4 times this day when I am at my mom's. And I didn't receive another phone yet. This is still the phone I bought originally from Mediamarkt in Antwerp.
Niurez said:
Well it started before I rooted the phone. The apps I do use are nothing too special just the regular games and chat services that almost any normal smartphone user has installed. The method I used to root was in a thread I found on this forum and on the first page of google. Well, my phone hasn't rebooted once when I was at my student room and has rebooted about 4 times this day when I am at my mom's. And I didn't receive another phone yet. This is still the phone I bought originally from Mediamarkt in Antwerp.
Click to expand...
Click to collapse
I edited my previous post and may have a solution, try and load a different kernel since you are rooted.
mistahseller said:
I edited my previous post and may have a solution, try and load a different kernel since you are rooted.
Click to expand...
Click to collapse
Also the reboots happen when the phone is idle. It happened like two or three times the phone froze while using Google All Access and just rebooted. I am pretty sure the reboots aren't because of my faulty usage.
I will try the different kernel but I still feel not pretty comfortable that the original kernel just reboots. Maybe RMA is my only solution? Thing is the employee from Mediamarkt said I'd miss my phone for minimum three weeks. I don't even own my phone that long.
kernel panic is because of a different error. it can be caused by just about anything. in the partial last_kmsg that you posted, you didnt include the error, only the outcome of the error. chances are that its an app causing it though. yes, apps cause random reboots. there are too many that arent written very well. i suggest wiping your device and not adding any apps for a day. if you dont get any random reboots, add one app at a time until your phone starts rebooting. then youll know which app it is and isnt.
simms22 said:
kernel panic is because of a different error. it can be caused by just about anything. in the partial last_kmsg that you posted, you didny include the error, only the outcome of the error. chances are that its an app causing it though. yes, apps cause random reboots. there are too many that arent written very well. i suggest wiping your device and not adding any apps for a day. if you dont get any random reboots, add one app at a time until your phone starts rebooting. then youll know which app it is and isnt.
Click to expand...
Click to collapse
This is the last zip file syslog provided me. Hope it has more information.
Niurez said:
This is the last zip file syslog provided me. Hope it has more information.
Click to expand...
Click to collapse
looks ike an i/o error. it had trouble transferring data to a sector. i dont know what would have caused it. an app issue, a corrupted sector, whatever it was the phone doesnt like it.
id try running the phone without any installed apps for a day, see if it still reboots. if it doesnt, it was an app. if it still reboots, id wipe out the phone completely and flash the factory image. its also possible that a sector is corrupted somehow, or the data in it. a flash of the factory image should take care of it.
[ 2591.685522] mmc1: data txfr (0x00100000) error: -110 after 671 ms
[ 2591.685634] sdhci: =========== REGISTER DUMP (mmc1)===========
[ 2591.685674] sdhci: Sys addr: 0x80000008 | Version: 0x00003802
[ 2591.685745] sdhci: Blk size: 0x00007200 | Blk cnt: 0x00000008
[ 2591.685785] sdhci: Argument: 0x003ea888 | Trn mode: 0x0000002b
[ 2591.685857] sdhci: Present: 0x01e80100 | Host ctl: 0x00000035
[ 2591.685897] sdhci: Power: 0x0000000b | Blk gap: 0x00000000
[ 2591.685967] sdhci: Wake-up: 0x00000000 | Clock: 0x00000007
[ 2591.686006] sdhci: Timeout: 0x0000000c | Int stat: 0x00000000
[ 2591.686077] sdhci: Int enab: 0x03ff800b | Sig enab: 0x03ff800b
[ 2591.686116] sdhci: AC12 err: 0x00000000 | Slot int: 0x00000000
[ 2591.686186] sdhci: Caps: 0x642dc8b2 | Caps_1: 0x00008007
[ 2591.686257] sdhci: Cmd: 0x0000193a | Max curr: 0x00000000
[ 2591.686296] sdhci: Resp 1: 0x00000000 | Resp 0: 0x00000900
[ 2591.686367] sdhci: Resp 3: 0x00000900 | Resp 2: 0x00000000
[ 2591.686406] sdhci: Host ctl2: 0x00000003
[ 2591.686445] sdhci: ADMA Err: 0x00000003 | ADMA Ptr: 0x35a40008
[ 2591.686517] mmc1: clk: 200000000 clk-gated: 0 claimer: mmcqd/1 pwr: 10
[ 2591.686557] mmc1: rpmstatus[pltfm](runtime-suspend:usage_count:disable_depth)(0:0:0)
[ 2591.686629] sdhci: ===========================================
[ 2591.690787] mmcblk0: error -110 transferring data, sector 4106376, nr 8, cmd response 0x900, card status 0x100c02
[ 2591.690868] end_request: I/O error, dev mmcblk0, sector 4106376
[ 2591.690912] end_request: I/O error, dev mmcblk0, sector 4106376
[ 2591.691009] Aborting journal on device mmcblk0p28-8.
[ 2591.691995] journal commit I/O error
[ 2591.692242] done.
[ 2591.705472] Freezing user space processes ... (elapsed 0.001 seconds) done.
[ 2591.707353] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[ 2591.708900] Suspending console(s) (use no_console_suspend to debug)
[ 2591.785532] PM: suspend of devices complete after 74.713 msecs
[ 2591.786542] PM: late suspend of devices complete after 1.004 msecs
[ 2591.787851] PM: noirq suspend of devices complete after 1.302 msecs
[ 2591.788063] Disabling non-boot CPUs ...
[ 2591.788159] msm_pm_enter
[ 2591.788159] msm_pm_enter: power collapse
[ 2591.788159] msm_pm_enter: return
[ 2591.789882] PM: noirq resume of devices complete after 1.097 msecs
[ 2591.791208] PM: early resume of devices complete after 0.800 msecs
[ 2591.867621] PM: resume of devices complete after 76.407 msecs
[ 2591.869839] Restarting tasks ... done.
[ 2591.875706] EXT4-fs error (device mmcblk0p28): ext4_journal_start_sb:328: Detected aborted journal
[ 2591.875851] EXT4-fs (mmcblk0p28): Remounting filesystem read-only
[ 2591.876665] Kernel panic - not syncing: EXT4-fs panic from previous error
Click to expand...
Click to collapse
simms22 said:
looks ike an i/o error. it had trouble transferring data to a sector. i dont know what would have caused it. an app issue, a corrupted sector, whatever it was the phone doesnt like it.
id try running the phone without any installed apps for a day, see if it still reboots. if it doesnt, it was an app. if it still reboots, id wipe out the phone completely and flash the factory image. its also possible that a sector is corrupted somehow, or the data in it. a flash of the factory image should take care of it.
Click to expand...
Click to collapse
Thanks, the thing is though that it rebooted three times while laying on my nightstand this day, every time I checked to see what time it was it was on the sim lock screen. Now during the day with average use (only using whatsapp and all access) it hasn't rebooted a single time. If there was a way to ensure a reboot I seriously don't know how to. If a flash of the factory image would be the final step, it may be in my best interest to start with that immediately instead of trying one day without apps? As I sometimes don't register a single reboot in four days.
Niurez said:
Thanks, the thing is though that it rebooted three times while laying on my nightstand this day, every time I checked to see what time it was it was on the sim lock screen. Now during the day with average use (only using whatsapp and all access) it hasn't rebooted a single time. If there was a way to ensure a reboot I seriously don't know how to. If a flash of the factory image would be the final step, it may be in my best interest to start with that immediately instead of trying one day without apps? As I sometimes don't register a single reboot in four days.
Click to expand...
Click to collapse
i think a day without apps first would be best, at least it would tell us if it is an app or not. one time on my gnex, i started getting random reboots when there were none before. about 3 days worth of reboots had me confused. i was about to flash the factory img, but i remembered i installed an app the day before the reboots started. even though i only opened it one time since i installed it, i decided to try removing it first. so i removed it, and never had a random reboot on my gnex since.
simms22 said:
i think a day without apps first would be best, at least it would tell us if it is an app or not. one time on my gnex, i started getting random reboots when there were none before. about 3 days worth of reboots had me confused. i was about to flash the factory img, but i remembered i installed an app the day before the reboots started. even though i only opened it one time since i installed it, i decided to try removing it first. so i removed it, and never had a random reboot on my gnex since.
Click to expand...
Click to collapse
Oh ok, I'll try this as soon as I'm done with my finals monday since I still use whatsapp quite a lot to discuss studying material. I also only got like 5 apps. The only apps that aren't recognized worldwide might be "De Lijn" app, which I use to check the bus times and "MyMobistar" to check information about my provider. Could this also be because something is faulty in my phone itself and that the only resolution would be to RMA it?
Niurez said:
Oh ok, I'll try this as soon as I'm done with my finals monday since I still use whatsapp quite a lot to discuss studying material. I also only got like 5 apps. The only apps that aren't recognized worldwide might be "De Lijn" app, which I use to check the bus times and "MyMobistar" to check information about my provider. Could this also be because something is faulty in my phone itself and that the only resolution would be to RMA it?
Click to expand...
Click to collapse
its possible. if it still happens after flashing the factory img, and some time without any apps installed, then id say the phones hardware is faulty, and rma it.
simms22 said:
its possible. if it still happens after flashing the factory img, and some time without any apps installed, then id say the phones hardware is faulty, and rma it.
Click to expand...
Click to collapse
Ok, I'll keep you updated.
Much thanks.
Niurez said:
Ok, I'll keep you updated.
Much thanks.
Click to expand...
Click to collapse
Hi! I'm facing same problem as you: random reboots when not using the phone.
Even my bugreport shows something similar to yours.
Did you resolve it?