From owner-freebsd-questions@FreeBSD.ORG Fri Jul 30 13:48:18 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 12DF816A4CE for ; Fri, 30 Jul 2004 13:48:18 +0000 (GMT) Received: from mail3.panix.com (mail3.panix.com [166.84.1.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id CF00343D5F for ; Fri, 30 Jul 2004 13:48:17 +0000 (GMT) (envelope-from stanb@panix.com) Received: from brillig.panix.com (brillig.panix.com [166.84.1.76]) by mail3.panix.com (Postfix) with ESMTP id 1031D98192; Fri, 30 Jul 2004 09:47:58 -0400 (EDT) Received: from teddy.fas.com (pcp01011587pcs.mplsnt01.sc.comcast.net [68.58.181.2]) by brillig.panix.com (Postfix) with ESMTP id D42462AA0E; Fri, 30 Jul 2004 09:47:57 -0400 (EDT) Received: from stan by teddy.fas.com with local (Exim 3.36 #1 (Debian)) id 1BqXjp-0000tA-00; Fri, 30 Jul 2004 09:47:57 -0400 Date: Fri, 30 Jul 2004 09:47:57 -0400 From: stan To: Steve Message-ID: <20040730134757.GA3401@teddy.fas.com> Mail-Followup-To: Steve , Free BSD Questions list References: <20040730112727.GA32528@teddy.fas.com> <021a01c47642$51378a50$47bf82d8@webairsteve> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <021a01c47642$51378a50$47bf82d8@webairsteve> X-Editor: gVim X-Operating-System: Debian GNU/Linux X-Kernel-Version: 2.4.23 X-Uptime: 09:45:46 up 62 days, 10:35, 1 user, load average: 0.01, 0.02, 0.00 User-Agent: Mutt/1.5.4i Sender: Stan Brown cc: Free BSD Questions list Subject: Re: Repeated lockups with 4.10 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Jul 2004 13:48:18 -0000 On Fri, Jul 30, 2004 at 07:34:27AM -0700, Steve wrote: > do you have anything in dmesg, logs, any cores, etc ...... Unfortunately no. It apears that teh systems are getting some sort of hardware intrupt (serial port?, disk I/O ?), and that they then corupt somthing, and since they are off in an iterupt, they never return. Is it possible to add any kernel debuging or something like that to try to track this? -- "They that would give up essential liberty for temporary safety deserve neither liberty nor safety." -- Benjamin Franklin