From nobody Mon Oct 13 16:14:56 2025 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 4clj9X2gjlz6C13R for ; Mon, 13 Oct 2025 16:14:56 +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 "R12" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4clj9X1vWHz3wQJ for ; Mon, 13 Oct 2025 16:14:56 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1760372096; 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=3x4L1N5erLD2C4gnKrtdsDDUZozkm9TWYije7Iz570M=; b=La8F2Mmx8ZFOZVNf5z4B2jHqBaO+eAq+R5L8IDXQEb/Po7dAVAeTlsRA4Rp/psVooe1RXO bBBDFzs7a6rQcU4Y6DC1Ib5vNASibErBExNNCip9XabOi68fipE2Rua3AzUNzYKvO5Bo5f uwSK9eiv53KNTYfLH6TZF+wWbgjA8mMfUvgVYq8dK435Nd1Gj01IA8DRODzzvWbp1FqYrQ z8G4vkAUwZGNAChPY3AmRHPHHmG52B+ViXUbNN8pj+pQ8EiEaFBp0Bgo2yElg07+bA0H77 qEtLLplp9sYH6GCLOZmqwlti98CGqux4XZIflWV3KwFGXYT+MFzOtSlPaELmlg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1760372096; 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=3x4L1N5erLD2C4gnKrtdsDDUZozkm9TWYije7Iz570M=; b=XXsQrmaNOe61XzPR1oJikvEMuRChxZdl5les8FCTiRKVGJ0dagzT4ENZvtwg0UaDtMlWGs gVeDAVun8aVLT64A/jOWZcqP35W58e4031pSz81qb9PfhirxXrfp122H5I8wOuC81U2/Mj hfDEwrt4yNRTHSBFHe7cvZGrsFJpyK17sxAFltv94V9NN432f9dD0vB6BQjU9JlrHzjU/u Dy8lSoZtLtJ5U6+KyURtOYkeOzt/fm0epSXnEVDpQtZi3kO+95SKibnPXpZlQaaexJT2VQ xXLUdjkiiGmQZmkc/6V+fLFCUNZqeZhynAourYybJ2c55cbx1vX6Reoqejvu6g== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1760372096; a=rsa-sha256; cv=none; b=FD+ZNshkbJjjBRfrYKZy9NS37y2wHwSM2CtlErkk/IBjU6Y2aZcyxRLyRwzJsp83nvK3PT VTzigjL5F5n5fCIm77s0gc8EnFYfl4i2No6VnjTbhw784SbYFFWTow9WMgJage3zTQLVTM 9o/lGAUKoxMEkJWkpfuvdHRL+qshFiBhF+en387alSvAxqpfOEJTYMbSz3qTi4y9SJsa4L fgL2H7tPU/O7gRGWWSVr7PPy8zUWzHPhRMuH1dSKqAbnDf8M8lUoaQho7Oo3IXB9WHGvoR IXhBZsKQ0HBAI5SESclFssl3uTWzPt67u4o5vPdmEpAZXJv6n9dlcXl0/hvtvA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none 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 4clj9X1Lj9z1Cn7 for ; Mon, 13 Oct 2025 16:14:56 +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 59DGEuQc092111 for ; Mon, 13 Oct 2025 16:14:56 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 59DGEus3092110 for bugs@FreeBSD.org; Mon, 13 Oct 2025 16:14:56 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 290156] mrsas driver 07.709.04.00-fbsd reports CACHE PAGE TOO SHORT errors Date: Mon, 13 Oct 2025 16:14:56 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 15.0-STABLE X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: cyric@mm.st X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" 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=3D290156 cyric@mm.st changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |cyric@mm.st --- Comment #3 from cyric@mm.st --- (In reply to Paul Telles (Starcat) from comment #2) I think this is just new diagnostic message added, properly checking the mo= de page. In any case, read the commit message for d5489f7d91a which introduced the checks/messages; pasting it below hoping bugzilla will keep the formatt= ing: commit d5489f7d91aee42e474bb66602bdbd6d9bedaffa Author: Warner Losh Date: Wed May 7 10:07:55 2025 -0600 scsi/da: Only send SYNC CACHE for devices with mode page 8 Mode page 8 is the 'cache' mode page. It's used to control the cache, if one is present, on a device. When it is absent, that's a very strong hint that SYNCHRONIZED CACHE willl not be necessary. Set the NO_SYNC_CACHE quirk for this situation. SBC defines the 2010 Profile which specifies that both SYNCRHONIZE CACHE and Cache Mode Page must be supported. There are additional vague statements tieing these two together, but nothing that explicitly requires Cache Mode Page support when SYNCHRONIZE CACHE is needed for cache coherency. However, when the Cace Mode Page is present, that's a very strong hint SYNCHRONIZE CACHE is supported (or at the very least won't hang the firmware). Given the diversity of implementations, it's hard to say this is 100% safe. However, many devices known to hang or worse on a SYNCHRONIZE CACHE tolerate querying an unsupported mode page well. If there's any devices that have a valid Cache page, but where SYNCHRONIZE CACHE actually hangs can be dealt with by specific quirks. --=20 You are receiving this mail because: You are the assignee for the bug.=