With some additional insights I can add: - I can boot in single user on 15.0-CURRENT (Thanks Dave C. for the idea). We're definitely getting to running the rc's and it's something that breaks about the time /etc/rc.d/devmatch starts
- At present there are no module loads in /etc/rc.conf: kld_list is commented-out - It seems like the cut off is when the kernel starts working with the 'hms' subsystem (see below) I was able to get the panic output from messages -- but there's no "here's where we failed," AFAICT. Have I gotten all the useful debugging messages at this point? Thanks for help. Hopefully useful log data are below. Steven === PANIC === Apr 2 04:16:27 freebsd kernel: iichid0: <DELL073B:00 06CB:7E7E I2C HID device> at addr 0x2c irq 51 on iicbus0 Apr 2 04:16:27 freebsd kernel: hidbus0: <HID bus> on iichid0 Apr 2 04:16:27 freebsd kernel: Apr 2 04:16:27 freebsd syslogd: last message repeated 1 times Apr 2 04:16:27 freebsd kernel: Fatal trap 12: page fault while in kernel mode Apr 2 04:16:27 freebsd kernel: cpuid = 0; apic id = 00 Apr 2 04:16:27 freebsd kernel: fault virtual address = 0x0 Apr 2 04:16:27 freebsd kernel: fault code = supervisor read instruction, page not present Apr 2 04:16:27 freebsd kernel: instruction pointer = 0x20:0x0 Apr 2 04:16:27 freebsd kernel: stack pointer = 0x28:0xfffffe0068dfce38 Apr 2 04:16:27 freebsd kernel: frame pointer = 0x28:0xfffffe0068dfce60 Apr 2 04:16:27 freebsd kernel: code segment = base 0x0, limit 0xfffff, type 0x1b Apr 2 04:16:27 freebsd kernel: = DPL 0, pres 1, long 1, def32 0, gran 1 Apr 2 04:16:27 freebsd kernel: processor eflags = interrupt enabled, resume, IOPL = 0 - I'm surprised by the "blank like" repeated 1 times - This portion of the trace didn't really help me, but these call stacks seemed interesting too Interesting stack data? Apr 2 04:16:27 freebsd kernel: KDB: stack backtrace: Apr 2 04:16:27 freebsd kernel: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe0068dfcb60 Apr 2 04:16:27 freebsd kernel: vpanic() at vpanic+0x136/frame 0xfffffe0068dfcc90 Apr 2 04:16:27 freebsd kernel: panic() at panic+0x43/frame 0xfffffe0068dfccf0 Apr 2 04:16:27 freebsd kernel: trap_pfault() at trap_pfault+0x466/frame 0xfffffe0068dfcd60 Apr 2 04:16:27 freebsd kernel: calltrap() at calltrap+0x8/frame 0xfffffe0068dfcd60 Apr 2 04:16:27 freebsd kernel: --- trap 0xc, rip = 0, rsp = 0xfffffe0068dfce38, rbp = 0xfffffe0068dfce60 --- Apr 2 04:16:27 freebsd kernel: ??() at 0/frame 0xfffffe0068dfce60 Apr 2 04:16:27 freebsd kernel: ithread_loop() at ithread_loop+0x266/frame 0xfffffe0068dfcef0 Apr 2 04:16:27 freebsd kernel: fork_exit() at fork_exit+0x82/frame 0xfffffe0068dfcf30 Apr 2 04:16:27 freebsd kernel: fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe0068dfcf30 Apr 2 04:16:27 freebsd kernel: --- trap 0, rip = 0, rsp = 0x1, rbp = 0x35013fc5ea44 ---Apr 2 04:16:27 freebsd kernel: KDB: enter: panic ==== Using my old, stable kernel:=== Here's what comes next: Mar 16 21:43:21 freebsd kernel: iichid0: <DELL073B:00 06CB:7E7E I2C HID device> at addr 0x2c irq 51 on iicbus0 Mar 16 21:43:21 freebsd kernel: hidbus0: <HID bus> on iichid0 Mar 16 21:43:21 freebsd kernel: hms0: <DELL073B:00 06CB:7E7E Mouse> on hidbus0 Mar 16 21:43:21 freebsd kernel: hms0: 2 buttons and [XY] coordinates ID=2 Mar 16 21:43:21 freebsd kernel: hmt0: <DELL073B:00 06CB:7E7E TouchPad> on hidbus0 Mar 16 21:43:21 freebsd kernel: hconf0: <DELL073B:00 06CB:7E7E Configuration> on hidbus0 Mar 16 21:43:21 freebsd kernel: hmt0: Multitouch touchpad with 0 external buttons, click-pad Mar 16 21:43:21 freebsd kernel: hmt0: 5 contacts with [C] properties. Report range [0:0] - [1229:749] Mar 16 21:43:21 freebsd kernel: wlan0: link state changed to UP Mar 16 21:43:21 freebsd kernel: ugen0.3: <vendor 0x8087 product 0x0a2a> at usbus0 --- Public Key: 22BE39E2FA68D8BA8DC4B43A55A16D8CE2B036DE Messages from this account are considered the best-secured and most reliable. Send information regarding health, wealth, or requiring higher standards of security to this address. Sent with [Proton Mail](https://proton.me/mail/home) secure email. On Saturday, March 29th, 2025 at 8:46 PM, Steven Harms (High-Security Mail) <sgha...@stevengharms.com> wrote: > Hey folks, > > I tried building current from source and when I boot, I get a panic after the > final Autoloading module (pchtherm, in my case) loads. Comparing to the > stable 14.2 kernel, the next step is for "Setting up harvesting," "Feeding > entropy," and starting wpa_supplicant. > > To be clear, this commit is not the thing that broke things. > > In pursuit of getting more data, I'm trying to isolate two questions: > > - Why am I not getting any panic dump artifacts? > - Did I built current from HEAD properly? > > In effort to get more data, I'm following: > https://docs.freebsd.org/en/books/developers-handbook/kerneldebug/ > > - Confirm that /etc/rc.conf has dumpdev set to AUTO > - Both /etc/fstab and swap info confirm that /dev/ada0p3 is configured for > swap. It is also the only device. Therefore I expect dumped to write to that > device > - Yet despite the kernel panicking, there's nothing in that directory except > file "minfree" which says "2048" in it. > - I manually set dumpdir to "/var/crash" which has 750 permissions and try to > boot the new kernel; panic; boot into stable kernel and...nothing in > /var/crash except minfree > > Now, I'm still very new to building CURRENT, but I've been following: > > https://docs.freebsd.org/en/books/handbook/cutting-edge/#updating-src-quick-start > > # etcupdate extract (1) > # etcupdate diff (2) > # git pull -C /usr/src (1) > check /usr/src/UPDATING (2) > # cd /usr/src (3) > # make -j4 buildworld (4) > # make -j4 kernel (5)# shutdown -r now (6) > > And am after the shutdown -r now step: > > If my process for kernel and world build is correct, then I have found a > panic. How can I help/debug? > > Thanks! > > Steven > > --- > > Public Key: 22BE39E2FA68D8BA8DC4B43A55A16D8CE2B036DE > > Messages from this account are considered the best-secured and most reliable. > Send information regarding health, wealth, or requiring higher standards of > security to this address. > > Sent with [Proton Mail](https://proton.me/mail/home) secure email.
