Bug#279666: marked as done (kernel-image-2.6.8-1-k7: Runs out of network buffers)
Your message dated Mon, 13 Dec 2004 16:36:51 +0900
with message-id <20041213073650.GB22426@verge.net.au>
and subject line Bug#279666: kernel-image-2.6.8-1-k7: Runs out of network buffers
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 4 Nov 2004 14:29:27 +0000
>From lsorense@csclub.uwaterloo.ca Thu Nov 04 06:29:27 2004
Return-path: <lsorense@csclub.uwaterloo.ca>
Received: from lsorense.tor.istop.com (athlon.lan) [66.11.182.144] (Debian-exim)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CPicA-000157-00; Thu, 04 Nov 2004 06:29:27 -0800
Received: from root by athlon.lan with local (Exim 4.34)
id 1CPic2-0001oO-Mx; Thu, 04 Nov 2004 09:29:18 -0500
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Len Sorensen <lsorense@csclub.uwaterloo.ca>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: kernel-image-2.6.8-1-k7: Runs out of network buffers
X-Mailer: reportbug 3.1
Date: Thu, 04 Nov 2004 09:29:18 -0500
Message-Id: <E1CPic2-0001oO-Mx@athlon.lan>
Delivered-To: submit@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level:
Package: kernel-image-2.6.8-1-k7
Version: 2.6.8-4
Severity: important
For the last week or so, I have had to reboot my machine to get network
access back. After a couple of days of doing the usually work
(webbrowsing, bittornado, email, irssi, and such) it stops being able to
establish network connections. It also shows an enourmous amount of
memory in use, even though nothing in top or ps has any indication of
using that memory. Basically about 250M of ram seems to have just
disappeared somewhere.
The kernel outputs this whenever I try to do something on the network:
kernel: dst cache overflow
While trying to run links or other programs with network connections
get:
connect: No buffer space available
I have never seen this under 2.6.7 or earlier, and I am not sure if it
started happening after going to 2.6.8, or just after the latest 2.6.8
update (although I believe it was only after the latest update or two).
I hope there is some explanation for this behavior in the current
kernel, since the machine load is the same as was working fine under
prior kernels, and I would hate to see this behaviour in the kernel that
would ship with sarge.
Any suggestions for things to make note of or log the next time it
happens (It probably will), I would be happy to try out.
Note: I am running with a set of drivers added to run a Sangoma ADSL
PCI card (www.sangoma.com) although I have been using those for a while
with no problems. I may try removing them to see if they are part of the
problem or not.
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-1-k7
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages kernel-image-2.6.8-1-k7 depends on:
ii coreutils [fileutils] 5.2.1-2 The GNU core utilities
ii fileutils 5.2.1-2 The GNU file management utilities
ii initrd-tools 0.1.74 tools to create initrd image for p
ii module-init-tools 3.1-pre6-1 tools for managing Linux kernel mo
-- no debconf information
---------------------------------------
Received: (at 279666-done) by bugs.debian.org; 13 Dec 2004 07:37:05 +0000
>From horms@koto.vergenet.net Sun Dec 12 23:37:05 2004
Return-path: <horms@koto.vergenet.net>
Received: from koto.vergenet.net [210.128.90.7]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CdklU-0005dX-00; Sun, 12 Dec 2004 23:37:04 -0800
Received: by koto.vergenet.net (Postfix, from userid 7100)
id 34385345AD; Mon, 13 Dec 2004 16:20:24 +0900 (JST)
Date: Mon, 13 Dec 2004 16:36:51 +0900
From: Horms <horms@verge.net.au>
To: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: 279666-done@bugs.debian.org
Subject: Re: Bug#279666: kernel-image-2.6.8-1-k7: Runs out of network buffers
Message-ID: <20041213073650.GB22426@verge.net.au>
References: <E1CPic2-0001oO-Mx@athlon.lan> <20041105041435.GC15070@verge.net.au> <[🔎] 20041209153123.GJ14160@csclub.uwaterloo.ca>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[🔎] 20041209153123.GJ14160@csclub.uwaterloo.ca>
X-Cluestick: seven
User-Agent: Mutt/1.5.6+20040907i
Delivered-To: 279666-done@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level:
On Thu, Dec 09, 2004 at 10:31:23AM -0500, Lennart Sorensen wrote:
> On Fri, Nov 05, 2004 at 01:14:35PM +0900, Horms wrote:
> > Sounds like a memory leak in the kernel somewhere.
>
> Certainly does. I never saw it before 2.6.7 I think and it seems as of
> one of the last 2.6.8 builds in testing it has gone away again.
>
> > I think it would be worth seeing if the behaviour is exhibited
> > without those drivers.
>
> Well I have seen it on other machines without those drivers.
>
> On the other hand it seems one of the recent kernel updates to 2.6.8 may
> have fixed it (I think I saw something about some memory leaks in the
> network code being patched) so it may actually be fixed now. At least
> my work machine running the same kernel (2.6.8 k7) shows perfectly
> reasonable memory use with no unaccounted for memory after 19 days
> uptime, which I think looks right. I think this bug can probably be
> closed for now.
Yes, there were two that I put in in response to another bug report.
I will go ahead and close this as you suggest, please reopen if pain
persists.
--
Horms
Reply to: