From owner-freebsd-bugs@FreeBSD.ORG Thu May 27 03:01:53 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 8BF911065672; Thu, 27 May 2010 03:01:53 +0000 (UTC) (envelope-from mayo@oyam.ca) Received: from zeus.nfy.ca (ns.nfy.ca [204.244.63.66]) by mx1.freebsd.org (Postfix) with ESMTP id 646D68FC08; Thu, 27 May 2010 03:01:53 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by zeus.nfy.ca (Postfix) with ESMTP id F3C6A33D10; Wed, 26 May 2010 20:01:51 -0700 (PDT) Received: from zeus.nfy.ca ([127.0.0.1]) by localhost (zeus.nfy.ca [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0l+xlTLnJ38T; Wed, 26 May 2010 20:01:49 -0700 (PDT) Received: from [10.0.4.22] (a226-smpa-906.blocka-154.stargate.ca [64.253.154.226]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by zeus.nfy.ca (Postfix) with ESMTP id D6BE033D0F; Wed, 26 May 2010 20:01:48 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v1078) Content-Type: text/plain; charset=us-ascii From: Mayo Jordanov In-Reply-To: Date: Wed, 26 May 2010 20:01:47 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <7353B9CB-BAEF-4A7E-9C89-6B46227DF779@oyam.ca> References: <201005261942.o4QJgacx011479@freefall.freebsd.org> <008FD1A4-F1AB-4683-A3A6-6EAA3C0AECED@oyam.ca> To: Garrett Cooper X-Mailer: Apple Mail (2.1078) 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 03:01:53 -0000 On 2010-05-26, at 19:34 , Garrett Cooper wrote: > On Wed, May 26, 2010 at 6:42 PM, Mayo Jordanov wrote: >>=20 >> On 2010-05-26, at 12:42 , remko@FreeBSD.org wrote: >>=20 >>> Synopsis: [uart] Serial ports unusable >>>=20 >>> 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 >>>=20 >>> http://www.freebsd.org/cgi/query-pr.cgi?pr=3D147082 >>=20 >> I'm gona re-reply here, to preserve the history. >>=20 >>>>> How-To-Repeat: >>>> 1) Edit /etc/ttys, do the ttyu0 line reads: >>>> ttyu0 "/usr/libexec/getty std.9600" vt100 on secure >>>> 2) kill -HUP 1 >>>> 3) Try connecting to it with terminal application >>>=20 >>>=20 >>> /etc/ttys >>> console "/usr/libexec/getty Pc" cons25 on secure >>>=20 >>> /boot/loader.conf >>> console=3D"comconsole" >>>=20 >>> That enabled serial access to my Soekris device running on = FreeBSD8(PFsense), it also works for several remote machines I have. >>>=20 >>> Can you confirm that you have these settings in loader.conf and = rebooted?! >>>=20 >>> -- >>> /"\ Best regards, | remko@FreeBSD.org >>> \ / Remko Lodder | remko@EFnet >>> X http://www.evilcoder.org/ | >>> / \ ASCII Ribbon Campaign | Against HTML Mail and News >>=20 >> test# cat /boot/loader.conf >> console=3D"comconsole" >>=20 >> looking at the /etc/ttys entry you pasted above, will that enable = serial console? That looks like a regular console on the machine itself. >>=20 >> 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 portion of the messages as nics are getting setup and then = nothing). >>=20 >> 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. >=20 > All of this is described in more grusome detail at > = http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/serialconsole-se= tup.html > . > HTH, > -Garrett Unfortunately, the handbook does not help in this case. If there is a = solution to the problem I describe in the PR description in the = handbook, please 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 = reboot 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 ttyin as they are supposed to be? Thanks, mayo