Re: kern/165903: mbuf leak

2013-04-17 Thread Jeremy Chadwick
On Wed, Apr 17, 2013 at 01:17:40PM -0700, Jeremy Chadwick wrote: > On Wed, Apr 17, 2013 at 05:38:12PM +, Chris Forgeron wrote: > > Hello, > > > > I'm happy to report that the patch from Gleb has fixed the problem. > > > > My system had 256 mbuf clusters in use at boot, and after a day, stil

Re: kern/165903: mbuf leak

2013-04-17 Thread Jeremy Chadwick
On Wed, Apr 17, 2013 at 05:38:12PM +, Chris Forgeron wrote: > Hello, > > I'm happy to report that the patch from Gleb has fixed the problem. > > My system had 256 mbuf clusters in use at boot, and after a day, still only > has 256 mbuf clusters in use. > > From the patch, I see we are no

Re: kern/165903: mbuf leak

2013-04-16 Thread Jeremy Chadwick
On Tue, Apr 16, 2013 at 04:43:49PM +, Chris Forgeron wrote: > Thanks, I've applied it, and am rebuilding now. I should know tonight/tomorrow > > I take it this proves that I don't have the latest source with cvsup, or is > this work in progress? > > Thanks again. The patch Gleb provided i

Re: kern/165903: mbuf leak

2013-04-15 Thread Gleb Smirnoff
Chris, can you please test attached patch? Jeremy, thanks for cc :) -- Totus tuus, Glebius. Index: if_ether.c === --- if_ether.c (revision 249327) +++ if_ether.c (working copy) @@ -558,13 +558,13 @@ in_arpinput(struct mbuf *m

Re: kern/165903: mbuf leak

2013-04-13 Thread Jeremy Chadwick
On Sun, Apr 14, 2013 at 12:02:56AM +, Chris Forgeron wrote: > Interesting about the drivers - I will look into that tomorrow, I could be on > an older version. I started down that path a little while ago, but when pkng > wasn't quite ready, I just reverted to the old ways/ommands that seemed

RE: kern/165903: mbuf leak

2013-04-13 Thread Chris Forgeron
Interesting about the drivers - I will look into that tomorrow, I could be on an older version. I started down that path a little while ago, but when pkng wasn't quite ready, I just reverted to the old ways/ommands that seemed to work. Here is the dump of the requested commands. I will point o

Re: kern/165903: mbuf leak

2013-04-13 Thread Jeremy Chadwick
On Sat, Apr 13, 2013 at 11:02:17PM +, Chris Forgeron wrote: > To follow-up: > > I installed 9.1-RELEASE last night, then went and cvsup'ed to the latest that > RELENG_9 would give me. > > Everything is completely stock, I have not modified any config files other > than filling out the setup

RE: kern/165903: mbuf leak

2013-04-13 Thread Chris Forgeron
To follow-up: I installed 9.1-RELEASE last night, then went and cvsup'ed to the latest that RELENG_9 would give me. Everything is completely stock, I have not modified any config files other than filling out the setup questions (hostname, em0 set to DHCP, added a base user so I can ssh to it)

RE: kern/165903: mbuf leak

2013-04-11 Thread Chris Forgeron
I was already starting to load up a fresh 9.1-STABLE box for other testing, I will also create a stock box (no changes anywhere) and let it idle for a few days to see if the problem is still there. I'll report back either way in the next few days with results. If I still have problems, I will

Re: kern/165903: mbuf leak

2013-04-10 Thread Eugene M. Zheganin
Hi. On 11.04.2013 01:39, Chris Forgeron wrote: > I do not experience the error if I load up vmware tools and use the vmx3f0 > adapter, it's just with em0. > > I have set the mbufs to very high numbers (322144) to buy more time between > lockups/crashes. Most often the systems stay functional,

Re: kern/165903: mbuf leak

2013-04-10 Thread Jeremy Chadwick
On Wed, Apr 10, 2013 at 04:53:47PM -0700, Jeremy Chadwick wrote: > On Wed, Apr 10, 2013 at 07:39:31PM +, Chris Forgeron wrote: > > I've updated the PR on this via bug track email (hopefully, it bounced my > > first email) , but I thought I should bring it to the attention of the list > > as

Re: kern/165903: mbuf leak

2013-04-10 Thread Jeremy Chadwick
On Wed, Apr 10, 2013 at 07:39:31PM +, Chris Forgeron wrote: > I've updated the PR on this via bug track email (hopefully, it bounced my > first email) , but I thought I should bring it to the attention of the list > as it's still happening, and the original PR was from March 2012. > > The