From owner-freebsd-current@FreeBSD.ORG Thu Dec 22 20:43:01 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0019016A41F for ; Thu, 22 Dec 2005 20:43:00 +0000 (GMT) (envelope-from andrea@acampi.hq.inet.it) Received: from acampi.hq.inet.it (out-11.hq.inet.it [194.185.62.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9F18943D53 for ; Thu, 22 Dec 2005 20:42:59 +0000 (GMT) (envelope-from andrea@acampi.hq.inet.it) Received: by acampi.hq.inet.it (Postfix, from userid 1000) id E62057C; Thu, 22 Dec 2005 21:42:57 +0100 (CET) Date: Thu, 22 Dec 2005 21:42:57 +0100 From: Andrea Campi To: Sam Leffler Message-ID: <20051222204257.GD30118@webcom.it> References: <20051221191919.GB17950@webcom.it> <43A9B5EA.8030905@errno.com> <20051221215457.GE17950@webcom.it> <43AA4415.8070300@errno.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43AA4415.8070300@errno.com> User-Agent: Mutt/1.5.11 Cc: Andrea Campi , current@freebsd.org Subject: Re: Panic and LOR on -CURRENT with ath X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Dec 2005 20:43:01 -0000 On Wed, Dec 21, 2005 at 10:13:41PM -0800, Sam Leffler wrote: > >Does this only need someone to sit down and code a solution, or is that > >a broader and not only technical issue? > > It's a design issue with implications. The net80211 ioctl code is > typically invoked from drivers w/ the driver lock held to guard against > changes in state used by code that is invoked from an interrupt thread. Yes, now I do remember you mentioning this before. So it looks like this isn't something I could help with, not unless a significant investment of time (which I sadly lack). But I might find it in a few months if nobody gets around to it sooner, as it would make a nice project for a networking course I have in the next semester. So basically I either have to live with it or turn off WITNESS, right? > The info you want is gone by the time the crash happens. Last time I > chased a similar problem I did some private hacks to write-protect mbufs > to catch unexpected modification. You might try removing ipfw or using > an alternate packet filter if that's feasible. I wouldn't be surprised > if this is related to ipfw and/or divert sockets. Will try switching to pf during the holidays (I've been meaning to do it but I kept procrastinating, so thanks for giving me an incentive ;-) Bye, Andrea -- Press every key to continue.