From owner-freebsd-hackers@FreeBSD.ORG Sun Oct 2 19:59:54 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E3C4716A41F for ; Sun, 2 Oct 2005 19:59:54 +0000 (GMT) (envelope-from david@madole.net) Received: from a.omd3.com (a.omd3.com [69.90.174.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7C2A843D45 for ; Sun, 2 Oct 2005 19:59:54 +0000 (GMT) (envelope-from david@madole.net) Received: from dhcp-66-212-201-164.myeastern.com ([66.212.201.164] helo=david) by a.omd3.com with esmtpa (Exim 4.50) id 1EMA01-000PpY-Ip for freebsd-hackers@freebsd.org; Sun, 02 Oct 2005 15:59:53 -0400 Message-ID: <049901c5c78b$d94163d0$c3e7a8c0@david> From: "David S. Madole" To: Date: Sun, 2 Oct 2005 15:59:50 -0400 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="Windows-1252"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2670 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670 Subject: How to troubleshoot solid freeze-up? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Oct 2005 19:59:55 -0000 I'm looking for some tips on how to troubleshoot a possible driver problem. Here is the scenario: 1. Using a Pentium II 333Mhz mobile processor, 82443BX motherboard, and Intel i82559 NIC (fxp driver). 2. A combination of heavy disk I/O, high CPU utilization, and high network traffic causes a solid machine freeze-up sometime between 10 minutes and 3 hours of running. 3. Replacing the NIC with a DP83815-based card (sis driver) seems to solve the problem. I have run the problem load for up to 8 hours without issue on this NIC. 4. The problem is reproducable on multiple identical machines with multiple identical NICs. Also reproducable on an i82558 NIC integrated on the motherboard. How can I go about collecting useful information to troubleshoot this when the machine locks solid? How can a get a core under this scenario? Switching to another NIC permanently is not a great solution because this is a semi-embedded application and I need to use the NIC on the motherboard. Thanks, David Madole