!RROtHmAaQIkiJzJZZE:nixos.org

NixOS Infrastructure

389 Members
Next Infra call: 2024-07-11, 18:00 CEST (UTC+2) | Infra operational issues backlog: https://github.com/orgs/NixOS/projects/52 | See #infra-alerts:nixos.org for real time alerts from Prometheus.120 Servers

Load older messages


SenderMessageTime
2 Mar 2025
@hexa:lossy.networkhexawhatever is on 24.1117:54:26
@hexa:lossy.networkhexa2.91.117:54:35
@raitobezarius:matrix.orgraitobezariusso 2.91.1 I guess17:54:38
@raitobezarius:matrix.orgraitobezariusi will investigate17:54:51
@hexa:lossy.networkhexathx17:55:00
@hexa:lossy.networkhexacapstone update17:55:49
@hexa:lossy.networkhexa5.0.3 -> 50.0517:55:51
@hexa:lossy.networkhexa* 5.0.3 -> 5.0.517:55:53
@hexa:lossy.networkhexahttps://termbin.com/1pam17:56:30
@hexa:lossy.networkhexaOVMF-202411 -> OVMF-20250217:56:44
@raitobezarius:matrix.orgraitobezariusOVMF looks more plausible to me17:56:58
@raitobezarius:matrix.orgraitobezariusthough this is firmware…17:57:03
@raitobezarius:matrix.orgraitobezariuscapstone is just there for diassembling, surely they're not starting weird cgroup while diassembling in qemu17:57:20
@adam:robins.wtfadamcstephensIf OVMF is the culprit, and we have better tests we should run it against, please let me know or open a PR.19:13:28
@raitobezarius:matrix.orgraitobezariusit doesn't reproduce in an obvious way on x86_6421:25:33
@hexa:lossy.networkhexa
59d6c1268a1ec26d23841fbe25f905d72f25b05b is the first bad commit
commit 59d6c1268a1ec26d23841fbe25f905d72f25b05b (HEAD)
Author: Adam C. Stephens <adam@valkor.net>
Date:   Tue Feb 25 10:26:48 2025 -0500

    edk2: 202411 -> 202502
    
    https://github.com/tianocore/edk2/releases/tag/edk2-stable202502

 pkgs/by-name/ed/edk2/package.nix | 12 +++++-------
 1 file changed, 5 insertions(+), 7 deletions(-)
21:26:43
@raitobezarius:matrix.orgraitobezariuswell i guess i had a good intuition but how did you reproduced it?21:27:13
@raitobezarius:matrix.orgraitobezarius* well i guess i had a good intuition but how did you reproduce it?21:27:17
@hexa:lossy.networkhexafailing builds got stuck here21:28:31
@hexa:lossy.networkhexa

nixos-disk-image-aarch64-linux> Press ESC in 5 seconds to skip startup.nsh or any other key to continue.Press ESC in 4 seconds to skip startup.nsh or any other key to continue.Press ESC in 3 seconds to skip startup.nsh or any other key to continue.Press ESC in 2 seconds to skip startup.nsh or any other key to continue.Press ESC in 1 seconds to skip startup.nsh or any other key to continue.

21:28:34
@hexa:lossy.networkhexafor much longer than 5s21:29:03
@raitobezarius:matrix.orgraitobezariusso there's kinda two problems21:29:12
@raitobezarius:matrix.orgraitobezariusfirst is that terminating builds seems to be misbehaving (which is expected in Lix tbh)21:29:23
@raitobezarius:matrix.orgraitobezariussecond is that booting on AA64 ceased to work on that OVMF21:29:42
@raitobezarius:matrix.orgraitobezariusone guess would be that openssl is desync21:30:24
@raitobezarius:matrix.orgraitobezariusthat OVMF upgraded to OpenSSL 3.421:30:34
@raitobezarius:matrix.orgraitobezariusbut now someone would need to git bisect over AA64 the boot failure21:30:55
@raitobezarius:matrix.orgraitobezariushonestly if mbedTLS is now available on public EDK2, people should move to it21:31:29
@raitobezarius:matrix.orgraitobezariusthe other weird change is all the confidential computing stuff21:31:50
@adam:robins.wtfadamcstephensI upgraded to openssl during the bump since upstream had done so as mentioned in the release notes, both to 3.421:36:47

Show newer messages


Back to Room ListRoom Version: 6