15:00:25 #startmeeting Fedora ARM and AArch64 Status Meeting 15:00:25 #chair pwhalen pbrobinson coremodule jlinton 15:00:25 Meeting started Tue Oct 12 15:00:25 2021 UTC. 15:00:25 This meeting is logged and archived in a public location. 15:00:25 The chair is pwhalen. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 15:00:25 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:00:25 The meeting name has been set to 'fedora_arm_and_aarch64_status_meeting' 15:00:25 Current chairs: coremodule jlinton pbrobinson pwhalen 15:00:26 #topic roll call 15:00:37 Good morning, who's here today? 15:00:44 I'm here 15:01:21 howdy rbutler1728 15:01:42 * coremodule is here 15:03:37 Ok, thanks for joining, lets get started. 15:03:44 #topic 1) ==== Userspace Status ==== 15:04:05 Any newly reported issues in user space? 15:05:15 #info No new issues reported. 15:05:25 #topic 2) ==== Kernel Status ==== 15:05:34 #info kernel-5.15.0-0.rc5.39.fc36 15:05:34 #link https://koji.fedoraproject.org/koji/buildinfo?buildID=1844258 15:06:09 I've not done enough testing of 5.15, I'll get that done today. 15:06:18 Has anyone done any testing there? 15:06:35 I haven't 15:06:49 this may be caused by a userspace issue, but I got kernel panic on reboot after installing fedora 35 15:06:56 https://bugzilla.redhat.com/show_bug.cgi?id=2013053 15:07:40 I think it was caused by a slow virtual UB CD drive 15:08:38 * pbrobinson is here. sorry I'm late 15:08:43 this also may be a userspace issue, but I got high cpu usage by cppc_fie even when idle - https://bugzilla.redhat.com/show_bug.cgi?id=2012226 15:08:55 rbutler1728: what HW? 15:09:03 Ampere Altra 15:10:56 ah, don't suppose you know if the platform is running the latest firmwares (BMC and others) or if the vendor is aware of a problem then? 15:11:35 I'm not sure offhand 15:12:13 on shutdown I could tell it was accessing the virtual USB CD drive which likely caused the timeout which led to the kernel panic 15:12:51 right, which given then way all the BMC virtual stuff works from memory it could be quite a chain of events 15:13:27 thanks rbutler1728, I'll try that hardware today to see if I can reproduce the panic 15:14:25 awesome, thanks! 15:15:58 #info kernel-5.14.10-300.fc35 15:15:58 #link https://koji.fedoraproject.org/koji/buildinfo?buildID=1843224 15:16:43 we have 5.14.11 as well, but I think the release kernel will be 5.14.10 so best to focus testing there 15:17:00 yes, ATM I would agree with that sentiment 15:17:03 #info Please test and report any issues to the list or #fedora-arm. 15:17:22 Any other kernel news? 15:17:40 not from me 15:17:59 #topic 3) ==== Bootloader Status ==== 15:18:39 #info uboot-tools-2021.10-1.fc35 15:18:39 #link https://koji.fedoraproject.org/koji/buildinfo?buildID=1840300 15:20:52 I tested this all around, only regression I saw was on the RPi400, which was similar to where it was before. Fails with the kernel provided dtb, working with firmware provided dtb 15:21:35 Did anyone else have a chance to test and see something not reporteD? 15:21:45 pwhalen, I saw the same thing. On a sidenote, I tested the serial console on the rpi400 and it worked fine. 15:22:19 right, so I'm not sure the regression there was ever fixed, I suspect it's boarder line that something else changed and it appeared to work for a little while 15:22:41 thanks coremodule 15:22:48 so I don't think the later issues are actually a regression because I don't think the other problem was ever fixed 15:23:06 pbrobinson: agreed, more of a return to where it was 15:23:47 I've got an issue with the UDOO Neo, but it's a minor device, I need to dig further 15:23:57 jlinton had an issue with shim, but I couldn't reproduce that. Could be the firmware he was using 15:23:59 I've got some more testing to do 15:24:26 I think that's not a main shim issue 15:24:46 else we'd have seen it on other platforms 15:25:02 Right. 15:25:05 there's other toolchain issues with shim and secureboot on aarch64 anyway 15:26:23 #topic 4) ==== Fedora 35 ==== 15:26:37 #info Blockers 15:26:37 #link https://qa.fedoraproject.org/blockerbugs/milestone/35/final/buglist 15:26:58 #info Fedora 35 aarch64 cloud image based openstack VM hangs 15:26:58 #link https://bugzilla.redhat.com/show_bug.cgi?id=2011928 15:27:41 trying to reproduce this now in AWS 15:28:54 It was nominated as a blocker but punted for more info 15:29:11 #info [abrt] gnome-shell: cogl_texture_get_gl_texture(): gnome-shell killed by SIGSEGV 15:29:11 #link https://bugzilla.redhat.com/show_bug.cgi?id=1989726 15:30:02 Karol posted a patch, I dont think we have a build yet 15:30:34 #info Patch posted, new build expected soon. 15:31:26 #info Latest Fedora 35 Nominated Nightly 15:31:26 #link https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test 15:31:49 I've just started testing this 15:32:24 OpenQA results look good. 15:32:32 #link https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=35&build=Fedora-35-20211010.n.0&groupid=5 15:32:54 I'm sure adam or others will do a build, I can if necessary 15:33:43 Ok, thanks. 15:33:52 Anything not mentioned? Concerns etc? 15:34:45 coremodule: do you think an RC is expected soon? Not sure the status of all the blockers 15:36:07 I can't really say, but I'm betting we will slip one week 15:36:26 *I can't really say, because I'm always wrong, not because I know something that you don't 15:36:39 *often wrong when it comes to this, hah 15:37:03 Oh sorry, read that wrong 15:37:03 Thanks, seems like it to me as well based on the number of blockers but not sure how far along they are. 15:37:33 some we are still waiting for upstream and theres really nothing we can do... I think there were three bugs as of yesterday like that 15:38:38 Right, ok. 15:38:41 Thanks coremodule 15:38:54 Anything else for F35? 15:39:26 #topic 5) == Open Floor == 15:41:33 Anything for open floor? 15:42:48 #endmeeting