From nobody Mon Nov 25 13:36:35 2024 X-Original-To: stable@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 4XxmvS5l3kz5dcks for ; Mon, 25 Nov 2024 13:36: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 "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XxmvS36V9z51qr for ; Mon, 25 Nov 2024 13:36:36 +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=1732541796; 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: in-reply-to:in-reply-to:references:references; bh=CMFvwnZSbvGxCXor7oay8i1vdXMjjrW+LilLfX+1+LY=; b=scvRufNprZ8abw96fuVDEVuu5McavxPZ5DB4V5ZK604ylAOj4u+T1A9P1lUhwnuDCHlocz OhEL0JSA+mAUhm4TZOwLb/ZFEOUPX8TU3AcIgK3DBfdsa1TPmReoQWWOePDWHRpk16IQgN yRL2McMFW4fwXVTTZk2FjlfATH4JTQuo51/JMIyGm/knQZfEyl+ohvuurhpUsU4uBU5dnH reDtV0d93xZ7/5ui2sPqGVAXL2kp5es8TcdoRsGiDB+FpnGHIx7UbbwTbh3/XDWsfulRjd t07HExY5WuSNPyc0MqLblVSZKvV/hgJnpvXRyedE3CkNVCEigPymG5/PI0A5DQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1732541796; a=rsa-sha256; cv=none; b=F0KLlzkU0tv1urYVVcs58hDmXDc49Rm2TsgpFmakKNo7d6Nl7Oa+E4H1DxIM+gpP5GjncH GCA0LzfLuDpqBk3zqf8dyOKQP8kdKkOpZYPZSA+zwiCHif7D3AKXSYFE6IsGyvStK/NQZP fwGV5CAtcy5VpvhAsmjGTReble7ik7OYLasptQw5Z02zk1omFHxRIEIUy1+LC0db3PW77C fnPZnlUEGPraC1mjLRBvzaddGEP40uM0NjCXY0N+kWK4K1ILS+K/elazHn6b3/Bfz2Ck+L mdjw4PhRltG+evBCCu45qUze1UDwcfieXD5IKluSwQEmLkGrGCukVV0wLWgPow== 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 4XxmvS2l8Dzj8W for ; Mon, 25 Nov 2024 13:36: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 4APDaadY084612 for ; Mon, 25 Nov 2024 13:36:36 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 4APDaaAx084611 for stable@FreeBSD.org; Mon, 25 Nov 2024 13:36: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: stable@FreeBSD.org Subject: [Bug 271238] mpr (LSI SAS3816) driver not finding all devices in HP D6020 enclosures Date: Mon, 25 Nov 2024 13:36:35 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 14.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: pen@lysator.liu.se X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: 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: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D271238 --- Comment #6 from Peter Eriksson --- Some more interresting details from the lastest boot. At boot all the disks= are detected, however.... Partial output from "mpr show devices" > 00 101 5000cca2912db98d 0039 0017 SAS Target 12 0002 85 = 1 > 00 102 5000cca2912e3619 003a 0017 SAS Target 12 0002 86 = 1 > 5000cca2912d19ed 003b 0017 SAS Target 12 0002 87 = 1 > 5000cca2912d8bc5 003c 0017 SAS Target 12 0002 88 = 1 Now looking at the boot output I notice this: > mpr0: Handle 0x003b SAS Address from SAS device page0 =3D 5000cca2912d19ed > mpr0: mprsas_add_device: Target ID for added device is 103. > mpr0: Found device <401,End Device> <12.0Gbps> handle<0x003b> en= closureHandle<0x0002> slot 87 > mpr0: At enclosure level 0 and connector name (C1 ) > mpr0: Target id 0x67 added > > mpr0: Handle 0x003c SAS Address from SAS device page0 =3D 5000cca2912d8bc5 > mpr0: mprsas_add_device: Target ID for added device is 104. > mpr0: Found device <401,End Device> <12.0Gbps> handle<0x003c> en= closureHandle<0x0002> slot 88 > mpr0: At enclosure level 0 and connector name (C1 ) > mpr0: Target id 0x68 added Ok here the ..19ed drive is detected and allocated the target id 103 - whic= h it looks like to be the next number... (and ...8bc5 gets target it 104. A bit further down in the boot sequence I find this: > mpr0: _mapping_find_enc_map_space: Looking for space in the mapping table= for added enclosure. > mpr0: _mapping_find_enc_map_space: Found space in the mapping for enclosu= re at map index 34. > mpr0: _mapping_get_dev_info: Initialize 18 map entries for the enclosure,= starting at map index 34. > mpr0: _mapping_flush_dpm_pages: Flushing DPM entry 1. >=20 > mpr0: Handle 0x0062 SAS Address from SAS device page0 =3D 5000cca25147fc2d > mpr0: mprsas_add_device: Target ID for added device is 103. > mpr0: Attempting to reuse target id 103 handle 0x003b >=20 > mpr0: Handle 0x0063 SAS Address from SAS device page0 =3D 5000cca251470281 > mpr0: mprsas_add_device: Target ID for added device is 104. > mpr0: Attempting to reuse target id 104 handle 0x003c If I'm reading this right it looks like the mpr driver overwrites the target entries for 103 & 104 with some other drive found later in the sequence. (there are more entries like this). I wonder if not the code in _mapping_find_enc_map_space() is mistakenly reu= sing some mapping table space that already is in use...=20 I'll upload the complete outputs from boot and mpr show devices for referen= ce too. --=20 You are receiving this mail because: You are on the CC list for the bug.=