From owner-freebsd-stable@FreeBSD.ORG Sat May 19 12:26:51 2007 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0C88416A402 for ; Sat, 19 May 2007 12:26:51 +0000 (UTC) (envelope-from stefan.lambrev@sun-fish.com) Received: from blah.sun-fish.com (blah.sun-fish.com [217.18.249.150]) by mx1.freebsd.org (Postfix) with ESMTP id BF74D13C44B for ; Sat, 19 May 2007 12:26:50 +0000 (UTC) (envelope-from stefan.lambrev@sun-fish.com) Received: from blah.sun-fish.com (localhost [127.0.0.1]) by blah.sun-fish.com (Postfix) with ESMTP id 8EAF21B10EB5 for ; Sat, 19 May 2007 14:26:49 +0200 (CEST) Received: from hater.cmotd.com (hater.cmotd.com [192.168.3.125]) by blah.sun-fish.com (Postfix) with ESMTP id 852421B10EA4 for ; Sat, 19 May 2007 14:26:49 +0200 (CEST) Message-ID: <464EED09.6000108@sun-fish.com> Date: Sat, 19 May 2007 15:26:49 +0300 From: Stefan Lambrev User-Agent: Thunderbird 2.0.0.0 (X11/20070425) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP on BLAH Subject: serial over /dev/ttyu0 does not work. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 May 2007 12:26:51 -0000 Hello list. There is a weird situation where my serial connection stoped working. I have disabled device sio in kernel and replaced it with device uart. And so dmesg |grep uart is : uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 on acpi0 I was expecting to see uart1 too .. but it is not here. I have: /dev/ttyu0 & /dev/cuau0, also in /etc/ttys I have the following line: ttyu0 "/usr/libexec/getty std.9600" vt100 on secure I have this configuration on other servers too and it works without problems, but the main difference that I found is when I use minicom. I think if I try to open /dev/cuau0 I should see "Device busy" - and on all other servers where I checked it does respond with "Device busy" as it is already used, but on this server I do not! Also I notice that where the serial is NOT working I have this line in ps xa: 1653 ?? I 0:00.00 /usr/libexec/getty std.9600 ttyu0 In first moment I thought it is OK to have getty on ttyu0, but what is this "??" :) so I checked on the other server and I saw that there is NO getty on ttyu0 running at all (it is started when I start minicom from the other side of the serial but then it shows: 99615 u0 Ss+ 0:00.00 /usr/libexec/getty std.9600 ttyu0 and it is stopped when I stop minicom) Any useful ideas where to look for ? Also switching back from uart to sio may sound OK, but it needs another restart :( both machines are using: uname -srm FreeBSD 6.2-STABLE amd64 P.S. I'm 100% sure it is not a cable problem as the serial console was working with device sio 5minutes ago :( The problem is that with sio the second com port that not work due I/O range conflicts and uart saved me once so I try same solution and here. -- Best Wishes, Stefan Lambrev ICQ# 24134177