**** BEGIN LOGGING AT Wed Jan 17 03:00:02 2018 Jan 17 05:10:46 Morning Jan 17 05:13:41 Tofe: Not sure this is the proper solution but it compiles at least: https://github.com/Herrie82/qt5-qpa-hwcomposer-plugin/commit/89a65020b22f79e187a47614a00d1aa327c87dfd Jan 17 05:50:10 OK seems to get a bit further but log spamming with IPC_RTR: msm_ipc_router_bind: pm-service Do not have permissions Jan 17 05:50:23 According to http://www.merproject.org/logs/%23sailfishos-porters/%23sailfishos-porters.2017-01-02.log.html it's due to missing udev rules Jan 17 05:50:30 So trying the ones from mer-hybris now Jan 17 05:53:49 I.e. addded https://github.com/mer-hybris/droid-hal-configs/blob/master/sparse/lib/udev/platform-device to /data/luneos/lib/udev/ and https://github.com/mer-hybris/droid-hal-configs/blob/master/sparse/lib/udev/rules.d/998-droid-system.rules to /data/luneos/lib/udev/rules.d/ Jan 17 06:01:36 That doesn't solve it.... Hmmz I guess it's not as simple as adding the file? Jan 17 06:01:59 Let me try to add it to 60-persistent-storage.rules instead Jan 17 06:03:24 Nope Jan 17 06:03:41 And log is full so cannot see what's teh actual cause in the log Jan 17 06:03:59 systemd-journald[478]: /dev/kmsg buffer overrun, some messages lost. Jan 17 06:16:51 Wow, what did I miss here... Jan 17 06:16:58 Morning! Jan 17 06:22:55 We definitely need to know why we don't get the journal file in /var/log/journal... Jan 17 06:25:39 Tofe: Yeah Jan 17 06:25:43 I tried again, still the same Jan 17 06:25:58 And my dmsg is spammed now :S Jan 17 06:26:04 So cannot trace far enough back Jan 17 06:26:10 Any way to increase the size of it? Jan 17 06:27:55 there might be a kernel config for that Jan 17 06:33:33 I'm trying now to turn off before it actually manages to flood, but that takes some trial and error Jan 17 06:33:46 Now at 10s before pressing power and get a bit of a usefull log Jan 17 06:33:54 Could use some more lines though ;) Jan 17 06:34:07 https://bpaste.net/show/471c7bd4f1e5 Jan 17 06:36:37 With a few more lines that give some clues it seems: https://bpaste.net/show/efe05412fea1 Jan 17 06:44:28 Seems we're missing some mounts? Jan 17 06:48:46 Tofe: This might give some clue? https://git.choose-a.name/SonyAosp/device_sony_rhine/commit/abe9116a141a0b8befac4cd477e7be227cdf184c?view=parallel Jan 17 06:48:54 Similar error with solution Jan 17 07:55:35 "invalid keyword 'syStem' " typo ? weird Jan 17 08:04:07 but you're right, it seems there are some mounts missing Jan 17 08:08:31 Ah, forget about the typo remark, it's just that kmsg was slightly corrupted by the reboot Jan 17 08:15:16 Tofe: yeah kmsg gets messed up a bit sometimes Jan 17 08:15:37 I noticed that frequently in other lines before too Jan 17 08:26:48 Let me first PR some stuff Jan 17 09:28:21 Tofe: OK PR-ed this to piggz for mido kernel: https://github.com/piggz/android_kernel_xiaomi_msm8953/pulls Jan 17 09:36:17 Tofe: Ok a small PR to get stuff a bit more correct and up to date. https://github.com/webOS-ports/meta-webos-ports/pull/272 Jan 17 10:44:27 Need to wait for piggz to merge the PR but he's quick usually Jan 17 10:44:33 Then can do the meta-smartphone one as well Jan 17 11:05:39 JaMa: Morning! Jan 17 11:09:43 JaMa: Maybe you have some clues on this one? https://bpaste.net/show/34d8eb0f11dc Jan 17 11:10:11 It's using this tree: https://github.com/Halium/android_kernel_oneplus_onyx/tree/cm-14.1 Jan 17 11:10:35 Code structure looks similar to what we have for Mako/Hammerhead kernels, so not really sure what causes this and how to possibly remedy this Jan 17 11:38:45 Herrie|Laptop: looks like one of the toolchain fixes is missing in this tree Jan 17 11:40:54 easiest work around would be CONFIG_NO_ERROR_ON_MISMATCH=y as suggested (not really) in the log Jan 17 11:42:35 JaMa: OK I can give that a try Jan 17 11:42:51 The CONFIG_NO_ERROR_ON_MISMATCH=y would cause other issues from what I understood Jan 17 11:43:44 JaMa: I added quite some: https://github.com/Herrie82/android_kernel_oneplus_onyx/commits/cm-14.1 Jan 17 11:44:07 do you have commit 45e27030ef80c97c7b1ea80951b025314d55f815 Jan 17 11:44:08 Author: Kirill A. Shutemov Jan 17 11:44:08 Date: Mon Oct 20 12:23:12 2014 +0300 Jan 17 11:44:08 kernel: use the gnu89 standard explicitly Jan 17 11:44:14 from the old linux repository? Jan 17 11:45:08 Seems not Jan 17 11:45:11 Let me add that one Jan 17 11:46:51 That's a very good pointer :) Jan 17 11:47:20 pity that the commit message isn't very clear about the error message it is fixing Jan 17 11:47:47 but I think I've seen this one before, so it's likely that I've found a fix somewhere back then Jan 17 11:50:34 JaMa: Applied & testing now :) Jan 17 11:51:49 JaMa: For this one, you believe this is the proper solution (it compiles) or you have other suggestions? https://github.com/Herrie82/qt5-qpa-hwcomposer-plugin/commit/89a65020b22f79e187a47614a00d1aa327c87dfd#commitcomment-26905258 Jan 17 12:05:29 Herrie|Laptop: looks reasonable Jan 17 12:24:36 JaMa: OK, no C(++) expert here Jan 17 12:24:43 Just something I found while browsing around :P Jan 17 20:54:04 Tofe: Seems CONFIG_LOG_BUF_SHIFT should help for the dmesg log size Jan 17 20:54:06 Checking that now Jan 17 20:54:10 As per https://cateee.net/lkddb/web-lkddb/LOG_BUF_SHIFT.html Jan 17 20:54:43 Put it to 21 Jan 17 20:54:46 That should be enough Jan 17 20:55:18 2MB ;) Jan 17 20:55:42 Max now was 256kb **** ENDING LOGGING AT Thu Jan 18 03:00:01 2018