Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Dave Land <xmechanic@landcomp.net>
To: Jeroen Roovers <jer@gentoo.org>, linux-parisc@vger.kernel.org
Cc: Helge Deller <deller@gmx.de>,
	John David Anglin <dave.anglin@bell.net>,
	Rolf Eike Beer <eike-kernel@sf-tec.de>
Subject: Re: [C8000] serial console drops input
Date: Sun, 26 Jan 2014 13:35:46 -0700	[thread overview]
Message-ID: <52E571A2.8060600@landcomp.net> (raw)
In-Reply-To: <20140126212225.0c6e88f9@marga.jer-c2.orkz.net>

On 1/26/14 1:22 PM, Jeroen Roovers wrote:
> On Sun, 26 Jan 2014 16:07:18 +0100
> Helge Deller <deller@gmx.de> wrote:
>
>> I'm pretty sure that I didn't changed anything in palo which is
>> PDC-console related and which would explain why you have such
>> problems. If there is a problem, then it might be because of kernel
>> and/or cable.
>
> Yes, that seems to be the case. I initially assumed something might
> actually reconfigure the serial port in the IPL, but I can't find any
> evidence in support.
>
> I think I am seeing two problems:
>
> 1) Pasting strings doesn't work on either the PDC console or the
>     IPL/Linux console.
>
> 2) Whereas typing on the PDC console works fine, even at some speed,
>     the same is not true for the IPL/Linux console, which lose many
>     characters along the way, and act as if the connection is
>     temporarily lost. Switching the client side terminal program
>     (I tested with minicom, picocom, screen) makes no difference.
>
> Do serial cables deteriorate over time? :-)
>
>
> Regards,
>       jer
> --

Jeroen,

It is a possibility that the serial cable may be a problem, or there may 
actually be a hardware issue with the machine itself.(Most of these 
machines are pretty old by computer world standards) :-) Sometimes just 
giving them a good cleaning with compressed air, and re-seating the RAM 
modules will make a difference. Just a thought... ;-)

Dave L.

P.S. I live in an area where dust is a major problem, and I have to blow 
the dust and crap out of mine about every 3 months or so. If I don't; 
when it *does* rain around here and the humidity goes up, I get all 
kinds of weird errors on some of my machines (the dust becomes 
electrically conductive). I experience this a lot with my customers 
machines too.

-- 
Dave Land
Land Computer Service  xmechanic@landcomp.net
ICQ: 676030523



  reply	other threads:[~2014-01-26 20:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-25  4:41 [C8000] serial console drops input Jeroen Roovers
2014-01-25  8:20 ` Rolf Eike Beer
2014-01-25 16:29   ` John David Anglin
2014-01-25 16:34     ` Rolf Eike Beer
2014-01-25 16:50       ` John David Anglin
2014-01-25 17:03         ` Rolf Eike Beer
2014-01-25 17:13           ` Jeroen Roovers
2014-01-25 19:54             ` Dave Land
2014-01-25 20:04               ` Dave Land
2014-01-25 20:13             ` John David Anglin
2014-01-26  0:02               ` Jeroen Roovers
2014-01-26  1:01                 ` Dave Land
2014-01-26 15:07                 ` Helge Deller
2014-01-26 20:22                   ` Jeroen Roovers
2014-01-26 20:35                     ` Dave Land [this message]
2014-01-26 21:01                     ` John David Anglin
2014-01-26 21:04                       ` John David Anglin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52E571A2.8060600@landcomp.net \
    --to=xmechanic@landcomp.net \
    --cc=dave.anglin@bell.net \
    --cc=deller@gmx.de \
    --cc=eike-kernel@sf-tec.de \
    --cc=jer@gentoo.org \
    --cc=linux-parisc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox