**** BEGIN LOGGING AT Sun Apr 21 02:59:57 2019
Apr 21 03:27:38 <ubptgbot> <TuxThePenguin> Ok I rebooted it differently and this appeared https://pastebin.com/8QmKWsiQ
Apr 21 03:59:05 <ubptgbot> <TuxThePenguin> @Tygerpro [Hmm, are there any full logs I can look at?], There is the one I sent earlier and this one which seems to be a second part https://pastebin.com/33DCL0yn
Apr 21 04:25:42 <lordcoma> wassap
Apr 21 04:27:10 <Guest77343> ey
Apr 21 04:27:20 <ubptgbot> <vvreddy> hello
Apr 21 04:27:40 <ubptgbot> <vvreddy> where do i clone my kernel source into … usually for aosp or los i clone into kernel/xiaomi/msm8937
Apr 21 04:27:48 <ubptgbot> <vvreddy> shud I do the same for Halium as well ?
Apr 21 04:28:02 <lordcoma> im a noob fren, sorry
Apr 21 04:28:50 <ubptgbot> <UniversalSuperBox> Yes
Apr 21 04:29:03 <ubptgbot> <vvreddy> thank you
Apr 21 04:36:11 <ubptgbot> <Tygerpro> @TuxThePenguin [There is the one I sent earlier and this one which seems to be a second part htt …], Im seeing what looks like a lot of gibberish in there, is your /data partition encrypted?
Apr 21 04:36:24 <ubptgbot> <TuxThePenguin> I do not think so
Apr 21 04:36:38 <ubptgbot> <TuxThePenguin> That made me wonder if something was causing memory corruption
Apr 21 04:37:43 <ubptgbot> <Tygerpro> Thats my other thought, just to test, double check that your phone doesnt have any encryption on the /boot and /data partitions
Apr 21 04:38:37 <ubptgbot> <TuxThePenguin> How would I check for encryption on /boot?
Apr 21 04:49:07 <ubptgbot> <UniversalSuperBox> dmesg-ramoops gets corrupted often
Apr 21 04:49:15 <ubptgbot> <TuxThePenguin> Oh ok
Apr 21 04:49:23 <ubptgbot> <UniversalSuperBox> RAM isn't getting refreshed while the SOC is being reset
Apr 21 04:49:27 <ubptgbot> <UniversalSuperBox> So it loses bits
Apr 21 04:49:29 <ubptgbot> <TuxThePenguin> Yeah, makes sense
Apr 21 04:49:50 <ubptgbot> <TuxThePenguin> It's annoying because it seems to be getting corrupted right around a very useful area
Apr 21 05:23:15 <ubptgbot> <TuxThePenguin> AH I got one that's not corrupted at all
Apr 21 05:23:18 <ubptgbot> <TuxThePenguin> (Document) https://irc.ubports.com/Ot0Iy1vd.txt
Apr 21 05:23:18 <ubptgbot> <TuxThePenguin> (Document) https://irc.ubports.com/CFjMfykI.txt
Apr 21 05:24:09 <ubptgbot> <TuxThePenguin> I had it fully powered off and turned it on by plugging it into USB port
Apr 21 05:24:13 <ubptgbot> <TuxThePenguin> [Edit] I had it fully powered off and turned it on by plugging it into USB power
Apr 21 05:24:30 <ubptgbot> <TuxThePenguin> Then once it rebooted I immediately booted it into recovery
Apr 21 05:26:30 <ubptgbot> <TuxThePenguin> Im not sure how nothing got corrupted but I'm not complaining
Apr 21 05:28:05 <ubptgbot> <TuxThePenguin> (Document) https://irc.ubports.com/TbkAfD22.txt
Apr 21 05:28:13 <ubptgbot> <TuxThePenguin> It seems like a few bits got corrupted but thats it
Apr 21 05:45:03 <ubptgbot> <Diago99> So I can't get ssh access from my laptop.. Tried mounting the rootfs.img and sync again...  … But still no access , hangs every time.. Any fix or any other problem?
Apr 21 05:50:35 <ubptgbot> <Diago99> @Flohack [You have duplicated partition entries, this probably wont work (data, cache)], So what should be the proper partition
Apr 21 06:02:01 <ubptgbot> <NotKit> @TuxThePenguin there seem to be some bug in your device kernel code which appears due to modified configuration
Apr 21 06:02:17 <ubptgbot> <NotKit> no point in modifying build environment
Apr 21 06:02:41 <ubptgbot> <TuxThePenguin> Any idea what that bug might be?
Apr 21 06:02:48 <ubptgbot> <TuxThePenguin> Or at least what it's related to?
Apr 21 06:03:13 <ubptgbot> <NotKit> [01-01 00:00:00.886] [3][1: swapper/0]pfk [pfk_lsm_init]: se linux is not enabled. … [01-01 00:00:00.886] [3][1: swapper/0]get_ice_device_from_storage_type: invalid device list … [01-01 00:00:00.886] [3][1: swapper/0]Unable to handle kernel paging request at virtual address fffffffffffffedb
Apr 21 06:03:44 <ubptgbot> <TuxThePenguin> Well se linux being disabled is expected
Apr 21 06:04:13 <ubptgbot> <Diago99> Apparmor should be enabled
Apr 21 06:04:47 <ubptgbot> <NotKit> I know, but I would personally reenable it to test if it still crashes, otherwise you know what to look for in code
Apr 21 06:05:17 <ubptgbot> <TuxThePenguin> Alright Ill see what happens
Apr 21 07:39:44 <ubptgbot> <TuxThePenguin> Well I tried enabling SELinux and correctly setting the related settings like audit but then it wouldn't even try to boot the kernel, it just turned off, when I modified the boot image to add audit=0 and selinux=0 to the commandline it did the exact same thing as having disabled SELinux earlier, so trying to boot but panicking
Apr 21 07:43:26 <ubptgbot> <TuxThePenguin> Oh and that uncorrupted log seems to have been a one-off
Apr 21 08:14:07 <ubptgbot> <NotKit> that's pretty weird for it to refuse to boot with SELinux on
Apr 21 08:14:35 <ubptgbot> <TuxThePenguin> Yeah idk why that was happening, and of course because it was powering off completely rather than rebooting I can't get any logs
Apr 21 08:54:32 <ubptgbot> <TuxThePenguin> So I realised that somehow the userdata partition was formatted as F2FS but even after recompiling everything and putting the reference rootfs on again with EXT4 it's having the same issue
Apr 21 09:06:12 <ubptgbot> <FTC55> Guys does anyone know what libandroid_runtime is and why am i missing it?
Apr 21 09:33:12 <ubptgbot> <TuxThePenguin> Tygerpro I have made almost no progress except that I got an uncorrupted log one time
Apr 21 09:34:30 <ubptgbot> <TuxThePenguin> I don't think it is even making it to the android part of the boot process
Apr 21 09:42:49 <ubptgbot> <TuxThePenguin> I wonder if this has anything to do with it "vmscan: error setting kswapd cpu affinity mask"
Apr 21 09:48:52 <ubptgbot> <FTC55> Guys I've found the sources for a library where should I put them for it to get build and hopefully show up in SHARED_LIBRARIES?
Apr 21 09:49:08 <ubptgbot> <FTC55> *built
Apr 21 09:50:59 <ubptgbot> <FTC55> @UniversalSuperBox [Something depends on that library (OpenSLES) but you don't have it. Your options …], Any hint on how to find that "proper place" lol?
Apr 21 10:46:45 <ubptgbot> <TuxThePenguin> Ah I just found this gist which is almost identical to the console log of my Axon 7, Ill see what this guy was doing https://gist.github.com/rockybulwinkle/b2cdfa892f1a313c01647cc7a1dab53d
Apr 21 10:47:57 <ubptgbot> <TuxThePenguin> Ok apparently nothing, great...
Apr 21 11:00:56 <ubptgbot> <TuxThePenguin> So it seems like this isn't a major halium compatibility issue but a common ZTE issue
Apr 21 11:39:48 <ubptgbot> <TuxThePenguin> Ok Im trying to disable some "optional" kernel settings to see if maybe one of those was causing it not to boot, Im not very hopeful though
Apr 21 12:20:37 <ubptgbot> <TuxThePenguin> Oh great now TWRP has decided to freak out so I have to use ADB to copy files, which is a LOT slower
Apr 21 12:37:57 <ubptgbot> <Tygerpro> For testing purposes, theres 2 main things that need to be set in defconfig, try reverting your defconfig to stock and set just …  CONFIG_IKCONFIG and CONFIG_IKCONFIG_PROC … Its not a propper config but these 2 are the bare minimum and if it still does it with just these then I dont know
Apr 21 13:49:05 <ubptgbot> <TuxThePenguin> Welp I compiled it with just those two and it still panics
Apr 21 13:49:10 <ubptgbot> <TuxThePenguin> Great...
Apr 21 13:50:55 <ubptgbot> <TuxThePenguin> Would it be possible to use the mainline kernel and compile it for the msm8996 board?
Apr 21 13:54:48 <ubptgbot> <TuxThePenguin> Well it probably won't work but I might as well try it since a lot of stuff will have been mainlined by now and I mean whats the worst that can happen :P
Apr 21 16:38:59 <ubptgbot> <Flohack> @Diago99 [So what should be the proper partition], I dont know but you can try to comment either of them and see if it mounts properly. Try to compare with other Halium partition tables