Re: crash in iflib_fast_intr

On 01/18/17 03:37, peter.blok_at_bsd4all.org wrote:
> Hi,
> 
> A kernel without option EARLY_AP_STARTUP crashes in if lib_fast_intr. Since GENERIC now has EARLY_AP_STARTUP, this probably got unnoticed. Problem is reproducible.
> 
> KDB: stack backtrace:
> #0 0xffffffff805cec97 at kdb_backtrace+0x67
> #1 0xffffffff80584816 at vpanic+0x186
> #2 0xffffffff80584683 at panic+0x43
> #3 0xffffffff8090f222 at trap_fatal+0x322
> #4 0xffffffff8090f3ec at trap_pfault+0x1bc
> #5 0xffffffff8090eaa0 at trap+0x280
> #6 0xffffffff808f35e1 at calltrap+0x8
> #7 0xffffffff806a202d at iflib_fast_intr+0x3d
> #8 0xffffffff8054963b at intr_event_handle+0x9b
> #9 0xffffffff80965f38 at intr_execute_handlers+0x48
> #10 0xffffffff8096b1cf at lapic_handle_intr+0x3f
> #11 0xffffffff808f3cc7 at Xapic_isr1+0xb7
> #12 0xffffffff805b994a at sched_idletd+0x37a
> #13 0xffffffff805460f5 at fork_exit+0x85
> #14 0xffffffff808f3b1e at fork_trampoline+0xe
> 
> Peter

Thanks for the report.  We're looking at this.

This is with an igb(4) interface or em(4)?

sean