Date: Sun, 30 Nov 2025 19:32:18 +0100 From: =?UTF-8?B?S2FybG8gTWlsacSNZXZpxIc=?= <karlo98.m@gmail.com> To: Adrian Chadd <adrian@freebsd.org> Cc: freebsd-hackers@freebsd.org Subject: Re: 15.0-RELEASE boot panic when if_iwm_load="YES" Message-ID: <CABcFG89GmxGSZF2wKJAkvZGsuowVPwjBLu7D%2BUSdYOUG2hEQwA@mail.gmail.com> In-Reply-To: <CAJ-VmokAWWesxdTZRS=H4K9xaQJA3mT98U7HsFrsw0ZiJwttew@mail.gmail.com> References: <CABcFG8-xFa0X86ai-EspQMSgPKv=pSWhvZMcyc_M2xfqrGcGcQ@mail.gmail.com> <CAJ-VmokAWWesxdTZRS=H4K9xaQJA3mT98U7HsFrsw0ZiJwttew@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Thank you for the clarification! It works now. Are a bunch of online resources are out-of-date/wrong now because of that change? I see that most tell you to first load the driver in /boot/loader.conf. I didn't check the handbook first and lost a few hours because of that. I never learn... On Sun, Nov 30, 2025 at 7:25 PM Adrian Chadd <adrian@freebsd.org> wrote: > > hi! > > The firmware loading migrated from "build all firmware as kernel > modules' to 'support loading firmware as files'. > However, that's resulted in a couple behavioural changes: > > * there's a known bug in the firmware loader where if it's invoked by > a driver before / is available, the kernel panics. > * .. and yes, since they're files now, but drivers have no way of > waiting cleanly until the filesystems are available, > things go sideways. > > Just add this to /etc/rc.conf : > > kld_list="if_iwm" > > (if you have an existnig kld_list line in there, add if_iwm to it instead) > > Then run "fwget" to fetch the latest firmware needed, and then reboot. > > > -a > > On Sat, 29 Nov 2025 at 08:01, Karlo Miličević <karlo98.m@gmail.com> wrote: > > > > I know 15.0 is not released yet but the image is up and I wanted to try it out on real hardware. > > > > After I put if_iwm_load="YES" in /boot/loader.conf it fails to boot. > > After saying it's loading loader.conf and briefly flashing FreeBSD logo I get a panic: > > > > panic: page fault > > cpuid = 0 > > time = 1 > > KDB: stack backtrace: > > #0 0xffffffff80bbe1ed at kdb_backtrace+0x5d > > #1 0xffffffff80b71576 at vpanic+0x136 > > #2 0xffffffff80b71433 at panic+0x43 > > #3 0xffffffff81079f69 at trap_pfault+0x3c9 > > #4 0xffffffff8104ff18 at calltrap+0x8 > > #5 0xffffffff80c4f974 at namei+0xe4 > > #6 0xffffffff80c768b2 at vn_open_cred+0x5b2 > > #7 0xffffffff80bb9ef4 at loadimage+0x274 > > #8 0xffffffff80bd4de2 at taskqueue_run_locked+0x182 > > #9 0xffffffff80bd5fb2 at taskqueue_thread_loop+0xc2 > > #10 0xffffffff80b2786b at fork_exit+0x7b > > #11 0xffffffff81050f3e at fork_trampoline+0xe > > Uptime: 1s > > Automatic reboot in 15 seconds - press a key on the console to abort > > > > Am I doing something wrong? > > IIRC this worked on 14.3 on the same hardware.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CABcFG89GmxGSZF2wKJAkvZGsuowVPwjBLu7D%2BUSdYOUG2hEQwA>
