"options MAXMEMDOM=2" vs. amd64 DBG kernel booting: 3000+ "kernel: Process (pid 1) got signal 5" notices during booting
Date: Wed, 22 Nov 2023 05:43:50 UTC
While my kernel/world build procedures build both DBG and NODBG kernels and worlds, I normally run the NODBG kernel and world, using DBG only when I need to for problem investigation. I recently had reason to use the DBG kernel and found it got the oddity of 3000+ instances of "kernel: Process (pid 1) got signal 5" during booting, as reported in /var/log/messages . An example is: . . . Nov 20 23:13:09 7950X3D-UFS shutdown[20174]: reboot by root: Nov 20 23:13:09 7950X3D-UFS syslogd: exiting on signal 15 Nov 20 23:14:21 7950X3D-UFS syslogd: kernel boot file is /boot/kernel/kernel Nov 20 23:14:21 7950X3D-UFS kernel: got signal 5 Nov 20 23:14:21 7950X3D-UFS kernel: Process (pid 1) got signal 5 Nov 20 23:14:21 7950X3D-UFS syslogd: last message repeated 3133 times Nov 20 23:14:21 7950X3D-UFS kernel: intsmb0: <AMD FCH SMBus Controller> at device 20.0 on pci0 . . . This stopped when I commented out the: options MAXMEMDOM=2 that I've had historically and built, installed, and booted the resulting DBG kernel. I'll note that I never had the messages for the NODDBG kernel, despite it also having that line. For reference: # uname -apKU FreeBSD 7950X3D-UFS 15.0-CURRENT FreeBSD 15.0-CURRENT #2 main-n266130-d521abdff236-dirty: Tue Nov 21 21:03:11 PST 2023 root@7950X3D-UFS:/usr/obj/BUILDs/main-amd64-dbg-clang/usr/main-src/amd64.amd64/sys/GENERIC-DBG amd64 amd64 1500002 1500002 # ~/fbsd-based-on-what-commit.sh -C /usr/main-src/ d521abdff236 (HEAD -> main, freebsd/main, freebsd/HEAD) Update ASLR stack sysctl description in security.7 and mitigations.7 Author: Ed Maste <emaste@FreeBSD.org> Commit: Ed Maste <emaste@FreeBSD.org> CommitDate: 2023-10-24 22:29:25 +0000 branch: main merge-base: d521abdff2367a5c72a773a815fc3d99403274f5 merge-base: CommitDate: 2023-10-24 22:29:25 +0000 n266130 (--first-parent --count for merge-base) === Mark Millard marklmi at yahoo.com