From owner-freebsd-current@FreeBSD.ORG Tue May 18 06:48:10 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E2AEA16A4CE for ; Tue, 18 May 2004 06:48:10 -0700 (PDT) Received: from smtp3b.sentex.ca (smtp3b.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3B30343D5A for ; Tue, 18 May 2004 06:48:08 -0700 (PDT) (envelope-from mike@sentex.net) Received: from avscan1.sentex.ca (avscan1.sentex.ca [199.212.134.11]) by smtp3b.sentex.ca (8.12.11/8.12.11) with ESMTP id i4IDm7oU060690; Tue, 18 May 2004 09:48:07 -0400 (EDT) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by avscan1.sentex.ca (8.12.10/8.12.10) with ESMTP id i4IDluee061346; Tue, 18 May 2004 09:47:56 -0400 (EDT) (envelope-from mike@sentex.net) Received: from simian.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.12.11/8.12.11) with ESMTP id i4IDlnlH069595; Tue, 18 May 2004 09:47:54 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <6.0.3.0.0.20040518094139.059b0cb0@64.7.153.2> X-Sender: mdtpop@64.7.153.2 (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 6.0.3.0 Date: Tue, 18 May 2004 09:49:43 -0400 To: Bruce Evans From: Mike Tancsa In-Reply-To: <20040518132157.B8772@gamplex.bde.org> References: <6.0.3.0.0.20040517154946.06d23d60@64.7.153.2> <20040518132157.B8772@gamplex.bde.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by amavisd-new cc: freebsd-current@freebsd.org Subject: Re: sio / puc wedging on both -current and -stable X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 May 2004 13:48:11 -0000 Hi, Thanks for the response! I will work on providing the information below today. One quick note that I am not sure if its a fluke yet or something important, the problem *seems* to go away, if on the STABLE box, I remove the defs for sio2 and sio3 device sio2 at isa? disable port IO_COM3 irq 5 device sio3 at isa? disable port IO_COM4 irq 9 to #device sio2 at isa? disable port IO_COM3 irq 5 #device sio3 at isa? disable port IO_COM4 irq 9 But it has not yet locked up in 12hrs and it usually takes 15-40min. On a possibly related point, I think I might have locked up my firewall at home in a similar manner once. I tried once to attach to a com port that was defined in the kernel, but disabled in the BIOS. This froze up the machine. I wonder now if it was perhaps the same root cause. At 11:50 PM 17/05/2004, Bruce Evans wrote: >Going through intr_mux() means that the interrupt is not fast >(options PUC_FASTINTR). Try that. OK, but I thought one is not supposed to use that option if the Interrupts are shared no ? >It may be significant that the hang seems to occur while openig the console >device. Do you have a serial console on the puc device? I thought that >this doesn't work. No, I have it on just the built in cuaa0. The hangs will happen with or without serial console support. I only moved to the serial debugger as I could not hit CTL+ALT+ESC to get into the debugger from the keyboard. Also this way I could control it from my workstation (its on an APC power console as well so I can reboot it remotely from home if need be!) >Did it work before then? The driver hasn't changed since long before then. I think it might have always been a problem. ---Mike