Date: Wed, 25 Dec 2013 17:33:56 +0400 From: Gleb Smirnoff <glebius@FreeBSD.org> To: Mark Felder <feld@FreeBSD.org> Cc: FreeBSD Net <freebsd-net@freebsd.org>, FreeBSD Stable Mailing List <freebsd-stable@freebsd.org> Subject: Re: 10.0-RC1: bad mbuf leak? Message-ID: <20131225133356.GL71033@FreeBSD.org> In-Reply-To: <3A115E20-3ADB-49BA-885D-16189B97842B@FreeBSD.org> References: <1387204500.12061.60192349.19EAE1B4@webmail.messagingengine.com> <CAJ-VmonGE2=vmFOnCtLVLyNp0=F%2BNUd6OdU6=rROH_PWkyXSDA@mail.gmail.com> <EE2A759D-B9BB-4176-BAC6-D6D3C45E2CD1@FreeBSD.org> <3A115E20-3ADB-49BA-885D-16189B97842B@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Mark, On Tue, Dec 24, 2013 at 10:54:33AM -0600, Mark Felder wrote: M> > finally found some free time today to try to look into this. I was digging into the SVN changelogs of sys/dev/e1000 and couldn't see any obvious changes that I should revert. Instead I went a different route and jumped to HEAD/CURRENT. I'm not seeing the mbufs leaking yet. I'll need another 24 hours to confirm. Hopefully this is a worthwhile clue. I'm a bit surprised nobody else has reported this type of behavior... maybe 10 isn't getting the amount of testing we expect? ...or maybe it's just my lonely, haunted hardware :( M> M> Ok, I feel safe confirming that 10.0-RCs are not stable on my hardware. The mbuf problem went away completely when I jumped to head/current. M> M> Can someone please suggest what patch I can attempt to back out to fix this? I'd like to try to assist in fixing this before 10.0-RELEASE happens or we're going to have some very angry users. Is it possible for you to bisect head from the stable/10 branchpoint up to the current date and narrow down the revisions that introduced (and later fixed?) the leak? -- Totus tuus, Glebius.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20131225133356.GL71033>