From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ferruh Yigit Subject: Re: [4.4 kernel] kni lockup, kernel dump Date: Thu, 14 Apr 2016 15:29:04 +0100 Message-ID: <570FA930.60105@intel.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable To: ALeX Wang , dev@dpdk.org Return-path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id A905F2986 for ; Thu, 14 Apr 2016 16:29:37 +0200 (CEST) In-Reply-To: List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On 4/13/2016 11:26 PM, ALeX Wang wrote: > Did more experiment, found that it has nothing to do with the kernel > version, >=20 > It only happens when using kni module with '--no-huge' eal flag... >=20 > Is that expected? >=20 Yes. KNI kernel module expects mempool is physically continuous, with '--no-huge' flag this is no more true, and as a result KNI module can access to incorrect address. Regards, ferruh