[SOLVED] [#2] panics collections on FreeBSD 11.0-RC1 RC2 PRERELEASE RELEASE STABLE

[Ivan Klymenko]

On Fri, 27 Jan 2017 00:33:10 +0200
Ivan Klymenko <fidaj at ukr.net> wrote:

> On Wed, 28 Dec 2016 09:57:29 -0800
> hiren panchasara <hiren at strugglingcoder.info> wrote:
> 
> > On 12/28/16 at 07:53P, Ivan Klymenko wrote:  
> > > On Wed, 28 Dec 2016 09:41:42 -0800
> > > hiren panchasara <hiren at strugglingcoder.info> wrote:
> > >     
> > > > Can you open a bug report at https://bugs.freebsd.org/bugzilla/
> > > > with necessary details? Looks like virtualbox is involved
> > > > here?    
> > > 
> > > I can not, because that does not make sense.
> > > PR are not considered for months and years.
> > > It was the last hope for the mail lists.
> > > Probably i must to change the operating system.    
> > 
> > Apologies for that. As you know people get busy in such opensource
> > projects.
> > 
> > The panic appears in tcp land so if you provide enough information,
> > I'll try to look at it. Again, I cannot promise anything more than
> > an honest attempt.
> > 
> > Cheers,
> > Hiren  
> 
> The reason most panics served as tuning Netisr:
> net.isr.numthreads=4
> net.isr.maxthreads=4
> net.isr.bindthreads=1
> 
> Apparently, this subsystem at some moment  had been broken.
> 
> Best regards,

The next problem of panic was associated with
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=148807

Feb  3 10:22:37 ns kernel: panic: sbsndptr: sockbuf 0xfffff802077c5bd8 and mbuf 0xfffff80019f26d00 clashing
Feb  3 10:22:37 ns kernel: cpuid = 4                                                                       
Feb  3 10:22:37 ns kernel: KDB: stack backtrace:                                                           
Feb  3 10:22:37 ns kernel: #0 0xffffffff80b3ebb7 at kdb_backtrace+0x67                                     
Feb  3 10:22:37 ns kernel: #1 0xffffffff80af39b6 at vpanic+0x186                                           
Feb  3 10:22:37 ns kernel: #2 0xffffffff80af3823 at panic+0x43                                             
Feb  3 10:22:37 ns kernel: #3 0xffffffff80b8e3da at sbsndptr+0xda                                          
Feb  3 10:22:37 ns kernel: #4 0xffffffff80d34119 at tcp_output+0x1129                                      
Feb  3 10:22:37 ns kernel: #5 0xffffffff80d301ee at tcp_do_segment+0x288e                                  
Feb  3 10:22:37 ns kernel: #6 0xffffffff80d2d1f2 at tcp_input+0x14d2                                       
Feb  3 10:22:37 ns kernel: #7 0xffffffff80c94372 at ip_input+0x192                                         
Feb  3 10:22:37 ns kernel: #8 0xffffffff80c2a4fd at netisr_dispatch_src+0xad                               
Feb  3 10:22:37 ns kernel: #9 0xffffffff80c124f9 at ether_demux+0x149                                      
Feb  3 10:22:37 ns kernel: #10 0xffffffff82b6971c at vboxNetFltFreeBSDinput+0x27c                          
Feb  3 10:22:37 ns kernel: #11 0xffffffff80b5204a at taskqueue_run_locked+0x14a                            
Feb  3 10:22:37 ns kernel: #12 0xffffffff80b51e3f at taskqueue_run+0xbf                                    
Feb  3 10:22:37 ns kernel: #13 0xffffffff80aad33f at intr_event_execute_handlers+0x20f                     
Feb  3 10:22:37 ns kernel: #14 0xffffffff80aad5a6 at ithread_loop+0xc6                                     
Feb  3 10:22:37 ns kernel: #15 0xffffffff80aa9de5 at fork_exit+0x85                                        
Feb  3 10:22:37 ns kernel: #16 0xffffffff8101022e at fork_trampoline+0xe                                   
Feb  3 10:22:37 ns kernel: Uptime: 21h36m52s                                                               
Feb  3 10:22:37 ns kernel: Dumping 7804 out of 32688 MB:..1%..11%..21%..31%..41%..51%..61%..71%..81%..91%


I have added an option hw.igb.num_queues=1 to /boot/loader.conf and the
server is running without panic over a few weeks is stable.

Panic my servers have multiple causes.

Best regards,