From owner-freebsd-bugs@FreeBSD.ORG Thu May 27 04:46:22 2010 Return-Path: Delivered-To: freebsd-bugs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 48C771065688; Thu, 27 May 2010 04:46:22 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from mail-qy0-f181.google.com (mail-qy0-f181.google.com [209.85.221.181]) by mx1.freebsd.org (Postfix) with ESMTP id 82ED88FC0C; Thu, 27 May 2010 04:46:19 +0000 (UTC) Received: by qyk11 with SMTP id 11so10807204qyk.13 for ; Wed, 26 May 2010 21:46:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=VsqI88taG4be5KwboAihRf2NmUilZlazU+p7uyTROD0=; b=AynNF6pkXVp2tMN3/O79IUnpMv69uQ4i8FnlTtmn8leBQAC9wg0VDbq3KQQ7ArHTiG wFUxUfGQOIeObD3KEC3S/A7AuIMZgm0FtptFEbyrHwSyWL/XstgA5S1Pah3VZKOCMJTK fd5h6+1h5M5Ieqe/tR7WtjBbOdqQZilsEJ/pY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=YiObP/8JRj3k7CBN7lUc02HTjgGgeCkJHjC7iYrHq4SXoBlm7ffaFOr4nJpegv08cx zqLOb/+azdrpJQW6P38KjLlzn8d9TqAsTPa1J3aihvLEOxUTGMkAv0g2qbkinNGLZPCa 1qAivIy+/TYBaalLEIxdyMLE7rTJabnjlqBCE= MIME-Version: 1.0 Received: by 10.229.215.138 with SMTP id he10mr2152420qcb.60.1274935578455; Wed, 26 May 2010 21:46:18 -0700 (PDT) Received: by 10.229.190.83 with HTTP; Wed, 26 May 2010 21:46:18 -0700 (PDT) In-Reply-To: <7353B9CB-BAEF-4A7E-9C89-6B46227DF779@oyam.ca> References: <201005261942.o4QJgacx011479@freefall.freebsd.org> <008FD1A4-F1AB-4683-A3A6-6EAA3C0AECED@oyam.ca> <7353B9CB-BAEF-4A7E-9C89-6B46227DF779@oyam.ca> Date: Wed, 26 May 2010 21:46:18 -0700 Message-ID: From: Garrett Cooper To: Mayo Jordanov Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: remko@freebsd.org, freebsd-bugs@freebsd.org Subject: Re: kern/147082: [uart] Serial ports unusable X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 May 2010 04:46:22 -0000 On Wed, May 26, 2010 at 8:01 PM, Mayo Jordanov wrote: > > On 2010-05-26, at 19:34 , Garrett Cooper wrote: > >> On Wed, May 26, 2010 at 6:42 PM, Mayo Jordanov wrote: >>> >>> On 2010-05-26, at 12:42 , remko@FreeBSD.org wrote: >>> >>>> Synopsis: [uart] Serial ports unusable >>>> >>>> State-Changed-From-To: open->feedback >>>> State-Changed-By: remko >>>> State-Changed-When: Wed May 26 19:42:36 UTC 2010 >>>> State-Changed-Why: >>>> I send my working serial line to Mayo, set status to feedback >>>> >>>> http://www.freebsd.org/cgi/query-pr.cgi?pr=3D147082 >>> >>> I'm gona re-reply here, to preserve the history. >>> >>>>>> How-To-Repeat: >>>>> 1) Edit /etc/ttys, do the ttyu0 line reads: >>>>> ttyu0 =A0 =A0 =A0 =A0"/usr/libexec/getty std.9600" =A0 vt100 =A0 on s= ecure >>>>> 2) kill -HUP 1 >>>>> 3) Try connecting to it with terminal application >>>> >>>> >>>> /etc/ttys >>>> console =A0 =A0"/usr/libexec/getty Pc" =A0 =A0 =A0 =A0 cons25 =A0on = =A0secure >>>> >>>> /boot/loader.conf >>>> console=3D"comconsole" >>>> >>>> That enabled serial access to my Soekris device running on FreeBSD8(PF= sense), it also works for several remote machines I have. >>>> >>>> Can you confirm that you have these settings in loader.conf and reboot= ed?! >>>> >>>> -- >>>> /"\ =A0 Best regards, =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0|= remko@FreeBSD.org >>>> \ / =A0 Remko Lodder =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0| remk= o@EFnet >>>> X =A0 =A0http://www.evilcoder.org/ =A0 =A0| >>>> / \ =A0 ASCII Ribbon Campaign =A0 =A0| Against HTML Mail and News >>> >>> test# cat /boot/loader.conf >>> console=3D"comconsole" >>> >>> looking at the /etc/ttys entry you pasted above, will that enable seria= l console? That looks like a regular console on the machine itself. >>> >>> I have rebooted numerous times, and I do get the kernel messages during= boot on serial up to the point where getty starts (presumably... I see por= tion of the messages as nics are getting setup and then nothing). >>> >>> I have some machines where serial works fine, but I have some machines = where it doesn't and behaves the same way as described above. If necessary,= I can provide access to a troublesome machine. >> >> =A0 =A0All of this is described in more grusome detail at >> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/serialconsole-= setup.html > > Unfortunately, the handbook does not help in this case. If there is a sol= ution to the problem I describe in the PR description in the handbook, plea= se be so kind and point it out to me, because I must be blind. > > Also, why do the gettys get stuck and I have to kill them manually (or re= boot because they can't be killed) to reflect changes to /etc/ttys instead = of simple `kill -HUP 1`? I've never ever had to do it manually in previous = FreeBSD installations/versions. Why are they stuck in ttydtd and not in tty= in as they are supposed to be? The comconsole bit is in the section of /etc/ttys in the beforementioned page. Details about debugging your connection is available here: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/term.html . What's the baud rate for your serial connection? The part about kill -HUP 1 not working sounds like a possible syscons/tty bug. Can you try killing init, then provide us with the wait state in ps/top for the relevant getty instance? Thanks! -Garrett