From owner-freebsd-current@freebsd.org Fri Oct 30 03:13:08 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id EC7CC4461F9 for ; Fri, 30 Oct 2020 03:13:08 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from smtp-out-so.shaw.ca (smtp-out-so.shaw.ca [64.59.136.138]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4CMnSM5lTKz4hTW for ; Fri, 30 Oct 2020 03:13:07 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from spqr.komquats.com ([70.67.229.168]) by shaw.ca with ESMTPA id YKqdkYSCfRAWfYKqeka8KM; Thu, 29 Oct 2020 21:13:05 -0600 X-Authority-Analysis: v=2.4 cv=P9aEOgMu c=1 sm=1 tr=0 ts=5f9b84c1 a=7AlCcx2GqMg+lh9P3BclKA==:117 a=7AlCcx2GqMg+lh9P3BclKA==:17 a=xqWC_Br6kY4A:10 a=kj9zAlcOel0A:10 a=afefHYAZSVUA:10 a=RgBw9RmQAAAA:8 a=YxBL1-UpAAAA:8 a=6I5d2MoRAAAA:8 a=EkcXrb_YAAAA:8 a=CX2mE1owdtc5oVmwsNcA:9 a=CjuIK1q_8ugA:10 a=Ia-lj3WSrqcvXOmTRaiG:22 a=IjZwj45LgO3ly-622nXo:22 a=LK5xJRSDVpKd5WXXoEvA:22 a=pHzHmUro8NiASowvMSCR:22 a=6VlIyEUom7LUIeUMNQJH:22 Received: from slippy.cwsent.com (slippy [IPv6:fc00:1:1:1::5b]) by spqr.komquats.com (Postfix) with ESMTPS id 21EF4470; Thu, 29 Oct 2020 20:13:02 -0700 (PDT) Received: from slippy (localhost [127.0.0.1]) by slippy.cwsent.com (8.16.1/8.16.1) with ESMTP id 09U3D0KZ006216; Thu, 29 Oct 2020 20:13:01 -0700 (PDT) (envelope-from Cy.Schubert@cschubert.com) Message-Id: <202010300313.09U3D0KZ006216@slippy.cwsent.com> X-Mailer: exmh version 2.9.0 11/07/2018 with nmh-1.7.1 Reply-to: Cy Schubert From: Cy Schubert X-os: FreeBSD X-Sender: cy@cwsent.com X-URL: http://www.cschubert.com/ To: qroxana cc: freebsd-current@freebsd.org Subject: Re: OpenZFS: kldload zfs.ko freezes on i386 4GB memory In-reply-to: References: Comments: In-reply-to qroxana message dated "Mon, 26 Oct 2020 05:47:09 -0000." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 29 Oct 2020 20:13:00 -0700 X-CMAE-Envelope: MS4xfOWqBOFaVDjZkRpo404mf8bfdCxw3EUBxdFr8FeKjmKuAS1G3qjhYy5xFfQ45x9xRf4i2qsAD9ZorskjVm/dcdwk/eDuTK0ilct/slnRRJNEdCSVcx1T GMxckf0MwkKy7/iwOd84hd2jp0I3ToPdOYJ5fDLTTWQ+v/Rxuc//Ju+De3QL+aHp1UNlkoE3QwqCU+RSHjpdDxkLiGL5PyVIOV14nk/sorw/n+4mjbbItlo4 X-Rspamd-Queue-Id: 4CMnSM5lTKz4hTW X-Spamd-Bar: / X-Spamd-Result: default: False [-0.23 / 15.00]; HAS_REPLYTO(0.00)[Cy.Schubert@cschubert.com]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; MV_CASE(0.50)[]; RCVD_COUNT_THREE(0.00)[4]; NEURAL_HAM_SHORT(-0.13)[-0.131]; RCPT_COUNT_TWO(0.00)[2]; FREEMAIL_TO(0.00)[mail.ru]; RECEIVED_SPAMHAUS_PBL(0.00)[70.67.229.168:received]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:6327, ipnet:64.59.128.0/20, country:CA]; MIME_TRACE(0.00)[0:+]; RCVD_IN_DNSWL_LOW(-0.10)[64.59.136.138:from]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.84)[-0.838]; REPLYTO_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-0.56)[-0.559]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[cschubert.com: no valid DMARC record]; AUTH_NA(1.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_TLS_LAST(0.00)[]; R_SPF_NA(0.00)[no SPF record]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Oct 2020 03:13:09 -0000 In message , qroxana writes : > > Hi, > > I have an old i386 machine running r364479. After upgrading to > r367045, running kldload zfs.ko freezes the whole system. > > I also tried to replace the 4GB memory with another 2GB one > and kldload zfs.ko works without freezing the machine. ZFS ARC stresses memory. I've found a number of bad RAM chips over the years using ZFS. The OpenZFS upgrade significantly changed how it manages ARC. It's likely that prior to the OpenZFS upgrade your memory wasn't stressed to the point of failure. You can try to mask the problem by reducing your RAM clock rate or or increase one of the other latency settings in your BIOS. However, again, this only masks an already weak RAM chip. Like everything, RAM does age over its lifetime. -- Cheers, Cy Schubert FreeBSD UNIX: Web: https://FreeBSD.org NTP: Web: https://nwtime.org The need of the many outweighs the greed of the few.