From owner-freebsd-threads@FreeBSD.ORG Sat Sep 16 21:00:46 2006 Return-Path: X-Original-To: freebsd-threads@hub.freebsd.org Delivered-To: freebsd-threads@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B777216A492 for ; Sat, 16 Sep 2006 21:00:46 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 80A9743D55 for ; Sat, 16 Sep 2006 21:00:46 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k8GL0kU4032100 for ; Sat, 16 Sep 2006 21:00:46 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k8GL0kGi032099; Sat, 16 Sep 2006 21:00:46 GMT (envelope-from gnats) Date: Sat, 16 Sep 2006 21:00:46 GMT Message-Id: <200609162100.k8GL0kGi032099@freefall.freebsd.org> To: freebsd-threads@FreeBSD.org From: John-Mark Gurney Cc: Subject: Re: threads/103127: Kernel panic while using thread features in Squid 2.6 X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John-Mark Gurney List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Sep 2006 21:00:46 -0000 The following reply was made to PR kern/103127; it has been noted by GNATS. From: John-Mark Gurney To: Anders Nordby Cc: FreeBSD-gnats-submit@FreeBSD.org, freebsd-threads@FreeBSD.org, Thomas-Martin Seck , Suleiman Souhlal Subject: Re: threads/103127: Kernel panic while using thread features in Squid 2.6 Date: Sat, 16 Sep 2006 13:50:44 -0700 Anders Nordby wrote this message on Wed, Sep 13, 2006 at 20:58 +0200: > After talking with Pawel, I tried the attached patch to get some kqueue > debug info. I just got it: > > Sep 13 20:18:56 cache3 kernel: NULL f_event in new kn > Sep 13 20:18:56 cache3 kernel: f_event == NULL This means that the f_attach method for that event isn't setting f_event properly... We need to figure out which event this is happening w/... Try the following modifications: > --- sys/kern/kern_event.c.orig Wed Sep 13 08:44:57 2006 > +++ sys/kern/kern_event.c Wed Sep 13 08:51:03 2006 > @@ -900,6 +900,8 @@ > goto done; > } > KN_LIST_LOCK(kn); > + if (kn->kn_fop->f_event == NULL) { > + printf("NULL f_event in new kn\n"); printf("kn: ident: %d, filter: %d\n", kn->kn_ident, kn->kn_filter); } > } else { > /* > * The user may change some filter values after the I have a feeling that this is a similar panic that jhb is seeing... Which means that filter will be EVFILT_VNODE (-4)... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not."