Date: Sat, 13 Apr 2024 18:20:27 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 278348] Sudden kernel panic Fatal double fault Message-ID: <bug-278348-227-czS7HsYz1M@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-278348-227@https.bugs.freebsd.org/bugzilla/> References: <bug-278348-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D278348 --- Comment #9 from mikhail.rokhin@gmail.com --- (In reply to Mark Johnston from comment #8) Thank you for reply. It is not reproduceable fast and I don't have enough time for thorough continuous heavy, overloading testing (like compiling world).=20 But on FBSD side, using fast servers, it is possible to run such burning, automated extended stress-test of example before release, including VMM just RAM and RAM + Swap configuration, paying precise attention to large scale testing like 128GB of RAM & 256GB of Swap, and 64 threads (-j 64) for 32 threads CPU, which easily could be achieved by compiling LLVM source code (= and simultaneously in multiple jails), for e.g. I'll be waiting for new kernel commits in up-coming weeks. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-278348-227-czS7HsYz1M>