From owner-freebsd-stable Mon Dec 27 20:20:13 1999 Delivered-To: freebsd-stable@freebsd.org Received: from inbox.org (inbox.org [216.22.145.8]) by hub.freebsd.org (Postfix) with ESMTP id 1CEE1153A6 for ; Mon, 27 Dec 1999 20:20:07 -0800 (PST) (envelope-from bsd@inbox.org) Received: from localhost (bsd@localhost) by inbox.org (8.9.3/8.9.3) with SMTP id XAA22548 for ; Mon, 27 Dec 1999 23:20:14 -0500 (EST) Date: Mon, 27 Dec 1999 23:20:14 -0500 (EST) From: "Mr. K." To: stable@freebsd.org Subject: panic Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG received the following messages in /var/log/messages, followed by a kernel panic (I assume that's why it rebooted, anyway)... Dec 27 23:08:36 freebsd50 /kernel: r rx list -- packet dropped! Dec 27 23:08:36 freebsd50 /kernel: xl0: no memory for rx list -- packet dropped! Dec 27 23:08:36 freebsd50 last message repeated 177 times Dec 27 23:13:50 freebsd50 /kernel: Copyright (c) 1992-1999 FreeBSD Inc. What I was doing was making 500 connections from this box to a linux box and sending 1 million messages (10 bytes) back and forth. This box was the client, the linux box was the server. Unfortunately, it looks like the linux box won :(. Totally untweaked kernel. I didn't get to tweaking yet. I shouldn't have to tweak anything to make the kernel not panic, though... Not complaining, just pre-empting possible flames. Is this a known problem? Yes, I should enable crash dumps, I'm going to go look for documentation on that now... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message