Bug#279666: kernel-image-2.6.8-1-k7: Runs out of network buffers
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
Reply to: