Date: Thu, 24 Feb 2005 17:37:51 -0600 (CST) From: Mike Silbersack <silby@silby.com> To: Dan Nelson <dnelson@allantgroup.com> Cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/kern uipc_mbuf.c src/sys/sys mbuf.h Message-ID: <20050224173517.M9200@odysseus.silby.com> In-Reply-To: <20050224202018.GA60363@dan.emsphone.com> References: <Pine.NEB.3.96L.1050224102854.95733H-100000@fledge.watson.org> <20050224202018.GA60363@dan.emsphone.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 24 Feb 2005, Dan Nelson wrote: > Nope; that particular panic has not reappeared on my system since you > sent me that extra M_ASSERTVALID call. Code knows when it's being > watched. Probably unrelated, but I have not seen a TX underrun error > since Jan 31, and I had been getting a couple every week before that. It's interesting that you say that... >From what I recall, TX underrun errors occur when a burst of packets get sent to the NIC driver. So, since you haven't seen one, that tells me that whatever app (maybe a change in the TCP stack?) which was sending the burst of packets is gone, and you're therefore not stressing the network card/driver anymore. Which is why you're not running into whatever problem had been occuring. Oh well. Mike "Silby" Silbersack
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050224173517.M9200>