From owner-freebsd-threads@FreeBSD.ORG Mon Sep 18 16:30:35 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 2793716A521 for ; Mon, 18 Sep 2006 16:30:35 +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 9DDFD43D78 for ; Mon, 18 Sep 2006 16:30:32 +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 k8IGUWoR075310 for ; Mon, 18 Sep 2006 16:30:32 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k8IGUWNF075309; Mon, 18 Sep 2006 16:30:32 GMT (envelope-from gnats) Date: Mon, 18 Sep 2006 16:30:32 GMT Message-Id: <200609181630.k8IGUWNF075309@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: Mon, 18 Sep 2006 16:30:35 -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 , jhb@FreeBSD.org Subject: Re: threads/103127: Kernel panic while using thread features in Squid 2.6 Date: Mon, 18 Sep 2006 09:27:36 -0700 Anders Nordby wrote this message on Mon, Sep 18, 2006 at 10:33 +0200: > Hi, > > On Sat, Sep 16, 2006 at 01:50:44PM -0700, John-Mark Gurney wrote: > >> 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: > >> (..) > > > + if (kn->kn_fop->f_event == NULL) > > { ^^^ > > > + printf("NULL f_event in new kn\n"); > > This modification was already done with the patch from Pawel, check the > audit-trail of this PR. By using that patch, I got the messages "NULL > f_event in new kn" and "f_event == NULL". You missed my modifications to the patch... They were done in addition to his patch, and as I said in that email, they should fix the problem, it's not an information gathering exercise... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not."