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.
--
You received this bug notification because you
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.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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.
** Tags removed: verification-needed
** Tags added: verification-done-oneiric
--
You received this bug notification because
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):
-
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):
-
I verified it on my Bulldozer processor, and it works perfectly without
crash.
** Tags added: verification-done-lucid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/979003
Title:
libc incorrectly
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
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
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.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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)
** Changed in: eglibc (Ubuntu Oneiric)
Assignee: Chris J Arges (christopherarges) = Adam Conrad (adconrad)
** Changed in: eglibc (Ubuntu Lucid)
Assignee: Chris J Arges (christopherarges) = Adam Conrad (adconrad)
--
You received this bug notification because you are a member of Ubuntu
Verified that the precise-proposed packages do the right thing for
AVX/FMA4 detection with third party testers.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/979003
Title:
libc incorrectly detects AVX support
To manage notifications about
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
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.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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
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:
Backport of quantal's AVX changes to precise
** Patch added: eglibc_2.15-0ubuntu11.1.precise.debdiff
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/979003/+attachment/3272669/+files/eglibc_2.15-0ubuntu11.1.precise.debdiff
--
You received this bug notification because you are a member
** Also affects: eglibc (Ubuntu Oneiric)
Importance: Undecided
Status: New
** Changed in: eglibc (Ubuntu Oneiric)
Status: New = Confirmed
** Changed in: eglibc (Ubuntu Oneiric)
Importance: Undecided = High
** Changed in: eglibc (Ubuntu Oneiric)
Assignee: (unassigned) =
** Branch linked: lp:ubuntu/eglibc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/979003
Title:
libc incorrectly detects AVX support
To manage notifications about this bug go to:
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
** Also affects: eglibc (Ubuntu Quantal)
Importance: High
Assignee: Adam Conrad (adconrad)
Status: In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/979003
Title:
libc
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
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/979003
Title:
** Changed in: eglibc (Ubuntu Precise)
Milestone: None = ubuntu-12.04.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/979003
Title:
libc incorrectly detects AVX support
To manage notifications
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
** Also affects: eglibc (Ubuntu Lucid)
Importance: Undecided
Status: New
** Changed in: eglibc (Ubuntu Lucid)
Status: New = Incomplete
** Changed in: eglibc (Ubuntu Lucid)
Status: Incomplete = Confirmed
** Changed in: eglibc (Ubuntu Lucid)
Importance: Undecided = High
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.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/979003
Removing from sponsorship queue as Adam has taken ownership of this
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/979003
Title:
libc incorrectly detects AVX support
To manage notifications about
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.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@adam,
thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/979003
Title:
libc incorrectly detects AVX support
To manage notifications about this bug go to:
Will have a look at SRUing for this, sure.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/979003
Title:
libc incorrectly detects AVX support
To manage notifications about this bug go to:
Adam, would you mind chasing this up?
** Changed in: eglibc (Ubuntu)
Assignee: Chris J Arges (christopherarges) = Adam Conrad (adconrad)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/979003
Attached is a patch that fixes this issue for lucid.
** Patch added: eglibc_lucid_fix979003.debdiff
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/979003/+attachment/3047295/+files/eglibc_lucid_fix979003.debdiff
--
You received this bug notification because you are a member of Ubuntu
** Description changed:
+ [Impact]
+ In processors with AVX support virtual machines running can cause the program
to execute invalid opcodes, thus crashing a running program.
+
+ [Development Fix]
+ This has been fixed in eglibc in precise. It it present in Lucid, Natty and
Oneiric.
+
+
** Changed in: eglibc (Ubuntu)
Assignee: (unassigned) = Chris J Arges (christopherarges)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/979003
Title:
libc incorrectly detects AVX support
To
36 matches
Mail list logo
