15:00:14 #startmeeting Fedora ARM and AArch64 Status Meeting 15:00:14 Meeting started Tue Apr 6 15:00:14 2021 UTC. 15:00:14 This meeting is logged and archived in a public location. 15:00:14 The chair is pwhalen. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:14 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:00:14 The meeting name has been set to 'fedora_arm_and_aarch64_status_meeting' 15:00:14 #chair pwhalen pbrobinson jlinton coremodule 15:00:15 #topic roll call 15:00:15 Current chairs: coremodule jlinton pbrobinson pwhalen 15:00:23 .hello2 15:00:25 good morning folks, who's here today? 15:00:25 coremodule: coremodule 'Geoffrey Marr' 15:00:26 * coremodule is here 15:01:50 * pbrobinson is here 15:02:01 .hello2 15:02:02 lorbus: lorbus 'Christian Glombek' 15:02:07 * lorbus is here too 15:02:39 ok, lets get started 15:02:44 #topic 1) ==== Userspace Status ==== 15:02:51 Any new user space issues to discuss? 15:02:52 * jlinton waves 15:02:58 howdy jlinton! 15:03:23 Not aware of anything in our stable releases, or nothing coming to mind 15:03:55 #info No new issues reported. 15:04:02 #topic 2) ==== Kernel Status ==== 15:04:10 #info kernel-5.11.11-300.fc34 15:04:10 #link https://koji.fedoraproject.org/koji/buildinfo?buildID=1729954 15:04:39 #info kernel-5.12.0-0.rc6.184.fc35 15:04:39 #link https://koji.fedoraproject.org/koji/buildinfo?buildID=1732452 15:05:25 5.11 seems good, has anyone hit issues with 5.12? 15:05:31 nothing of note from me here, I think the 5.11.x is mostly looking pretty good 15:05:45 no trouble found here 15:06:14 If people could give 5.12 a quick test that would be greatly appreciated, I expect it will land shortly after our GA 15:06:35 yes, i've been mostly running 5.12, it seems ok so far. 15:07:26 excellent. thanks. 15:07:37 #topic 3) ==== Bootloader Status ==== 15:07:46 #info uboot-tools-2021.04-0.6.rc4.fc35 15:07:46 #link https://koji.fedoraproject.org/koji/buildinfo?buildID=1724531 15:08:27 we have a bug in uboot, filed and accepted as a blocker - https://bugzilla.redhat.com/show_bug.cgi?id=1946278 15:09:15 #info grub2-2.06~rc1-3.fc34 15:09:15 #link https://koji.fedoraproject.org/koji/buildinfo?buildID=1728120 15:10:14 Any other issues? 15:10:48 latest grub2 seems ok 15:11:01 what's the issue with grub2? 15:11:19 I'm working on the rockchip issue and trying to bisect it 15:11:54 not seeing anything with the new grub2, there was a previous bug with the config (no menu entry to boot) 15:12:09 U-Boot 2021.04 GA was released yesterday, working to get a build done for that, trying to get to the bottom of the blocker and rockchip bugs before I push that 15:12:28 awesome, thanks pbrobinson 15:12:38 ok, so the grub2 link was just for reference, I wasn't sure if it was in context of a bug 15:12:43 pbrobinson++ 15:12:43 lorbus: Karma for pbrobinson changed to 9 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 15:12:48 just to ask for testing 15:13:50 #topic 4) ==== Fedora 34 ==== 15:14:11 #info List of final Blockers - https://qa.fedoraproject.org/blockerbugs/milestone/34/final/buglist 15:14:32 #info F34 - Final Freeze - 2021-04-06 (today) 15:14:52 #info F34 - GA - 2021-04-20 15:15:15 #info OpenQA testing: https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=34&build=Fedora-34-20210406.n.0&groupid=5&groupid=1 15:15:33 There is another kernel-firmware tweak needed for the cm4/rpi400's wifi since the SMBIOS string changes, although I guess we can call that F35. 15:16:33 dgilmore submitted a PR to remove the lpae kernel from the armhfp disk images (thanks dgilmore). 15:16:59 jlinton: thee firmware for the rpi400 isn't upstream, it's a different module than the rpi4 so it's a mute point ATM 15:17:46 jlinton: the rpi400 (and I'm assuming cm4) wifi is a broadcom, now synaptics, part 15:17:50 oh figures, well solves the problem of finding a test monkey 15:18:18 jlinton: I'm trying to find a contact there but I've not yet been able to dig deep enough 15:19:04 couple of other issues remain - with the removal of plymouth from comps, some boot messages arent displayed. Not sure what to do about this one, seeing if it causes issues on other arches as well 15:19:23 pwhalen++ 15:19:27 pbrobinson++ 15:20:01 pwhalen: I notices there was a new plymouth that fixes a bunch of stuff, I wonder if the fix is to add it back if that's now fixed? 15:20:05 other issue is we're missing a broswer for armv7. Doesnt look like we'll get firefox back as we had hoped so we should add something else 15:20:37 pbrobinson: it might be, if it solved the x86 issue in openqa. I think that was the only problem 15:21:22 - Fixes 1933378 - Bootsplash doesn't always fully clear on boot to console 15:21:22 - Fixes 1941329 - Flickering plymouth on shutdown/reboot 15:22:13 pwhalen: they're the bits fixed, they sound familiar, but I'm not tracking that, maybe reach out to adamw for his plans/thoughts there? 15:22:16 nice! so we should be able to add it back in 15:22:22 will do , thanks 15:22:58 ok, I think that's all I had for f34 issues. Did I miss anything? 15:25:13 #topic 5) == Open Floor == 15:25:34 Hey everyone. ;) Just thought I would mention my fav 32bit arm oom thing. 15:25:49 with freeze coming, I hope I can find some time to do some more isolation on it. 15:25:57 https://bugzilla.redhat.com/show_bug.cgi?id=1920183 15:26:24 nirik: great, feel free to ping pwhalen/me on the arm channel and we can assist 15:26:33 5.11 didn't seem to help. 15:26:38 I can try 5.12 15:26:45 and/or possibly f34 userspace? 15:26:57 hey nirik, I havent had time to look either, sorry, not forgotten about it at all 15:27:29 now that the account system rollout is done, stg should hopefully be more stable/easy to add access to too 15:29:32 nirik: I suppose where we are ATM maybe if we could get f34 up and running in stage we can test from there? 15:29:44 yeah, should be doable 15:30:32 thanks nirik 15:30:46 nirik: a bunch of the UEFI stuff was cleaned up in the f34 cycle 15:31:38 Anything else for today> 15:31:39 ? 15:32:28 #endmeeting