Date: Mon, 1 Nov 2004 19:37:16 +0000 (GMT) From: Robert Watson <rwatson@freebsd.org> To: Arjan de Vet <devet@devet.org> Cc: current@freebsd.org Subject: Re: if_sk patch to get more info from people with problems Message-ID: <Pine.NEB.3.96L.1041101193549.87725D-100000@fledge.watson.org> In-Reply-To: <20041101164723.GA7375@adv.devet.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 1 Nov 2004, Arjan de Vet wrote: > In article <1099326109.23508.133.camel@leguin> you write: > > >On Mon, 2004-11-01 at 05:54, User Valera wrote: > > [...] > > >debug.mpsafenet=0 has been my cure here as well for basically the same > >symptoms. I'll apply this patch and get info on what hardware I have > >soon. > > I filed a bug report for if_sk.c for possibly related symptoms: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern%2F73038 The > IFF_NEEDSGIANT flag seems to solve the problem but I need to do much > more testing with it this week (had to go back to 5.2.1 because 5.3 > hangs for me after 1-1.5 days; still need to debug that one as well :(). Note that it could well be a locking bug in if_sk, but that debug.mpsafenet and IFF_NEEDSGIANT both substantially change the timing in the driver, so these changes could just mask an existing bug in your configuration (yet still leave it present in other's). The if_de bug recently, btw, turned out to be an existing (real) bug that was unmasked due to timing changes from running with IFF_NEEDSGIANT, but was in fact (we believe) present even with Giant over the stack... Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96L.1041101193549.87725D-100000>