Date: Wed, 31 Aug 2022 21:23:28 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 266145] [Intel Alder Lake] Crashes on CURRENT vfs/softupdate Message-ID: <bug-266145-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D266145 Bug ID: 266145 Summary: [Intel Alder Lake] Crashes on CURRENT vfs/softupdate Product: Base System Version: CURRENT Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: rkoberman@gmail.com Created attachment 236272 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D236272&action= =3Dedit core.text from crash I have had multiple crashes on a new Alder Lake system (Lenovo T16 (Intel)). The backtraces on all showed vfs and a couple also included softupdate. Softupdate is further implicated by the fact that "fsck -l /" consistently reported "SOFTUPDATE INCONSISTENCY" and required a full fsck and managed to corrupt the pkg database at least three times. In all cases, I was building ports on the system. Due to this being a fresh install, I was unable to get a dump, but I finally got one this morning. I disabled softupdate and have yet to have a crash; y= et another indication that softupdate is the trigger. Possibly a race caused by the different speeds and thread counts of the different cores. FreeBSD 14.0-CURRENT #0 main-n257619-c1a0ab5ec52: Fri Aug 26 09:37:24 UTC 2= 022 I will attach the core.text file to this report. --=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>