libc incorrectly detects AVX support

Attached is a patch that fixes this issue for lucid.

Adam, would you mind chasing this up?

Will have a look at SRUing for this, sure.

Turns out that we've found still more issues with AVX detection upstream. Carlos is working on testing a refined patchset right now, and if that all goes smoothly, I'll be backporting this across the board.

@adam,
thanks

Removing from sponsorship queue as Adam has taken ownership of this

Why is this taking so long? The 12.04 release is completely boken using the new amd servers. I would classify this as a major compatibility issue.

It's taken some time upstream to properly fix AVX and FMA4 issues (the last comment in this bug log is actually about FMA4, not AVX, though the two relate).

We have bits landed upstream for 2.15, which I'll be getting into quantal and precise ASAP, backporting to older releases will be a bit more challenging, but I'll jump on that next.

I think this is the same problem as in https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/956051

In addition it affects 12.10 Quantal

This bug was fixed in the package eglibc - 2.15-0ubuntu16

---------------
eglibc (2.15-0ubuntu16) quantal; urgency=low

  * Backport fix from 2.16 to fix htons() conversion errors on non-x86
    architectures, by correctly casting to uint16_t (LP: #1016349)
  * Restore missing AT_EMPTY_PATH definition in fnctl.h (LP: #1010069)
  * Backport FMA4/AVX detection from glibc 2.16 (LP: #956051, #979003)
  * Backport fixups to AVX-using code to match the detection backport.
 -- Adam Conrad <email address hidden> Thu, 09 Aug 2012 15:15:53 -0600

Backport of quantal's AVX changes to precise

I've built a do-no-harm fix just for the original AVX bug using the patch identified in #1. If somebody can verify this on AMD hardware (with AVX extension) that would be much appreciated.

Here is the package in my PPA:
https://launchpad.net/~christopherarges/+archive/ppa-test/+sourcepub/2629659/+listing-archive-extra

To be clear, the precise fix for this has been sitting in the precise-proposed queue since August 10th, this isn't being ignored, just needs some review love before it can be accepted.

Hello Chris, or anyone else affected,

Accepted eglibc into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/eglibc/2.15-0ubuntu10.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please change the bug tag from verification-needed to verification-done. If it does not, change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

On an AMD bulldozer/fma4:
I have verified the precise -proposed package 2.15-0ubuntu10.1 and it does fix the issue. I can use 'xm list', boot a lucid domU, and run apache.
I have also verified that the do-no-harm package in comment #12. It will allow me to use 'xm list' and boot a lucid domU machine and run apache as well.

Hello Chris, or anyone else affected,

Accepted eglibc into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/eglibc/2.15-0ubuntu10.3 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please change the bug tag from verification-needed to verification-done. If it does not, change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Verified that the precise-proposed packages do the right thing for AVX/FMA4 detection with third party testers.

The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions.

Hi wondering if Lucid fix (identified in #1) could be uploaded, I verified this in comment #15 on an AMD machine with those extensions as well as an Intel machine.

This bug was fixed in the package eglibc - 2.15-0ubuntu10.3

---------------
eglibc (2.15-0ubuntu10.3) precise; urgency=low

  * Backport fixes for dbl-64 and ldbl-128 issues (LP: #1000498)
  * Backport another FMA support patch from glibc master branch.

eglibc (2.15-0ubuntu10.2) precise-security; urgency=low

  * SECURITY UPDATE: stack buffer overflow in vfprintf handling
    (LP: #1031301)
    - debian/patches/any/CVE-2012-3406.patch: switch to malloc when
      array grows too large to handle via alloca extension
    - CVE-2012-3406
  * SECURITY UPDATE: stdlib strtod integer/buffer overflows
    - debian/patches/any/CVE-2012-3480.patch: rearrange calculations
      and modify types to void integer overflows
    - CVE-2012-3480

eglibc (2.15-0ubuntu10.1) precise; urgency=low

  * Backport fix from 2.16 to fix htons() conversion errors on non-x86
    architectures, by correctly casting to uint16_t (LP: #1016349)
  * Restore missing AT_EMPTY_PATH definition in fnctl.h (LP: #1010069)
  * Backport FMA4/AVX detection from glibc 2.16 (LP: #956051, #979003)
  * Backport fixups to AVX-using code to match the detection backport.
  * Backport fix from 2.16 for sscanf/realloc deadlock (LP: #1028038)
  * Backport for bogus FPE on underflow for exp(double) (LP: #1007457)
 -- Adam Conrad <email address hidden> Wed, 03 Oct 2012 15:58:02 -0600

Hello Chris, or anyone else affected,

Accepted eglibc into oneiric-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/eglibc/2.13-20ubuntu5.3 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please change the bug tag from verification-needed to verification-done. If it does not, change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Hello Chris, or anyone else affected,

Accepted eglibc into lucid-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/eglibc/2.11.1-0ubuntu7.12 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please change the bug tag from verification-needed to verification-done. If it does not, change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

I verified it on my Bulldozer processor, and it works perfectly without crash.

Verified this on a Sandybridge process with AVX extensions using a lucid domU. I had to install xen 4.2 to ensure I could see the avx extensions in the guest.

Verified this on a Sandybridge processor with AVX extensions using an oneiric domU, (had to boot with xen_emul_unplug=never). Using xen 4.2 to see proper avx extensions.

This bug was fixed in the package eglibc - 2.13-20ubuntu5.3

---------------
eglibc (2.13-20ubuntu5.3) oneiric; urgency=low

  * Pull three interdependent patches from Debian to fix AVX detection
    problems on kernels or CPUs that lack support for it (LP: #979003):
    - amd64/cvs-avx-detection.diff: Improved detection on old kernels.
    - amd64/cvs-dl_trampoline-cfi.diff: fix CFI in dl_trampoline code.
    - amd64/cvs-avx-osxsave.diff: Disable AVX without OSXAVE support.
 -- Adam Conrad <email address hidden> Wed, 14 Nov 2012 16:03:25 -0700

This bug was fixed in the package eglibc - 2.11.1-0ubuntu7.12

---------------
eglibc (2.11.1-0ubuntu7.12) lucid; urgency=low

  * Pull three interdependent patches from Debian to fix AVX detection
    problems on kernels or CPUs that lack support for it (LP: #979003):
    - amd64/cvs-avx-detection.diff: Improved detection on old kernels.
    - amd64/cvs-dl_trampoline-cfi.diff: fix CFI in dl_trampoline code.
    - amd64/cvs-avx-osxsave.diff: Disable AVX without OSXAVE support.
  * Also backport amd64/submitted-tst-audit6-avx.diff from oneiric to
    skip tests if AVX extensions are not available on the build host.
  * Use non-deprecated --reject-format=unified QUILT_PATCH_OPTS option.
 -- Adam Conrad <email address hidden> Wed, 14 Nov 2012 16:14:37 -0700

This change really needs to be pushed to main; debootstrap and friends aren't smart enough to consider *-updates repositories, which (for instance) renders xen-create-image useless on a Precise system with a CPU that triggers the original bug.