From owner-freebsd-hackers Mon Jun 7 9:23:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from tofu.alt.net (tofu.alt.net [207.14.113.2]) by hub.freebsd.org (Postfix) with ESMTP id 21A2014E10 for ; Mon, 7 Jun 1999 09:23:30 -0700 (PDT) (envelope-from abourov@alt.net) Received: from comp3.addr.com ([209.152.191.146]) by tofu.alt.net (8.9.3/8.8.5) with ESMTP id JAA18862 for ; Mon, 7 Jun 1999 09:23:28 -0700 (PDT) Message-Id: <4.2.0.56.19990607091352.030eb820@mail.addr.com> X-Sender: abourov@mail.alt.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.56 (Beta) Date: Mon, 07 Jun 1999 09:22:58 -0700 To: hackers@FreeBSD.org From: Anthony Bourov Subject: Q: xl0: no memory for rx list -- packet dropped! Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I am running a FreeBSD server, and I am running into this problem very often. The machine stops responding and instead outputs 1000s of xl0: no memory for rx list -- packet dropped! xl0: no memory for rx list -- packet dropped! xl0: no memory for rx list -- packet dropped! xl0: no memory for rx list -- packet dropped! messages. The machine is usually pulling about 4-5 megabits but there is usually a traffic spike right before this happens so an attack is not out of the question, but I was wondering if there was any way I can raise the threshold for this (would more BUFFERs do the trick?). Thanks in advance, Anthony To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message