15:00:55 #startmeeting Fedora ARM and AArch64 Status Meeting 15:00:55 Meeting started Tue Feb 9 15:00:55 2021 UTC. 15:00:55 This meeting is logged and archived in a public location. 15:00:55 The chair is pwhalen. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:55 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:00:55 The meeting name has been set to 'fedora_arm_and_aarch64_status_meeting' 15:00:55 #chair pwhalen pbrobinson jlinton coremodule 15:00:55 Current chairs: coremodule jlinton pbrobinson pwhalen 15:00:55 #topic roll call 15:01:05 good morning folks, who's here today? 15:01:33 * jlinton waves 15:01:58 * coremodule is here! 15:03:30 ok, lets get started 15:03:37 #topic 1) ==== Userspace Status ==== 15:04:15 Not aware of anything significant here, anyone else? 15:05:22 #info No new problems reported. 15:05:32 #topic 2) ==== Kernel Status ==== 15:05:41 #info kernel-5.11.0-0.rc7.149.fc34 15:05:41 #link https://koji.fedoraproject.org/koji/buildinfo?buildID=1705020 15:06:05 #info Fixes some Virt & Podman issues on all arches. [Bug 1920857] 15:06:29 * x3mboy waves his hands on the air 15:07:01 Some other reported issues 15:07:05 #info Raspberry Pi 3B+ boots incredibly slow after CPU failed to come online errors 15:07:05 #link https://bugzilla.redhat.com/show_bug.cgi?id=1921924 15:08:13 I've not yet tested RC7 to see if it improves there 15:09:31 #info Overeager OOM kills on 5.10 kernels on 32bit arm with lpae 15:09:31 #link https://bugzilla.redhat.com/show_bug.cgi?id=1920183 15:10:24 This is the builder issue, last weke nirik setup a test builder in staging, queued up a task and the python3.8 build worked ok. 15:11:19 builds of GCC and python3.8 (with tests) have also worked ok for me, so it seems this is tricky to reproduce 15:11:47 I'm just starting to look more at the 5.11 kernels 15:12:31 pbrobinson: awesome, thanks 15:12:57 pwhalen: I'm not seeing the rpi3 issue but will be taking a closer look at it soon, we kind of need a reproducer there 15:13:51 Ok, I think I reproduced last week just booting aarch64, but I'll check again 15:14:18 I'll dedicate some cycles to testing the rpi3 today 15:14:20 as I said, I'm going to be taking a closer look 15:14:22 and report in-bug 15:15:17 Any other kernel issues not mentioned? 15:15:55 * pwhalen hopes not 15:16:18 I need to check the enterprise stuff as well, last check it was looking ok on 5.11 15:16:54 I'm slowly circling through things, nothing major of note 15:17:08 #topic 3) ==== Bootloader Status ==== 15:17:23 #info uboot-tools-2021.04-0.1.rc1.fc34 15:17:23 #link https://koji.fedoraproject.org/koji/buildinfo?buildID=1699614 15:18:09 there's issues with rk3399 devices here 15:18:20 This looks ok so far, no issues. Fixed rpi4 armhfp boot for me 15:18:25 I think it's limited to either that or rockchip in general 15:18:54 #info Reported issues on rk3399 device (may be Rockchip in general, needs more testing). 15:19:30 it's a regression in 2021.04, it's working in 2021.01 15:20:11 ok, I still a working rockchip device so if others have them please help to test 15:20:16 #info Please test and report any issues to the list or #fedora-arm. 15:21:08 #topic 4) ==== Fedora 34 ==== 15:21:38 #info Fedora 34 mass rebuild complete. 15:21:38 #link https://kojipkgs.fedoraproject.org/mass-rebuild/f34-failures.html 15:22:11 #info Fedora 34 will branch from Rawhide today(2021-02-09). 15:22:32 #info Latest nominated compose 15:22:32 #link https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test 15:23:27 Yesterdays rawhide testing - https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=Rawhide&build=Fedora-Rawhide-20210208.n.0&groupid=5 15:24:03 lots of soft failures (yellow), most seem to be AVC's 15:25:40 #info Fedora 34 Changeset 15:25:40 #link https://fedoraproject.org/wiki/Releases/34/ChangeSet 15:26:19 #link Full Fedora 34 schedule - https://fedorapeople.org/groups/schedule/f-34/f-34-key-tasks.html 15:27:36 Has anyone hit any issues not yet mentioned? Concerns? 15:29:11 #topic 5) == Open Floor == 15:29:24 Anything else for today? 15:29:33 yes, hang on one second while i pull up the ticket 15:30:28 I know there was some talk before the holidays on getting an "officially supported hardware" list going, just wondering if there was any progress there? 15:30:33 in regard to https://pagure.io/fedora-qa/issue/615 15:31:06 I think the last I talked with pbrobinson, he was figuring up a list, but wasn't ready to release it (this was probably around late November). 15:31:24 I have to finish writing that up 15:31:27 thanks for the reminder 15:31:35 haha no problem! 15:31:54 Hi 15:31:56 part of it is finishing up things like the pinebook pro support which is generally just driving me insane 15:32:17 okay, wfm. as far as pinebook pro, do you mean like an install guide? 15:32:21 the Jetson Nano stuff is done 15:32:35 Is there a recommendation or advice to install a tablet that is not supported? 15:32:39 that makes me sad, can I send you cookies pbrobinson so that you won't be as sad? 15:32:44 no as in actually making it boot again, it was before and it's not now, and it's driving me insane 15:33:02 defolos: it's getting to the point I'll just feed it into a shredder 15:33:21 pbrobinson: anything a non-kernel expert can do? 15:33:51 gotcha, I see. id love to help troubleshoot/debug, but don't have a pinebook pro to do it with. if I can help with docs or anything else, glad to 15:33:59 it's very frustrating, at one point it was all basically working and needed polish, now I don't even get early kernel output, firmware seems OK except the issue I mentioned above 15:34:47 defolos: it's basically 1) early firmware (see above), 2) early kernel stuff 3) dealing with corporate politics of sales of wireless IP AKA wifi modules. Not sure you can deal with any of them sadly 15:35:01 thank goodness most arm devices aren't so difficult. :/ 15:35:15 coremodule: once I have the damn thing working docs etc is easier :) 15:35:16 oh boy, I have no clue about any of these 15:35:26 I only have a pinebook pro 15:35:59 defolos: I thought it was an issue with the rockchips support in the kernel in general but I've booted 4 different devices, 2 of which are rk3399 and they're all OK 15:36:17 it's extremely frustrating 15:36:43 and it may even be a firmware problem that's spilling over into the kernel so ¯\_(ツ)_/¯ 15:37:34 what do other distros do? I've heard that some debian derivatives and postmarketos run superb on the pinebook pro 15:39:50 defolos: massive forked kernels 15:39:58 great 15:40:02 let's not do that 15:40:12 defolos: exactly my point 15:40:43 we just need teams of 10-12 developers working on pinebook pro support specifically, then we'll be oka 15:40:49 ;) 15:40:49 it was working, I suspect it's a very minor thing that changed and broke it, it's just a matter of finding that needle in the haystack, and me finding that time to look for it 15:41:15 coremodule: I think we just need one actually, just one with the right skillset and a few days to go down a rabbit hole 15:41:56 any volunteers? defolos? jlinton? :P 15:42:16 I barely have the knowledge to install postmarketos on the pinephone… 15:42:30 I'd love to, but realistically: I won't be of much help 15:44:23 Lets continue this over in #fedora-arm, closing the meeting 15:44:26 #endmeeting