public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Alexander E. Patrakov" <patrakov@ums.usu.ru>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org,
	Kenneth.Parrish@familynet-international.net
Subject: Re: [SERIAL, -mm] CRC failure
Date: Wed, 14 Dec 2005 18:03:24 +0500	[thread overview]
Message-ID: <43A0181C.10205@ums.usu.ru> (raw)
In-Reply-To: <1134551256.25663.3.camel@localhost.localdomain>

Alan Cox wrote:
> On Mer, 2005-12-14 at 06:45 +0000, Kenneth Parrish wrote:
> 
>>        Three -mm kernels of late, and now v2.6.15-rc5-mm2, give
>>frequent z-modem crc errors with minicom, lrz, and an external v90 modem
>>to a couple of local bb's.  2.6.15-rc5-git2 and before are okay.
> 
> 
> 
> Which -mm kernels gave the error, and which do you know ehrre ok. Also
> can you tell me more about the hardware arrangement you are using - what
> cpu, what serial driver ?
> 
> The -mm tree contains some buffering changes I made and those would be
> the obvious candidate for suspicion

Please CC: me on all replies to this thread, because I think this is 
also related to the ppp failures (a packet repeating over and over) that 
I reported earlier on -mm kernels.

-- 
Alexander E. Patrakov

  reply	other threads:[~2005-12-14 13:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-14  6:45 [SERIAL, -mm] CRC failure Kenneth Parrish
2005-12-14  9:07 ` Alan Cox
2005-12-14 13:03   ` Alexander E. Patrakov [this message]
2005-12-14 13:06 ` Alexander E. Patrakov
2005-12-15  3:37   ` Kenneth Parrish
  -- strict thread matches above, loose matches on Subject: below --
2005-12-14 13:04 Kenneth Parrish
     [not found] <1134574264.25663.38.camel@localhost.localdomain>
2005-12-15  3:37 ` Kenneth Parrish

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=43A0181C.10205@ums.usu.ru \
    --to=patrakov@ums.usu.ru \
    --cc=Kenneth.Parrish@familynet-international.net \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@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