Bug 1567941 - "8 bytes ignored in each record" for intel I7 6700k
Summary: "8 bytes ignored in each record" for intel I7 6700k
Alias: None
Product: Fedora
Classification: Fedora
Component: mcelog
Version: 27
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Prarit Bhargava
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2018-04-16 13:15 UTC by ben_redhat
Modified: 2018-11-30 22:20 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2018-11-30 22:20:58 UTC
Type: Bug

Attachments (Terms of Use)

Description ben_redhat 2018-04-16 13:15:38 UTC
Description of problem:
mcelog daemon is running but not functional due to the "warning" (should in fact be a critical error I guess, as not logs are produced as a result?)

$ journalctl -u mcelog
-- Reboot --
Apr 16 14:07:13 eas.b18 systemd[1]: Started Machine Check Exception Logging Daemon.
Apr 16 14:07:13 eas.b18 mcelog[2398]: mcelog: warning: 8 bytes ignored in each record
Apr 16 14:07:13 eas.b18 mcelog[2398]: mcelog: consider an update
Apr 16 14:12:04 eas.b18 systemd[1]: Stopping Machine Check Exception Logging Daemon...
Apr 16 14:12:04 eas.b18 systemd[1]: Stopped Machine Check Exception Logging Daemon.

I am currently seeing mce kernel oopses every second, so there should be much more there...

Version-Release number of selected component (if applicable):
$ uname -r
$ rpm -q kernel-debug
$ mcelog --version
mcelog unknown
$ rpm -q mcelog

How reproducible:

Steps to Reproduce:
1. run mcelog

Actual results:
mcelog: warning: 8 bytes ignored in each record
mcelog: consider an update

Expected results:
an mce log.

Additional info:

Comment 1 Olivier Crête 2018-08-02 17:29:58 UTC
Same thing on my i7-3520M, possibly we just need to update to the latest version of mcelog, version 153 is getting a bit old.

Comment 2 Olivier Crête 2018-08-02 17:32:17 UTC
I confirm that running v159 fixes this problem and it can read it correctly.

Comment 3 Ben Cotton 2018-11-27 14:51:03 UTC
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora  'version' of '27'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 27 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Ben Cotton 2018-11-30 22:20:58 UTC
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.