From nobody Wed Nov 10 10:23:36 2021 X-Original-To: bugs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 9C8F01859079 for ; Wed, 10 Nov 2021 10:23:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Hq1CX3xMxz3Dg5 for ; Wed, 10 Nov 2021 10:23:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 683C116FC1 for ; Wed, 10 Nov 2021 10:23:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 1AAANaVJ086354 for ; Wed, 10 Nov 2021 10:23:36 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 1AAANaqp086353 for bugs@FreeBSD.org; Wed, 10 Nov 2021 10:23:36 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 259748] Loading mlx4en kernel module hangs Date: Wed, 10 Nov 2021 10:23:36 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: thj@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org 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 Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Bug reports List-Archive: https://lists.freebsd.org/archives/freebsd-bugs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-bugs@freebsd.org MIME-Version: 1.0 X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D259748 Bug ID: 259748 Summary: Loading mlx4en kernel module hangs Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: thj@FreeBSD.org Loading mlx4en on CURRENT (main-n250453-7ac82c96fe7) hangs kldload. Pressin= g ^C allows the module to continue and to load properly. This happens from a shell and when loading the module using 'kld_list' The mlx4en part of dmesg is: mlx4_core0: mem 0xfce00000-0xfcefffff,0xe0000000-0xe07fffff irq= 54 at device 0.0 on pci9 mlx4_core: Mellanox ConnectX core driver v3.7.0 (July 2021) mlx4_core: Initializing mlx4_core mlx4_core0: Unable to determine PCI device chain minimum BW mlx4_en mlx4_core0: Activating port:1 mlxen0: Ethernet address: ec:0d:9a:e1:34:20 mlx4_en: mlx4_core0: Port 1: Using 16 TX rings mlxen0: link state changed to DOWN mlx4_en: mlx4_core0: Port 1: Using 16 RX rings mlx4_en: mlxen0: Using 16 TX rings mlx4_en: mlxen0: Using 16 RX rings mlx4_en: mlxen0: Initializing port mlx4_en mlx4_core0: Activating port:2 mlxen1: Ethernet address: ec:0d:9a:e1:34:21 mlx4_en: mlx4_core0: Port 2: Using 16 TX rings mlxen1: link state changed to DOWN mlx4_en: mlx4_core0: Port 2: Using 16 RX rings mlx4_en: mlxen1: Using 16 TX rings mlx4_en: mlxen1: Using 16 RX rings mlx4_en: mlxen1: Initializing port mlx4_en: mlxen1: Link Up mlxen1: link state changed to UP mlx4_en: mlxen0: Link Up mlxen0: link state changed to UP This happens on my Ryzen 3700X system, but happened previously on other systems. 13-RELEASE doesn't have this problem --=20 You are receiving this mail because: You are the assignee for the bug.=