From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 7630DA00C4; Mon, 18 Apr 2022 10:33:36 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 18C1540150; Mon, 18 Apr 2022 10:33:36 +0200 (CEST) Received: from mx0b-00169c01.pphosted.com (mx0b-00169c01.pphosted.com [67.231.156.123]) by mails.dpdk.org (Postfix) with ESMTP id 8359B4014F for ; Mon, 18 Apr 2022 10:33:34 +0200 (CEST) Received: from pps.filterd (m0281122.ppops.net [127.0.0.1]) by mx0b-00169c01.pphosted.com (8.17.1.5/8.17.1.5) with ESMTP id 23I86fX7007000 for ; Mon, 18 Apr 2022 01:33:33 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paloaltonetworks.com; h=mime-version : from : date : message-id : subject : to : cc : content-type; s=PPS12012017; bh=E4+h0ygDl78bPMxyO+6/EqWQ6H/X+WiDJCaCUBoJkz4=; b=OG5WywiHVxaxJ3AtvC4612NFKGZGZI2OkUCBcYKAmEHM9AM226CDIrb1jhVWv+liAXTg g6tM3D2JZs4xG0mFAyxkuN0eePh93I4JcTsuKO5XTjvFzsvBJb3Im9U4qx5Z3o6D8r1C LaNJWpr8nRXLnuvF/GObYDkWwDzdcLBpMUjhuaEf6GvbrlmbD/7yAWzMam2I281U0hWX lQbCJFbbnUEPcQydl81cJ1jx0AG+z2Lq21F9MfVLI+c7JWGQLhTDOLA6s0Ss6EnEloss wzdYJrU6XEBUR4ZoEQWazRgU/4CA0L0jwmS8fY/lftmOpf5uHeVvS10ayRioKpeOk0V/ rw== Received: from mail-ua1-f69.google.com (mail-ua1-f69.google.com [209.85.222.69]) by mx0b-00169c01.pphosted.com (PPS) with ESMTPS id 3ffudjaqbt-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT) for ; Mon, 18 Apr 2022 01:33:33 -0700 Received: by mail-ua1-f69.google.com with SMTP id 8-20020a9f2008000000b0035d1a29391cso6196759uam.16 for ; Mon, 18 Apr 2022 01:33:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paloaltonetworks-com.20210112.gappssmtp.com; s=20210112; h=mime-version:from:date:message-id:subject:to:cc; bh=E4+h0ygDl78bPMxyO+6/EqWQ6H/X+WiDJCaCUBoJkz4=; b=5HmRRv9V+CtIS053WG2o54JHQKpSPrG5NLiGcQ4eIE7bssvlmDQdJCk9V2afFaaPrF MxEqTf1UdknZbG0BLZhaTM8CcHWJG93IvGIEHP8EXeO6ZeuvFvBu0zGRFZrOWNk3BhLC uuPc6I8VHuTTj2jjdml/0EAXXpa9Yd8XCBACuwgYzixD6WtSDP6aeehx6WAtz841L1vx 85XabfTJBqhACaFyHNOKQW/2vOfQQosUnBuU27p470Rcl4hrUj5+J3t6HJtFK5+HT5wb lT4eM91LWuSyNyRYZCsPdMUtOFUJCt+TpNcaxlxAIlfMeKcp11NsWIvAL6PNgMTbbPLZ WGGg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=E4+h0ygDl78bPMxyO+6/EqWQ6H/X+WiDJCaCUBoJkz4=; b=YU9Ztp7gq8G/Wzodn1Z9zKuGyso58GsImM6Wm82IlG6/IQTG75+auEfRCwNS9UvIlJ ozdwDKKL8Xw48Z4rcUcDvREnDi0oaE7TS72yh/O9cfd+ljPMlAeStqlU+XrHYLzyBr7K 9bFjWJ8DlWIS8Lu7JHuqC+4Po/qDXEMsBTZmF3kWgdWHSyeeTd1Vme5pdVmBKygtvkIM txGUBQ0fKjyjdwYo7Q9D1uWelZY+f7qHcdbzpXB4MvfUQOHbYdJXH1rUM51PXiN6DICX QsgxHx3j9vwy5Asd11gjx8TgVmrfSgMpWwkWvjqWsl8s5CoekS8P64WpCBtTBl1pi+h/ iVEA== X-Gm-Message-State: AOAM531cnghyeaMyM0PONcvCnFkwspf6g3KyNc7QG2zI+Emy6G3T7gVF PJBa+EH6b7qM8gy35xoXjapfAO3hp0/oAOQiMX4+zayxs4aM3WzbqtdIiQfWtzmZ7kwTjRBUCgy s4nDEeN8auOPLTsFRUds= X-Received: by 2002:a1f:9c09:0:b0:344:fe68:fa84 with SMTP id f9-20020a1f9c09000000b00344fe68fa84mr2528395vke.8.1650270812819; Mon, 18 Apr 2022 01:33:32 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxY7jf77eYbm3EbLSwPnHrp4pJPCV/z0xoqHTdJG/vSxa1JOP1GbBG9qZkABcABrjKqMr7kj2s5k6/lussQkXA= X-Received: by 2002:a1f:9c09:0:b0:344:fe68:fa84 with SMTP id f9-20020a1f9c09000000b00344fe68fa84mr2528385vke.8.1650270812493; Mon, 18 Apr 2022 01:33:32 -0700 (PDT) MIME-Version: 1.0 From: Amiya Mohakud Date: Mon, 18 Apr 2022 14:03:21 +0530 Message-ID: Subject: DPDK:20.11.1: net/ena crash while fetching xstats To: mk@semihalf.co, dev@dpdk.org Cc: Amiya Mohakud , Sachin Kanoje Content-Type: multipart/alternative; boundary="0000000000008ffab505dce99d45" X-Proofpoint-GUID: Qhdv36CbSPNnrAT5Y1DSoz7aIT4P0FXU X-Proofpoint-ORIG-GUID: Qhdv36CbSPNnrAT5Y1DSoz7aIT4P0FXU X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.205,Aquarius:18.0.858,Hydra:6.0.486,FMLib:17.11.64.514 definitions=2022-04-18_02,2022-04-15_01,2022-02-23_01 X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 bulkscore=0 spamscore=0 suspectscore=0 malwarescore=0 mlxlogscore=693 phishscore=0 mlxscore=0 impostorscore=0 priorityscore=1501 adultscore=0 lowpriorityscore=0 clxscore=1011 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2202240000 definitions=main-2204180051 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org --0000000000008ffab505dce99d45 Content-Type: text/plain; charset="UTF-8" Hi Michal/DPDK-Experts, I am facing one issue in net/ena driver while fetching extended stats (xstats). The DPDK seems to segfault with below backtrace. DPDK Version: 20.11.1 ENA version: 2.2.1 Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `/opt/dpfs/usr/local/bin/brdagent'. Program terminated with signal SIGSEGV, Segmentation fault. #0 __memmove_avx_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:232 232 VMOVU %VEC(0), (%rdi) [Current thread is 1 (Thread 0x7fffed93a400 (LWP 5060))] Thread 1 (Thread 0x7fffed93a400 (LWP 5060)): #0 __memmove_avx_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:232 #1 0x00007ffff3c246df in ena_com_handle_admin_completion () from ../lib64/../../lib64/libdpdk.so.20 #2 0x00007ffff3c1e7f5 in ena_interrupt_handler_rte () from ../lib64/../../lib64/libdpdk.so.20 #3 0x00007ffff3519902 in eal_intr_thread_main () from /../lib64/../../lib64/libdpdk.so.20 #4 0x00007ffff510714a in start_thread (arg=) at pthread_create.c:479 #5 0x00007ffff561ff23 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 *Background:* - This used to work fine with DPDK-19.11.3 , that means there was no crash observed with the 19.11.3 DPDK version, but now after upgrading to DPDK 20.11.1, DPDK is crashing with the above trace. - It looks to me as a DPDK issue. - I could see multiple fixes/patches in the net/ena area, but not able to identify which patch would exactly fix this issue. For example: http://git.dpdk.org/dpdk/diff/?h=releases&id=aab58857330bb4bd03f6699bf1ee716f72993774 https://inbox.dpdk.org/dev/20210430125725.28796-6-mk@semihalf.com/T/#me99457c706718bb236d1fd8006ee7a0319ce76fc Could you please help here and let me know what patch could fix this issue. Regards Amiya --0000000000008ffab505dce99d45 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Michal/DPDK-Experts,

I am facing one issue in net/ena d= river while fetching extended stats (xstats). The DPDK seems to segfault wi= th below backtrace.=C2=A0

DPDK Version: 20.11.1
ENA version: 2.2.1

Using host libthread_db library "/lib64/libthread_db.so.1"= .

Core was generated by `/opt/dpfs/usr/local/bin/brdagent'.

