From owner-freebsd-stable Thu Mar 30 23: 9:38 2000 Delivered-To: freebsd-stable@freebsd.org Received: from gateway.mindmaker.com (gateway.mindmaker.com [209.66.98.130]) by hub.freebsd.org (Postfix) with ESMTP id 3011837B6A1 for ; Thu, 30 Mar 2000 23:09:31 -0800 (PST) (envelope-from bbeck@mindmaker.com) Received: (from root@localhost) by gateway.mindmaker.com (8.8.8/8.8.7) id XAA05291 for ; Thu, 30 Mar 2000 23:09:19 -0800 (PST) Received: from mail.int.mindmaker.com(192.168.10.10) by gateway.mindmaker.com via smap (V2.0) id xma005289; Thu, 30 Mar 00 23:09:09 -0800 Received: from mindmaker.com (auth.int.mindmaker.com [192.168.10.15]) by mail.int.mindmaker.com (8.9.3/8.9.3) with ESMTP id XAA54164; Thu, 30 Mar 2000 23:03:17 -0800 (PST) Message-ID: <38E44DD8.8BAAE0CE@mindmaker.com> Date: Thu, 30 Mar 2000 23:03:52 -0800 From: Bernhard Beck X-Mailer: Mozilla 4.6 [en] (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: stable@freebsd.org Subject: trap 12 / kernel panic in ping with ep0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Not sure if this is the right mailing list. One of our test systems (TEST) is running 4.0-RELEASE with a custom kernel (pretty much stock GENERIC kernel with IDE and most drivers commented out in configuration). The system has a 3com 509 NIC. Today we were stress-testing one of our web servers with ab and http_load generating high network load from TEST. Eventually, TEST stopped sending packets. I saw this same behaviour in earlier versions of FreeBSD with 3com cards (2.2 and 3.2). Usually an ifconfig ep0 down and ifconfig ep0 up was enough the revive the network layer. Not this time. I ran ping on TEST without responses. Got back to the command line, started ping again and got a trap 12: kernel panic. I have all the panic information written down if anyone is interested in that, but since this is a custom build kernel I guess the address information won't help a lot. The active process at the time of the panic was ping. Did anybody see a crash like this before in 4.0? Thanks, Bernhard To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message