On Sun, Nov 19, 2017 at 07:31:20PM -0800, Paul B. Henson wrote: > I just updated a server to 6.2; unfortunately this box has an oddball > SOL com2 on irq10 so I need to run 'config -e' on the kernel to update > it and make the serial console work. I noticed afterwards in the boot > messages it was complaining about kernel reordering failures, and > thinking I was fixing it, I updated the file /var/db/kernel.SHA256 with > the hash of my modified kernel. I quickly discovered that resulted in a > successfully reordered kernel with a stock com2 irq :(. > > I didn't see anything in the config man page or faq about interaction > between kernel reordering and config on a binary kernel. In hindsight I > see that the hash check is to keep from replacing a locally modified > kernel. Is there a supported way to both fix hardcoded settings on a > stock kernel and use reordering? Or do you need to update your settings > in the config and compile a kernel from scratch? If you do, does > /usr/share/compile automatically get populated with your new kernel > objects and reordering just starts working, or do you need to do > something manually to get it running with a locally compiled kernel?
This is what I do in rc.shutdown to handle this case: /usr/bin/printf "disable inteldrm*\nquit\n" | /usr/sbin/config -ef /bsd /bin/sha256 -h /var/db/kernel.SHA256 /bsd
