| situ | vgrade_: This patch fixes lipstick crash http://pastie.org/9360382 | 09:08 |
|---|---|---|
| situ | morphis: Thanks for helping me fix it. | 09:08 |
| situ | I sent a pull request https://github.com/CyanogenMod/android_hardware_qcom_display/pull/5 | 09:24 |
| situ | until it gets accepted please use my repository https://github.com/siteshwar/android_hardware_qcom_display | 09:25 |
| vgrade_ | situ: nice work | 10:35 |
| vgrade_ | morphis: thanks | 10:35 |
| vgrade_ | it was the intersting patch then | 10:35 |
| morphis | vgrade_: np | 10:37 |
| morphis | situ: btw. I think you have to submit your patch for cyanogenmod through gerrit instead of a PR | 10:41 |
| situ | morphis: oops, never submitted a patch to cyanogenmod before. | 11:01 |
| situ | morphis: Done. http://review.cyanogenmod.org/#/c/67489/ | 11:20 |
| morphis | situ: you afaik need to set some reviewers | 11:21 |
| situ | hmm | 11:22 |
| situ | morphis: I am not sure who to add for this change. | 11:24 |
| situ | Should I pickup someone from frameworks team ? | 11:25 |
| morphis | possible | 11:25 |
| morphis | maybe look at other reviews for the same component and add the same peopl | 11:25 |
| situ | or check in git log ;) | 11:26 |
| morphis | :) | 11:28 |
| situ | We have to remove 'qt5-qtsensors-plugin-sensorfw' package (to remove /etc/xdg/QtProject/Sensors.conf) after installing from automatically generated .ks. | 13:15 |
| situ | and unmount debugfs | 13:15 |
| situ | and lipstick comes up fine. | 13:16 |
| situ | We need to fix audio issue now. | 13:17 |
| vgrade_ | situ: is /system mount issue still there | 13:20 |
| situ | vgrade_: no, but since I have added 'RequiredBy=local-fs.target' in /lib/systemd/system/system.mount , sometimes device does not boot and gets stuck. Let me show you the logs from one such boot : | 13:22 |
| situ | Last 1000 lines of dmesg output http://pastebin.com/PGAeKJyJ | 13:24 |
| situ | journal logs : http://pastie.org/9360815 | 13:24 |
| situ | mount output : http://pastie.org/9360817 | 13:26 |
| situ | so /system is mounted | 13:26 |
| vgrade_ | situ: from dmesg init seems to be running before | 13:27 |
| vgrade_ | system is mountef | 13:27 |
| situ | vgrade_: Looking at line 884 of dmesg output, it seems we are dropped to emergency mode. | 13:30 |
| situ | vgrade_: are you talking about droid-hal-init ? | 13:33 |
| vgrade_ | yes from the start of dmesg log its running through init process | 13:34 |
| vgrade_ | it should be droid-hal-init | 13:34 |
| situ | systemctl output http://pastie.org/9360840 | 13:35 |
| vgrade_ | do you have the start of that dmesg | 13:36 |
| vgrade_ | from t=0 | 13:36 |
| situ | vgrade_: [ 44.795424] systemd[1]: About to execute: /bin/mount /dev/mmcblk0p25 /system -t ext4 -o ro,barrier=1 | 13:36 |
| situ | vgrade_: [ 45.044822] systemd[1]: Got notification message for unit droid-hal-init.service | 13:36 |
| situ | so /system is mounted before droid-hal-int starts | 13:36 |
| situ | Yes I have dmesg from t=0 (actually right now my device is in this state only). | 13:37 |
| situ | vgrade_: I blieve something is wrong with mounting /acct | 13:38 |
| vgrade_ | ok | 13:39 |
| situ | vgrade_: https://www.dropbox.com/s/2iezdx7zttu7tke/dmesg.log | 13:39 |
| vgrade_ | I'm looking at the log from the start | 13:39 |
| vgrade_ | its runing init before 44.79 and 45.04 | 13:39 |
| vgrade_ | I wonder if thats the android init and not droid-hal-init | 13:40 |
| situ | Jul 14 16:15:47 Jolla mount[371]: mount: special device /devices/platform/xhci-hcd does not exist | 13:40 |
| situ | Jul 14 16:15:48 Jolla mount[389]: mount: none is already mounted or /acct busy | 13:40 |
| situ | Jul 14 16:15:48 Jolla mount[392]: mount: unknown filesystem type 'functionfs' | 13:40 |
| vgrade_ | or droid-hal-init running early | 13:41 |
| situ | vgrade_: Can I reboot my device or you need more information ? | 13:42 |
| situ | so that we can check when should droid-hal-init run on succesful run. | 13:42 |
| vgrade_ | I think the dropbox log is better | 13:42 |
| vgrade_ | looking at the log now | 13:43 |
| situ | [ 43.899157] systemd[1]: Starting droid-hal-init... | 13:44 |
| situ | so that is before /system is mounted | 13:44 |
| vgrade_ | right | 13:46 |
| situ | I rebooted and lipstick comes up fine : | 13:47 |
| situ | [ 12.971909] systemd[1]: About to execute: /bin/mount /dev/mmcblk0p25 /system -t ext4 -o ro,barrier=1 | 13:47 |
| situ | [ 13.060390] systemd[1]: Starting droid-hal-init... | 13:47 |
| situ | this is in order | 13:47 |
| situ | lbt_: ^ | 13:48 |
| vgrade_ | so the order is not being configured correctly | 13:48 |
| situ | hmm | 13:48 |
| situ | Added : RequiredBy=droid-hal-init.service | 13:50 |
| situ | in local-fs.target | 13:51 |
| vgrade_ | bbl | 13:52 |
| situ | I tested by booting several times and booting issues seems to be resolved | 13:56 |
| situ | lbt_: This is my '/lib/systemd/system/local-fs.target' http://pastie.org/9360890 , I have added line 17 and 18 | 13:57 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!