**** BEGIN LOGGING AT Sat Jan 09 02:59:57 2021
Jan 09 13:58:47 <Herrie> Morning!
Jan 09 13:59:15 <Herrie> Tofe: Any thoughts to what I can check? Seems system.img might not be mounted?
Jan 09 15:07:19 <Herrie> Tofe: Well actually mounts do look ok? https://paste.ubuntu.com/p/6JvdskdmqP/
Jan 09 18:54:54 <Tofe> morning!
Jan 09 18:55:27 <Tofe> I'm in the train, but I'll try and see :)
Jan 09 18:57:24 <Tofe> Herrie: I think you're missing one mount here, the android-rootfs.img onto var/....../lxc/rootfs
Jan 09 18:57:45 <Tofe> i.e. the main one
Jan 09 18:59:28 <Tofe> it's quite surprising, because you do have the one onto /android, which should be a bind mount of the other one
Jan 09 20:30:07 <Herrie> Tofe: I have no clue what could be wrong there :P
Jan 09 20:31:02 <Tofe> Herrie: I'm home now, let me recheck your logs
Jan 09 20:31:25 <Tofe> first, we agree you're reusing my modified halium script for initramfs ?
Jan 09 20:35:42 <Herrie> Well I should be let me double check to be sure
Jan 09 20:35:53 <Tofe> mmmh are you sure your generated system.img is actually a system-on-root ?
Jan 09 20:36:19 <Tofe> if you mount it, do you see the android init*.rc at the root ?
Jan 09 20:36:44 <Tofe> because in the logs, seeing "Sep 20 10:16:04 mido mount: mounting /android-rootfs/system on /android-system failed: No such file or directory" is weird
Jan 09 20:36:58 <Herrie> Yeah I guess so: to_exclude.txt is in there
Jan 09 20:37:13 <Herrie> In init.sh from meta-smartphone
Jan 09 20:37:19 <Herrie> You added that bit right in Halium 9?
Jan 09 20:37:39 <Tofe> right, to fix a big issue we had with /var handling in general
Jan 09 20:39:16 <Herrie> Let me just reflash to be 1000% sure :P
Jan 09 20:39:56 <Tofe> I'm downloading your mido halium tar.gz, to check my hypothesis
Jan 09 20:40:23 <Tofe> let's see in 5min, I don't have your bandwidth :D
Jan 09 20:42:24 <Herrie> Hehe
Jan 09 20:42:30 <Herrie> Still not :P ?
Jan 09 20:42:47 <Herrie> Macron allows you to go by train, but still no fiber :P
Jan 09 20:44:36 <Herrie> I didn't include your Rosy "device fixes" at my end yet
Jan 09 20:44:40 <Herrie> And kernel is our 7.1 one
Jan 09 20:44:47 <Herrie> Since that one at least does something
Jan 09 20:46:51 <Tofe> ah, wait, it's a sparse image, can't mount as-is let me fix it locally
Jan 09 20:47:25 <Tofe> yup, that's a classic "system" image
Jan 09 20:47:58 <Tofe> maybe you need to set the boolean for system-as-root in the .mk ?
Jan 09 20:48:22 <Herrie> Tofe: Ah yeah you might be right let me check
Jan 09 20:52:58 <Herrie> OK added it and building again
Jan 09 21:46:24 <Herrie> OK that took a bit longer
Jan 09 21:46:31 <Herrie> And was painting some stairs in the meanwhile
Jan 09 21:46:33 <Herrie> Image flashed
Jan 09 21:57:59 <Herrie> Now bootloop and no logs :(
Jan 09 21:59:05 <Tofe> ah, damn
Jan 09 21:59:35 <Tofe> with 7.1 kernel, right?
Jan 09 22:00:38 <Herrie> Ah wait now I have logs
Jan 09 22:00:48 <Herrie> I could ADB in and save some
Jan 09 22:01:02 <Herrie> https://paste.ubuntu.com/p/DtZb5VqCJy/
Jan 09 22:01:06 <Tofe> adb ? great
Jan 09 22:01:15 <Herrie> Well it reboots
Jan 09 22:01:23 <Herrie> This log was a few seconds before reboot
Jan 09 22:04:41 <Tofe> maybe it's similar to what I have, i.e. some kernel driver crashes or triggers a reboot
Jan 09 22:04:50 <Herrie> It doesn't look too bad actually
Jan 09 22:04:55 <Tofe> here you seem to have issues with adsp, i.e. sound support
Jan 09 22:05:12 <Tofe> right, apart from this spam it's quite alright
Jan 09 22:06:39 <Tofe> for me, often, "kernel: firmware adsp.b05: firmware_loading_store: unexpected value (0) " is the last thing before the crash
Jan 09 22:07:30 <Tofe> looks like from adsp firmware is loaded multiple times in parallel, or something like that; not sure how robust the kernel is w.r.t. that
Jan 09 22:10:06 <Herrie> It's weird it doesn't like adsp.b05 file for some reason
Jan 09 22:10:13 <Tofe> nor b03
Jan 09 22:10:30 <Tofe> it tries to load it multiple times, maybe in parallel
Jan 09 22:10:34 <Tofe> it=ueventd
Jan 09 22:11:05 <Tofe> but still, no crash it seems, you're lucky :)
Jan 09 22:13:01 <Tofe> it's probably adsprpcd that starts the spamming, but it doesn't look fatal
Jan 09 22:13:13 <Tofe> you also have some "binder" issues, but not sure it's fatal either
Jan 09 22:13:46 <Tofe> I'm a bit tired, maybe I'll sleep a bit and resume this tomorrow :p
Jan 09 22:14:25 <Herrie> SOunds good, same here
Jan 09 22:14:32 <Herrie> Gn8
Jan 09 22:14:41 <Tofe> gn8 too !
Jan 09 22:38:26 <Herrie> Tofe: For tomorrow: https://paste.ubuntu.com/p/gPZyqFXhcg/
Jan 09 22:38:30 <Herrie> Seems WCNSS again
Jan 09 22:38:52 <Herrie> Sep 20 10:16:58 mido kernel: Fatal error on wcnss!
Jan 09 22:44:47 <Herrie> Issue might be in /vendor/firmware somehow
Jan 09 22:47:12 <Herrie> Hmmz have /vendor/firmware/wlan/prima/WCNSS_qcom_wlan_nv.bin though it seems
**** ENDING LOGGING AT Sun Jan 10 03:00:21 2021