15:00:21 <pwhalen> #startmeeting Fedora ARM and AArch64 Status Meeting 15:00:21 <zodbot> Meeting started Tue Apr 13 15:00:21 2021 UTC. 15:00:21 <zodbot> This meeting is logged and archived in a public location. 15:00:21 <zodbot> The chair is pwhalen. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:21 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:00:21 <zodbot> The meeting name has been set to 'fedora_arm_and_aarch64_status_meeting' 15:00:21 <pwhalen> #chair pwhalen pbrobinson jlinton coremodule 15:00:21 <zodbot> Current chairs: coremodule jlinton pbrobinson pwhalen 15:00:21 <pwhalen> #topic roll call 15:00:32 <pwhalen> Good morning folks, who's here today? 15:00:37 <coremodule> ./me is here 15:00:41 * coremodule is here 15:00:52 <pwhalen> howdy coremodule! 15:01:07 <coremodule> how are you pwhalen? 15:01:18 <pwhalen> doing ok, yourself? 15:02:06 <coremodule> ready to release!! haha. 15:02:18 <coremodule> ls 15:03:43 * pwhalen waits a few more minutes for others 15:03:47 <pwhalen> I'm not 15:03:51 * jlinton waves 15:03:58 <coremodule> pwhalen, why not? 15:04:31 <pwhalen> no arm disk images yet, we still have an issue loading the dtb in uboot 15:04:41 * pbrobinson is here 15:05:07 <pwhalen> let's do this! 15:05:08 <coremodule> that's true. I guess my thought is I'm ready for release *assuming* everything works 15:05:13 <pwhalen> #topic 1) ==== Userspace Status ==== 15:05:24 <pwhalen> hhe, ok then always ready :D 15:05:40 <pwhalen> Any new user space issues? 15:05:49 <pbrobinson> coremodule: that's a massive assumption ;-) 15:06:04 <pbrobinson> none from me I'm aware of 15:06:22 <pwhalen> #info No new issues. 15:06:25 <pwhalen> nor I 15:06:32 <pwhalen> #topic 2) ==== Kernel Status ==== 15:06:46 <pwhalen> #info kernel-5.11.13-300.fc34 15:06:46 <pwhalen> #link https://koji.fedoraproject.org/koji/buildinfo?buildID=1734897 15:06:55 <jlinton> Maybe a bit late for userspace issues, but i'm seeing parsec start failures on the fedora iot image 15:07:10 <pbrobinson> jlinton: which image, that was fixed 15:07:12 <pwhalen> jlinton: should be fixed in your next update 15:07:49 <pbrobinson> jlinton: fixed in parsec-0.7.0-2.fc34 15:08:11 <pwhalen> https://openqa.fedoraproject.org/tests/855175#step/base_services_start/9 15:08:28 <jlinton> yah this was 6.x f34, ok 15:09:23 <pwhalen> #info kernel-5.12.0-0.rc7.189.fc35 15:09:23 <pwhalen> #link https://koji.fedoraproject.org/koji/buildinfo?buildID=1735336 15:09:48 <pbrobinson> yup, was working with the parsec people on that 15:10:15 <pwhalen> Any idea when we expect 5.12 to land in f34? I expect a couple weeks after GA 15:11:09 <coremodule> I heard 5.12 early may 15:11:25 <pwhalen> #info Please test and report any issues to the list or #fedora-arm. 15:11:43 <coremodule> sorry, 5.12 in updates-testing in early May 15:12:12 <pwhalen> thanks 15:12:30 <pwhalen> Anything else for kernel news? 15:12:56 <pbrobinson> normally after .3 is released, probably 2 weeks to GA as it looks like there will be a rc8 15:12:59 * nirik is lurking in back to mention his armv7 lpae oom bug again if anyone has cycles to poke at it. ;) 15:13:32 <pbrobinson> nirik: I meant to comment on that bug if you could add details for how you recreate it each time 15:13:57 <nirik> Sure, just a python3.8 build in stg does it. But I can add the exact steps. 15:14:10 <pbrobinson> that would be great 15:14:42 <pwhalen> yea, not sure what to do about that one. I couldn't reproduce outside koji but its been a while since I tried. 15:15:04 <pwhalen> And as nirik mentioned last night, the builders are on f32, so soon EOL 15:15:12 <pbrobinson> right 15:15:34 <nirik> https://bugzilla.redhat.com/show_bug.cgi?id=1920183 for those following along at home. 15:16:30 <pwhalen> #topic 3) ==== Bootloader Status ==== 15:17:42 <pwhalen> #info No change here. 15:18:24 <pwhalen> #topic 4) ==== Fedora 34 ==== 15:18:39 <pwhalen> #info OpenQA testing: 15:18:40 <pwhalen> #link https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=34&build=Fedora-34-20210413.n.0&groupid=5&groupid=1 15:19:35 <pwhalen> most failures look common between x86 and aarch64 15:20:04 <pbrobinson> We have the DT blocker, I thought that may have been mentioned in the bootloader status 15:20:05 <jlinton> But it looks like there are fewer aarch64 failures than x86! 15:21:11 <pwhalen> Right, our big blocker is Uboot failing to load the dtb, falls back to firmware provided - which works very well and easy to miss 15:22:43 <pbrobinson> I've think got to the bottom of the bug here, I've now just got to work out the fix 15:23:17 <pwhalen> We're also missing the armhfp disk images, that should get fixed in tomorrows compose I think, we need to pull in the new anaconda . Kickstart change was merged. 15:23:26 <pbrobinson> hoping to close it out today if luck is on my side, which I highly doubt as it hasn't been so far this week 15:23:51 <pwhalen> excellent, thanks pbrobinson 15:24:31 <pwhalen> the plymouth change was also merged last night (thanks nirik), so we should console messages back to normal on new composes 15:24:41 <pwhalen> s/change/revert/ 15:25:18 <pwhalen> anything else not mentioned? 15:25:20 <pbrobinson> that was after Hans improved plymouth I believe 15:25:46 <pwhalen> Right, there was a bug on x86 that got fixed, so we could add plymouth back. 15:27:29 <pwhalen> #topic 5) == Open Floor == 15:27:29 <pbrobinson> the dracut issue with encrypted filesystems landed a fix too in the last compose 15:27:42 <pwhalen> #undo 15:27:42 <zodbot> Removing item from minutes: <MeetBot.items.Topic object at 0x7f25b6ef4190> 15:28:01 <pwhalen> Right, I didnt get hit by that but it should be fixed 15:28:38 <pwhalen> #topic 5) == Open Floor == 15:29:22 <pwhalen> Anything else for today? 15:30:41 <coremodule> just wanted to mention 15:30:58 <coremodule> there is an IoT test week occurring currently: https://testdays.fedoraproject.org/events/110 15:31:20 <coremodule> I realize this is the ARM meeting. 15:31:30 <coremodule> but just a reminder 15:32:04 <pwhalen> thanks. 15:34:03 <pwhalen> #endmeeting