Date: Sun, 20 Feb 2011 04:54:34 +0100 From: Pawel Tyll <ptyll@nitronet.pl> To: Jack Vogel <jfvogel@gmail.com> Cc: Brandon Gooch <jamesbrandongooch@gmail.com>, freebsd-ipfw@freebsd.org, Luigi Rizzo <rizzo@iet.unipi.it>, freebsd-net@freebsd.org Subject: Re: [Panic] Dummynet/IPFW related recurring crash. Message-ID: <1145317277.20110220045434@nitronet.pl> In-Reply-To: <AANLkTi=CLDFGxLQ8rdq3hg0KN9aYZA_YDwDWbqk5gcz2@mail.gmail.com> References: <410175608.20110220013900@nitronet.pl> <AANLkTimWkWYj=HB5BTM0nwYWgNia-Wq4bYHsRB=OjVP7@mail.gmail.com> <AANLkTi=CLDFGxLQ8rdq3hg0KN9aYZA_YDwDWbqk5gcz2@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> I've never seen a trace like this, and no absolutely nothing about dummyn= et, sorry. > If it is in some way em's fault, then making sure you have the latest cod= e would be > a good idea. I have a test driver that is under selective test, it does e= ffect the code > path that you seem to be in, so it might be worth a try. If you want to t= ry it early > just pipe up and I'll send it. I'm less and less sure that it has anything to do with em. I'd like to hear Luigi's take on all this. That being said, I'll gladly try the new driver -- if I'm right, I'll drop under 7 day reboot threshold later into the year anyway, so I really need a permanent solution of some kind. Apparently next crash always comes sooner that previous one, which coincides with growing traffic.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1145317277.20110220045434>