From owner-freebsd-threads@FreeBSD.ORG  Mon Sep 18 08:33:49 2006
Return-Path: <owner-freebsd-threads@FreeBSD.ORG>
X-Original-To: freebsd-threads@FreeBSD.org
Delivered-To: freebsd-threads@FreeBSD.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 5687516A416;
	Mon, 18 Sep 2006 08:33:49 +0000 (UTC) (envelope-from anders@fupp.net)
Received: from fupp.net (totem.fix.no [80.91.36.20])
	by mx1.FreeBSD.org (Postfix) with ESMTP id A7B9443D64;
	Mon, 18 Sep 2006 08:33:45 +0000 (GMT) (envelope-from anders@fupp.net)
Received: from localhost (totem.fix.no [80.91.36.20])
	by fupp.net (Postfix) with ESMTP id B45FF8D98A3;
	Mon, 18 Sep 2006 10:33:43 +0200 (CEST)
Received: from fupp.net ([80.91.36.20])
	by localhost (totem.fix.no [80.91.36.20]) (amavisd-new,
	port 10024) with LMTP
	id 39230-01-6; Mon, 18 Sep 2006 10:33:43 +0200 (CEST)
Received: by fupp.net (Postfix, from userid 1000)
	id 564A78D989D; Mon, 18 Sep 2006 10:33:43 +0200 (CEST)
Date: Mon, 18 Sep 2006 10:33:43 +0200
From: Anders Nordby <anders@fupp.net>
To: FreeBSD-gnats-submit@FreeBSD.org, freebsd-threads@FreeBSD.org,
	Thomas-Martin Seck <tmseck@netcologne.de>,
	Suleiman Souhlal <ssouhlal@FreeBSD.org>,
	John-Mark Gurney <gurney_j@resnet.uoregon.edu>
Message-ID: <20060918083343.GA38761@totem.fix.no>
References: <20060911075431.D12758D9874@fupp.net>
	<200609110800.k8B80ie3041853@freefall.freebsd.org>
	<20060912195547.GA71462@totem.fix.no>
	<20060913185803.GA27955@totem.fix.no>
	<20060916205044.GF9421@funkthat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20060916205044.GF9421@funkthat.com>
X-PGP-Key: http://anders.fix.no/pgp/
X-PGP-Key-FingerPrint: 1E0F C53C D8DF 6A8F EAAD  19C5 D12A BC9F 0083 5956
User-Agent: Mutt/1.5.11
Cc: jhb@FreeBSD.org
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
List-Id: Threading on FreeBSD <freebsd-threads.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>, 
	<mailto:freebsd-threads-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-threads>
List-Post: <mailto:freebsd-threads@freebsd.org>
List-Help: <mailto:freebsd-threads-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>,
	<mailto:freebsd-threads-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Sep 2006 08:33:49 -0000

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".

Cheers,

-- 
Anders.