These are using the following build and kernel:
Build: generic/full_msm/msm/msm:2.2.1/FRX04/eng.bryan.20110121.213411:eng/release-keys
Hardware: msm
Bootloader: unknown
Radio: unknown
Kernel: Linux version 2.6.27.46-01253-gd53ddf6-dirty ([email protected]) (gcc version 4.4.0 (GCC) )
KERNEL PANIC - FRX04 - MO... ON THE 3RD OF FEB 2011 http://pastebin.com/TvJ4mCAG
KERNEL PANIC - FRX04 - WE... ON THE 3RD OF FEB 2011 http://pastebin.com/ccKsETYk
KERNEL PANIC - FRX04 - WE... ON THE 3RD OF FEB 2011 --- http://pastebin.com/UfLvnbdD
Related
commit 234d96ee0f3b8e49501d068a2a3165aa4db60903
Author: Greg Kroah-Hartman <[email protected]>
Date: Wed Nov 20 10:43:41 2013 -0800
Linux 3.4.70
style2345 said:
commit 234d96ee0f3b8e49501d068a2a3165aa4db60903
Author: Greg Kroah-Hartman <[email protected]>
Date: Wed Nov 20 10:43:41 2013 -0800
Linux 3.4.70
Click to expand...
Click to collapse
Care to elaborate?
style2345 said:
commit 234d96ee0f3b8e49501d068a2a3165aa4db60903
Author: Greg Kroah-Hartman <[email protected]>
Date: Wed Nov 20 10:43:41 2013 -0800
Linux 3.4.70
Click to expand...
Click to collapse
This has nothing to do with Galaxy Nexus.
https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.4.70
thats where he may have saw it
still nothing though
Devs are working on the 3.4 porting on pur gnex :thumbup:
Sent from my Galaxy Nexus using xda app-developers app
lets hope we get a working one for gnex soon!
Alright, so, I'm trying to compile a custom kernel with all the rooting restrictions disabled, but I can't get anything to boot.
I've used Samsung's source (N930FXXU1APGI) and TWRP's stock-6.0 branch.
When building with no modifications:
TWRP stock-6.0 boots, but panics shortly after: Kernel panic - not syncing: Watchdog detected hard LOCKUP on cpu 1
Samsung's doesn't boot (stuck at bootloader splash)
Both using the same ramdisk (with verify disabled) that I'm running with the stock kernel.
Anyone got any suggestions?
Compilers tested:
Ubuntu 16.04's arm64 toolchain (gcc version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.1))
gcc-linaro-4.9-2016.02-x86_64_aarch64
Google's 4.9 (gcc version 4.9.x 20150123 (prerelease) (GCC))
Firmware :
PDA - E500HXXU1BPD1
CSC - E500HODD1BPD1
Version - Android 5.1.1
Changelist - 7897892
What's New - 1. Ultra data saving mode
2. New Smart Manager
3. New system app added
(Opera Max and My Galaxy)
4. Fast Battery Charging
5. Smooth and fast operation
Knox Version :
Knox 2.4
Standard SDK 5.4.0
Premium SDK 2.4.0
Customization SDK v2.5.0
Container 2.4.0
CEP 2.0.1
Enterprise Billing 1.2.0
OTP 1.1.1
SE for Android 2.3.0
SSO 2.4.0
TIMA 3.1.000
VPN 2.2.0
Kernel Version :
3.10.49-7897892
[email protected] #1
Android Security Patch Level :
2016-05-01
Baseband Version :
E500HXXU1BOI6
Any Download link bro?
Hello everyone. I am spinning up on a project that requires a custom rom for the flo based on 5.1.1_r28, and a custom kernel as well. The rom is built and working, but currently uses the prebuilt flo kernel. When I boot the prebuilt kernel, I can check the kernel version, 7597781.
Linux version 3.4.0-g7597781 ([email protected]) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #1 SMP PREEMPT Thu Mar 12 01:10:18 UTC 2015
This corresponds to the last commit hash, so after checking out the msm kernel source, I created a branch based on that hash.
You can find my kernel source here - https://github.com/FutureHax/flo-kernel/tree/7597781, and the actual zImage file attached to the post.
After the kernel is installed however, I am unable to boot. The device doesnt even make it to the splash screen, just loops over the initial google logo before rebooting to repeat. This also means that since nothing is started, I cant get any logs from adb to see whats wrong. The kernel is just completely failing.
The resulting boot.img file sizes are slightly off as well.
Not working
Custom built kernel boot.img size = sending 'boot' (7356 KB)...
Working
Prebuilt kernel boot.img size = sending 'boot' (7358 KB)...
I was able to get my last_kmsg as well after the panic.
http://pastebin.com/YfDzNbGS
Hello, have you fixed it?
r2DoesInc said:
I was able to get my last_kmsg as well after the panic. http://pastebin.com/YfDzNbGS
Click to expand...
Click to collapse
I see a null pointer just before the ramdisk is supposed to be unpacked...
Code:
[ 0.447845] Unable to handle kernel NULL pointer dereference at virtual address 00000001
[ 0.448059] pgd = c0004000
[ 0.448181] [00000001] *pgd=00000000
Try to pack your kernel with the original/prebuilt ramdisk and see what happens.
I did in fact resolve it. I dont actually know what that issue was, but it went away to be replaced with a real error
Unable to handle kernel paging request at virtual address 32797474
Click to expand...
Click to collapse
I was then pointed to a few commits by a friend of mine and they resolved the issue!
https://review.cyanogenmod.org/#/q/...ect:CyanogenMod/android_kernel_motorola_ghost
Like in the subject - reversed view in a 2din Android station
MCU version - mtcd_kgl_v2.60_4
Aug 15 2017 19:26:09
Andriod version
5.1.1
Kernel version
3.0.101+
[email protected] #265
Tue Jun 20 00:45:21 CST 2017
Built number
rk3188-userdebug 20072017.21:56:11
Version info
Model number
A-MEDIA AUTO (1024X600 S)
S/N
f401030f1300180707e0fa5133504b52
CPU
ARM Cortex-A9 @1.6GHz (x4)
Memory
1024 MB
The touch functions are correct and in the right place - they are not reversed (like the view on the display). The station works smoothly. It looks like the display itself has gone into headup mode and the touch has remained unchanged. It happened after the installation of Sygic and unsuccessful attempt to start the car engine ... Entering the service menu does not give anything - no reboot settings - only changing the logo and other little needed "goodies" After entering the "recovery" menu, you can not start system restore - no file (s) or recovery. Reflecting the screen in the mirror, as you can see, helps
Thank You