From: Jon Masters <jonathan@jonmasters.org>
To: andi@firstfloor.org
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: PROBLEM: first read of /dev/mcelog fails
Date: Wed, 10 Nov 2010 05:32:31 -0500 [thread overview]
Message-ID: <1289385151.3916.554.camel@constitution.bos.jonmasters.org> (raw)
Hi Andi,
I recently took some time to look at the daemon side of mcelog. I found
a few issues with that[0] that I will detail in a separate mail, but I
am more concerned that in recent kernels, the first read() of the mcelog
device performed by mcelog after boot always fails. 100% reproducible on
several machines - mcelog client always bombs out in process() due to
getting a "no such device" error from the kernel read attempt.
The /dev/mcelog device exists, but the first read fails.
Can you do a fresh boot, run mcelog, and see what I mean?
Jon.
[0] ignoredev not documented, cache-error-trigger uses $CPUS_AFFECTED
when it should be $AFFECTED_CPUS, mcelog-client socket is always created
no matter what the config says (and not deleted on shutdown).
next reply other threads:[~2010-11-10 10:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-10 10:32 Jon Masters [this message]
2010-11-10 10:40 ` Jon Masters
2010-11-11 9:29 ` Jon Masters
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1289385151.3916.554.camel@constitution.bos.jonmasters.org \
--to=jonathan@jonmasters.org \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®