Bug 595930 - please update to 1.0pre2
Summary: please update to 1.0pre2
Alias: None
Product: Fedora
Classification: Fedora
Component: mcelog
Version: 14
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Prarit Bhargava
QA Contact: Fedora Extras Quality Assurance
: 615530 623550 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2010-05-25 22:50 UTC by James Ralston
Modified: 2011-11-18 18:15 UTC (History)
33 users (show)

Fixed In Version: mcelog-1.0-0.1.pre3.fc14
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2011-10-08 18:02:48 UTC
Type: ---

Attachments (Terms of Use)

Description James Ralston 2010-05-25 22:50:14 UTC
The mcelog author/developer has abandoned the 0.9 stream of mcelog in favor of a new 1.0 stream with new features:


Please consider building 1.0pre2 for rawhide, and optionally for the fedora-updates-testing channels.


Comment 1 Bug Zapper 2010-07-30 11:42:40 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 14 development cycle.
Changing version to '14'.

More information and reason for this action is here:

Comment 2 Dave Jones 2010-11-01 14:08:33 UTC
please update this for f14.  my laptop complains hourly about 'no such device', which is fixed in 1.0pre2.

Comment 3 Jon Masters 2010-11-02 21:14:16 UTC
ok Dave. I'll do it. I pinged Anton a couple of weeks back to see if one of those guys in Brno was taking over mcelog, but I'll take care of it for the moment.

Comment 4 Fedora Update System 2010-11-10 02:20:15 UTC
mcelog-1.0-0.1.pre3.fc14 has been submitted as an update for Fedora 14.

Comment 5 Jon Masters 2010-11-10 02:26:18 UTC
I'll keep this package, and just pay better attention to it now Andi is doing mcelog again. I've done all the updates for devel, F14, F13 just now.

Comment 6 Jon Masters 2010-11-10 04:14:59 UTC
*** Bug 623550 has been marked as a duplicate of this bug. ***

Comment 7 Jon Masters 2010-11-10 04:15:55 UTC
*** Bug 615530 has been marked as a duplicate of this bug. ***

Comment 8 Orion Poplawski 2010-11-10 18:09:15 UTC
1.0pre3 looks god in rawhide, fixes 615530 for me.

Comment 9 Fedora Update System 2010-11-10 21:44:32 UTC
mcelog-1.0-0.1.pre3.fc14 has been pushed to the Fedora 14 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update mcelog'.  You can provide feedback for this update here: https://admin.fedoraproject.org/updates/mcelog-1.0-0.1.pre3.fc14

Comment 10 Phil Anderson 2010-11-15 03:13:16 UTC
Bug 615530 still occurs for me.
$rpm -q mcelog

After installing, I rebooted.  At the next hour I got:

read: No such device

Comment 11 Orion Poplawski 2010-11-15 16:24:03 UTC
Hmm, looks good for me on fc14 as well.  Phil - what is your hardware?

Comment 12 Orion Poplawski 2010-11-15 18:04:47 UTC
Ah, bug 615530 not fixed for me on a Dell Inspiron 6400 with Core2 T5500.

Comment 13 Phil Anderson 2010-11-15 23:47:17 UTC
I getting the problem on an old Intel(R) Core(TM)2 CPU 6300:

Comment 14 pigetak178 2010-11-16 01:36:14 UTC
Failing for me:


read: No such device



yum says mcelog is update to day and I'm on F14.

rpm -qa| grep release

Comment 15 James Ralston 2010-11-16 03:58:52 UTC
For people complaining about the "read: No such device", please note:

1. The error only occurs the first time that /dev/mcelog is read after the host boots. For subsequent attempts, it won't fail.

2. It fails due to a bug in the kernel, not mcelog. (See comment 17 in bug 615530.)

In effect, this problem has to be fixed upstream (in the kernel); there's nothing that mcelog can do about it.

Comment 16 Jon Masters 2010-11-16 06:44:01 UTC
Except, in talking with Andi he has agreed to a fix to the read handling in mcelog so we'll retry on failure (I need to check his logic). I'm slightly concerned that he didn't seem desperate to fix the upstream breakage, but that is another issue and one that is in hand.

Comment 17 Jon Masters 2010-11-16 06:44:28 UTC
So, to be clear, I will be pushing a second update with the fix for the first run of mcelog on next boot causing a read error too.

