From nobody Sat Jul 23 09:33:44 2022 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 4Lqh2V0528z4XBb3 for ; Sat, 23 Jul 2022 09:33:54 +0000 (UTC) (envelope-from SRS0=ky3J=X4=klop.ws=ronald-lists@realworks.nl) Received: from smtp-relay-int.realworks.nl (smtp-relay-int.realworks.nl [194.109.157.24]) (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 mx1.freebsd.org (Postfix) with ESMTPS id 4Lqh2S56lGz3qPn for ; Sat, 23 Jul 2022 09:33:52 +0000 (UTC) (envelope-from SRS0=ky3J=X4=klop.ws=ronald-lists@realworks.nl) Date: Sat, 23 Jul 2022 11:33:44 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=klop.ws; s=rw2; t=1658568825; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to; bh=jmJAsiOgUhNo2fpGtqkqjz8O87Tq7R4wi982PCohTR0=; b=EzeXiCTBUwuYwDCNHIXzDSf+4UZcSKkGm3cirph6NC2eZpJ9IYaH8aFsW1srUfvEs8cSQG PNWeVzm1QLuVIkBOH0WYuWl/BI/Tkx/USZu++GTEFIOl6cryAn2nU8vTP1rUYyfmRjP5fj EHNX2jf304Weo6lIuDvQ1dNQaQOd8vgTR9w6OZAXxI7GXJghQmThUBJTmHZvhCA2fZFb2c ThcDoQQrcRq5UbFBpDYIGGpEEPoRkC2nCP4sN/TFlOlzmBCZkL43XbgeIvg+7R5w6JD8KH x3dZAfiKcUmjrOvU+P89C6qtel9KDXnfYaOT9sNbcuktWES14Ftb3J3ohwt36w== From: Ronald Klop To: Juraj Lutter , stable@freebsd.org Message-ID: <1854386355.11751.1658568824946@localhost> In-Reply-To: <0A76E2FF-1423-48D9-A32B-9784BF3DCBDD@lutter.sk> Subject: Re: panic in zfs(?) on stable/12 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: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_11750_900121351.1658568824944" X-Mailer: Realworks (616.105.1ef8494) Importance: Normal X-Priority: 3 (Normal) X-Rspamd-Queue-Id: 4Lqh2S56lGz3qPn X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=klop.ws header.s=rw2 header.b=EzeXiCTB; dmarc=pass (policy=quarantine) header.from=klop.ws; spf=pass (mx1.freebsd.org: domain of "SRS0=ky3J=X4=klop.ws=ronald-lists@realworks.nl" designates 194.109.157.24 as permitted sender) smtp.mailfrom="SRS0=ky3J=X4=klop.ws=ronald-lists@realworks.nl" X-Spamd-Result: default: False [-3.15 / 15.00]; NEURAL_HAM_LONG(-1.00)[-0.999]; NEURAL_HAM_SHORT(-1.00)[-0.998]; NEURAL_HAM_MEDIUM(-0.95)[-0.955]; MID_RHS_NOT_FQDN(0.50)[]; DMARC_POLICY_ALLOW(-0.50)[klop.ws,quarantine]; FORGED_SENDER(0.30)[ronald-lists@klop.ws,SRS0=ky3J=X4=klop.ws=ronald-lists@realworks.nl]; R_DKIM_ALLOW(-0.20)[klop.ws:s=rw2]; R_SPF_ALLOW(-0.20)[+ip4:194.109.157.0/24]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; MLMMJ_DEST(0.00)[stable@freebsd.org]; RCVD_COUNT_ZERO(0.00)[0]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:3265, ipnet:194.109.0.0/16, country:NL]; ARC_NA(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; FROM_NEQ_ENVFROM(0.00)[ronald-lists@klop.ws,SRS0=ky3J=X4=klop.ws=ronald-lists@realworks.nl]; FROM_HAS_DN(0.00)[]; HAS_X_PRIO_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; DKIM_TRACE(0.00)[klop.ws:+]; TO_MATCH_ENVRCPT_SOME(0.00)[]; SUBJECT_HAS_QUESTION(0.00)[] X-ThisMailContainsUnwantedMimeParts: N ------=_Part_11750_900121351.1658568824944 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable My choice would be to test the memory and try 13. BTW: What checksum algorithm are you using? Something standard or a more ob= scure one? Regards, Ronald. Van: Juraj Lutter Datum: 13 juli 2022 10:08 Aan: stable@freebsd.org Onderwerp: panic in zfs(?) on stable/12 >=20 >=20 > Hi. >=20 > every now and then I=E2=80=99m getting: >=20 > panic: vm_fault: fault on nofault entry, addr: 0xfffffe01d9620000 > cpuid =3D 5 > time =3D 1657698436 > KDB: stack backtrace: > #0 0xffffffff80c2e775 at kdb_backtrace+0x65 > #1 0xffffffff80be4ba8 at vpanic+0x178 > #2 0xffffffff80be4a23 at panic+0x43 > #3 0xffffffff80f63b1b at vm_fault+0x20fb > #4 0xffffffff80f61920 at vm_fault_trap+0x60 > #5 0xffffffff81100270 at trap_pfault+0x1e0 > #6 0xffffffff810d7c28 at calltrap+0x8 > #7 0xffffffff824bf80d at abd_iterate_func+0x12d > #8 0xffffffff8257ced6 at zio_checksum_generate+0x66 > #9 0xffffffff8257b26d at zio_execute+0xad > #10 0xffffffff80c412b4 at taskqueue_run_locked+0x144 > #11 0xffffffff80c426a2 at taskqueue_thread_loop+0xd2 > #12 0xffffffff80ba592e at fork_exit+0x7e > #13 0xffffffff810d8c5e at fork_trampoline+0xe > Uptime: 3d11h13m45s >=20 >=20 > Machine is stable/12 (very recent, built from clean sources), zpool upgra= ded to version 28. >=20 > I=E2=80=99m now on a crossroad: Is it better to thoroughly test the memor= y, upgrade to stable/13, switch to out-of-tree OpenZFS or diagnose the ZFS = further? >=20 > Thanks! > otis >=20 > =E2=80=94 > Juraj Lutter > otis@FreeBSD.org >=20 >=20 >=20 >=20 >=20 >=20 ------=_Part_11750_900121351.1658568824944 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable My choice would be to test the memory and try 13.<= div>BTW: What checksum algorithm are you using? Something standard or a mor= e obscure one?

Regards,
Ronald.
<= div>

Van: Juraj Lutter <juraj@lutter.sk&= gt;
Datum: 13 juli 2022 10:08
Aan: stable@freebsd.org
Onderwerp: panic in zfs(?) on = stable/12

Hi.

every now and then I=E2=80=99m getting:

panic: vm_fault: fault on nofault entry, addr: 0xfffffe01d9620000
cpuid =3D 5
time =3D 1657698436
KDB: stack backtrace:
#0 0xffffffff80c2e775 at kdb_backtrace+0x65
#1 0xffffffff80be4ba8 at vpanic+0x178
#2 0xffffffff80be4a23 at panic+0x43
#3 0xffffffff80f63b1b at vm_fault+0x20fb
#4 0xffffffff80f61920 at vm_fault_trap+0x60
#5 0xffffffff81100270 at trap_pfault+0x1e0
#6 0xffffffff810d7c28 at calltrap+0x8
#7 0xffffffff824bf80d at abd_iterate_func+0x12d
#8 0xffffffff8257ced6 at zio_checksum_generate+0x66
#9 0xffffffff8257b26d at zio_execute+0xad
#10 0xffffffff80c412b4 at taskqueue_run_locked+0x144
#11 0xffffffff80c426a2 at taskqueue_thread_loop+0xd2
#12 0xffffffff80ba592e at fork_exit+0x7e
#13 0xffffffff810d8c5e at fork_trampoline+0xe
Uptime: 3d11h13m45s


Machine is stable/12 (very recent, built from clean sources), zpool upgrade= d to version 28.

I=E2=80=99m now on a crossroad: Is it better to thoroughly test the memory,= upgrade to stable/13, switch to out-of-tree OpenZFS or diagnose the ZFS fu= rther?

Thanks!
otis

=E2=80=94
Juraj Lutter
otis@FreeBSD.org





------=_Part_11750_900121351.1658568824944--