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 AC139437C8; Sat, 30 Dec 2023 04:42:15 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 9834A40271; Sat, 30 Dec 2023 04:42:13 +0100 (CET) Received: from inbox.dpdk.org (inbox.dpdk.org [95.142.172.178]) by mails.dpdk.org (Postfix) with ESMTP id F061240150 for ; Sat, 30 Dec 2023 04:42:11 +0100 (CET) Received: by inbox.dpdk.org (Postfix, from userid 33) id BD35B437C9; Sat, 30 Dec 2023 04:42:11 +0100 (CET) From: bugzilla@dpdk.org To: dev@dpdk.org Subject: [Bug 1339] Ice pmd driver ice_rss_init error message "not support in safe mode" Date: Sat, 30 Dec 2023 03:42:11 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: DPDK X-Bugzilla-Component: ethdev X-Bugzilla-Version: 20.11 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: 501359811@qq.com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: dev@dpdk.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: multipart/alternative; boundary=17039077310.EEFaBf71.684901 Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All MIME-Version: 1.0 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 --17039077310.EEFaBf71.684901 Date: Sat, 30 Dec 2023 04:42:11 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All https://bugs.dpdk.org/show_bug.cgi?id=3D1339 Bug ID: 1339 Summary: Ice pmd driver ice_rss_init error message "not support in safe mode" Product: DPDK Version: 20.11 Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: Normal Component: ethdev Assignee: dev@dpdk.org Reporter: 501359811@qq.com Target Milestone: --- In the ice pmd driver code, ad ->is_safe_mode uninitialized ,with a random value may cause ice_rss_Init() return error message " not support in safe = mode " .To solve this problem, it is necessary to add code at the beginning of t= he ice_dev_init() "ad->safe_mode=3D0;" // I encountered this issue while debugging the e810 network card. The ice dri= ver code uses rte_socket_zmalloc, but this function does not initialize the mem= ory to 0 (but the annotation will clear 0? A bug ? only memset 0 in debug code), which caused the above problem. --=20 You are receiving this mail because: You are the assignee for the bug.= --17039077310.EEFaBf71.684901 Date: Sat, 30 Dec 2023 04:42:11 +0100 MIME-Version: 1.0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All

Bug ID	1339
Summary	Ice pmd driver ice_rss_init error message "not support= in safe mode"
Product	DPDK
Version	20.11
Hardware	All
OS	All
Status	UNCONFIRMED
Severity	normal
Priority	Normal
Component	ethdev
Assignee	dev@dpdk.org
Reporter	501359811@qq.com
Target Milestone	---

In the ice pmd driver code, ad -&g=
t;is_safe_mode uninitialized ,with a random
value may cause ice_rss_Init() return error message "  not support in =
safe mode
" .To solve this problem, it is necessary to add code at the beginning=
 of the
ice_dev_init()  "ad->safe_mode=3D0;"


//
I encountered this issue while debugging the e810 network card. The ice dri=
ver
code uses rte_socket_zmalloc, but this function does not initialize the mem=
ory
to 0 (but the annotation will clear 0? A bug ? only memset 0 in debug code),
which caused the above problem.

You are receiving this mail because:

You are the assignee for the bug.

=20=20=20=20=20=20=20=20=20=20

= --17039077310.EEFaBf71.684901--