Re: Panic on kern_event.c

2018-11-21 Thread Mark Johnston
On Tue, Nov 20, 2018 at 11:55:54AM +0100, Sylvain GALLIANO wrote: > No issue using patched kernel on 2 servers (under stress test since +2 > hours), Thanks ! Thanks for your help. This is fixed in head now, and I'll try and get the change into 12.0. ___

Re: Panic on kern_event.c

2018-11-20 Thread Sylvain GALLIANO
No issue using patched kernel on 2 servers (under stress test since +2 hours), Thanks ! Le mar. 20 nov. 2018 à 07:45, Mark Johnston a écrit : > On Mon, Nov 19, 2018 at 10:26:51AM +0100, Sylvain GALLIANO wrote: > > With this latest patch, after stressing syslog-ng few minutes, it do not > > log

Re: Panic on kern_event.c

2018-11-19 Thread Mark Johnston
On Mon, Nov 19, 2018 at 10:26:51AM +0100, Sylvain GALLIANO wrote: > With this latest patch, after stressing syslog-ng few minutes, it do not > log anymore and a simple kill do not work (I have to do kill -9) Thanks for your patience. I finally managed to reproduce the problem and can see the bug

Re: Panic on kern_event.c

2018-11-19 Thread Sylvain GALLIANO
With this latest patch, after stressing syslog-ng few minutes, it do not log anymore and a simple kill do not work (I have to do kill -9) Le dim. 18 nov. 2018 à 01:35, Mark Johnston a écrit : > On Fri, Nov 16, 2018 at 05:56:54PM +0100, Sylvain GALLIANO wrote: > > Le ven. 16 nov. 2018 à 16:42, Ma

Re: Panic on kern_event.c

2018-11-17 Thread Mark Johnston
On Fri, Nov 16, 2018 at 05:56:54PM +0100, Sylvain GALLIANO wrote: > Le ven. 16 nov. 2018 à 16:42, Mark Johnston a écrit : > > > On Fri, Nov 16, 2018 at 03:47:39PM +0100, Sylvain GALLIANO wrote: > > > Le jeu. 15 nov. 2018 à 23:10, Mark Johnston a écrit > > : > > > > > > > On Thu, Nov 08, 2018 at

Re: Panic on kern_event.c

2018-11-16 Thread Sylvain GALLIANO
Le ven. 16 nov. 2018 à 16:42, Mark Johnston a écrit : > On Fri, Nov 16, 2018 at 03:47:39PM +0100, Sylvain GALLIANO wrote: > > Le jeu. 15 nov. 2018 à 23:10, Mark Johnston a écrit > : > > > > > On Thu, Nov 08, 2018 at 05:05:03PM +0100, Sylvain GALLIANO wrote: > > > > Hi, > > > > > > > > I replaced

Re: Panic on kern_event.c

2018-11-16 Thread Mark Johnston
On Fri, Nov 16, 2018 at 03:47:39PM +0100, Sylvain GALLIANO wrote: > Le jeu. 15 nov. 2018 à 23:10, Mark Johnston a écrit : > > > On Thu, Nov 08, 2018 at 05:05:03PM +0100, Sylvain GALLIANO wrote: > > > Hi, > > > > > > I replaced > > > << printf("XXX knote %p already in tailq status:%x kq_count:%d

Re: Panic on kern_event.c

2018-11-16 Thread Sylvain GALLIANO
Le jeu. 15 nov. 2018 à 23:10, Mark Johnston a écrit : > On Thu, Nov 08, 2018 at 05:05:03PM +0100, Sylvain GALLIANO wrote: > > Hi, > > > > I replaced > > << printf("XXX knote %p already in tailq status:%x kq_count:%d [%p %p] > > > %u\n",kn,kn->kn_status,kq->kq_count,kn->kn_tqe.tqe_next,kn->kn_tq

Re: Panic on kern_event.c

2018-11-15 Thread Mark Johnston
On Thu, Nov 08, 2018 at 05:05:03PM +0100, Sylvain GALLIANO wrote: > Hi, > > I replaced > << printf("XXX knote %p already in tailq status:%x kq_count:%d [%p %p] > %u\n",kn,kn->kn_status,kq->kq_count,kn->kn_tqe.tqe_next,kn->kn_tqe.tqe_prev,__LINE__); > by > >> panic("XXX knote %p already in tailq

Re: Panic on kern_event.c

2018-11-08 Thread Sylvain GALLIANO
Hi, I replaced << printf("XXX knote %p already in tailq status:%x kq_count:%d [%p %p] %u\n",kn,kn->kn_status,kq->kq_count,kn->kn_tqe.tqe_next,kn->kn_tqe.tqe_prev,__LINE__); by >> panic("XXX knote %p already in tailq status:%x kq_count:%d [%p %p] %u\n",kn,kn->kn_status,kq->kq_count,kn->kn_tqe.t

Re: Panic on kern_event.c

2018-11-06 Thread Mark Johnston
On Tue, Nov 06, 2018 at 10:50:06AM +0100, Sylvain GALLIANO wrote: > Hi, > > I got random panic on Current & 11.2-STABLE on kern_event.c > > Panic occur in syslog-ng (logging at high rate) with the folloging lines: > > Panic String: Bad tailq NEXT(0xf80039ae7a38->tqh_last) != NULL > Panic

Panic on kern_event.c

2018-11-06 Thread Sylvain GALLIANO
Hi, I got random panic on Current & 11.2-STABLE on kern_event.c Panic occur in syslog-ng (logging at high rate) with the folloging lines: Panic String: Bad tailq NEXT(0xf80039ae7a38->tqh_last) != NULL Panic String: Bad tailq head 0xf80039f1a238 first->prev != head It's look like kno