[ROM][4.4.2][April 8] SlimKat DLX ((Build 4.1)) -unofficial- Looking For A New Maintainer

zawata · Jun 30, 2014

crpalmer said:
If omni says that you need to revert it then you probably will. As a word of warning, that was literally the 5th commit in the M8 bringup. That says omni is going to be very different...

another few questions

1. say the kernel was initializing and turning everything on and it encountered and irrecoverable error(huge major error(cant give an example)) would the kernel stop dead in its tracks and complain about that error or run through the rest of the initialization and still attempt to boot the device?

2. would not being able to register one of the CPU cores prevent the device from booting?

Code:

[    1.909446] c0      1 MSM_DCVS: msm_dcvs_register_core: msm_dcvs_register_core: scm register core fail handle = 1 ret = -22
[    1.909476] c0      1 Unable to register core for 0
[    1.909476] c0      1 msm_dcvs_gov: probe of msm_dcvs_gov failed with error -22

3. what does the number that comes after the c0 but before the message mean? is it like how important the message is? the higher, the more urgent? or is it like a device identifier code?

4. would an error in the SEpolicy prevent a device from booting?

5. if the device gets stuck at the HTC screen, would the last_kmsg be the place to look for the error?

as you can see from these questions, the device wont boot in the rom, its stuck on the HTC screen

crpalmer · Jun 30, 2014

zawata said:
another few questions

1. say the kernel was initializing and turning everything on and it encountered and irrecoverable error(huge major error(cant give an example)) would the kernel stop dead in its tracks and complain about that error or run through the rest of the initialization and still attempt to boot the device?

2. would not being able to register one of the CPU cores prevent the device from booting?

Code:

[ 1.909446] c0 1 MSM_DCVS: msm_dcvs_register_core: msm_dcvs_register_core: scm register core fail handle = 1 ret = -22 [ 1.909476] c0 1 Unable to register core for 0 [ 1.909476] c0 1 msm_dcvs_gov: probe of msm_dcvs_gov failed with error -22

3. what does the number that comes after the c0 but before the message mean? is it like how important the message is? the higher, the more urgent? or is it like a device identifier code?

4. would an error in the SEpolicy prevent a device from booting?

5. if the device gets stuck at the HTC screen, would the last_kmsg be the place to look for the error?

as you can see from these questions, the device wont boot in the rom, its stuck on the HTC screen

If there is a really bad error, the kernel usually panics which will cause it to reboot. The MSM_DCVS errors look pretty bad but maybe I just haven't noticed it in a normal boot. You can check by booting something that works and looking at its dmesg output to see if there are similar messages.

It's hard to know where to look because it's hard to tell if the kernel is what's making it not work or the android system. You should plug it into a linux computer and let it sit for a fairly long time and see if you can get an adb connection. If so, it may tell you more.

The boot animation requires that the android system be running so you're right at the point where it could be failing to start or the kernel may not be getting far enough to start the android runtime.

zawata · Jun 30, 2014

crpalmer said:
If there is a really bad error, the kernel usually panics which will cause it to reboot. The MSM_DCVS errors look pretty bad but maybe I just haven't noticed it in a normal boot. You can check by booting something that works and looking at its dmesg output to see if there are similar messages.

It's hard to know where to look because it's hard to tell if the kernel is what's making it not work or the android system. You should plug it into a linux computer and let it sit for a fairly long time and see if you can get an adb connection. If so, it may tell you more.

The boot animation requires that the android system be running so you're right at the point where it could be failing to start or the kernel may not be getting far enough to start the android runtime.

in the last kmesg after the error i posted above it then posted for about .2 seconds(a VERY long time) thermal id stats and then froze(?) the system and checked every 4 seconds for something up until i decided to hard reboot the phone(~105 seconds)

it just posted this until posting a bunch a battery stats at 1 minute

Code:

[   39.990691] c3      1 init: untracked pid 546 exited
[   45.205005] c3      1 request_suspend_state: wakeup (0->0) at 45193146118 (2014-06-30 03:25:34.810717918 UTC)
[   45.205920] c3      1 init: untracked pid 581 exited
[   49.415595] c3      1 request_suspend_state: wakeup (0->0) at 49403767209 (2014-06-30 03:25:39.021339009 UTC)
[   49.416786] c3      1 init: untracked pid 614 exited
[   54.637204] c3      1 request_suspend_state: wakeup (0->0) at 54625375631 (2014-06-30 03:25:44.242916910 UTC)
[   54.638180] c3      1 init: untracked pid 649 exited
[   59.856279] c3      1 request_suspend_state: wakeup (0->0) at 59844420343 (2014-06-30 03:25:49.461992143 UTC)
[   59.857317] c3      1 init: untracked pid 681 exited

nothing came after that except checking the proximity sensor for "pocket mode"

is adb run in the kernel? i thought it was a system process(-ish sort of thing) that it was executed by the runtime

i think i might found the problem, the zip is 160mb compared the most recent m7 zip which is 180mb

i dont know what would be missing though, i rebuilt and switched out some of the repos(back to omni's repos) and got the same size in terms of zip size
i think i might trade the CM kernel for omni kernel and rebuild and see how that works

Topics

Topics

[ROM][4.4.2][April 8] SlimKat DLX ((Build 4.1)) -unofficial- Looking For A New Maintainer

zawata

Senior Member

crpalmer

Inactive Recognized Developer

zawata

Senior Member

Similar threads

Top Liked Posts

New posts