Set to 'Won't Fix' in agreement with HWS - better status to handle such
cases (Incomplete does not fit very well ...)
** Changed in: ubuntu-z-systems
Status: Incomplete => Won't Fix
** Changed in: ubuntu-z-systems
Importance: Critical => Medium
--
You received this bug notification be
** Tags removed: severity-critical targetmilestone-inin1604
** Tags added: severity-high targetmilestone-inin1610
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1563784
Title:
S390: glibc should not
** Also affects: glibc (Ubuntu Y-series)
Importance: Undecided
Status: New
** Also affects: glibc (Ubuntu Xenial)
Importance: Wishlist
Assignee: Adam Conrad (adconrad)
Status: Incomplete
** Changed in: glibc (Ubuntu Xenial)
Status: Incomplete => Opinion
** Changed
** Changed in: ubuntu-z-systems
Status: New => Incomplete
** Changed in: ubuntu-z-systems
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1563784
Title:
S3
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1563784
Title:
S390: glibc should not be configured with lock elision.
To
lock elision is enabled by default on s390x, ppc64el, amd64 on Ubuntu.
Note that s390x port of Ubuntu _only_ targets zEC12 and up, thus we can
rely on TX (Hardware Transactional Execution / Transacational Memory) to
be available.
This is inline with other distributions too, e.g. fedora and opensu
hwup is racy, when compared with chzdev udev-rules.
specifically since the wait_for_sysfs key has been removed from udev, the
current hwup doesn't wait for the complete group to be available before
attempting to activate it. And it doesn't attempt to do so again.
I would like to do following
1)
** Changed in: glibc (Ubuntu)
Importance: High => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1563784
Title:
S390: glibc should not be configured with lock elision.
To manage notifica
** Changed in: glibc (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1563784
Title:
S390: glibc should not be configured with lock elision.
To manage notific
What's wrong with the s390x lock elision implementation that makes it
fundamentally worse than other architectures? This is a pretty strange
request, given the obvious benefits of lock elision.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: glibc (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1563784
Title:
S390: glibc should not be configured with lock elision.
To manage notific
** Changed in: glibc (Ubuntu)
Assignee: Skipper Bug Screeners (skipper-screen-team) => 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/1563784
Title:
S390: glibc should no
** Package changed: ubuntu => glibc (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1563784
Title:
S390: glibc should not be configured with lock elision.
To manage notifications about this
13 matches
Mail list logo