Comment 18 pigetak178 2010-12-26 15:38:17 UTC
From root@localhost.localdomain  Sun Dec 26 07:01:01 2010
Return-Path: <root@localhost.localdomain>
Date: Sun, 26 Dec 2010 07:01:01 -0500
From: root@localhost.localdomain (Cron Daemon)
To: root@localhost.localdomain
Subject: Cron <root@localhost> run-parts /etc/cron.hourly
Content-Type: text/plain; charset=UTF-8
Auto-Submitted: auto-generated
X-Cron-Env: <SHELL=/bin/bash>
X-Cron-Env: <PATH=/sbin:/bin:/usr/sbin:/usr/bin>
X-Cron-Env: <MAILTO=root>
X-Cron-Env: <HOME=/root>
X-Cron-Env: <LOGNAME=root>
X-Cron-Env: <USER=root>
Status: R


read: No such device

# rpm -q mcelog

Comment 19 gregor 2011-01-14 20:13:24 UTC

i have the same error on 4 machines.

mcelog version: mcelog-0.9pre1-0.1.fc13.x86_64

any solutions in the meantime that are not reported?


Comment 20 Stephen E Clark 2011-01-18 14:58:33 UTC

I have mcelog-1.0-0.1.pre3.fc14.x86_64
kernel 2.6.37-1.fc15.x86_64

and I still get:

read: No such device

Comment 21 Stephen E Clark 2011-01-18 14:59:59 UTC

forgot to add Core 2 CPU T5600

Comment 22 wbiker 2011-05-20 16:13:04 UTC
Hi all,

Problem is still there.

mcelog mcelog-0.9pre1-0.1.fc13.x86_64

Hourly I get:
read: No such device.

On the command line I tried the command manually and it works without errors.
mcelog --ignorenodev --filter >> /var/log/mcelog


Comment 23 John Freed 2011-07-11 10:16:53 UTC
I had the same experience as Wolfgang in Comment 22, but I tried a variant that is sort-of documented in `man mcelog`:

mcelog --ignorenodev --filter --logfile=/var/log/mcelog

This produced an SELinux error! Seems odd to me that SELinux prevents mcelog from reaching its own file but doesn't prevent a shell redirect, but hey ...

In any case, I'm now getting a new error:

mcelog: Cannot open log file /var/log/mcelog. Exiting.

So I made a new SELinux module to repair that. The security context of /var/log/mcelog as created by the shell redirect (default cron job) is:


I also deleted the /var/log/mcelog file and ran mcelog with the --logfile= option, and it created a new logfile with the security context:


Anyhow I'm reporting this as an SELinux bug, though I can't see how it would be related to the underlying error (read: No such device).

I am, however, happy to report that I am no longer getting the emails!

To recap, here are the steps I took:

1) edit /etc/cron.hourly/mcelog to read:
mcelog --ignorenodev --filter --logfile=/var/log/mcelog

2) delete /var/log/mcelog

Comment 24 John Freed 2011-07-11 11:27:48 UTC

It turns out that it's not as simple as deleting the file, as SELinux expects a certain context that mcelog doesn't provide. See the other bug report for details.

Comment 25 rh001 2011-09-30 15:58:09 UTC
"... please update to 1.0pre2"
Wow, a year after bug reported and this still has not been fixed for Fedora 14.  There is NO update to the above release in any of the Fedora 14 repositories - at least non that I could find.  Why hasn't this been pushed to the Fedora 14 repositories?  Has this application been abandoned?

I still have mcelog 0.8pre2.  I have updated system with latest updates (i.e. yum update) - still not updated.

Comment 26 Fedora Admin XMLRPC Client 2011-10-04 13:27:24 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 27 Prarit Bhargava 2011-10-04 18:56:43 UTC
Please download an up karma if the package works on f14:




Comment 28 Fedora Update System 2011-10-08 18:02:48 UTC
mcelog-1.0-0.1.pre3.fc14 has been pushed to the Fedora 14 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 29 rh001 2011-10-12 21:09:22 UTC
Does not seemed to be fixed.
Lenovo T500 Laptop - Intel Centrino 2 vPro

Installed --> mcelog-1.0-0.1.pre3.fc14.x86_64.rpm

Still getting mail messages with...


read: No such device

yum list mcelog ==>
mcelog.x86_64  2:1.0-0.1.pre3.fc14 installed

also... yum complains that package is not signed.

I used rpm to install it.  Maybe it did not install correctly.

I'll use ...
yum --nogpgcheck reinstall mcelog-1.0-0.1.pre3.fc14.x86_64.rpm

I'll update if any change.

Comment 30 W.C. Epperson 2011-11-18 16:18:02 UTC

Still get the after boot error message.  I can fix the annoyance with 2>/dev/null in the cron job, but every mcelog update overwrites it.  Maybe the script should just have 2>&1, logging the failure.

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