/usr/bin/qemu-aarch64-static:11:__memset_avx2_unaligned_erms:memset:zero_bss:load_elf_image:load_elf_binary

Bug #1914014 reported by errors.ubuntu.com bug bridge
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
qemu (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

The Ubuntu Error Tracker has been receiving reports about a problem regarding qemu. This problem was most recently seen with package version 1:5.0-5ubuntu9.3, the problem page at https://errors.ubuntu.com/problem/177c77a02dc6097dacf98cd449e4274f96685c30 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/.

Tags: groovy
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

__memset_avx2_unaligned_erms suggests that the code takes an optimization path for AVX which fails due to alignment issues. In regard to the recent upload it comes to mind that it now might take other glibc code (static link) which has different alignment constraints than whatever worked before.
But then a) glibc should not pick this method (not 100% qemu's fault until we know where/how this path is taken)
and b) since all workloads we tried worked we'd need the workload that fails for debugging. It seems it is all about some android cross build check "/usr/bin/qemu-aarch64-static ./conftest" and the PWD often references "android29".

I've checked a few but none crashed, if anyone affected by this could provide steps to reproduce that would help a lot!

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Potentially related, but not necesarily a dup of bug 1912605

Changed in qemu (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for qemu (Ubuntu) because there has been no activity for 60 days.]

Changed in qemu (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.