threads/103127: Kernel panic while using thread features in
Squid 2.6
John-Mark Gurney
gurney_j at resnet.uoregon.edu
Mon Sep 18 09:30:35 PDT 2006
The following reply was made to PR kern/103127; it has been noted by GNATS.
From: John-Mark Gurney <gurney_j at resnet.uoregon.edu>
To: Anders Nordby <anders at fupp.net>
Cc: FreeBSD-gnats-submit at FreeBSD.org, freebsd-threads at FreeBSD.org,
Thomas-Martin Seck <tmseck at netcologne.de>,
Suleiman Souhlal <ssouhlal at FreeBSD.org>, jhb at 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."
More information about the freebsd-threads
mailing list