Re: BOOT CRASH -- Current -CURRENT
- Reply: Warner Losh : "Re: BOOT CRASH -- Current -CURRENT"
- In reply to: Warner Losh : "Re: BOOT CRASH -- Current -CURRENT"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Sun, 02 Oct 2022 03:06:12 UTC
On 10/01/2022 10:04 pm, Warner Losh wrote: > Do you have a /boot tarball that can be loaded in a VM that recreates > the problem (along with a clean hash)? > > But before you try that, have you tried a completely clean rebuild of > the kernel to preclude the possibility that something is somehow cross > threaded? > > Warner > > On Sat, Oct 1, 2022 at 8:39 PM Larry Rosenman <ler@freebsd.org> wrote: > >> ❯ more info.11 >> Dump header from device: /dev/mfid0p3 >> Architecture: amd64 >> Architecture Version: 2 >> Dump Length: 126748815 >> Blocksize: 512 >> Compression: zstd >> Dumptime: 2022-10-01 21:26:40 -0500 >> Hostname: >> Magic: FreeBSD Kernel Dump >> Version String: FreeBSD 14.0-CURRENT #168 >> ler/freebsd-main-changes-n258354-6cdd871ebc4: Sat Oct 1 21:13:01 CDT >> 2022 >> root@borg.lerctr.org:/usr/obj/usr/src/amd64.amd64/sys/LER-MINIMAL >> Panic String: page fault >> Dump Parity: 501115454 >> Bounds: 11 >> Dump Status: good >> >> I do have source and debug stuff, BUT kgdb croaks on me. >> >> I *CAN* give access to the machine. >> >> the console backtrace showed something about the kld load of >> dependencies. >> >> -- >> Larry Rosenman http://people.freebsd.org/~ler >> Phone: +1 214-642-9640 E-Mail: ler@FreeBSD.org >> US Mail: 5708 Sabbia Dr, Round Rock, TX 78665-2106 let me wipe /usr/obj, and rebuild everything (I *DO* use meta-mode). -- Larry Rosenman http://people.freebsd.org/~ler Phone: +1 214-642-9640 E-Mail: ler@FreeBSD.org US Mail: 5708 Sabbia Dr, Round Rock, TX 78665-2106