Re: kern/147082: [uart] Serial ports unusable

On 2010-05-26, at 21:46, Garrett Cooper <yanefbsd@gmail.com> wrote:

> On Wed, May 26, 2010 at 8:01 PM, Mayo Jordanov <mayo@oyam.ca> wrote:
>>=20
>> On 2010-05-26, at 19:34 , Garrett Cooper wrote:
>>=20
>>> On Wed, May 26, 2010 at 6:42 PM, Mayo Jordanov <mayo@oyam.ca> 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(PFs=
ense), it also works for several remote machines I have.
>>>>>=20
>>>>> Can you confirm that you have these settings in loader.conf and reboot=
ed?!
>>>>>=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 seria=
l 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 port=
ion 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 w=
here 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-=
setup.html
>>=20
>> 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, pleas=
e be so kind and point it out to me, because I must be blind.
>>=20
>> 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 o=
f simple `kill -HUP 1`? I've never ever had to do it manually in previous Fre=
eBSD installations/versions. Why are they stuck in ttydtd and not in ttyin a=
s they are supposed to be?
>=20
>    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

Thanks for pointing me to the term debugging section in handbook, I wasn't a=
ware if it. It does not offer anything new that I haven't tried yet, though.=

Cheers,
mayo=
_______________________________________________
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscribe@freebsd.org"