Re: was: CURRENT [r308087] still crashing: Backtrace provided

From: O. Hartmann <o.hartmann_at_walstatt.org>
Date: Sun, 13 Nov 2016 20:49:27 +0100
Am Sun, 13 Nov 2016 12:41:07 +0300
"Andrey V. Elsukov" <ae_at_FreeBSD.org> schrieb:

> On 13.11.2016 12:23, O. Hartmann wrote:
> >>>>> Great, thank you. I would first like to confirm that r307234 is indeed
> >>>>> causing the crash - since it appears to be easy to trigger, that should
> >>>>> be faster. If not, the core will help track down the real problem.    
> >>>>
> >>>> Although I was under the impression the in-kernel-config option
> >>>>
> >>>> makeoptions    DEBUG=-g
> >>>>
> >>>> would make debugging symbols available, I'm proved wrong.    
> >>
> >> Do you have option FLOWTABLE in your kernel config?  
> > 
> > Would you suggest to disable this feature in the kernel? Or does the feature, by
> > accident, influence the debugging ??  
> 
> Hi,
> 
> I never used FLOWTABLE, but as I know, when L2 caching was reintroduced
> the kernel with enabled FLOWTABLE has started crashing almost
> immediately. glebius_at_ added workaround in r300854 to prevent the panic.
> Then we discussed with him that the change in in_pcb.c should be
> reasonable. And he decided to revert the workaround. Now it seems
> without r300854 FLOWTABLE isn't usable.
> 

... it seems that FLOWTABLE is the culprit.

Running CURRENT 308616 for hours now ...

-- 
O. Hartmann

Ich widerspreche der Nutzung oder Übermittlung meiner Daten für
Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG).

Received on Sun Nov 13 2016 - 18:54:50 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:08 UTC