Date: Mon, 18 Sep 2006 08:40:25 GMT From: Anders Nordby <anders@fupp.net> To: freebsd-threads@FreeBSD.org Subject: Re: threads/103127: Kernel panic while using thread features in Squid 2.6 Message-ID: <200609180840.k8I8ePue027109@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/103127; it has been noted by GNATS.
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>
Cc: jhb@FreeBSD.org
Subject: Re: threads/103127: Kernel panic while using thread features in Squid 2.6
Date: Mon, 18 Sep 2006 10:33:43 +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".
Cheers,
--
Anders.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200609180840.k8I8ePue027109>