Bug 623550 - /etc/cron.hourly/mcelog.cron: read: No such device
Summary: /etc/cron.hourly/mcelog.cron: read: No such device
Keywords:
Status: CLOSED DUPLICATE of bug 595930
Alias: None
Product: Fedora
Classification: Fedora
Component: mcelog
Version: 14
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Jon Masters
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F14Target
TreeView+ depends on / blocked
 
Reported: 2010-08-12 06:13 UTC by Nicolas Mailhot
Modified: 2011-03-03 09:05 UTC (History)
10 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-11-10 04:14:59 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Nicolas Mailhot 2010-08-12 06:13:47 UTC
Description of problem:
/etc/cron.hourly/mcelog.cron:

read: No such device

Version-Release number of selected component (if applicable):
mcelog-0.9pre1-0.1.fc13.x86_64
kernel-2.6.35.1-5.rc1.fc14.x86_64


How reproducible:
Happens every once in a while

Comment 1 Jon Masters 2010-08-17 18:03:12 UTC
Thanks. We've seen a few of these, so it's probably a DUP and I'll fix that up later. Just taking the bug for now.

Comment 2 Paul Howarth 2010-10-28 13:21:33 UTC
Looks like a duplicate of kernel Bug #615530

Comments there suggest the message appears the first time the job runs after reboot.

Comment 3 Jon Masters 2010-11-10 04:14:59 UTC

*** This bug has been marked as a duplicate of bug 595930 ***

Comment 4 Jon Masters 2010-11-10 09:04:26 UTC
Ok. There are two bugs here. Some systems don't have an MCE device. Some do, and in either case you might have a /dev/mcelog device but the first read from it generally will fail after booting. I added a hack to the version of mcelog that I just built (which also reworks it to use systemd and run as a daemon) such that it will try twice - delaying between opens - as a horrible hack until Andi fixes whatever is broken in the kernel. I will ping him shortly as I have quite a list of things I had to fix in mcelog to make it work as a daemon that obviously had never been tested in the upstream version.


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