From: "Wiles, Keith" <keith.wiles@intel.com>
To: "McCullough, Harrison" <harrison_mccullough@labs.att.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] bug: pktgen-dpdk leaves terminal in abnormal state, no text or cursor
Date: Tue, 27 Jun 2017 21:17:56 +0000 [thread overview]
Message-ID: <9A7FA347-17F2-41FC-890F-529C951748DA@intel.com> (raw)
In-Reply-To: <942AD08E4186F644A54168E4F84117C93178BB@SAUSMAILMBX1.ad.tri.sbc.com>
> On Jun 27, 2017, at 1:23 PM, McCullough, Harrison <harrison_mccullough@labs.att.com> wrote:
>
> When I start pktgen-dpdk just like the example in the documentation, like this:
>
> ./test_pmd -c 0x3 -n 2
>
> And then quit by typing 'quit' or 'Ctrl-x' and hitting enter, my terminal is
> left in a very abnormal state. I can see my PS1 showing up but the cursor does
> not move and text does not appear when I type. At first I assumed it was frozen,
> but eventually I discovered that my commands were working and I could see the
> output of commands, but the text that I type doesn't show up.
Yes, normally do not run pktgen using the command line format, but I use the ./tools/run.py or ./tools/run.sh.
The run.py python script is the newer script and it uses .cfg files in the ./cfg directory to execute pktgen with the correct options. The run.sh script needs to be edited to run the correct options. I would suggest using the run.py script as in:
$ ./tools/run.py default
And yes pktgen needs to be fixed to not leave the tty in a funny state. I hope I can get to that later.
>
> If I use the `reset` command then everything goes back to normal.
>
> I am using PuTTY from Windows 7 to connect to a Ubuntu 14.04 server.
Regards,
Keith
prev parent reply other threads:[~2017-06-27 21:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-27 20:23 McCullough, Harrison
2017-06-27 21:17 ` Wiles, Keith [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=9A7FA347-17F2-41FC-890F-529C951748DA@intel.com \
--to=keith.wiles@intel.com \
--cc=harrison_mccullough@labs.att.com \
--cc=users@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).