From: Stephen Hemminger <stephen@networkplumber.org>
To: "Wiles, Keith" <keith.wiles@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Question about log levels and rte_panic
Date: Sun, 14 Feb 2016 12:23:17 -0800 [thread overview]
Message-ID: <20160214122317.2bb33bed@xeon-e3> (raw)
In-Reply-To: <74FAD086-9CA8-44F2-9AA5-F2E707F5232A@intel.com>
On Sat, 13 Feb 2016 17:43:38 +0000
"Wiles, Keith" <keith.wiles@intel.com> wrote:
> 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?
You got what you asked for. I don't see a problem with that...
prev parent reply other threads:[~2016-02-14 20:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-13 17:43 Wiles, Keith
2016-02-13 19:12 ` Matthew Hall
2016-02-14 20:23 ` Stephen Hemminger [this message]
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=20160214122317.2bb33bed@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=keith.wiles@intel.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;
as well as URLs for NNTP newsgroup(s).