Re: crash in iflib_fast_intr

2017-01-19 Thread Shawn Webb
On Wed, Jan 18, 2017 at 02:45:34PM -0500, Shawn Webb wrote: > On Wed, Jan 18, 2017 at 07:31:12AM -0700, Sean Bruno wrote: > > > > > > On 01/18/17 03:37, peter.b...@bsd4all.org wrote: > > > Hi, > > > > > > A kernel without option EARLY_AP_STARTUP crashes in if lib_fast_intr. > > > Since GENERIC

Re: crash in iflib_fast_intr

2017-01-18 Thread Shawn Webb
On Wed, Jan 18, 2017 at 07:31:12AM -0700, Sean Bruno wrote: > > > On 01/18/17 03:37, peter.b...@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 > >

Re: crash in iflib_fast_intr

2017-01-18 Thread peter . blok
This is with an igb interface. Peter > On 18 Jan 2017, at 15:31, Sean Bruno wrote: > > > > On 01/18/17 03:37, peter.b...@bsd4all.org > wrote: >> Hi, >> >> A kernel without option EARLY_AP_STARTUP crashes in if lib_fast_intr. Since >>

Re: crash in iflib_fast_intr

2017-01-18 Thread Sean Bruno
On 01/18/17 03:37, peter.b...@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 0x805cec97 at