**** BEGIN LOGGING AT Fri Oct 25 03:00:04 2019
Oct 25 05:00:11 <ubptgbot> AngusJackMeyer was added by: AngusJackMeyer
Oct 25 05:00:25 <ubptgbot> TeidoSentz was added by: TeidoSentz
Oct 25 05:00:39 <ubptgbot> MSchulzFliesenNaturstein was added by: MSchulzFliesenNaturstein
Oct 25 05:05:16 <ubptgbot> <ankaos> Fwd from ankaos: https://paste.ubuntu.com/p/snHgKPhgGG/ @frknkrc44 al sana log
Oct 25 05:05:24 <ubptgbot> <ankaos> Sound error log
Oct 25 06:08:17 <ubptgbot> asdadafa was added by: asdadafa
Oct 25 07:24:51 <vlad_> Hey, everybody. I started to understand porting helium to my device. I'm having trouble at this stage https://docs.halium.org/en/latest/porting/debug-build/early-init.html. the phone does not start and throws in recovery. I read the kernel log but didn't understand anything. I'm new to this. Here's the log https://pastebin.com/jPV9ju12. Phone - Asus ZenFone 2 ZE551ML (Z00A)
Oct 25 07:25:59 <Danct12[m]> huh
Oct 25 07:26:05 <Danct12[m]> sounds like the watchdog is causing it to reboot
Oct 25 07:26:31 <Danct12[m]> like i guess it didn't detect that it was android and reboots
Oct 25 07:26:59 <Danct12[m]> can you give me the link to kernel source?
Oct 25 07:27:34 <Danct12[m]> is there anything before that?
Oct 25 07:27:48 <ubptgbot> <rixchy> @Danct12[m] [like i guess it didn't detect that it was android and reboots], Maybe it's CONFIG_NAMESPACES?
Oct 25 07:27:49 <Danct12[m]>  * for the log, is there anything before that?
Oct 25 07:28:11 <ubptgbot> <rixchy> @rixchy [Maybe it's CONFIG_NAMESPACES?], I had the same issue on my device too, (still havin' it.)
Oct 25 07:29:04 <vlad_> https://github.com/LineageOS/android_kernel_asus_moorefield
Oct 25 07:31:22 <Danct12[m]> no idea, i never worked on intel kernels
Oct 25 07:31:30 <Danct12[m]> only qualcomm which doesn't seem to have this issue
Oct 25 07:32:26 <Danct12[m]> maybe disabling CONFIG_INTEL_SCU_WATCHDOG_EVO should get rid of the watchdog stuff
Oct 25 07:33:47 <asriel> Could very well be possible that the watchdog needs to be kicked
Oct 25 07:34:35 <asriel> Or.. just need "Magic Close"
Oct 25 07:40:26 <vlad_> There were difficulties compiling after the configuration change. Сorrected it commenting lines on which the compiler swore. But I'm not sure that's right.
Oct 25 07:42:27 <ubptgbot> <rixchy> @Danct12[m] [maybe disabling CONFIG_INTEL_SCU_WATCHDOG_EVO should get rid of the watchdog stu …], Ok, but if it still reboots, try to disable the CONFIG_NAMESPACES, because it was kernel panicking my device. (Confirmed in logcat.)
Oct 25 08:55:20 <ubptgbot> <Deathmist1337> @Meron [Can the Oneplus 5 work if I start Halium to port Ubuntu touch to it?], I worked with Vince on it, the device boots to UI, gets SSH (with configfs hybris-usb package) and "most" apps start fine :) I can give you the manifest if you want to help too
Oct 25 08:59:13 <ubptgbot> <Deathmist1337> should probably do a PR to halium-devices repo tbh
Oct 25 09:48:32 <ubptgbot> <rixchy> Is it possible to somehow look at rootfs logs?
Oct 25 09:49:22 <ubptgbot> <rixchy> Or are the only logs you can get is te last_kmsg and the other log?
Oct 25 10:18:49 <ubptgbot> <rixchy> Hm, my USERDATA's partition table is broken. Could this cause device rebooting?
Oct 25 10:19:53 <ubptgbot> <NotKit> you should not have any *partition table* on userdata
Oct 25 10:21:09 <ubptgbot> <rixchy> Oh, thank you for letting me know that. Maybe I said that incorrectly.
Oct 25 10:21:54 <ubptgbot> <rixchy> @rixchy ["Disk /dev/block/mmcblk0p9: 8 MB, 8388608 bytes … 4 heads, 16 sectors/track, 256 c …], I apologize, it is not USERDATA.
Oct 25 10:22:07 <ubptgbot> <rixchy> But, I don't really know what that is.
Oct 25 10:22:35 <ubptgbot> <NotKit> a single partition is not supposed to contain partition table so that warning is correct
Oct 25 10:22:51 <ubptgbot> <rixchy> Hm, alright.
Oct 25 10:23:02 <ubptgbot> <rixchy> Then that is not the culprit..
Oct 25 10:23:34 <ubptgbot> <NotKit> if you mean CONFIG_NAMESPACES crash, then something is wrong in kernel code
Oct 25 10:23:43 <ubptgbot> <rixchy> @NotKit [if you mean CONFIG_NAMESPACES crash, then something is wrong in kernel code], Yeah, but I am not sure what.
Oct 25 10:23:51 <ubptgbot> <rixchy> Last_kmsg didn't give a hint.
Oct 25 10:24:04 <ubptgbot> <NotKit> is it empty or?
Oct 25 10:24:16 <ubptgbot> <rixchy> IDK what OR even is. xD
Oct 25 10:24:19 <ubptgbot> <rixchy> [    3.202052]  [B0:       swapper/0:     1] Code: bad PC value … [    3.202357]  [B0:       swapper/0:     1] ---[ end trace a9b7f26e052d705d ]--- … [    3.202619]  [B0:       swapper/0:     1] Kernel panic - not syncing: Fatal exception
Oct 25 10:24:35 <ubptgbot> <NotKit> is that all of it?
Oct 25 10:25:09 <ubptgbot> <rixchy> Ofc not, just showed some lines that may be.. eye catching, I guess.. Would you like to see the whole file?
Oct 25 10:25:19 <ubptgbot> <NotKit> yes, on pastebin
Oct 25 10:25:27 <ubptgbot> <rixchy> Sure, give me a moment, please.
Oct 25 10:25:49 <ubptgbot> <rixchy> Here you go. https://pastebin.com/9d8P0FcH
Oct 25 10:26:08 <ubptgbot> <rixchy> I am going to be surprised if you are going to find the culprit.
Oct 25 10:27:06 <ubptgbot> <NotKit> it is not that simple, but at least knowing which stage of boot is it may sched some light
Oct 25 10:27:22 <ubptgbot> <rixchy> Okay, I understand.
Oct 25 11:25:31 <ubptgbot> <nanu a> @Meron [Can the Oneplus 5 work if I start Halium to port Ubuntu touch to it?], Quote from vince: left to right, Oneplus2,3T,5 :D
Oct 25 11:25:47 <ubptgbot> <nanu a> (Photo, 1280x960) https://irc.ubports.com/qBrGPejn.png left to right, Oneplus2,3T,5 :D
Oct 25 11:27:58 <ubptgbot> <rixchy> Hm, is this critical? "RAMDISK: gzip decompressor not configured!"
Oct 25 11:32:22 <ubptgbot> <rixchy> I think I finally found the reason for my device rebooting, but I am not sure. https://superuser.com/questions/1231593/reason-for-kernel-panic-unable-to-handle-kernel-paging-request-at-virtual-addre
Oct 25 11:32:55 <ubptgbot> <rixchy> Got this error: "internal error: Oops: 80000005 [#1] PREEMPT SMP ARM", searched it on google and thread above appeared.
Oct 25 11:33:31 <ubptgbot> <Akatsu .> CONFIG_PREEMPT
Oct 25 11:33:43 <ubptgbot> <rixchy> @Akatsu . [CONFIG_PREEMPT], Configure it to what value?
Oct 25 11:34:02 <ubptgbot> <Akatsu .> https://stackoverflow.com/questions/15756597/kernel-oops-oops-80000005-on-arm-embedded-system
Oct 25 11:34:09 <ubptgbot> <dohniks> @rixchy [Hm, is this critical? "RAMDISK: gzip decompressor not configured!"], might be. it's right above the panic. can you pastebin the diff of your config to the original again?
Oct 25 11:34:23 <ubptgbot> <rixchy> @dohniks [might be. it's right above the panic. can you pastebin the diff of your config t …], Hm, let me find it.
Oct 25 11:34:34 <ubptgbot> <Akatsu .> Original one has premmpt
Oct 25 11:34:43 <ubptgbot> <rixchy> Found the original.
Oct 25 11:35:15 <ubptgbot> <Akatsu .> In short your gzip encryption fails what leads to crash
Oct 25 11:35:40 <ubptgbot> <rixchy> Hm, I hear you.
Oct 25 11:35:47 <ubptgbot> <rixchy> @Akatsu . [Original one has premmpt], Let me check in the orig.
Oct 25 11:35:55 <ubptgbot> <Akatsu .> Doniks have good idea
Oct 25 11:36:08 <ubptgbot> <rixchy> This is in my original defconfig: "CONFIG_PREEMPT=y"
Oct 25 11:36:24 <ubptgbot> <rixchy> @dohniks [might be. it's right above the panic. can you pastebin the diff of your config t …], Oh yeah, sure. BRB.
Oct 25 11:36:41 <ubptgbot> <rixchy> diff [the orig config] [modified config]
Oct 25 11:36:42 <ubptgbot> <rixchy> ?
Oct 25 11:36:48 <ubptgbot> <rixchy> Or reversed?
Oct 25 11:37:48 <ubptgbot> <Akatsu .> Get into directory
Oct 25 11:37:52 <ubptgbot> <rixchy> Did.
Oct 25 11:37:55 <ubptgbot> <Akatsu .> And git diff
Oct 25 11:38:11 <ubptgbot> <Akatsu .> Then scroll with enter
Oct 25 11:38:23 <ubptgbot> <rixchy> Wait what. Just go into ~/halium directory or what?
Oct 25 11:40:25 <ubptgbot> <Akatsu .> Halium directory/kernel/vendor/type
Oct 25 11:40:30 <ubptgbot> <rixchy> Oh.
Oct 25 11:40:47 <ubptgbot> <Akatsu .> That's how it is rite.
Oct 25 11:40:51 <ubptgbot> <rixchy> halium/kernel/samsung/exynos5420/ ?
Oct 25 11:40:56 <ubptgbot> <rixchy> Okay.
Oct 25 11:41:08 <ubptgbot> <Akatsu .> You can even go to defconfig catalog
Oct 25 11:41:19 <ubptgbot> <rixchy> I did git diff, returned nothing.
Oct 25 11:41:37 <ubptgbot> <Akatsu .> (Sticker, 512x368) https://irc.ubports.com/F8LhkaH9.webp
Oct 25 11:41:45 <ubptgbot> <rixchy> What? 😂😂
Oct 25 11:41:45 <ubptgbot> <NotKit> @rixchy you still didn't post the full log
Oct 25 11:42:07 <ubptgbot> <Akatsu .> Didn't he? RAMDISK had issue with decompressing
Oct 25 11:42:13 <ubptgbot> <rixchy> @rixchy [Here you go. https://pastebin.com/9d8P0FcH], Uhm.
Oct 25 11:42:18 <ubptgbot> <rixchy> Here it is..?
Oct 25 11:42:40 <ubptgbot> <rixchy> @Akatsu . [<reply to media>], I gotta save this to my stickers.
Oct 25 11:43:35 <ubptgbot> <Akatsu .> (Photo, 720x1280) https://irc.ubports.com/Jykc8HWn.png
Oct 25 11:43:46 <ubptgbot> <rixchy> @Akatsu . [<reply to media>], Saved it.
Oct 25 11:44:00 <ubptgbot> <rixchy> (Sticker, 512x512) https://irc.ubports.com/0hyCRl8p.webp
Oct 25 11:44:16 <ubptgbot> <Akatsu .> Well you should try to get decompressor in kernel config
Oct 25 11:44:21 <ubptgbot> <Akatsu .> And use git tho
Oct 25 11:44:47 <ubptgbot> <rixchy> MY CAT JUST RAN ACCROSS THE KEYBOARD GOD DAM.
Oct 25 11:45:03 <ubptgbot> <rixchy> What is preempt?
Oct 25 11:45:24 <ubptgbot> <rixchy> I have it enabled (CONFIG_PREEMPT=y) BTW.
Oct 25 11:45:35 <ubptgbot> <NotKit> @rixchy [Here it is..?], missed, sorry
Oct 25 11:45:48 <ubptgbot> <rixchy> @NotKit [missed, sorry], That's alright.
Oct 25 11:46:53 <ubptgbot> <Akatsu .> Ignore preempt it's time to fix decompression
Oct 25 11:47:02 <ubptgbot> <Akatsu .> As it's on top of stack
Oct 25 11:47:06 <ubptgbot> <rixchy> Sure, just wondered what that is.
Oct 25 11:47:16 <ubptgbot> <NotKit> but wait, does decompression fail only with namespaces?
Oct 25 11:47:23 <ubptgbot> <rixchy> @NotKit [but wait, does decompression fail only with namespaces?], Yup.
Oct 25 11:47:24 <ubptgbot> <NotKit> it should not be related at all
Oct 25 11:47:36 <ubptgbot> <rixchy> IDK, but for some bizzare reason that happens.
Oct 25 11:48:02 <ubptgbot> <rixchy> But the RAMDISK error was the last error above the "kernel panic" line.
Oct 25 11:48:14 <ubptgbot> <rixchy> So I assumed that was the reason of the issue.
Oct 25 11:51:12 <ubptgbot> <Akatsu .> Ok it indeed can be namespaces
Oct 25 11:52:36 <ubptgbot> <Akatsu .> (Photo, 720x1280) https://irc.ubports.com/kyNFkUQO.png
Oct 25 11:52:59 <ubptgbot> <rixchy> @Akatsu . [<reply to media>], Ah-ha! Knew that, Akatsu! Thank you for your confirmation.
Oct 25 11:53:15 <ubptgbot> <rixchy> Hm, but why didn't  I notice that myself?
Oct 25 11:53:39 <ubptgbot> <Akatsu .> I'm more used to see windows stacks
Oct 25 11:53:49 <ubptgbot> <Akatsu .> Where faulty module is on top
Oct 25 11:53:58 <ubptgbot> <Akatsu .> And here it's just log with timestamp
Oct 25 11:54:31 <ubptgbot> <rixchy> Alright, any idea how to fix that?
Oct 25 11:55:38 <ubptgbot> <rixchy> Maybe this was a kernel bug? This kernel is 3.4 BTW, so maybe that caused something a little bit?
Oct 25 11:57:12 <ubptgbot> <Akatsu .> https://android.googlesource.com/kernel/mediatek/+/e35612c63f33f02e09e370a865ab583f5f32d387%5E!/
Oct 25 11:57:20 <ubptgbot> <Akatsu .> Yes mediatek
Oct 25 11:58:22 <ubptgbot> <rixchy> But what we're now looking for here, is the fix. Since we know the cause, am I correct?
Oct 25 12:03:26 <ubptgbot> <NotKit> I'm not so sure, as your problem is with unpacking initramfs and their is with mounting root device, but maybe worth a try
Oct 25 12:03:56 <ubptgbot> <NotKit> otherwise you should check the failure codepath and compare it with kernel source of working 3.4 device like Nexus 5
Oct 25 12:04:05 <ubptgbot> <NotKit> probably vendor made a mistake backporting patches
Oct 25 12:06:40 <ubptgbot> <rixchy> The fun fact is, most of all the files in the build directory are placed by me manually, (IDK if that is strange..)
Oct 25 12:09:05 <ubptgbot> <a_lick> Tweet from @patri_usi … https://twitter.com/patri_usi/status/1186002330342318080 … @patri_usi: Yo https://t.co/Mv1gWyGQxE
Oct 25 12:09:28 <ubptgbot> <a_lick> Sorry, wrong chat
Oct 25 12:09:36 <ubptgbot> <rixchy> That is alright.
**** BEGIN LOGGING AT Fri Oct 25 12:27:43 2019
Oct 25 12:33:41 <ubptgbot> <rixchy> I know that this is not a Samsung device (a Raspberry Pie), but I think I could try this: https://github.com/raspberrypi/linux/issues/499
Oct 25 12:40:16 <ubptgbot> <rixchy> I cannot apply this patch, or I can? https://android.googlesource.com/kernel/exynos/+/refs/heads/android-exynos-3.4/arch/arm/mach-exynos/tmu-exynos.c
Oct 25 14:06:11 <ubptgbot> <rixchy> Technically it is for a Exynos processor, so..
Oct 25 14:24:54 <ubptgbot> zetronast was added by: zetronast
Oct 25 14:25:04 <ubptgbot> <rixchy> So, I am really not sure. I found this here: "This is usually application code, and sometimes compiler option if over optimizing for the wrong CPU arch/model - which is usually fixed by a makefile option if using GCC.."
Oct 25 14:25:24 <ubptgbot> <rixchy> @NotKit [probably vendor made a mistake backporting patches], Maybe this was the issue.
Oct 25 14:25:43 <ubptgbot> <rixchy> @NotKit [if you mean CONFIG_NAMESPACES crash, then something is wrong in kernel code], Or this.
Oct 25 14:26:25 <ubptgbot> <NotKit> those are same basically
Oct 25 14:26:48 <ubptgbot> <rixchy> Okay.
Oct 25 14:27:12 <ubptgbot> <rixchy> @rixchy [So, I am really not sure. I found this here: "This is usually application code, …], "which is usually fixed by a makefile option if using GCC.."?
Oct 25 14:28:18 <ubptgbot> <rixchy> @NotKit What do you think about this?
Oct 25 14:28:42 <ubptgbot> <rixchy> @rixchy [So, I am really not sure. I found this here: "This is usually application code, …], From here: https://forum.armbian.com/topic/11160-oops-80000005-1-smp-thumb2/
Oct 25 14:29:52 <ubptgbot> <NotKit> do not look for the problem just by Oops: numbers, that is too general issue
Oct 25 14:29:59 <ubptgbot> <NotKit> you have the call stack in your last_kmsg
Oct 25 14:30:28 <ubptgbot> <rixchy> I am a nooby, what is a "call stack". It's like where some code calls for a function or something like that?
Oct 25 14:31:35 <ubptgbot> <NotKit> basically the order in which functions got called before the crash happened
Oct 25 14:31:50 <ubptgbot> <rixchy> Ok, thanks for the info.
Oct 25 14:32:18 <ubptgbot> <NotKit> you can try to follow this path in kernel source code and diff your code with working 3.4 kernel from Nexus 5
Oct 25 14:32:25 <ubptgbot> <NotKit> that part is likely not very device-specific
Oct 25 14:32:42 <ubptgbot> <NotKit> by diff I mean compare, don't just go copy-pasting files blindly
Oct 25 14:33:45 <ubptgbot> <rixchy> @NotKit [you can try to follow this path in kernel source code and diff your code with wo …], What path?
Oct 25 14:34:25 <ubptgbot> <rixchy> @NotKit
Oct 25 14:35:10 <ubptgbot> <NotKit> @Akatsu . [<reply to media>], ^
Oct 25 14:36:48 <ubptgbot> <NotKit> kernel_init seems to call prepare_namespace, then prepare-namespace calls initrd_load and initrd_load calls rd_load_image which fails to decompress gzip for some reason
Oct 25 14:37:03 <ubptgbot> <rixchy> What is preempt?
Oct 25 14:37:44 <ubptgbot> <rixchy> It says that GZIP is unconfigured, right?
Oct 25 14:37:57 <ubptgbot> <rixchy> Yep. "RAMDISK: gzip decompressor not configured!".
Oct 25 14:38:05 <ubptgbot> <rixchy> So, how do we "configure" it then?
Oct 25 14:38:40 <ubptgbot> <NotKit> @rixchy [What is preempt?], see https://kernelnewbies.org/FAQ/Preemption. Don't modify CONFIG_PREEMPT though
Oct 25 14:39:59 <ubptgbot> <rixchy> @rixchy [So, how do we "configure" it then?], Do you have answers to his, @NotKit ?
Oct 25 14:40:07 <ubptgbot> <rixchy> @rixchy [So, how do we "configure" it then?], [Edit] Do you have answers to this, @NotKit ?
Oct 25 14:40:13 <ubptgbot> <rixchy> @rixchy [So, how do we "configure" it then?], [Edit] Do you have answers to this, @NotKit?
Oct 25 14:41:24 <ubptgbot> <NotKit> @rixchy [So, how do we "configure" it then?], no, need to read code to understand conditions under which this may be emitted
Oct 25 14:42:18 <ubptgbot> <NotKit> one common sense assumption may be that it tries to load ramdisk earlier than compressor code is initialized, but again it won't help much without studying the actual code
Oct 25 14:42:18 <ubptgbot> <zetronast> Guys,i already have android 10 port to my device (redmi note 7 pro). Mine phone was once Lineage os official(it will be again official in 1 month). … Which halium version should i choose?
Oct 25 14:43:12 <ubptgbot> <rixchy> @NotKit [one common sense assumption may be that it tries to load ramdisk earlier than co …], Where is the code's location? How do we find where the code is located?
Oct 25 14:43:44 <ubptgbot> <NotKit> you can try to grep kernel source files by the function names
Oct 25 14:43:57 <ubptgbot> <NotKit> at least basic C knowledge is required though
Oct 25 14:44:54 <ubptgbot> <NotKit> @zetronast [Guys,i already have android 10 port to my device (redmi note 7 pro). Mine phone …], Halium does not support Android 8 and newer devices yet, your device is too new
Oct 25 14:46:05 <ubptgbot> <rixchy> @NotKit [at least basic C knowledge is required though], Here is the problem! I know C very little.
Oct 25 14:47:01 <ubptgbot> <dohniks> @rixchy [Do you have answers to this, @NotKit?], well, or ... you have been playing with compression options to squeeze it smaller, so maybe that messed with gzip capabilities ... that's why I asked for config diff
Oct 25 14:47:24 <ubptgbot> <rixchy> @dohniks [well, or ... you have been playing with compression options to squeeze it smalle …], Wait, didn't you tell me to do something?
Oct 25 14:47:33 <ubptgbot> <rixchy> With the compression things?
Oct 25 14:47:57 <ubptgbot> <rixchy> AH-ha!!
Oct 25 14:48:04 <ubptgbot> <rixchy> Found it!
Oct 25 14:48:04 <ubptgbot> <dohniks> sure. could totally be my fault ;)
Oct 25 14:48:14 <ubptgbot> <rixchy> Not your fault.
Oct 25 14:48:14 <ubptgbot> <rixchy> Fwd from dohniks: Unset gzip and set lzma
Oct 25 14:48:22 <ubptgbot> <rixchy> @dohniks [sure. could totally be my fault ;)], Not your fault. :)
Oct 25 14:48:50 <ubptgbot> <rixchy> This?
Oct 25 14:49:02 <ubptgbot> <NotKit> heh, then it's obvious
Oct 25 14:49:09 <ubptgbot> <rixchy> But.
Oct 25 14:49:27 <ubptgbot> <rixchy> My device didn't work even before disabling GZIP, but we will look in logs for that.
Oct 25 14:49:35 <ubptgbot> <NotKit> @NotKit [but wait, does decompression fail only with namespaces?], ^
Oct 25 14:49:37 <ubptgbot> <rixchy> For now, I will rebuild the boot, and cat the logs.
Oct 25 14:50:05 <ubptgbot> <rixchy> @NotKit [^], What do you mean with that?
Oct 25 14:50:24 <ubptgbot> <rixchy> # CONFIG_KERNEL_GZIP is not set
Oct 25 14:50:33 <ubptgbot> <rixchy> Shouldn't this be set to y?
Oct 25 14:50:49 <ubptgbot> <NotKit> before I asked you if you have this problem only when CONFIG_NAMESPACES is set
Oct 25 14:50:57 <ubptgbot> <NotKit> with your current config, it will fail even without namespaces
Oct 25 14:51:02 <ubptgbot> <NotKit> @rixchy [Shouldn't this be set to y?], yes
Oct 25 14:51:12 <ubptgbot> <rixchy> Well. It isn't.
Oct 25 14:51:18 <ubptgbot> <rixchy> It is unset, as you see.
Oct 25 14:51:46 <ubptgbot> <rixchy> Is it okay if these both are enabled? "CONFIG_KERNEL_GZIP=y … CONFIG_KERNEL_LZMA=y"
Oct 25 14:52:01 <ubptgbot> <NotKit> yes
Oct 25 14:52:23 <ubptgbot> <rixchy> Okay. I enabled GZIP in all 4 lines, let's see what device will do.
Oct 25 14:52:44 <ubptgbot> <NotKit> but basically to make use of LZMA if you tried to fit into 8 mb partiton, you need to recompress halium-boot ramdisk with it instead of gzip
Oct 25 14:55:51 <ubptgbot> <rixchy> That is why I disabled GZIP, because I tried to build halium-boot, for now I want to see running Plasma Mobile or atleast Halium reference rootfs.
Oct 25 14:59:45 <ubptgbot> <rixchy> Okay, I flashed the hybris-boot, aand. It is rebooting...
Oct 25 14:59:55 <ubptgbot> <rixchy> Let's look at the logs again.
Oct 25 15:01:29 <ubptgbot> <rixchy> The userdata's is again doing this.
Oct 25 15:01:38 <ubptgbot> <rixchy> We successfully fixed the GZIP problem, but...
Oct 25 15:01:40 <ubptgbot> <rixchy> "[    6.491936]  [B2:           mount:   298] EXT2-fs (mmcblk0p21): error: couldn't mount because of unsupported optional features (44) … [    6.523131]  [B2:           mount:   298] EXT4-fs (mmcblk0p21): couldn't mount as ext3 due to feature incompatibilities"
Oct 25 15:02:05 <ubptgbot> <rixchy> @rixchy ["[    6.491936]  [B2:           mount:   298] EXT2-fs (mmcblk0p21): error: could …], Oh, let me reformat it manually.
Oct 25 15:03:14 <ubptgbot> <rixchy> Hm, still rebooting.
Oct 25 15:04:09 <ubptgbot> <rixchy> Now, the log is shorter. The "mount" issue is gone, because I reformatted userdata as ext3.
Oct 25 15:04:44 <ubptgbot> <rixchy> Hey, we're getting a new error! "mmc_force_presence_change: called for device exynos5_device_dwmci1"
Oct 25 15:11:05 <ubptgbot> <dohniks> @rixchy [Hey, we're getting a new error! "mmc_force_presence_change: called for device ex …], full log pls
Oct 25 15:11:14 <ubptgbot> <rixchy> Hm sure.
Oct 25 15:11:27 <ubptgbot> <rixchy> Here is something: "arch/arm/configs/lineageos_chagalllte_defconfig:1090:warning: unexpected data … arch/arm/configs/lineageos_chagalllte_defconfig:1240:warning: override: reassigning to symbol BT_HCIUART" Not the whole log obvi, BRB.
Oct 25 15:11:48 <ubptgbot> <rixchy> Here, https://pastebin.com/etX78Q5j
Oct 25 15:12:19 <ubptgbot> <rixchy> It is confused about this line? "CONFIG_BT_HCIUART=y"...
Oct 25 15:12:34 <ubptgbot> <dohniks> flex-2.5.39: loadlocale.c:130: _nl_intern_locale_data: Assertion `cnt < (sizeof (_nl_value_type_LC_TIME) / sizeof (_nl_value_type_LC_TIME[0]))' failed.
Oct 25 15:12:40 <ubptgbot> <dohniks> known problem, look at the docs
Oct 25 15:12:57 <ubptgbot> <rixchy> @dohniks [flex-2.5.39: loadlocale.c:130: _nl_intern_locale_data: Assertion `cnt < (sizeof …], Didn't notice that, sorry. (I hit this error on my first build too.)
Oct 25 15:14:11 <ubptgbot> <rixchy> That fixed it, thanks!
Oct 25 15:17:52 <ubptgbot> <nanu a> @rixchy [That fixed it, thanks!], You know porting is a game with lots of traps hahaha
Oct 25 15:18:23 <ubptgbot> <rixchy> I DIDNT REALIZE THAT WE ARE CHATTING IN THE GROUP @dohniks
Oct 25 15:18:26 <ubptgbot> <rixchy> HAHA.
Oct 25 15:18:47 <ubptgbot> <rixchy> @nanu a [You know porting is a game with lots of traps hahaha], Yeah, that is kind of true. Have been porting for like idk 5 days now.
Oct 25 15:20:12 <ubptgbot> <nanu a> In this chat are lots of solutions for really specific devices that can be used, but the game so difficult that there is no common walkthrough ;)
Oct 25 15:20:53 <ubptgbot> <rixchy> I hope seeing something appearing on screen and every feature working on my device, will motivate me to port more. ;)
Oct 25 15:21:10 <ubptgbot> <rixchy> I wish Apple would give such freedom on their devices.
Oct 25 15:21:36 <ubptgbot> <Shakendo> @nanu a [In this chat are lots of solutions for really specific devices that can be used, …], Thats cause each device has different issues
Oct 25 15:22:01 <ubptgbot> <rixchy> Well, yeah. And sometimes, those issues you are having, are not found on Google!
Oct 25 15:28:32 <ubptgbot> <rixchy> (Document) https://irc.ubports.com/UKLC0K5x.png
Oct 25 15:30:07 <ubptgbot> <Mattia990> @rixchy [<reply to media>], Yeah, me too😂😂
Oct 25 15:30:25 <ubptgbot> <rixchy> Haha. 😂
Oct 25 15:31:02 <ubptgbot> <fredldotme> If you know this is off-topic then why post it?
Oct 25 15:34:32 <ubptgbot> <rixchy> Is it normal that TWRP says that there is no OS installed? Tho I pushed the system.img and rootfs to ADB using halium-install?
Oct 25 15:34:37 <ubptgbot> <UniversalSuperBox> Yes
Oct 25 15:34:58 <ubptgbot> <rixchy> Oh, alright. Thank you for letting me know that!
Oct 25 15:35:18 <ubptgbot> <rixchy> I booted my device, waited for a couple of seconds. It didn
Oct 25 15:35:30 <ubptgbot> <rixchy> [Edit] I booted my device, waited for a couple of seconds. It didn't reboot... but then it rebooted.
Oct 25 15:35:53 <ubptgbot> <rixchy> But it took a longer time after start-up, so some other error is causing this.
Oct 25 15:36:36 <ubptgbot> <rixchy> Hm. "kernel BUG at /home/rixchy_/halium/kernel/samsung/exynos5420/drivers/net/loopback.c:205!"
Oct 25 15:39:09 <ubptgbot> <rixchy> The same error as before, too. "Internal error: Oops - BUG: 0 [#1] PREEMPT SMP ARM"
Oct 25 16:19:54 <ubptgbot> <rixchy> Hm, if "CONFIG_BTRFS_FS" is set to y, then ninja and build fails.
Oct 25 16:23:57 <Herrie> rixchy: You shouldn't/wouldn't need that one really. Stick to standard FS and not the exotic ones.
Oct 25 16:24:12 <ubptgbot> <rixchy> Ok, I fixed those values and disable BTRFS, but..
Oct 25 16:24:18 <ubptgbot> <rixchy> My device reboots, and I have good news.
Oct 25 16:24:26 <ubptgbot> <rixchy> The log doesn't end with device rebooting line..
Oct 25 16:24:31 <ubptgbot> <rixchy> It ends with "EXT4-fs (loop0): couldn't mount as ext3 due to feature incompatibilities"
Oct 25 16:24:40 <ubptgbot> <rixchy> And then "no errors were detected"...
Oct 25 16:25:26 <Herrie> Ok well maybe you need to adjust your fstab?
Oct 25 16:25:43 <Herrie> Or you don't get to that part yet where it's reading fstab
Oct 25 16:25:44 <ubptgbot> <rixchy> @Herrie [Ok well maybe you need to adjust your fstab?], Hm, I will look into that.
Oct 25 16:26:06 <Herrie> This should be documented in general
Oct 25 16:26:51 <ubptgbot> <rixchy> @Herrie [Ok well maybe you need to adjust your fstab?], No such thing as "loop0" here.
Oct 25 16:27:08 <ubptgbot> <rixchy> Should I pastebin the fstab?
Oct 25 16:27:14 <Herrie> Yes please
Oct 25 16:27:18 <ubptgbot> <rixchy> Alright.
Oct 25 16:27:35 <Herrie> Can have a quick peak while I'm in the train
Oct 25 16:27:42 <ubptgbot> <rixchy> Sure. Here: https://pastebin.com/zSfTjkeW
Oct 25 16:31:12 <Herrie> Not sure about this. I don't see anything odd, but removing errors=panic might be a good start
Oct 25 16:31:46 <Herrie> I don't remember f2fs was OK or not
Oct 25 16:31:58 <Herrie> Also encryptable footer
Oct 25 16:32:06 <Herrie> Which device is this again?
Oct 25 16:32:07 <ubptgbot> <rixchy> That error is the only error I found in the log.
Oct 25 16:32:19 <ubptgbot> <rixchy> @Herrie [Which device is this again?], Samsung Galaxy Tab S 10.5 LTE (chagalllte)
Oct 25 16:37:51 <Herrie> For another Samsung device: https://github.com/minlexx/android_device_samsung_klte-common/commit/b63dbe84bf71d43f2dd3afc02deed50ab48bc9fb
Oct 25 16:37:53 <Herrie> They put errors=continue
Oct 25 16:37:58 <Herrie> That might make more sense
Oct 25 16:38:16 <ubptgbot> <rixchy> Hm, I deleted the line error=panic, is that alright?
Oct 25 16:39:24 <Herrie> Another one seems to have no errors at all: https://github.com/TuxThePenguin0/android_device_samsung_loganreltexx/blob/halium-7/rootdir/fstab.qcom#L8
Oct 25 16:39:29 <Herrie> So I guess you should be OK
Oct 25 16:39:34 <ubptgbot> <rixchy> Alright.
Oct 25 16:39:39 <Herrie> I'm not too familiar with all this fstab bits either
Oct 25 16:39:53 <Herrie> just errors=panic is not the best option for sure ;)
Oct 25 16:40:04 <Herrie> This low level part is always the most tedious
Oct 25 16:40:19 <ubptgbot> <rixchy> @Herrie [just errors=panic is not the best option for sure ;)], I agree, let's try that.
Oct 25 16:40:26 <Herrie> I remember I was stuck with my Xiaomi Mido for a while with all this
Oct 25 16:40:35 <Herrie> Once I got these bits sorted it was mostly straight forward
Oct 25 16:41:26 <ubptgbot> <rixchy> Okay, that gave me some motivation. But the device is still rebooting, let's see the logs..
Oct 25 16:42:45 <ubptgbot> <rixchy> Nope, didn't fix.. "EXT4-fs (loop0): couldn't mount as ext3 due to feature incompatibilities"
Oct 25 16:43:38 <Herrie> Did you enable ext4 in defconfig
Oct 25 16:43:45 <ubptgbot> <rixchy> How..?
Oct 25 16:43:46 <ubptgbot> <rixchy> xD
Oct 25 16:43:49 <Herrie> Seems it's trying to mount ext4 and ext3 by reading it
Oct 25 16:43:59 <ubptgbot> <rixchy> Maybe it is enabled by default? What is the CONFIG?
Oct 25 16:44:33 <Herrie> https://github.com/Halium/android_kernel_lge_hammerhead/blob/20f7c00077aac7890cd0c9f3404727614e64b9e0/arch/arm/configs/cyanogenmod_hammerhead_defconfig#L3054
Oct 25 16:44:48 <Herrie> Those are set for Hammerhead
Oct 25 16:45:15 <Herrie> But I would expect that Mer's verify kernel script would cover those?
Oct 25 16:45:28 <ubptgbot> <rixchy> "CONFIG_EXT4_FS=y … CONFIG_EXT4_USE_FOR_EXT23=y"
Oct 25 16:45:54 <Herrie> Well you can enable the other EXT4 ones that are in Hammerhead
Oct 25 16:45:58 <Herrie> They shouldn't hurt
Oct 25 16:46:31 <ubptgbot> <rixchy> How about I enable this? "# CONFIG_EXT4_DEBUG is not set"
Oct 25 16:46:46 <ubptgbot> <rixchy> What is this line? "CONFIG_EXT4_FS_SECURITY=y"
Oct 25 17:03:04 <Herrie> Not sure what all of them do
Oct 25 17:03:13 <Herrie> Debug one might be good to enable
Oct 25 17:26:43 <ubptgbot> <rixchy> I did.
Oct 25 17:27:14 <ubptgbot> <rixchy> Are👏you👏kidding👏me? "[    6.595012]  [B3:           mount:   302] EXT3-fs (loop0): error: couldn't mount because of unsupported optional features (240) … [    6.627085]  [B3:           mount:   302] EXT2-fs (loop0): error: couldn't mount because of unsupported optional features (244)"
Oct 25 17:29:25 <Akatsu> its normal, it will retry till it get it
Oct 25 17:29:32 <Akatsu> it takes like 2 more attempts
Oct 25 17:29:43 <Akatsu> have you fixed namespaces?
Oct 25 17:29:52 <ubptgbot> <rixchy> WDYM?
Oct 25 17:32:47 <ubptgbot> <rixchy> @Akatsu [it takes like 2 more attempts], What do you mean by "2 more attempts"? Like 2 more boot times?
Oct 25 17:34:04 <ubptgbot> <Mattia990> @rixchy [What do you mean by "2 more attempts"? Like 2 more boot times?], No, it tries with ext2, ext3 and ext4
Oct 25 17:34:09 <ubptgbot> <Akatsu .> *
Oct 25 17:34:10 <ubptgbot> <Akatsu .> ^
Oct 25 17:34:16 <ubptgbot> <rixchy> Oh.
Oct 25 17:34:18 <ubptgbot> <Flohack> @rixchy [It ends with "EXT4-fs (loop0): couldn't mount as ext3 due to feature incompatibi …], Thats expected, it probes ext2, 3 and finally 4
Oct 25 17:34:35 <ubptgbot> <rixchy> But the device is rebooting in a loop.
Oct 25 17:34:50 <ubptgbot> <Mattia990> @rixchy [But the device is rebooting in a loop.], After that lines do you see something else?
Oct 25 17:34:52 <ubptgbot> <Flohack> So no errors detected means it found the partition and will mount it
Oct 25 17:35:10 <ubptgbot> <Flohack> You got a different problem, fs support seems ok
Oct 25 17:35:37 <ubptgbot> <rixchy> @Mattia990 [After that lines do you see something else?], I will pastebin the whole log, BRB.
Oct 25 17:36:08 <ubptgbot> <rixchy> Here is the last_kmsg https://pastebin.com/g462gsAr
Oct 25 17:36:21 <ubptgbot> <Flohack> @Mattia990 [After that lines do you see something else?], Did you ever try to add break=bottom to the kernel cmdline to halt in the init script?
Oct 25 17:36:37 <ubptgbot> <rixchy> No.
Oct 25 17:36:54 <ubptgbot> <Flohack> This will allow you early init debugging and is documented in the docs I think
Oct 25 17:37:05 <ubptgbot> <Flohack> Will open a telnet session
Oct 25 17:37:06 <ubptgbot> <Mattia990> @rixchy [I will pastebin the whole log, BRB.], I remember one thing … For my device there are 2 branches for kernel, one called cm-14.1 and the other called cm14.1-caf, for me the first didn't work and the second yes. … Can you check if you have different branches?
Oct 25 17:37:19 <ubptgbot> <rixchy> Hm, let me see.
Oct 25 17:37:25 <ubptgbot> <Flohack> If this does not bootloop anymore then your kernel is roughly ok
Oct 25 17:37:32 <ubptgbot> <rixchy> On the kernel repo?
Oct 25 17:37:54 <ubptgbot> <Flohack> If it still bootloops you might still have kernel issues
Oct 25 17:38:00 <ubptgbot> <rixchy> @Mattia990 [I remember one thing … For my device there are 2 branches for kernel, one called c …], Nope.
Oct 25 17:38:10 <ubptgbot> <rixchy> @Flohack [Did you ever try to add break=bottom to the kernel cmdline to halt in the init s …], But how do you do that?
Oct 25 17:38:17 <ubptgbot> <rixchy> What is that cmdline?
Oct 25 17:38:53 <ubptgbot> <Flohack> Kernel cmdline can be added in device cinfig .mk file or as kernel config option
Oct 25 17:39:09 <ubptgbot> <Flohack> I have no time rn but guys here can explain hopefully
Oct 25 17:39:21 <ubptgbot> <rixchy> Okay.
Oct 25 17:39:32 <ubptgbot> <dohniks> @Flohack [Did you ever try to add break=bottom to the kernel cmdline to halt in the init s …], That's for ubports though. If @rixchy you are on hybris-boot it will not work
Oct 25 17:39:46 <ubptgbot> <rixchy> @dohniks [That's for ubports though. If @rixchy you are on hybris-boot it will not work], Why?
Oct 25 17:40:01 <ubptgbot> <dohniks> It's a feature of ubports init
Oct 25 17:40:14 <ubptgbot> <rixchy> Oh, then okay.
Oct 25 17:40:26 <ubptgbot> <rixchy> Thank you for letting me know that.'
Oct 25 17:40:38 <ubptgbot> <Flohack> Oh sorry but there is telnet on Halium reference as well
Oct 25 17:40:51 <ubptgbot> <Flohack> Dont know how to turn it on :)
Oct 25 17:41:19 <ubptgbot> <dohniks> really? in the rootfs or the one in init?
Oct 25 17:43:04 <ubptgbot> <dohniks> actually, where is the source for halium reference rootfs?
Oct 25 17:43:22 <ubptgbot> <dohniks> it's not here: https://github.com/Halium/rootfs-builder 😋
Oct 25 17:43:28 <ubptgbot> <rixchy> @Flohack [Dont know how to turn it on :)], I think he is talking about hybris-recovery.
Oct 25 17:43:44 <ubptgbot> <Mattia990> @dohniks [really? in the rootfs or the one in init?], Here https://github.com/Halium/hybris-boot/blob/2394e925f72226e1c6c2fa98bce62a63596d5430/init-script#L293
Oct 25 17:43:55 <ubptgbot> <Mattia990> @dohniks [really? in the rootfs or the one in init?], [Edit] Here https://github.com/Halium/hybris-boot/blob/2394e925f72226e1c6c2fa98bce62a63596d5430/init-script#L293 … In the init script
Oct 25 17:44:27 <ubptgbot> <dohniks> @Mattia990 no, that's initrd. I mean the rootfs and the init system inside
Oct 25 17:44:39 <ubptgbot> <dohniks> the one we hand over to with switch_root
Oct 25 17:44:52 <ubptgbot> <Mattia990> @dohniks [@Mattia990 no, that's initrd. I mean the rootfs and the init system inside], Ahhh idk😂
Oct 25 17:46:01 <ubptgbot> <dohniks> the one that we download from @bhushanshah 's server here: http://docs.halium.org/en/latest/porting/install-build/reference-rootfs.html#install-rootfs-and-system-img
Oct 25 17:47:42 <ubptgbot> <Mattia990> @rixchy Are you using this kernel? … https://github.com/LineageOS/android_kernel_samsung_exynos5420
Oct 25 17:47:49 <ubptgbot> <rixchy> Yup.
Oct 25 17:54:27 <ubptgbot> <rixchy> But this happens only when CONFIG_NAMESPACES is set to y in defconfig.
Oct 25 18:54:44 <ubptgbot> <Matti Laine> 🛑  🔥️️️️️️📣🧠}  💰🔥️️️️️️🔥️️️️️️💰Еvеrуdау payоuts 9.99%ЕTH  25% rеf. 299.7% mоnthlу! Withоut limits Withdrawаl💵💰🔥️️️️️️🔥️️️️️️  🚧🚧🥇💰
Oct 25 19:20:18 <ubptgbot> <rixchy> "[   12.944908]  [B1:      (ostnamed):   865] kernel BUG at /home/rixchy_/halium/kernel/samsung/exynos5420/drivers/net/loopback.c:205! … [   12.945146]  [B1:      (ostnamed):   865] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP ARM"
Oct 25 19:50:01 <ubptgbot> <Mattia990> @rixchy ["[   12.944908]  [B1:      (ostnamed):   865] kernel BUG at /home/rixchy_/halium …], https://stackoverflow.com/questions/13302046/kernel-oops-page-fault-error-codes-for-arm
Oct 25 19:50:15 <ubptgbot> <Mattia990> What i've found
Oct 25 19:50:23 <ubptgbot> <rixchy> " … Put "rootfstype=ext4" on your boot command line and it should go away."
Oct 25 19:50:29 <ubptgbot> <rixchy> Where is this boot command line?
Oct 25 19:50:39 <ubptgbot> <rixchy> If there's such a thing in Halium.
Oct 25 19:51:10 <ubptgbot> <rixchy> I found that thread too, saw it a couple of times, looked into it, but there isn't a fix for my problem.
Oct 25 19:55:34 <ubptgbot> <Mattia990> @rixchy [I found that thread too, saw it a couple of times, looked into it, but there isn …], Cmdline is in device common tree/BoardConfigCommon.mk but in your i can't find it … Mine for example: https://github.com/halium-gemini/android_device_xiaomi_msm8996-common/blob/a38f321de99588b2304134c5be143b1d197a6779/BoardConfigCommon.mk#L47
Oct 25 19:57:11 <ubptgbot> <rixchy> Oh, sure.
Oct 25 19:57:19 <ubptgbot> <Mattia990> @rixchy [I found that thread too, saw it a couple of times, looked into it, but there isn …], Maybe you can add it here: https://github.com/LineageOS/android_device_samsung_exynos5420-common/blob/771624a8b093668d0cfe70f6e31c0e3a71a1fca9/BoardConfigCommon.mk#L46
Oct 25 19:57:28 <ubptgbot> <rixchy> https://forums.gentoo.org/viewtopic-p-7259024.html
Oct 25 19:57:35 <ubptgbot> <Mattia990> And put your things
Oct 25 20:20:51 <ubptgbot> <rixchy> What kind of error is this anyways: "Internal error: Oops - BUG: 0 [#1] PREEMPT SMP ARM" Is this a RAM memory or a storage memory error? I am confused a little now.
Oct 25 20:21:10 <ubptgbot> <rixchy> "This looks like memory corruption,".
Oct 25 20:21:22 <ubptgbot> <rixchy> (found that in a thread.)
Oct 25 20:22:22 <ubptgbot> <rixchy> Maybe these two issues: "[    6.595012]  [B3:           mount:   302] EXT3-fs (loop0): error: couldn't mount because of unsupported optional features (240) … [    6.627085]  [B3:           mount:   302] EXT2-fs (loop0): error: couldn't mount because of unsupported optional features (244)" and "Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
Oct 25 20:22:22 <ubptgbot>  ARM" are somehow bound together?
**** BEGIN LOGGING AT Fri Oct 25 20:51:06 2019
Oct 25 21:02:38 <ubptgbot> <rixchy> @rixchy [Maybe these two issues: "[    6.595012]  [B3:           mount:   302] EXT3-fs (l …], I have found that these issues are actually bound together, I guess.
Oct 25 21:04:06 <ubptgbot> <rixchy> Could this "kernel BUG at /home/rixchy_/halium/kernel/samsung/exynos5420/drivers/net/loopback.c:205!" and this "Internal error: Oops - BUG: 0 [#1] PREEMPT SMP ARM" bound?
**** ENDING LOGGING AT Sat Oct 26 02:59:57 2019