From: Tracy Smith <tlsmith3777@gmail.com>
To: linux-edac@vger.kernel.org
Cc: backports@vger.kernel.org, linux-newbie@vger.kernel.org,
util-linux@vger.kernel.org, linux-mmc@vger.kernel.org
Subject: Re: FW: edac driver initialization, interrupt, & debug
Date: Fri, 16 Nov 2018 11:07:50 -0600 [thread overview]
Message-ID: <CAChUvXP6eu76xqEZNspooUMb+311mmDH8=St=awCL77hJPus9Q@mail.gmail.com> (raw)
In-Reply-To: <CAChUvXMp6S6MBY_LmrfgdPcctQw70FoyxbiHeFqK+5fQx5omCw@mail.gmail.com>
I’m attempting to insmod/modprobe the layerscape_edac_mod.ko driver.
It seems the driver enters layerscape_edac.c fsl_ddr_mc_init() and
completes successfully. But there is no EDAC boot messages and no
/proc/interrupts entry for the EDAC. I’m backporting the EDAC from the
LSDK to the SDK 2.0.
I have set CONFIG_EDAC_DEBUG and set edac_debug_level to 4, but I
don’t see any debug messages other than printk()s that I add to
fsl_ddr_mc_init() in layerscape_edac.c. No debug messages appear in
any logs from fsl_ddr_edac.c.
1. How can I enable debug information? Is debugfs required to print
the debug messages for the edac_debug_level and CONFIG_EDAC_DEBUG in
the 4.1.35-rt41 kernel for drivers/edac?
2. The default EDAC_OPSTATE_INT in fsl_ddr_mc_init() and the
platform_driver_register() is successful. But I don’t see any printk()
messages in fsl_mc_err_probe() within fsl_ddr_edac.c. No errors appear
in any /var/log/*.
3. I don’t see any interrupts, so why would there not be an edac
interrupt in /proc/inturrupts? Do I need to inject an error before
seeing an edac interrupt in /proc/interrupts?
lsmod
module: layerscape_edac_mod 12594 0
4. To inject an error I can use the fsl_mc_inject …. routines in
fsl_ddr_edac.c and write to the registers. But is there a utility that
already uses these routines that can be used to inject an error
(FSL_MC_ECC_ERR_INJECT, FSL_MC_DATA_ERR_INJECT_LO,
Thanks you for any assistance. Instrumenting throughout the driver now
to see if I can trace through the driver.
thx, Tracy Smith
--
To unsubscribe from this list: send the line "unsubscribe backports" in
next parent reply other threads:[~2018-11-16 17:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BYAPR02MB431115EC4735AE5B7E29F2CEF6DC0@BYAPR02MB4311.namprd02.prod.outlook.com>
[not found] ` <BYAPR02MB43110062F32BFDEA712AB371F6DC0@BYAPR02MB4311.namprd02.prod.outlook.com>
[not found] ` <CAChUvXMp6S6MBY_LmrfgdPcctQw70FoyxbiHeFqK+5fQx5omCw@mail.gmail.com>
2018-11-16 17:07 ` Tracy Smith [this message]
2018-11-17 14:05 ` FW: edac driver initialization, interrupt, & debug Borislav Petkov
2018-11-17 23:22 ` Tracy Smith
2018-11-18 1:05 ` Steve Inkpen
2018-11-19 16:37 ` Tracy Smith
2018-11-19 16:48 ` York Sun
2018-11-21 17:01 ` Tracy Smith
2018-11-21 22:02 ` Tracy Smith
2018-11-19 16:24 ` FW: " York Sun
2018-11-19 15:55 ` York Sun
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='CAChUvXP6eu76xqEZNspooUMb+311mmDH8=St=awCL77hJPus9Q@mail.gmail.com' \
--to=tlsmith3777@gmail.com \
--cc=backports@vger.kernel.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-newbie@vger.kernel.org \
--cc=util-linux@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).