From owner-freebsd-bugs@freebsd.org Mon Feb 25 08:21:50 2019 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B44BB1501A85 for ; Mon, 25 Feb 2019 08:21:50 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 3274E820AD for ; Mon, 25 Feb 2019 08:21:50 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id E9D941501A84; Mon, 25 Feb 2019 08:21:49 +0000 (UTC) Delivered-To: bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C74A31501A83 for ; Mon, 25 Feb 2019 08:21:49 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6693F820A9 for ; Mon, 25 Feb 2019 08:21:49 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 9FDEFD93E for ; Mon, 25 Feb 2019 08:21:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x1P8Lmpk041597 for ; Mon, 25 Feb 2019 08:21:48 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x1P8LmEp041596 for bugs@FreeBSD.org; Mon, 25 Feb 2019 08:21:48 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 235944] jedec_dimm(4) does not attach to KFA2 (aka Galax) Hall of Fame DDR4 sticks Date: Mon, 25 Feb 2019 08:21:48 +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: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: avg@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: 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 MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Feb 2019 08:21:51 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D235944 --- Comment #14 from Andriy Gapon --- (In reply to Ravi Pokala from comment #13) Oh, I recall this now. Thank you for refreshing my memory. And I could ha= ve checked the code more thoroughly myself. So, sorry for the noise. In one part-specific datasheet I noticed this curious bit: https://www.onsemi.com/pub/Collateral/N34C04-D.PDF > 17. The N34C04MU3ETG will respond with NoACK following the dummy Data Byt= e, > while the N34C04MU3EKTG will respond with ACK. Maybe that NoACK (NACK) is what we are seeing here as an SMBus error. Although the code mapped PIIX4_SMBHSTSTAT_ERR | PIIX4_SMBHSTSTAT_INTR to SMB_EBUSERR rather than to SMB_ENOACK, I am not sure if that mapping is (universally) correct. E.g., in one AMD BKDG document I see this: > Bits Description > 2 DeviceErr. Read; Write-1-to-clear; Set-by-hardware. > Reset: 0. > 1=3DAn error of one of the following occurred: > =E2=80=A2 Illegal command field. > =E2=80=A2 Unclaimed cycle > =E2=80=A2 Host device time-out. > 1 SMBusInterrupt. Read; Write-1-to-clear; Set-by-hardware. > Reset: 0. 1=3DCompletion of the last host command. A combination of these bits can mean an "unclaimed cycle" and maybe that me= ans "NACK" in the SMBus protocol terminology. So, it would be interesting to see - what specific EEPROM part the DIMM in question uses (a looking glass can help) - what happens if we ignore the error from the page change write --=20 You are receiving this mail because: You are the assignee for the bug.=