-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Segment fault with Ubuntu 24.04 20250120.5.0 #11471
Comments
The gcc version |
I can confirm this as well at https://github.com/pbkhrv/rtl_433-hass-addons/actions/runs/12972957498/job/36181006667. That job is compiling aarch64 in Docker under QEMU (I know, proper cross compiling would be better, but this is what the official Home Assistant builder action does so 🤷 ). Is there a way to specify the runner image version to a previous 24.04 release to confirm the regression? |
The same problem for buildx for linux/arm64 via QEMU: https://github.com/woblerr/docker-pgbackrest/actions/runs/12965488407/job/36165276019#step:7:2658 Rollback to the ubuntu-22.04 runner solved the problem. |
Chiming in to say that we are seeing segfaults on our test runners for pygame-ce in the ppc64le architecture build since getting version 20250120.5.0. and, perhaps related, it also reporting that it can no longer detect the GNU compiler type for our S390x architecture build. As @deviantintegral says it would be nice to have a way to roll back to a previous runner image to isolate the problem. |
Hi @RadxaYuntian Thank you for bringing this issue to our attention. We will look into this issue and will update you after investigating. |
Due to an [issue](actions/runner-images#11471) with Ubuntu 24.04 20250120.5.0 runner image we have been seeing failures in our multi-arch images for the last few days which is blocking the release. I assume that the issue is something related to qemu, so downgrade to 22.04 until this issue is resolved. Signed-off-by: stevenhorsman <[email protected]>
I'm also having very similar issues in tamp when using cibuildwheel to build python wheels for ppc64le and aarch64 targets. |
This issue is being currently discussed and fixed at actions/runner-images#11471 Signed-off-by: Rodrigo Tobar <[email protected]>
This issue is being currently discussed and fixed at actions/runner-images#11471 Signed-off-by: Rodrigo Tobar <[email protected]>
Same issue here with gcc segfault, but in my case I saw it both with |
Due to an [issue](actions/runner-images#11471) with Ubuntu 24.04 20250120.5.0 runner image we have been seeing failures in our multi-arch images for the last few days which is blocking the release. I assume that the issue is something related to qemu, so downgrade to 22.04 until this issue is resolved. Signed-off-by: stevenhorsman <[email protected]>
Dear @ashwin153, thank you so much for your suggestion. We needed to apply that fix to fix the OCI build on ARM.
With kind regards, NB: Shall this ticket be re-opened? Do participants of this conversation have any other suggestions or news on this topic? |
IMHO yes until it's all fully working again without having to pin versions, or bump to an older Ubuntu version etc. |
Due to actions/runner-images#11471 we see similar problems when using ubuntu24.04 to do cross build for arm64 images. A workaround is to downgrade to ubuntu22.04. Fixes confidential-containers#715 Signed-off-by: Xynnn007 <[email protected]>
Due to actions/runner-images#11471 we see similar problems when using ubuntu24.04 to do cross build for arm64 images. A workaround is to downgrade to ubuntu22.04. Fixes confidential-containers#715 Signed-off-by: Xynnn007 <[email protected]>
Due to actions/runner-images#11471 we see similar problems when using ubuntu24.04 to do cross build for arm64 images. A workaround is to downgrade to ubuntu22.04 and use Qemu v7. Fixes confidential-containers#715 Signed-off-by: Xynnn007 <[email protected]>
Due to actions/runner-images#11471 we see similar problems when using ubuntu24.04 to do cross build for arm64 images. A workaround is to downgrade to ubuntu22.04 and use Qemu v8. Fixes confidential-containers#715 Signed-off-by: Xynnn007 <[email protected]>
Due to actions/runner-images#11471 we see similar problems when using ubuntu24.04 to do cross build for arm64 images. A workaround is to downgrade to ubuntu22.04 and use Qemu v8. Fixes confidential-containers#715 Signed-off-by: Xynnn007 <[email protected]>
Due to actions/runner-images#11471 we see similar problems when using ubuntu24.04 to do cross build for arm64 images. A workaround is to downgrade to ubuntu22.04 and use Qemu v8. Fixes confidential-containers#715 Signed-off-by: Xynnn007 <[email protected]>
@kishorekumar-anchala: Based on the information above, can you please re-open this ticket, if you agree? |
Due to actions/runner-images#11471 we see similar problems when using ubuntu24.04 to do cross build for arm64 images. A workaround is to downgrade to ubuntu22.04 and use Qemu v8. Fixes #715 Signed-off-by: Xynnn007 <[email protected]>
The workaround seems to be no good as well: https://github.com/RadxaOS-SDK/rsdk/actions/runs/13560439931 |
We're having the issue as well. Building this image: https://github.com/Jahia/jahia/blob/JAHIA_8_1_8_0/docker/docker-jahia-core/Dockerfile Running with:
Error logs:
|
actions/runner-images#11471 (comment) Signed-off-by: ZHANG Yuntian <[email protected]>
Try switching to Ubuntu 22 and use |
Trying with:
EDIT: This resolved the issue for us. |
any solution to this? |
→ /lib/systemd/system/systemd-pstore.service. |
output with debug flag: W: listening on child socket failed: |
Current workaround
GitHub has refused to acknowledge this problem. The current workaround can be found here.
Description
We have a scheduled job running every Sunday, which failed today, with no code change in last 2 weeks.
After checking the build log, it always failed at a dkms package installation. Once the workflow file is changed to print the dkms log, the error is always gcc segment fault.
Changing running environment to
ubuntu22-04
fixed the segment fault. Action still failed but that's because the change we made to investigate this issue.What may be unusual for us is that we are using binfmt to run aarch64
gcc
in a devcontainer, because the final output is an aarch64 system image. So this is not some normal gcc failing.Platforms affected
Runner images affected
Image version and build link
20250120.5.0
Is it regression?
20250105.1.0: https://github.com/RadxaOS-SDK/rsdk/actions/runs/12848906725
Expected behavior
DKMS install successfully without gcc segfault.
Actual behavior
gcc segfault:
Repro steps
workflow_dispatch
forbuild.yaml
The text was updated successfully, but these errors were encountered: