16:00:24 <pwhalen> #startmeeting Fedora ARM and AArch64 Status Meeting 16:00:24 <zodbot> Meeting started Tue Feb 8 16:00:24 2022 UTC. 16:00:24 <zodbot> This meeting is logged and archived in a public location. 16:00:24 <zodbot> The chair is pwhalen. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 16:00:24 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:00:24 <zodbot> The meeting name has been set to 'fedora_arm_and_aarch64_status_meeting' 16:00:24 <pwhalen> #chair pwhalen pbrobinson coremodule jlinton 16:00:24 <pwhalen> #topic roll call 16:00:24 <zodbot> Current chairs: coremodule jlinton pbrobinson pwhalen 16:00:38 * jlinton waves 16:00:39 <pwhalen> Good morning folks, who's here today? 16:00:42 * coremodule is here, good morning pwhalen. 16:01:34 * pwhalen gives it a couple of minutes for others to join 16:03:23 <pwhalen> #topic 1) ==== Userspace Status ==== 16:03:39 <pwhalen> Any new issues in user space to discuss? 16:04:55 <pwhalen> #info No new issues reported. 16:05:03 <pwhalen> #topic 2) ==== Kernel Status ==== 16:05:13 <pwhalen> #info kernel-5.17.0-0.rc3.89.fc36 16:05:13 <pwhalen> #link https://koji.fedoraproject.org/koji/buildinfo?buildID=1914552 16:06:01 <pwhalen> started testing this, have a couple bugs to file. Not seeing console output on the mustang, I think that started in rc2. 16:07:10 <pwhalen> also seeing an issue with the Raspberry Pi 4 wired network 16:07:54 <pwhalen> Jetson NX crashes under any network load, I believe thats a known issue 16:07:58 <jlinton> Yah, I saw some ugly XHCI loading splat on the rpi4 yesterday from the prove locking config, I haven't tracked that down yet. 16:08:11 <coremodule> updating jetson nano now to give a test... 16:09:33 <pwhalen> Great, thanks. 16:09:53 <pwhalen> Any other kernel issues? 16:11:02 <pwhalen> #info Please test and report any issues to the list or #fedora-arm. 16:11:22 <pwhalen> #topic 3) ==== Bootloader Status ==== 16:11:41 <pwhalen> #info uboot-tools-2022.04-0.1.rc1.fc36 16:11:41 <pwhalen> #link https://koji.fedoraproject.org/koji/buildinfo?buildID=1911839 16:12:05 <pwhalen> New uboot to test on your favourite device 16:12:57 <pwhalen> I just noticed a fancy yellow submarine uboot logo when testing yesterday, I think thats new with this release 16:13:51 <pwhalen> #topic 4) ==== Fedora 36 ==== 16:14:04 <pwhalen> #info Today (Tue 2022-02-08) - Branch Fedora Linux 36 from Rawhide. 16:14:22 <pwhalen> #info OpenQA testing - https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=Rawhide&build=Fedora-Rawhide-20220208.n.0&groupid=5 16:15:55 <pwhalen> I'm going to rerun some of those failures after the meeting 16:16:06 <pwhalen> #info F36 Beta Blocker Bugs - https://qa.fedoraproject.org/blockerbugs/milestone/36/beta/buglist 16:16:44 * nirik has a few items for open floor. ;) 16:16:46 <pwhalen> hrm, apparently that page isnt working of me 16:16:57 <pwhalen> Reason: DNS lookup failure for: worker04.ocp.iad2.fedoraproject.org 16:17:05 <pwhalen> heh, howdy nirik 16:17:16 <nirik> weird. it loads ok here. 16:17:30 <pwhalen> refresh worked 16:17:40 <nirik> it was just moved to openshift. 16:17:48 <pwhalen> ah, ok 16:18:19 <pwhalen> I also filed an issue with the disk images being corrupted when sent from the builder to hub 16:18:29 <nirik> yeah, thats really weird 16:18:37 <pwhalen> #info armhfp disk images are often corrupted during transfer from builder to hub 16:18:37 <pwhalen> #link https://pagure.io/releng/issue/10622 16:18:48 <nirik> do you know when it started faiiing? 16:19:17 <pwhalen> I mentioned it in releng when I first noticed, a couple weeks back I think 16:19:30 <nirik> huh. but the job is successfull right? 16:19:52 <pwhalen> Yes> checksum matches as well 16:21:13 <nirik> ok, odd. just needs digging now I guess... 16:21:19 <pwhalen> There is also still an issue with the raspberry pi fw on armhfp, aarch64 seems ok 16:22:09 <pwhalen> nirik: I'll try to see when I first noticed it, add it to the ticket. 16:22:24 <nirik> yeah, that might be helpfull to figure out where to look for what changed. 16:23:12 <pwhalen> Any other issues in F36? 16:25:39 <pwhalen> #topic 5) == Open Floor == 16:25:51 <pwhalen> nirik: the floor is yours :) 16:26:03 <nirik> ok, one thing was that image thing we already talked about. ;) 16:26:29 <pwhalen> I figured :) 16:26:33 <nirik> Next thing was pinephone* :) I don't suppose new uboot has any support yet? 16:26:49 <pwhalen> I got one! Need to unbox 16:27:26 <nirik> cool. ;) 16:27:34 <nirik> I got my keyboard battery case... 16:28:06 <nirik> things are pretty early days for fedora support tho. There are some better signs than pinephone had at least... 16:29:10 <pwhalen> we need our uboot expert 16:29:28 <pwhalen> I see 'pinephone' in the latest, but nothing pro 16:29:56 <nirik> encouraging from megi (who's done lots of kernel support): "I'll step away from this work for a while to prepare basic device tree for Pinephone Pro and submit it mainline." 16:30:23 <nirik> I really someday need to learn how dts/uboot/etc all work. 16:30:37 <nirik> anyhow, that was it, just wanted to raise some awareness. There's also a thread on the arm list. 16:30:38 <pwhalen> nirik: does anything exist now for someone to get started with Fedora? 16:30:45 <coremodule> me too 16:31:05 <nirik> there's a test image I have now, hopefully we will have a remix before too long. 16:31:26 <pwhalen> right, thanks for mentioning it. I need to get some time to play around with it 16:31:27 <nirik> note: I am not making the test image or remix, it's folks in #fedora-mobility. Please see there for more info. 16:31:33 <pwhalen> ok 16:32:37 * pwhalen gives it another minute before closing the meeting 16:32:42 <nirik> oh, and there's a move to make a 'standard' kernel 16:33:45 <pwhalen> cool, I need to get caught up 16:34:20 <pwhalen> #endmeeting