From: "Wiles, Keith" <keith.wiles@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] Question about log levels and rte_panic
Date: Sat, 13 Feb 2016 17:43:38 +0000 [thread overview]
Message-ID: <74FAD086-9CA8-44F2-9AA5-F2E707F5232A@intel.com> (raw)
I have some code I have been debugging that does a rte_panic() at some point. The problem is it just appeared to exit without printing the panic message. I tracked it down to rte_vlog() doing the following test.
if ((level > rte_logs.level) || !(logtype & rte_logs.type))
return 0;
The reason it appears to just exit to the shell is I was setting —log-level 0 on the command line, which means no CRIT, EMERG or ALERTs panic messages are printed. If I set the log-level 3 then I am able to see these ‘critical’ panic messages, is this the expected behavior?
I would expect EMERG, ALERT and CRIT messages to be printed regardless of the log-level value, but I guess it just means log-level 3 is the lowest level unless you really do not want these messages printed.
Regards,
Keith
next reply other threads:[~2016-02-13 17:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-13 17:43 Wiles, Keith [this message]
2016-02-13 19:12 ` Matthew Hall
2016-02-14 20:23 ` Stephen Hemminger
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=74FAD086-9CA8-44F2-9AA5-F2E707F5232A@intel.com \
--to=keith.wiles@intel.com \
--cc=dev@dpdk.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 NNTP newsgroup(s).