From: Shiju Jose <shiju.jose@huawei.com>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: "linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
Linuxarm <linuxarm@huawei.com>,
tanxiaofei <tanxiaofei@huawei.com>
Subject: RE: [PATCH 3/3] rasdaemon: ras-mc-ctl: Add exception handling
Date: Mon, 4 Jan 2021 09:35:43 +0000 [thread overview]
Message-ID: <33ab986d1db24992a23e3adc3ae76abb@huawei.com> (raw)
In-Reply-To: <20201223110336.3c14233c@coco.lan>
Hi Mauro,
>-----Original Message-----
>From: Mauro Carvalho Chehab [mailto:mchehab+huawei@kernel.org]
>Sent: 23 December 2020 10:04
>To: Shiju Jose <shiju.jose@huawei.com>
>Cc: linux-edac@vger.kernel.org; Linuxarm <linuxarm@huawei.com>;
>tanxiaofei <tanxiaofei@huawei.com>
>Subject: Re: [PATCH 3/3] rasdaemon: ras-mc-ctl: Add exception handling
>
>Em Tue, 3 Nov 2020 14:22:58 +0000
>Shiju Jose <shiju.jose@huawei.com> escreveu:
>
>> Add exception handling in the ras-mc-ctl.
>>
>> For example, when an event's table is not present in the SQLite DB,
>> then the DBI would detect exception and ras-mc-ctl exit without read
>> and log remaining event's information. This would happen when an event
>> is not enabled in the rasdaemon. Following is the error log when the
>> devlink_event table is not present in the DB, "DBD::SQLite::db prepare
>> failed: no such table: devlink_event at ./ras-mc-ctl line 1198.
>> Can't call method "execute" on an undefined value at ./ras-mc-ctl line
>1199"
>>
>> Also disabled the DBI's automatic error logging by setting the
>> $dbh->{PrintError} = 0 to avoid duplicate exception logs.
>
>Hmm...
>
>
> $ ./util/ras-mc-ctl --summary
> No Memory errors.
>
> No PCIe AER errors.
>
> No ARM processor errors.
>
> No Extlog errors.
>
> No devlink errors.
> No disk errors.
> Exception: no such table: memory_failure_event
>
> No MCE errors.
>
>While it sounds a good idea to catch such events, printing it as an exception
>doesn't seem the right thing to me, at least for things like "no such table".
>
>IMO, it should print something more intuitive, like:
>
> "Warning: Memory failure detection not enabled"
Sure. I will change.
>
>-
>
>Yet, on a separate note, there's no memory_failure_event upstream.
>
>Maybe I missed some prior patch to be applied before this one?
This patch was posted previously.
https://patchwork.kernel.org/project/linux-edac/patch/20201002180144.1365-1-shiju.jose@huawei.com/
>
>
>Thanks,
>Mauro
Thanks,
Shiju
next prev parent reply other threads:[~2021-01-04 9:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-03 14:22 [PATCH 0/3] rasdaemon: ras-mc-ctl: Add exception handling and support memory_failure_event Shiju Jose
2020-11-03 14:22 ` [PATCH 1/3] rasdaemon: ras-mc-ctl: Modify ARM processor error summary log Shiju Jose
2020-11-03 14:22 ` [PATCH 2/3] rasdaemon: ras-mc-ctl: Add memory failure events Shiju Jose
2020-11-03 14:22 ` [PATCH 3/3] rasdaemon: ras-mc-ctl: Add exception handling Shiju Jose
2020-12-23 10:03 ` Mauro Carvalho Chehab
2021-01-04 9:35 ` Shiju Jose [this message]
2021-01-12 18:06 ` Shiju Jose
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=33ab986d1db24992a23e3adc3ae76abb@huawei.com \
--to=shiju.jose@huawei.com \
--cc=linux-edac@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mchehab+huawei@kernel.org \
--cc=tanxiaofei@huawei.com \
/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