Date: Tue, 25 Jul 2006 13:22:00 -0700 From: Jo Rhett <jrhett@svcolo.com> To: Bruce Evans <bde@zeta.org.au> Cc: "Rick C. Petty" <rick-freebsd@kiwi-computer.com>, freebsd-hardware@FreeBSD.org Subject: Re: device busy -- no locks? Message-ID: <8B9E167C-89DC-4CC7-84E6-4339AA443574@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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8B9E167C-89DC-4CC7-84E6-4339AA443574>