Date: Fri, 2 Sep 2022 06:17:43 +0000 From: Amar Takhar <verm@darkbeer.org> To: questions@freebsd.org Subject: Re: Alder Lake and similar CPU support for FreeBSD Message-ID: <20220902061743.GA35332@darkbeer.org> In-Reply-To: <CAN6yY1tQH3WhLVdrAzT=hz5W4siZHmnVEb7DwXnkrZnbSbP%2B8g@mail.gmail.com> References: <CAN6yY1tePdcAR%2Bqnknz1it72-ThDgWAUzmCkS=rPx02R-U%2B9XA@mail.gmail.com> <CAN6yY1tQH3WhLVdrAzT=hz5W4siZHmnVEb7DwXnkrZnbSbP%2B8g@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I had to disable my E cores and I turned soft updates back on. I'll have to get my other drive with CURRENT setup so I can try that out to see if this is just a 13.1 issue. The problems are random but the interesting part is when it happens it's repeatable. In this case installing packages using conda caused the initial crash then an rm -rf of the env dir caused this error: g_vfs_done():gpt/data0[READ(offset=207974961480630272, length=32768)]error = 6 UFS: forcibly unmounting /dev/gpt/data0 from /mnt/devel After the 2nd crash in X is when I saw the above error from the commandline. When I booted back into multiuser I did get a savecore: panic: vm_fault_lookup: fault on nofault entry, addr: 0xfffffe0083841000 This one was new the rest were either 'ffs_blkfree_cg: freeing free block' or 'page fault'. Amar.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20220902061743.GA35332>