From nobody Thu Nov 21 10:13:21 2024 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 4XvDZn6mxNz5cKkv for ; Thu, 21 Nov 2024 10:13:21 +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 "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XvDZn4Mmsz42R7 for ; Thu, 21 Nov 2024 10:13:21 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1732184001; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=zHtJmFy5omSYq/iSMr6yIcnfIWPfSMndhbeIHDYyCxo=; b=qkgadaRyXhp/T7XdKsLaL6cWGl0qTuLSVK2pib1JJOuJoL4e6rMGbU5c0S2RpX5sTza0IQ oX+4EwMtJBrfxgEW52ePVtd8khV5Gp5hOognSswh7Db2pJllAslBFVHDE1uOvC+2S0D8kB ERlZihpZxVmi6PIUj6VTgoBMgV//g2O2PGfirRz6IKTvEkwbwEbBZfidKc40ZLf6xX9vUN nNpWfDFCZ6fGy3mxxOsMxVqAxe90+SYlNVOXAj9r7iVSC7eUVsH5bS7x34OJleKpAu+V8T 7RGFcXlz2V4U6JhBXXvBIKJkciSFJ6cPJFRSxLKM3iLpTSL+6mE2FYCEbvvulA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1732184001; a=rsa-sha256; cv=none; b=e9xRNj8MhQdT/SR41N6VAl497QfCzCz2Q+4gBDDbdwQzjdfs6iqvB5GtvD49lg8nDS20x2 339JVBjzQUdQmOsBlnTDspzs/LEYQOyvBzGcuZt/d5Di920IAK4LoPv2L38u6ftADMkR82 Gr1ZRQPuISrO9e1KWt4JVcKVLjpijjAjOeLfIPRsfjPB8bELaa6AZ6E1AJBbdd+vcJVncp egjT3orBeGhqYpWstO4J+bIMSuDZZUgd0syFGqog2TKbp8upydzz83W03Qi1V6Nbxa8GO6 8d2zTLPenV+qODaMVk3/Us/BMSZKVtlzhFMPT7qr9jqqs2AfV0v9a6P2JPrDyA== 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 4XvDZn3zW0zbGR for ; Thu, 21 Nov 2024 10:13:21 +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 4ALADLrB013955 for ; Thu, 21 Nov 2024 10:13:21 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 4ALADLCG013954 for bugs@FreeBSD.org; Thu, 21 Nov 2024 10:13:21 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 282887] [13.4]Broadcom mpi3mr driver: DMA allocation fails Date: Thu, 21 Nov 2024 10:13:21 +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: 13.4-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: chandrakanth.patil@broadcom.com 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 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D282887 Bug ID: 282887 Summary: [13.4]Broadcom mpi3mr driver: DMA allocation fails Product: Base System Version: 13.4-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: chandrakanth.patil@broadcom.com We are encountering DMA allocation failures during driver load on the recen= tly released FreeBSD 13.4 OS. Were there any changes made to DMA handling that might have caused this issue? Notably, the requested memory allocation size= is relatively small, yet the allocation is still failing. Below are the driver load logs: mpi3mr: Loading Broadcom mpi3mr driver version: 8.12.0.0.0 OS version: 13.04.000 mpi3mr0: mem 0x28080f00000-0x28080f03fff at device 0.0 on pci17 mpi3mr0: Hard secure controller is detected mpi3mr0: SOD ioc_status: 0x8 ioc_control: 0x472000 ioc_info: 0xff000000 mpi3mr0: IOC state: reset IOC ready timeout: 510 mpi3mr0: Set up 1 MSI-x interrupts mpi3mr0: ioc_num(0), maxopQ(127), maxopRepQ(127), maxdh(1023),maxreqs(8192), mindh(1) maxPDs(0) maxvectors(128) maxperids(1024) mpi3mr0: SGEModMask 0x80 SGEModVal 0x80 SGEModShift 0x18 mpi3mr0: max_dev_per_throttle_group(16), max_throttle_groups(241), io_throttle_data_len(68KiB), io_throttle_high(128MiB), io_throttle_low(64Mi= B) mpi3mr0: dma_mask bits: 63 loaddr 0x8000000000000000 hiaddr 0xfffffffffffff= fff mpi3mr0: Current Personality: RAID mpi3mr0: fw version: 8.12.0.100.00000-00004 mpi3mr0: Protocol=3D(Initiator,NVMe attachment), Capabilities=3D(RAID) mpi3mr0: Issue CI Header Upload: Failed IOCStatus(0x00b2) Loginfo(0x3001045= 3) mpi3mr0: Supported MSI-x count: 128 CPU count: 128 Requested MSI-x count: = 127 mpi3mr0: Set up 127 MSI-x interrupts mpi3mr0: mpi3mr_create_op_req_queue: Cannot allocate replies memory mpi3mr0: Failed to create Request queue 127 mpi3mr0: Successfully created 126 Operational Queue pairs mpi3mr0: Request Queue QD: 512 Reply queue QD: 1024 mpi3mr0: Failed to create operational queues, error: -1 mpi3mr0: Retrying controller initialization,retry_count: 1 mpi3mr0: SOD ioc_status: 0x1 ioc_control: 0x472001 ioc_info: 0xff000000 mpi3mr0: IOC state: ready IOC ready timeout: 510 mpi3mr0: Issuing Message Unit Reset(MUR) mpi3mr0: IOC Status/Config after successful MUR is (0x0)/(0x472000) mpi3mr0: Set up 1 MSI-x interrupts mpi3mr0: ioc_num(0), maxopQ(127), maxopRepQ(127), maxdh(1023),maxreqs(8192), mindh(1) maxPDs(0) maxvectors(128) maxperids(1024) mpi3mr0: SGEModMask 0x80 SGEModVal 0x80 SGEModShift 0x18 mpi3mr0: max_dev_per_throttle_group(16), max_throttle_groups(241), io_throttle_data_len(68KiB), io_throttle_high(128MiB), io_throttle_low(64Mi= B) mpi3mr0: dma_mask bits: 63 loaddr 0x8000000000000000 hiaddr 0xfffffffffffff= fff mpi3mr0: Current Personality: RAID mpi3mr0: fw version: 8.12.0.100.00000-00004 mpi3mr0: Protocol=3D(Initiator,NVMe attachment), Capabilities=3D(RAID) mpi3mr0: Func: mpi3mr_reply_dma_alloc line: 1784 DMA mem alloc failed mpi3mr0: func:mpi3mr_reply_alloc line:1989 DMA memory allocation failed mpi3mr0: Failed to allocated reply and sense buffers, error: 0xffffffff mpi3mr0: FW initialization failed device_attach: mpi3mr0 attach returned -1 --=20 You are receiving this mail because: You are the assignee for the bug.=