Program terminated with signal SIGSEGV, Segmentation fault.

#0=C2=A0 __memmove_avx_unaligned_erms () at ../sysdeps/= x86_64/multiarch/memmove-vec-unaligned-erms.S:232

232 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 VMOVU =C2=A0 %VEC(0), (%rdi)

[Current thread is 1 (Thread 0x7fffed93a400 (LWP 5060))]


Thread 1 (Thread 0x7fffed93a400 (LWP 5060)):

#0=C2=A0 __memmove_avx_unaligned_erms () at ../sysdeps/= x86_64/multiarch/memmove-vec-unaligned-erms.S:232

#1=C2=A0 0x00007ffff3c246df in ena_com_handle_admin_com= pletion () from ../lib64/../../lib64/libdpdk.so.20

#2=C2=A0 0x00007ffff3c1e7f5 in ena_interrupt_handler_rt= e () from ../lib64/../../lib64/libdpdk.so.20

#3=C2=A0 0x00007ffff3519902 in eal_intr_thread_main () = from /../lib64/../../lib64/libdpdk.so.20

#4=C2=A0 0x00007ffff510714a in start_thread (arg=3D<= optimized out>) at pthread_create.c:479

#5=C2=A0 0x00007ffff561ff23 in clone () at ../sysdeps/u= nix/sysv/linux/x86_64/clone.S:95



<= br>

Background:
  • This used to work fine with DPDK-19.11.3 , that=C2=A0= means there was no crash observed with the 19.11.3 DPDK version, but now af= ter upgrading to DPDK 20.11.1, DPDK is crashing with the above trace.=C2=A0=
  • It looks to me as a DPDK issue.
  • I could see multiple fixes= /patches in the net/ena area, but not able to identify which patch would ex= actly fix this issue.
For example: <= a href=3D"http://git.dpdk.org/dpdk/diff/?h=3Dreleases&id=3Daab58857330b= b4bd03f6699bf1ee716f72993774" target=3D"_blank">http://git.dpdk.org/dpdk/di= ff/?h=3Dreleases&id=3Daab58857330bb4bd03f6699bf1ee716f72993774


Could you please hel= p here and let me know what patch could fix this issue.


Regards
Amiya
--0000000000008ffab505dce99d45--