DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: David Liu <dliu@iol.unh.edu>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] DTS Error / can not find cores
Date: Wed, 25 Mar 2020 01:17:47 +0000	[thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BBF0F73@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <CAAuqQpQZMgjxnmJ2wL_KD1mTo4ZL7txrycegzRszUn6ieFFa3w@mail.gmail.com>

It seems it caused by that dts not compatible with pexpect 4.8.0 , we met it before, and we have fixed it in latest version.

Here are 3 options for you:
               1, lower pexpect to 4.2.1
               2, update dts to latest commit
               3, apply the patch set below:
               https://mails.dpdk.org/archives/dts/2020-March/009084.html
            https://mails.dpdk.org/archives/dts/2020-March/009085.html


thanks
Lijuan
From: David Liu [mailto:dliu@iol.unh.edu]
Sent: Tuesday, March 24, 2020 11:40 PM
To: Tu, Lijuan <lijuan.tu@intel.com>
Cc: dev@dpdk.org
Subject: Re: DTS Error / can not find cores

The log file may be useful.

On Tue, Mar 24, 2020 at 11:32 AM David Liu <dliu@iol.unh.edu<mailto:dliu@iol.unh.edu>> wrote:
Hi,

We are currently having an issue when running the command to set up the DTS with T-Rex on the machines.
We tried to look into the code, but we are still not sure why and what cause the issue.
Do you have any clue how we can fix this?  We know the DTS working, T-Rex is able to be detected.

Best,
David

      reply	other threads:[~2020-03-25  1:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-24 15:32 David Liu
2020-03-24 15:39 ` David Liu
2020-03-25  1:17   ` Tu, Lijuan [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=8CE3E05A3F976642AAB0F4675D0AD20E0BBF0F73@SHSMSX101.ccr.corp.intel.com \
    --to=lijuan.tu@intel.com \
    --cc=dev@dpdk.org \
    --cc=dliu@iol.unh.edu \
    /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).