This is fixed in the latest development version of Ubuntu (Vivid
Ververt, 15.04), if you need a fix for the bug in previous versions of
Ubuntu, please perform as much as possible of the SRU Procedure
(https://wiki.ubuntu.com/StableReleaseUpdates#Procedure) to bring it to
a developer's attention.
*
** Changed in: mcelog (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1279293
Title:
post-install fails
To manage notifications about this bug go to:
https
** Changed in: mcelog (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1279293
Title:
post-install fails
To manage notifications about this bug go to:
https://bu
** Attachment added: "New version of the init file using --is-cpu-supported"
https://bugs.launchpad.net/debian/+source/mcelog/+bug/1279293/+attachment/4207327/+files/mcelog.init
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
I've now implemented and tested (on AMD families 15 and 16) the solution
I suggested in comment #4. The patch is in two parts: one for the
upstream source code, to be dropped into debian/patches/, and a new
version of debian/mcelog.init to take advantage of the new feature.
** Patch added: "Implem
** Bug watch added: Debian Bug tracker #738927
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738927
** Also affects: mcelog (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738927
Importance: Unknown
Status: Unknown
--
You received this bug notification because yo
Last paragraph of comment #4 is the key consideration - not that certain
unsupported CPU types exist, but that successful package configuration
(i.e. dpkg --configure mcelog) depends on the CPU type being supported.
Effect on the graphical update-manager tool isn't ideal - reports all
subsequent u
My earlier patch solves the problem for AMD family 15, but clearly not for
family 16 and newer. For a complete fix one will need to modify the init
script. If the CPU is unsupported, both daemon and trigger mode should be
disabled.
It may be useful to add an --is-cpu-supported command-line option
The attachment "fix-amd-cpu-supported.patch" seems to be a patch. If it
isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by
~
The description of this bug is incomplete, so I can't be sure that the
root cause is the same in my case as for the original reporter. Anyway,
here goes:
I'm seeing this on an AMD family 15 CPU. If I try to run mcelog
--foreground by hand, I get the following output:
mcelog: AMD Processor family
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mcelog (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1279293
Title:
pos
11 matches
Mail list logo
