From owner-freebsd-hardware@FreeBSD.ORG Tue Jul 25 20:22:34 2006 Return-Path: X-Original-To: freebsd-hardware@FreeBSD.org Delivered-To: freebsd-hardware@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 45F0816A53F for ; Tue, 25 Jul 2006 20:22:34 +0000 (UTC) (envelope-from jrhett@svcolo.com) Received: from outbound0.sv.meer.net (outbound0.mx.meer.net [209.157.153.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id 47CDA43D7B for ; Tue, 25 Jul 2006 20:22:25 +0000 (GMT) (envelope-from jrhett@svcolo.com) Received: from mail.meer.net (mail.meer.net [209.157.152.14]) by outbound0.sv.meer.net (8.12.10/8.12.6) with ESMTP id k6PKMNis033967; Tue, 25 Jul 2006 13:22:24 -0700 (PDT) (envelope-from jrhett@svcolo.com) Received: from [10.66.240.106] (public-wireless.sv.svcolo.com [64.13.135.30]) by mail.meer.net (8.13.3/8.13.3/meer) with ESMTP id k6PKMJAv088401; Tue, 25 Jul 2006 13:22:19 -0700 (PDT) (envelope-from jrhett@svcolo.com) In-Reply-To: <20060724154856.I58894@delplex.bde.org> References: <20060721000018.GA99237@svcolo.com> <20060721001607.GA64376@megan.kiwi-computer.com> <20060721004731.GC8868@svcolo.com> <20060724154856.I58894@delplex.bde.org> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <8B9E167C-89DC-4CC7-84E6-4339AA443574@svcolo.com> Content-Transfer-Encoding: 7bit From: Jo Rhett Date: Tue, 25 Jul 2006 13:22:00 -0700 To: Bruce Evans X-Mailer: Apple Mail (2.752.2) Cc: "Rick C. Petty" , freebsd-hardware@FreeBSD.org Subject: Re: device busy -- no locks? X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jul 2006 20:22:34 -0000 On Jul 23, 2006, at 11:57 PM, Bruce Evans wrote: > Killing all processes sleeping in serial device open unwedges the > port for > the bug that I know about (provided the close doesn't hang). This and > making the open succeed by raising DCD in hardware are the only > ways that > I know of to unwedge the port once the open gets stuck. Hm. So I just noticed that ttyd0 was locked even though nothing was using it. I shut down qpage and disabled the getty (vi /etc/ttys and kill -1 1) and now there's no processes to use it and its still locked. Anything else I can gather to help debug this? Or in particular, get a bug open on this and perhaps get it fixed? -- Jo Rhett senior geek Silicon Valley Colocation