ok some might have seen this strange board in a thread...
I had purchased a broken g1... and i talked about this strange EVT1 in hboot, and it would get stuck on G1 logo
so I waited until i got a usb/serial cable and jtag... I have both and i went on with the whole process
everything worked, up until i tried to get into the recovery, this device will not go into recovery for some reason.
==update==
looking at serial what its displaying... and it does go into recovery when the display turns off, the device is on, i just get error for the display and few others...
I had first the radio that was stated in the jtag process the 3.22.26.17
so hboot stating evt1 32b and were dread1000 or something like that supposed to be... i get drea*****
i researched and ran into other ppl that had a magic/sapphire that was evt 32b
fastboot/hboot is working at that point
here is a pic if you dont believe me
serial display of boot up... txt file is for boot recovery boot up
Code:
OEMSBL VERSION: 3.22.26.17
OEMSBL Build Date: Jan 17 2010 12:08:33
PLATFORM: DREAM
PID: 31
PLATFORM ID: 0
Boot CE manually...
Done.
+16 bit
-msm_nand_probe
[MDDI_HW_ERR] mddi_send_rtd fail!!
[MDDI_EID] mddi_eid_probe enter.
[EID_HW_ERR] mddi_eid_probe: Unknown panel type!!
GetModelName- Default[DREA*****]
Board_PID : 0x1F
Wlan data header ++++++++++++++++++++
Signature : 0xEE1251
UpdateStatus : 0x1
UpdateCount : 0x1
BodyLength : 0x2F0
BodyCRC : 0xC8545E10
aDieId(0) : 0x0
aDieId(1) : 0x0
aDieId(2) : 0x0
aDieId(3) : 0x0
countryID : 0x10
Wlan data header --------------------------
chipset_bootmode reset_reason:0
ARM11 Boot Mode: 0
Platform: HBOOT-7201A
###[ Fastboot Mode ]###
nobody has a clue
did some more forum searching...
in this thread someone states
http://forum.xda-developers.com/showpost.php?p=7582535&postcount=1530
http://forum.xda-developers.com/showpost.php?p=7967905&postcount=1538
that E is for engineering and P is for production?
so it seems that i can get into recovery, BUT there is an error, right when i go into recovery the display is off and below errors and txt file from the serial say the rest of the story...
Code:
boot reason: PM_KPD_PWR_KEY_ON_RT_ST
(PowerOn Status,Boot Reason)=(1,1)
NAND_FLASH_READ_ID : HYNIX_256MB_FLASH_128MB_SDRAM
ARM9_BOOT_MODE0, Boot Android
+16 bit
-msm_nand_probe
[MDDI] Bitmap_Width = 480
[MDDI] Bitmap_Height = 640
[MDDI] RGB_Capability = 0x8888
[MDDI] Mfr_Name = 0xD263
[MDDI] Product_Code = 0x0
GetModelName- Default[DREA*****]
Board_PID : 0x1F
Wlan data header ++++++++++++++++++++
Signature : 0xEE1251
UpdateStatus : 0x1
UpdateCount : 0x1
BodyLength : 0x2F0
BodyCRC : 0xC8545E10
aDieId(0) : 0x0
aDieId(1) : 0x0
aDieId(2) : 0x0
aDieId(3) : 0x0
countryID : 0x10
Wlan data header --------------------------
chipset_bootmode reset_reason:0
ARM11 Boot Mode: 0
Platform: HBOOT-7201A
setup_tag addr=0xA0000100 cmdline add=0x98071C80
TAG:Ramdisk OK
TAG:smi ok, size = 64
TAG:hwid 0x0
TAG:skuid 0xFFFFFFFF
TAG:hero panel = 0x0
TAG:engineerid = 0xFFFFFFFF
Device CID is not super CID
CID is T-MOB010
setting.cid::T-MOB010
serial number: 0123456789*******
commandline from head: no_console_suspend=1 console=null
command line length =331
active commandline: board_trout.disable_uart3=0 board_trout.usb_h2w_sw=0 board_trout.disable_sdcard=0 smisize=64 androidboot.baseband=2.22.23.02 androidboot.cid=T-MOB010 androidboot.carrier=TMUS androidboot.keycaps=qwerty androidboot.mode=normal androidboot.serialno=0123456789*****
androidboot.bootloader=1.33.2005 no_console_suspend=1 console=null
PARTITIOM_NUM_MAX =6 Valid partition num=6
(note put **** in serial number)
im going to attach txt of the recovery boot up
this is from serial cable while home + power (recovery mode)
note this is with the 1.7 dream recovery and the 2.22.23.02 dream radio
also worked fine with the jtag radio and recovery, i believe same error
look at the error, seems with display? as i can pass commands blindly (tried to flash from memory card, but still i believe the device then reboots...)
ignore other errors as only mobo + display and daughter board are connected...
this is one error while going into recov:
hsusb: ONLINE -> OFFLINE
[ 7.667053] ekt8232_probe enter.
[ 7.670471] elan-touch 0-0010: without platform data??!!
[ 7.876098] elan-touch 0-0010: __hello_packet_handler: failed!
[ 7.882019] looks like it's not Elan, so..i'll quit
[ 7.926300] msm_i2c msm_i2c.0: error, status c8
[ 7.931091] msm_i2c msm_i2c.0: Error during data xfer (-5)
[ 7.936828] i2c_smbus_write_byte_data failed
[ 7.941375] msm_i2c msm_i2c.0: error, status c8
[ 7.946563] msm_i2c msm_i2c.0: Error during data xfer (-5)
[ 8.056213] msm_i2c msm_i2c.0: error, status 43c8
[ 8.061157] msm_i2c msm_i2c.0: Error during data xfer (-5)
[ 8.183258] msm_i2c msm_i2c.0: error, status c8
[ 8.188140] msm_i2c msm_i2c.0: Error during data xfer (-5)
[ 8.298706] msm_i2c msm_i2c.0: error, status c8
[ 8.303558] msm_i2c msm_i2c.0: Error during data xfer (-5)
[ 8.418060] msm_i2c msm_i2c.0: error, status c8
[ 8.422912] msm_i2c msm_i2c.0: Error during data xfer (-5)
[ 8.538055] msm_i2c msm_i2c.0: error, status c8
[ 8.542907] msm_i2c msm_i2c.0: Error during data xfer (-5)
[ 8.658050] msm_i2c msm_i2c.0: error, status c8
[ 8.662872] msm_i2c msm_i2c.0: Error during data xfer (-5)
[ 8.778167] msm_i2c msm_i2c.0: error, status c8
[ 8.783020] msm_i2c msm_i2c.0: Error during data xfer (-5)
[ 8.898071] msm_i2c msm_i2c.0: error, status c8
[ 8.902893] msm_i2c msm_i2c.0: Error during data xfer (-5)
[ 9.018066] msm_i2c msm_i2c.0: error, status c8
[ 9.022918] msm_i2c msm_i2c.0: Error during data xfer (-5)
[ 9.137939] i2c_smbus_read_byte_data failed
[ 9.142425] synaptics-rmi-ts: probe of 0-0020 failed with error -5
[ 9.150451] GPIO Input Driver: Start gpio inputs for trout-nav in interrupt mode
the error that keeps on repeating is:
msmfb_pan_display timeout waiting for frame start, 1 1
i attached hboot commands?!?
so i was playing with a lot of hboot commands that were in that txt file
i ran into writesku/readsku
so what did i do? write some diff words... and result? wow things change...
so how did i fix? simple plugged in a working G1 mobo and copied all the readsku info
now my EVT1 magically turned into PVT, though it now reads DREAM and not DREA**** and not DREAM1000 either... oh well
and i went right into recovery after rebooting
here are the contacts of readsku before and after (is cloned from other mobo)
messed up EVT mobo
Code:
hboot>readsku
skuid item:FunctionSKUField
index:0x0, value:0x0
skuid item:PCBIDField
index:0x1, value:0xFFFF
skuid item:RFSKUIDField_D0
index:0x2, value:0xFFFFFFFF
skuid item:RFSKUIDField_D1
index:0x3, value:0xFFFFFF
skuid item:RFSKUIDField_D2
index:0x4, value:0xFFFFFFFF
skuid item:RFSKUIDField_D3
index:0x5, value:0xFFFFDFFF
skuid item:RFSKUIDField_D4
index:0x6, value:0xFFFFBFFF
skuid item:RFSKUIDField_D5
index:0x7, value:0xEFFFFFFF
skuid item:RFSKUIDField_D6
index:0x8, value:0xFFFFFFFF
skuid item:RFSKUIDField_D7
index:0x9, value:0xFFFFFFFF
skuid item:SKUIDChecksum
index:0xA, value:0xFFFFFF
skuid item:EngineerID
index:0xB, value:0xFFFFFFFF
copy from working mobo
Code:
hboot>readsku
skuid item:FunctionSKUField
index:0x0, value:0x1BE00
skuid item:PCBIDField
index:0x1, value:0x80FFFFFF
skuid item:RFSKUIDField_D0
index:0x2, value:0x12
skuid item:RFSKUIDField_D1
index:0x3, value:0x20000D4
skuid item:RFSKUIDField_D2
index:0x4, value:0xFFFFFFFF
skuid item:RFSKUIDField_D3
index:0x5, value:0xFFFFFFFF
skuid item:RFSKUIDField_D4
index:0x6, value:0xFFFFFFFF
skuid item:RFSKUIDField_D5
index:0x7, value:0xFFFFFFFF
skuid item:RFSKUIDField_D6
index:0x8, value:0xFFFFFFFF
skuid item:RFSKUIDField_D7
index:0x9, value:0xFFFFFFFF
skuid item:SKUIDChecksum
index:0xA, value:0xD8A37369
skuid item:EngineerID
index:0xB, value:0xFFFFFFFF
as you can see the first line is the key and then others too...
this explains all the serial code that i saw, interesting that all the flashing erasing and what not did not touch these values
all those errors were because there was no id to the device and recovery couldnt ID it and couldnt init the display, and not only that funny how the keyboard maping wasnt working either... so its possible to change your device to whatever I guess, its just an ID tag
I had the problem on stock few month back and thought it was time for me to go custom Rom while wauting for my OnePlus invite. So I installed Cyanogenmod. I did my homework, I think, and got started with CyanogenMod 11 M6. I am:
- Bootloader 2.18.0000 unlocked ( and *** TAMPERED *** ) ? for whatever that means.
- S-ON (so I use `./fastboot flash boot boot.img` everytime)
- non rooted (because some app I need do not like rooted phone), but CWM is quite flexible for that,
I use CWM revovery:recovery-clockwork-touch-6.0.4.8-evita.img
I am relatively novice to all this so you have to be patient as I do not always understand all I am doing. I am using:
gapps-kk-20140105-signed.zip
I installed the following roms:
cm-11-20140504-SNAPSHOT-M6-evita.zip
cm-11-20140608-SNAPSHOT-M7-evita.zip
cm-11-20140708-SNAPSHOT-M8-evita.zip
cm-11-20140804-SNAPSHOT-M9-evita.zip
cm-11-20140829-NIGHTLY-evita.zip
I tend to do the Wipe data and Factory reset on CWM when applying a new ROM.
I still had issues with M6 (automatic switch off). I found that M7 was relatevly stable. With M8 & M9, the device kept turning itself off after a while (anything between 1 min to 2 days). It sometime turn itself off whlibe booting, or even when I am in fastboot.
I managed to get a last_kmsg, and that shows something like this at the end:
Code:
...
[ 64.695956] mipi_dsi_clk_enable: dsi_escWclk - clk_set_rate failed
[ 64.712864] mipi_dsi_clk_enable: dsi_esc_clk - clk_set_rate failed
[ 64.730016] mipi_dsi_clk_enable: dsi_esc_clk - clk_set_rate failed
[ 64.755379] mipi_dsi_clk_enable: dsi_esc_clk - clk_set_rate failed
S 64.775644] mipi_dsi_clk_enable: dsi_esc_clk - clk_set_rate failed
[ 65.549793] mipi_dsi_clk_enable: dsi_esc_clk - clk_set_rate failed
[ 65.56¶671] mipi_dsi_clk_enable: dsi_esc_clk - clk_set_rate failed
[ 65.771188] [BATT] batT_worker: total_time since last batt update = 60030 ms. at 65766048772 (2014-08-30 11:14:23.808850840 UTC)
[ 65.786571] [BATT][BMS] FCC=0784000,UC=0,RC=963360,CC=12727,CC_reset=0,RUC=950633,SOC=54,SOC_R=511300,start_percent=-22,end_percent=-22,OCV=3840441,OCV_raw=3855441,rbatt=128,rbatt_sf=0,batt_temp=327,soc_rbatt=0,last_rbatt=-22,V_unusable_uv=3000000,pc_unusable=0,rc_pc=54,scalefactor=100,no_ocv_update_is=0,consistent=0
[ 65.814283] [BATT][BMS] soc = 54 reporting last_soc = 53
[ 65.818922] [BATT][BMS] pm8921_bms_get_batt_soc: state_of_charge=53, store_soc_ui=-1, last_good_ocv_uv=3840441, raw.cc=2957555, stored_cc_uv:2957555, currtime_ms=647990725
[ 65.834274] [BATT][CHG] usbin_ov_irq_state:1 -> 1 [1,0,1]
[ 65.839615] [BATT] remap: no soc drop and no additional 1%, ui:53%
[ 65.845811] [BATT][BMS] pm8921_bms_get_battery_ui_soc: batt_stored_soc: 0
[ 65.852525] [BATT] htc_batt_get_battery_ui_soc: original soc: 53, changed soc: 53. at 65848758982 (2014-08-30 11:14:23.890177113 UTC)
[ 65.866870] [BATT][BMS] soc = 54 reporting last_soc = 53
[ 65.879719] [BATT][CHG] V=3595 mV, I=873 mA, T=32 C, SoC=53%, FCC=1784000, id=256 mV, H=1, P=1, CHG=1, S=0, FSM=0, AC=0, USB=0, DC=0, WLC=0 iusb_ma=100, usb_target_ma=0, OVP=0, UVP=0, TM=0, eoc_count/by_curr=0/0, vbatdet_low=1, is_ac_ST=0, batfet_dis=0x2, pwrsrc_dis=0x1, is_full=0, temp^fault=0, is_bat_warm/cool=0/0, btm_warm/cool=0/0, ichg=797 uA, vph_pwr=3567699 uV, usbin=7572 uV, dcin=11358 uV, pwrsrc_unDer_rating=0, usbin_critical_low_cnt=0, disable_reverse_boost_check=0, flag=0000, hsml_target_ma=0, vin_iin=4400, pj_exist=0
[ 65.893575] mipi_dsi_clk_enable:`dsi_esc_clk - clk_set_rate failed
[ 65.932946] [BATT][CHG] [irq1] 0110 1010 0000 000 [irq2] 0011 0000 1010 011[ 65.939081] KBATT][CHG] CNTRL=0x85,CNTRL_2=0x72,CNTRL_3=0x88,PBL_ACCESS1=0x4,PBL_ACCESS2=0x2¬SYS_CONFIG_1=0x3,SYS_CONFIG_2=0xd8,IBAT_SAFE=0x10,IBAT_MAX=0x10,VBAT_DET=0x7f,VDD_SAFE=0x30,VDD_MAX=0x30,VIN_MIN=0x6,VTRICKLE=0xfa,ITRICKLE=0x8a,ITERM=0x0,TCHG_MAX=0x7f,TWDOG=0xa0,TEMP_THRESH=0x94,COMP_OVR=0x0,BUCK_CTRL_TEST1=0x1,BUCK_CTRL_TEST2=0x8d,BUCK_CTRL_TEST3=0x91,CHG_TEST=0xd0,USB_OVP_CONTROL=0x42,USB_OVP_TEST=0xa0,DC_OVP_CONTROL=0x4c,DC_OVP_TEST=0xa0,REGULATION_LOOP_CONTROL=0x0
[ 65.982755] [BATT][BMS] CONTROL=0x99,OUTPUT0=0x8c,OUTPUT1=0x06,TOLERANCES=0x2f,BMS_TEST1=0x11,OCV_UPDATE_STORAGE=0xa0,read_cc=0x2968823,last_good_ocv=0x3840441,vbatt_for_rbatt=0x0,vsense_for_rbatt=0x0,ocv_for_rbatt=0x0,vsense_avg=0x9493, [irq]0010000
[ 66.004089] [BATT] ID=2,level=53,level_raw=53,vol=3604,temp=327,current=896700,chg_src=0,chg_en=0,pj_src=0,pj_level=0,full_bat=1800,over_vchg=0,batt_state=1,overload=0,ui_chg_full=0 at 66009082497 (2014-08-30 11:14:24.041771801 UTC)
[ 66.025362] [BATT] power_supply_changed: battery at 66018360690 (2014-08-30 11:14:24.063044501 UTC)
[ 66.033633] [BATT] batt_worker: done
[ 66.333923] [LS][cm3629] lightsensor_ioctl LIGHTSENSOR_IOCTL_ENABLE, value = 0
[ 66.344605] [LS][cm3629] lightsensor_disable
[ 66.353792] [LS][cm3629] lightsensor_release
[ 67.020265] mipi_dsi_clk_enable: dsi_esc_clk - clk_set_rate failed
[ 67.030489] mipi_dsi_panel_power: state : 0
[ 67.030489] mipi_dsi_panel_power: off
[ 67.071204] request_suspend_state: sleep (0->3) at 67060082039 (2014-08-30 11:14:25.108886100 UTC)
Y 67.079169] [LS][cm3629] cm3629_early_suspend
[ 67.084205] [PS][cm3621] capella_pl_sensor_lpm_power: enter lmp,OK
[ 67.089638] [TP] synaptics_ts_suspend: enter
[ 67.096871] [DISP] sii9234_early_suspend(isMHL=0)
[ 67.100564] [DISP] MhlTx: SiiMhlTxInitialize
[ 67.109781] [DISP] Drv: SiiMhlTxChipInitialize: 9244
[ 67.114298] [DISP] SiI 9234
[ 67.116496] [DISP] Drv: WriteInitialRegisterValues
[ 67.145368] [DISP] Drv: MHL 1.0 Compliant Clock
[ 67.181168] [DISP] Drv: InitCBuqRegs
[ 67.187913] [DISP] Drv: Switch To 3: pinAllowD3 = 1
[ 67.281580] [BMA250] GSensor Low Power Mode
[ 67.286983] [GSNR][MPU3050][TIMERIRQ]stop_timerirq: data->period = 66, data->run = 1
[ 67.798351] [VIB_PWM]pm8xxx_vib_enable vibrate period: 0 msec
[ 67.803082] [VIB_PM]pm8xxx_vib_sep_off
[ 68.688020] NOHZ: local_softirq_pending 08
[ 68.751747] NOHZ: local_softirq_pending 08
[ 69.146223] NOHZ: local_softirq_pending 08
[ 69.197192] NOHZ: local_softirq_pending 08
[ 69.583946] NOHZ: local_softirq_pending 08
[ 70.700961] NOHZ: local_softirq_pending 08
[ 71.692629] NOHZ: local_softirq_pending 08
[ 71.788768] NOHZ: local_softirq_pending 08
[ 71.804425] NOHZ: local_softirq_pending 08
[ 71.848527] NOHZ: local_softirq_pending 08
[ 72.792339] resout_irq_handler PMIC Initiated shutdown
[ 72.796459] PMIC Initiated shutdown cpu_power_off cpu=0
[ 72.801648] [K] Powering off the SoC
[ 72.805249] Calling scm to disable arbiter
[ 72.809308] SCM returned even when asked to busy loop rc=-4
[ 72.814832] waiting on pmic to shut msm down
=== EOF ===
I also ran an `./adb bugreport` command but that gave me 7MB of stuff I cannot understand..
Any idea to help resolve that automatic power off would be welcome.
Thanks
JM
If your phone is shutting off or rebooting while in fastboot mode, you're dealing with a hardware fault. It's a fault with the battery or the emmc.
Transmitted via Bacon
timmaaa said:
If your phone is shutting off or rebooting while in fastboot mode, you're dealing with a hardware fault. It's a fault with the battery or the emmc.
Click to expand...
Click to collapse
Oh dear... At least I know that it is not me playing up with flashing that put me into that state. Thanks for taking the time to read my post.
Hopefully it is not as bad as being a faulty emmc. Let's pray it is just the power button playing up and I can fix it myself. Phone is way out of warranty and maybe it is time to consider a nice upgrade.
Thanks
JM
Fixed: HTC One XL (evita) keeps dying on me..
jm_paulin said:
Let's pray it is just the power button playing up and I can fix it myself.
Click to expand...
Click to collapse
Ok, so after the excellent suggestion from @timmaaa it might well be hardware, I decided to open it and figure out what could go wrong. Had nothing to loose anyway. I just followed video PrArAes5liM on YouTube (good evening spam control), but used a credit card as I do not have the guitare thingy...
It is incredible the amount of crap that got into that phone over the last 2 years. So I brushed everything, cleaned the power button, and put it back together. Since then, not a problem... Okay, it is only 28 hours but that is nearly a record.
I also installed an app to switch the screen on using one of the sensor.
JM
Iam on omni ROM 6. When I attach my external HDD through a (powerd) otg cable my tabe doesn't detect it. It used to work before. Looking at the dmesg I get
241.787292] accessorry_id irq handler: dock_irq gpio val = 1
[ 241.787567] 30pin: duplicated otg connection event,ignore(1).
[ 241.791503] accessorry_id irq handler: dock_irq gpio val = 0
[ 242.488281] Accessory attached, adc=2728
[ 242.488708] adc change notified: acc_adc = 2728
[ 242.488922] 30pin_c: detect: device=0
[ 242.489166] cable detect: otg attach, current device = 0x0001
[ 242.489562] [espresso_usb_host_attach]
[ 242.489776] accessory_power: acc_device 0x0, new 0 : OFF
[ 242.490173] accessory_power: force turn off
[ 242.491638] otg espresso_otg_work(864): current device 0001
[ 242.492065] accessory_power: acc_device 0x0, new 2 : ON
[ 242.551055] accessorry_id irq handler: dock_irq gpio val = 0
[ 242.551483] 30pin: duplicated otg connection event,ignore(0
I rebooted several time but still I have the same message.
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.