Date: Sat, 23 Jul 2022 11:33:44 +0200 (CEST) From: Ronald Klop <ronald-lists@klop.ws> To: Juraj Lutter <juraj@lutter.sk>, stable@freebsd.org Subject: Re: panic in zfs(?) on stable/12 Message-ID: <1854386355.11751.1658568824946@localhost> In-Reply-To: <0A76E2FF-1423-48D9-A32B-9784BF3DCBDD@lutter.sk>
next in thread | previous in thread | raw e-mail | index | archive | help
------=_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 <juraj@lutter.sk> 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 <html><head></head><body>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?</div><div><br /></div><div>Regards,</div><div>Ronald.</div><= div><br /><p><small><strong>Van:</strong> Juraj Lutter <juraj@lutter.sk&= gt;<br /><strong>Datum:</strong> 13 juli 2022 10:08<br /><strong>Aan:</stro= ng> stable@freebsd.org<br /><strong>Onderwerp:</strong> panic in zfs(?) on = stable/12<br /></small></p><blockquote style=3D"margin-left: 5px; border-le= ft: 3px solid #ccc; margin-right: 0px; padding-left: 5px;"><div class=3D"Me= ssageRFC822Viewer do_not_remove" id=3D"P"><!-- P --> <!-- processMimeMessage --><div class=3D"TextPlainViewer do_not_remove" id= =3D"P.P"><!-- P.P -->Hi.<br /> <br /> every now and then I=E2=80=99m getting:<br /> <br /> panic: vm_fault: fault on nofault entry, addr: 0xfffffe01d9620000<br /> cpuid =3D 5<br /> time =3D 1657698436<br /> KDB: stack backtrace:<br /> #0 0xffffffff80c2e775 at kdb_backtrace+0x65<br /> #1 0xffffffff80be4ba8 at vpanic+0x178<br /> #2 0xffffffff80be4a23 at panic+0x43<br /> #3 0xffffffff80f63b1b at vm_fault+0x20fb<br /> #4 0xffffffff80f61920 at vm_fault_trap+0x60<br /> #5 0xffffffff81100270 at trap_pfault+0x1e0<br /> #6 0xffffffff810d7c28 at calltrap+0x8<br /> #7 0xffffffff824bf80d at abd_iterate_func+0x12d<br /> #8 0xffffffff8257ced6 at zio_checksum_generate+0x66<br /> #9 0xffffffff8257b26d at zio_execute+0xad<br /> #10 0xffffffff80c412b4 at taskqueue_run_locked+0x144<br /> #11 0xffffffff80c426a2 at taskqueue_thread_loop+0xd2<br /> #12 0xffffffff80ba592e at fork_exit+0x7e<br /> #13 0xffffffff810d8c5e at fork_trampoline+0xe<br /> Uptime: 3d11h13m45s<br /> <br /> <br /> Machine is stable/12 (very recent, built from clean sources), zpool upgrade= d to version 28.<br /> <br /> 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?<br /> <br /> Thanks!<br /> otis<br /> <br /> =E2=80=94<br /> Juraj Lutter<br /> otis@FreeBSD.org<br /> <br /> <br /> </div><!-- TextPlainViewer --> <hr /> </div><!-- MessageRFC822Viewer --> </blockquote><br /><br /><br /></div></body></html> ------=_Part_11750_900121351.1658568824944--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1854386355.11751.1658568824946>