Hi Ben,
You were correct.
It is offload and it is X and/or pulse which is throwing enough TCP at
the system to trigger the memory allocation failures.
You can close the bug now.
Turning off all offloads except checksumming looks like a valid
workaround. I have had the system running for a while. The memory
allocation failures should have shown up by now.
It may be worth it to have an init script as a part of the ethtool
package which sets offloads and defaults to turning off segmentation
offloads at if there is no swap. I will be happy to write it, if you and
the ethtool maintainer think it is a good idea.
Brgds,
--
Understanding is a three-edged sword:
your side, their side, and the truth. --Kosh Naranek
A. R. Ivanov
E-mail: aiva...@sigsegv.cx
WWW: http://www.sigsegv.cx/
pub 1024D/DDE5E715 2002-03-03 Anton R. Ivanov <ai...@sigsegv.cx>
Fingerprint: C824 CBD7 EE4B D7F8 5331 89D5 FCDA 572E DDE5 E715
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
