I was hoping someone could help me figure out why my phone had a force reboot which went into recovery. Right now it is stock ICS with stock kernel and setting - though it is rooted. I went to a clean stock install today with the hopes of it stopping the issue but it happened again.
Below is from the last_kmsg file at the time of the crash - any help interpreting it and maybe pointing to the cause of the reboots would be welcome:
[ 3.925411] s3c-rtc s3c2410-rtc: setting system clock to 2012-06-16 22:59:24 UTC (1339887564)
[ 3.926991] FIMC0 registered successfully
[ 3.928373] FIMC1 registered successfully
[ 3.929790] FIMC2 registered successfully
[ 3.929994] max8998_charger_probe : MAX8998 Charger Driver Loading
[ 3.931981] max8998_charger_probe : pmic interrupt registered
[ 3.933422] wake enabled for irq 39
[ 3.933706] Freeing init memory: 152K
[ 3.997046] init: Unable to open persistent property directory /data/property errno: 2
[ 3.999240] enabling adb
[ 4.000259] adb_open
[ 4.058176] yaffs: dev is 32505860 name is "mtdblock4" rw
[ 4.058274] yaffs: passed flags ""
[ 4.058431] yaffs: yaffs: Attempting MTD mount of 31.4,"mtdblock4"
[ 4.064059] yaffs: yaffs_read_super: is_checkpointed 1
[ 4.194496] mmc0: new high speed MMC card at address 0001
[ 4.201024] mmcblk0: mmc0:0001 SEM16G 14.8 GiB
[ 4.201455] mmcblk0: p1 (system) p2 (userdata) p3 (media)
[ 11.794385] Restarting system.
[ 11.794487]
[ 11.794572] Restarting Linux version 2.6.35.14KalimochoAz+ ([email protected]) (gcc version 4.4.3 (GCC) ) #13 PREEMPT Wed Sep 21 15:59:01 CEST 2011
[ 11.794584]
[ 11.796704] arch_reset: attempting watchdog reset
I have a mytouch 4g rooted with visionary but it has a different emmc all together. I have searched the internet but didnt find anyone with the same emmc chip.
#cat /sys/class/block/mmcblk0/device/name
M4G1FB
#
And it now keeps rebooting randomly. i have flashed roms, kernels, wiped, wiped in different file systems(ext4 and ext3) but still keeps rebooting.
It sometimes gets stuck on the splash screen sometimes in bootanimation. it has even rebooted in recovery twice.
Help???
Dunno wat to do. I dont get any of those errors in recovery.
What could the problem be?
Edit: I dont think its the battery cause after those reboots it hold it charge, for example if i was left with 50% battery before it rebooted, i still would have that same 50% once its done with the reboot.
So i have just runned lastkmsg and this is what i got.
[ 411.407928] unwind: Unknown symbol address c0052e4c
[ 411.408172] unwind: Index not found c0052e4c
[ 411.408294] Code: e59f00b8 e59f10b8 e59f20a0 eb0e4246 (e5943080)
[ 411.408508] ---[ end trace da227214a82491ba ]---
[ 411.408630] Kernel panic - not syncing: Fatal exception in interrupt
[ 411.408843] unwind: Unknown symbol address c0034b88
[ 411.408966] unwind: Index not found c0034b88
[ 411.409179] Rebooting in 5 seconds..
[ 416.401153] Restarting Linux version 2.6.32.21-g899d047 ([email protected])
(gcc version 4.4.0 (GCC) ) #1 PREEMPT Tue Oct 26 16:10:01 CST 2010
[ 416.401153]
[ 416.401489] unwind: Unknown symbol address c0034b88
[ 416.401702] unwind: Index not found c0034b88
[ 416.401824] ARM9 has CRASHED
[ 416.401947] smem: DIAG '[WCDMA] 04:13:52 FATAL: (cm :Undef :65535) Excepti
on detected (irq:0)
[ 416.401977] '
5 Corrected bytes, 0 unrecoverable blocks
Can anyone tell me why it keeps rebooting??
FYI, if someone gives me the right response, I will paypal $50 in their account. This is how desperate I am.
I have spent a week trying to enable kernel level debugging over the serial jack port and have got nowhere. Every time I enable them, I get a number of errors. I've gone through endless tutorials and books on the subject, but nothing seems to work properly.
This is the kprobe self test at boot time:
Code:
[ 6.502088] Internal error: Oops - undefined instruction: 0 [#1] PREEMPT SMP ARM
[ 6.508480] Modules linked in:
[ 6.511517] CPU: 0 Not tainted (3.4.0-geaa8415 #1)
[ 6.516675] PC is at kprobe_arm_test_cases+0x520/0x18bac
[ 6.521931] LR is at 0x7
[ 6.524484] pc : [<c010e59c>] lr : [<00000007>] psr: 00000013
[ 6.524486] sp : ee04fdf8 ip : 21522d52 fp : 21522a52
[ 6.535939] r10: 21522b52 r9 : 21522852 r8 : 21522952
[ 6.541118] r7 : 21522652 r6 : 21522752 r5 : 21522452 r4 : 21522552
[ 6.547658] r3 : 21522252 r2 : 21522352 r1 : 21522052 r0 : 21522152
[ 6.554136] Flags: nzcv IRQs on FIQs on Mode SVC_32 ISA ARM Segment kernel
[ 6.561461] Control: 10c5787d Table: 0000406a DAC: 00000015
[ 6.567159]
[ 6.567160] PC: 0xc010e51c:
[ 6.571409] e51c 6c646e61 31720965 72202c34 72202c30 202c3331 206c736c 00343172 00000001
[ 6.579570] e53c f00f00ff 00000e01 00000008 00002000 000c000c e320f000 d000ee1d e320f000
[ 6.587729] e55c ebfffcfd ebfffcf6 09646e61 2c323172 2c637020 34317220 6f72202c 31722072
[ 6.595889] e57c 00000034 00000e01 f00f00ff 00000e01 00000007 00002000 000c000c e7f001f8
[ 6.604051] e59c e00fce7e e7f001f8 ebfffceb ebfffce4 09646e61 2c343172 2c307220 2c637020
[ 6.612209] e5bc 6c736c20 34317220 00000000 00000001 f00f00ff 00000e01 00000008 00002000
[ 6.620368] e5dc 000c000c e320f000 e000ee1f e320f000 ebfffcd9 ebfffcd2 65646e61 30720971
[ 6.628529] e5fc 7220202c 202c3131 66783023 00000035 00000b01 12345678 00002000 000c000c
KGDB boot time test:
Code:
[ 198.615183] WARNING: at drivers/misc/kgdbts.c:813 run_simple_test+0x11c/0x29c()
[ 198.622441] Modules linked in:
[ 198.625482] [<c010e414>] (unwind_backtrace+0x0/0x144) from [<c0a4b118>] (dump_stack+0x20/0x24)
[ 198.634077] [<c0a4b118>] (dump_stack+0x20/0x24) from [<c0194138>] (warn_slowpath_common+0x5c/0x74)
[ 198.643048] [<c0194138>] (warn_slowpath_common+0x5c/0x74) from [<c019417c>] (warn_slowpath_null+0x2c/0x34)
[ 198.652685] [<c019417c>] (warn_slowpath_null+0x2c/0x34) from [<c0510f3c>] (run_simple_test+0x11c/0x29c)
[ 198.662058] [<c0510f3c>] (run_simple_test+0x11c/0x29c) from [<c0510be4>] (kgdbts_put_char+0x30/0x38)
[ 198.671174] [<c0510be4>] (kgdbts_put_char+0x30/0x38) from [<c01feae0>] (put_packet+0xa8/0x120)
[ 198.679737] [<c01feae0>] (put_packet+0xa8/0x120) from [<c01ff51c>] (gdb_serial_stub+0x348/0x1060)
[ 198.688620] [<c01ff51c>] (gdb_serial_stub+0x348/0x1060) from [<c01fe028>] (kgdb_cpu_enter+0x318/0x6a4)
[ 198.697911] [<c01fe028>] (kgdb_cpu_enter+0x318/0x6a4) from [<c01fe5a0>] (kgdb_handle_exception+0x94/0x1b0)
[ 198.707545] [<c01fe5a0>] (kgdb_handle_exception+0x94/0x1b0) from [<c010d84c>] (kgdb_compiled_brk_fn+0x38/0x40)
[ 198.717528] [<c010d84c>] (kgdb_compiled_brk_fn+0x38/0x40) from [<c01000fc>] (do_undefinstr+0xfc/0x20c)
[ 198.726816] [<c01000fc>] (do_undefinstr+0xfc/0x20c) from [<c0a5da28>] (__und_svc+0x48/0x60)
[ 198.735114] Exception stack(0xee04fe78 to 0xee04fec0)
Also, I compiled my own kernel and enabled module loading, but when I try and load my own module I get this error:
127|[email protected]:/data/local/tmp # insmod ./kgdboc.ko
insmod: init_module './kgdboc.ko' failed (Function not implemented)
My question is, has anyone got this working? There must be a way of doing it, or else there would be no point in having it in the kernel.
Does anyone know how to enable/initialise the FIQ debugger? I really don't want to go down the printk path.
Thanks
Have you gotten the magic sysrq key working over serial? Have you tried enabling just kdb? (I don't remember if you can do this, I've just used it on x86 with a keyboard and monitor).
Do you have the disassembly of the instruction that's causing the kprobes exception?
---------- Post added at 11:14 PM ---------- Previous post was at 10:59 PM ----------
Also, how are you invoking the kgdb test suite? What is it outputting before the warning? (Looks like it's an eprintk line at the end of a packet throwing a warning if the LXR code is the same as yours).
Have you tried just running the debugger without running the test suite? Maybe the test suite is broken?
My Moto X (2013, Dev Edition on VZW, 5.1 L w/ Xposed and root and unlocked BL) seem to spontaneous reboot a couple times a day, doing different things, usually Bluetooth is on while I'm doing something else, but can't find any other common factors. Sometimes I'm just checking Google Now topics, sometimes I'm checking links in Chrome (but also happens with Dolphin)
I searched XDA and it says to check out last_kmsg which I got, but it's rather... dense? But there seems to be no kernel error. The log mainly contains "wlan:" notes, until it reaches the following:
[ 1021.376560,1] wlan: [1142:E :HDD] wlan_hdd_set_filter: Packet Filter Request
: FA 1 params 2
[ 1021.376651,0] wlan: [1118:E :CTL] Data Offset 4 Data Len 6
[ 1021.376682,0]
[ 1021.376834,0] wlan: [1118:E :CTL] CData: 51:51:255:154:134:164
[ 1021.376834,0]
[ 1021.376956,0] wlan: [1118:E :CTL] MData: 0:0:0:0:0:0
[ 1021.376956,0]
[ 1021.377658,0] wlan: [1118:E :CTL] UsData Off 8 UsSend 68 cfg -549414016
[ 1021.377780,0] wlan: [1118:E :CTL] Out: FID 3 FT 1
[ 1021.377841,0] wlan: [1118:E :CTL] NParams 2 CT 0
[ 1021.377903,0] wlan: [1118:E :CTL] Outroto 2 Comp Flag 1
[ 1021.377903,0]
[ 1021.378086,0] wlan: [1118:E :CTL] Data Offset 6 Data Len 2
[ 1021.378086,0]
[ 1021.378238,0] wlan: [1118:E :CTL] CData: 8:6:0:0:0:0
[ 1021.378238,0]
[ 1021.378360,0] wlan: [1118:E :CTL] MData: 0:0:0:0:0:0
[ 1021.378360,0]
[ 1021.378543,0] wlan: [1118:E :CTL] Outroto 2 Comp Flag 1
[ 1021.378543,0]
[ 1021.378666,0] wlan: [1118:E :CTL] Data Offset 32 Data Len 4
[ 1021.378666,0]
[ 1021.378849,0] wlan: [1118:E :CTL] CData: 10:0:0:4:0:0
[ 1021.378849,0]
[ 1021.379032,0] wlan: [1118:E :CTL] MData: 0:0:0:0:0:0
[ 1021.379032,0]
[ 1027.570333,1] SysRq : Emergency Remount R/O
[ 1027.621913,1] EXT4-fs (mmcblk0p36): re-mounted. Opts: (null)
[ 1027.661437,1] EXT4-fs (mmcblk0p23): re-mounted. Opts: (null)
[ 1027.671447,1] pn544 reboot notification received
[ 1027.671509,1] pn544_dev_ioctl ven_logic_high = 1.
[ 1027.671570,1] pn544_dev_ioctl ven_logic_low = 0.
[ 1027.671661,1] pn544_dev_ioctl discharge_delay = 0.
[ 1027.671722,1] pn544_dev_ioctl : power off
[ 1027.705997,1] pn544 calling ioctl power off returned = 0
[ 1027.706058,1] mmc0: reboot notification received
[ 1027.759132,1] EXT4-fs (mmcblk0p28): re-mounted. Opts: (null)
[ 1027.759377,1] Emergency Remount complete
[ 1028.306851,1] Disabling non-boot CPUs ...
[ 1028.308896,0] CPU1: shutdown
[ 1028.314115,0] Restarting system with command ''.
[ 1028.314176,0] Current task:init(1) Parent task:swapper/0(0)
[ 1028.314298,0] Going down for restart now
ABOOT.GIT = MBM-NG-V30.BE-0-g34b7ccb
TZ.GIT = MBM-NG-V30.BE-0-gc10fd11
RPM.GIT = MBM-NG-V30.BE-0-g2aa06de
SBL3.GIT = MBM-NG-V30.BE-0-gb2b97c8
SBL2.GIT = MBM-NG-V30.BE-0-gb2b97c8
SBL1.GIT = MBM-NG-V30.BE-0-gb2b97c8
Linux version 3.4.42-g756aa87 ([email protected]) (gcc version 4.8 (GCC) ) #1 S
MP PREEMPT Mon Aug 17 07:58:00 CDT 2015
RAM: Samsung, S4 SDRAM, 2048 MB, MR5:0x01, MR6:0x11, MR7:0x00, MR8:0x18
ACPU Krait PVS: 2 Hexagon: 1 Fuse: 0x10800
socinfo: id=138, ver=1.1, raw_id=2017, raw_ver=1, hw_plat=0, hw_plat_ver=65536,
hw_plat_subtype=0
No errors detected
Click to expand...
Click to collapse
So for 6 seconds WiFi went blank, which caused OS to panic and reboot? I'm a little confused. Where do I go and what do I read to figure out what's my phone's problem?
kschang said:
My Moto X (2013, Dev Edition on VZW, 5.1 L w/ Xposed and root and unlocked BL) seem to spontaneous reboot a couple times a day, doing different things, usually Bluetooth is on while I'm doing something else, but can't find any other common factors. Sometimes I'm just checking Google Now topics, sometimes I'm checking links in Chrome (but also happens with Dolphin)
I searched XDA and it says to check out last_kmsg which I got, but it's rather... dense? But there seems to be no kernel error. The log mainly contains "wlan:" notes, until it reaches the following:
So for 6 seconds WiFi went blank, which caused OS to panic and reboot? I'm a little confused. Where do I go and what do I read to figure out what's my phone's problem?
Click to expand...
Click to collapse
Greetings,
As a senior member of this site, with a device that has a dedicated forum, you are expected to know how to find your way. XDA Assist is for new members who need help finding their way, it is not a help desk for troubleshooting issues. Please re-read the sticky threads for this forum so you have a better understanding of what we do here.
Regards,
The_Merovingian
Forum Moderator
Thread closed.
Hello Android kernel hackers,
I am trying to port the current ASB-patched LOS12.1 (github "cm12-amami") to a Teclast 98 (M1E9) tablet for which kernel sources are missing. My build completes fine, however, I run into a boot loop due to kernel panic with an (at least for me) totally unhelpful stack trace:
During init.rc processing, the kernel panics on logd startup when logd tries to read from /proc/meminfo with the following stack trace:
Code:
[ 126.200788]00:02:29.656321 openat(AT_FDCWD, "/proc/meminfo", O_RDONLY) = 4
[ 126.200956]00:02:29.656496 fstat(4, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
[ 126.201077]00:02:29.656614 mprotect(0x7faf52b000, 4096, PROT_READ|PROT_WRITE) = 0
[ 126.201187]00:02:29.656726 mprotect(0x7faf52b000, 4096, PROT_READ) = 0
[ 126.202709]00:02:29.656833 read(4,
* KERNEL PANIC HAPPENS HERE!!! *
Code:
[ 126.202739]<1> (1)[949:logd]<1>start....
[ 126.202805]<1> (1)[949:logd]Unable to handle kernel NULL pointer dereference at virtual address 00000016
[ 126.202817]<1> (1)[949:logd]pgd = ffffffc070dee000
[ 126.202828]<1> (1)[949:logd][00000016] *pgd=0000000000000000 (1)[949:logd]
[ 126.202846]<1> (1)[949:logd][KERN Warning] ERROR/WARN forces debug_lock off!
[ 126.202854]<1> (1)[949:logd][KERN Warning] check backtrace:
[ 126.202868]<1> (1)[949:logd]CPU: 1 PID: 949 Comm: logd Tainted: G W 3.10.65+ #1
[ 126.202878]<1> (1)[949:logd]Call trace:
[ 126.202899]<1> (1)[949:logd][<ffffffc000088f50>] dump_backtrace+0x0/0x16c
[ 126.202913]<1> (1)[949:logd][<ffffffc0000890cc>] show_stack+0x10/0x1c
[ 126.202931]<1> (1)[949:logd][<ffffffc0009a69a0>] dump_stack+0x1c/0x28
[ 126.202947]<1> (1)[949:logd][<ffffffc0002f7210>] debug_locks_off+0x40/0x5c
[ 126.202960]<1> (1)[949:logd][<ffffffc00009a260>] oops_enter+0xc/0x28
[ 126.202974]<1> (1)[949:logd][<ffffffc000089100>] die+0x28/0x1d8
[ 126.202989]<1> (1)[949:logd][<ffffffc0009a49ec>] __do_kernel_fault.part.5+0x70/0x84
[ 126.203003]<1> (1)[949:logd][<ffffffc000094260>] do_page_fault+0x348/0x34c
[ 126.203017]<1> (1)[949:logd][<ffffffc000094350>] do_translation_fault+0x40/0x4c
[ 126.203030]<1> (1)[949:logd][<ffffffc0000813fc>] do_mem_abort+0x38/0x98
which does not seem to uncover the root cause, but rather the root cause stack trace seems to be:
Code:
[ 133.341226]<1>-(1)[949:logd]Call trace:
[ 133.341239]<1>-(1)[949:logd][<ffffffc0001f37d8>] meminfo_proc_show+0x50/0x3c4
[ 133.341255]<1>-(1)[949:logd][<ffffffc0001aefb8>] seq_read+0x1a4/0x40c
[ 133.341271]<1>-(1)[949:logd][<ffffffc0001ebeec>] proc_reg_read+0x4c/0x7c
[ 133.341285]<1>-(1)[949:logd][<ffffffc00018e75c>] vfs_read+0x88/0x170
[ 133.341298]<1>-(1)[949:logd][<ffffffc00018ebf0>] SyS_read+0x40/0x8c
[ 133.341310]<1>-(1)[949:logd]Code: 52800001 91326000 97fe67c1 aa0003f3 (f9400c00)
[ 133.341322]<1>-(1)[949:logd]---[ end trace 1b75b31a2719ed20 ]---
[ 133.341332]<1>-(1)[949:logd]Kernel panic - not syncing: Fatal exception
[ 133.341423]<1>-(1)[949:logd]mrdump: cpu[1] tsk:ffffffc073a3e000 ti:ffffffc070e64000
[ 134.241428]<1>-(1)[949:logd]
Most interestingly, the exact same kernel blob can successfully boot stock Android 5.1 and successfully read from /proc/meminfo when booted from stock boot.img while it crashes with my LOS12.1 build boot.img.
bootimg.cfg (using abootimg) is identical in both cases (except the boot size):
Code:
bootsize = 0x780000
pagesize = 0x800
kerneladdr = 0x40080000
ramdiskaddr = 0x44000000
secondaddr = 0x40f00000
tagsaddr = 0x4e000000
name = 1513588375
cmdline = bootopt=64S3,32N2,64N2 androidboot.selinux=permissive
Thanks a million in advance for any ideas or pointers about what might be going wrong with this stock kernel blob and my LOS12.1 build with regards to meminfo_proc_show()! :highfive:
awl14
Issue resolved!
Finally resolved by making changes (a whole number of, so I haven't tracked it down to one particular change) to my CM12.1 build's system partition, making it resemble the stock image more closely.
I still don't have any clues why the kernel would crash on reading from /proc/meminfo due to "wrong"/buggy contents in the system partition (/system file system), but as the issue is resolved, this can be regarded as a proof that such content in system can indeed matter in a critical way for the behaviour of the kernel...
My custom ROM for Teclast 98 (M1E9) runs fine now, I will publish a download link soon on xda.
Panic caused by kernel reading file /system/bin/cpuinfo
I encountered the same issue and was able to find the root cause. The kernel I'm dealing with has been modified by Chinese crooks who fake the amount of memory in the device by intercepting meminfo_proc_show(). In this routine, they read the file /system/bin/cpuinfo, apparently extracting the value to be shown to the user as the memory size from that file. The code does not even test the return code from the file opening routine, and simply crashes the kernel if the file is not present.