Date: Mon, 05 Sep 2022 05:55:24 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 266145] [Intel Alder Lake] Crashes on CURRENT vfs Message-ID: <bug-266145-227-WJEHJrCVoX@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-266145-227@https.bugs.freebsd.org/bugzilla/> References: <bug-266145-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=3D266145 --- Comment #4 from rkoberman@gmail.com --- (In reply to Amar Takhar from comment #3) I'm reasonably sure that it is not that it has a problem with the file syst= em. It's likely a race of some sort caused by the different performance of the cores. When a process moves between different sped cores, it looks like thi= ngs go wonky, probably in the vfs or maybe the UFS code. I now have about 7 dumps, though only one since disabling soft updates that look tie to vfs. I can make the cores available as they are all from a system being prepped = for use with no sensitive data files. --=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-266145-227-WJEHJrCVoX>