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

From: O. Hartmann <ohartmann_at_walstatt.org>
Date: Sun, 13 Nov 2016 10:23:52 +0100
Am Wed, 9 Nov 2016 17:11:37 +0300
"Andrey V. Elsukov" <ae_at_FreeBSD.org> schrieb:

> On 08.11.2016 21:28, Mark Johnston wrote:
> > On Sun, Nov 06, 2016 at 11:13:56AM +0100, 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 ??

> 
> >> #9  0xffffffff807b44fb in __rw_wlock_hard (c=<value optimized out>, 
> >>     tid=<value optimized out>, file=<value optimized out>, 
> >>     line=<value optimized out>) at /usr/src/sys/kern/kern_rwlock.c:830  
> 
> Just my opinion. Setting RT_LLE_CACHE flag in ip_output is wrong. This
> flag should be set when ro_lle actually filled with cached data.
> 



-- 
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 - 08:24:09 UTC

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