All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Carlson <carlsonj@workingcode.com>
To: linux-ppp@vger.kernel.org
Subject: Re: ifconfig ppp0 errors
Date: Wed, 12 Jan 2011 21:23:29 +0000	[thread overview]
Message-ID: <4D2E1BD1.7070808@workingcode.com> (raw)
In-Reply-To: <Pine.GSO.4.64.1101111527150.23601@sunfire13.eecs.tufts.edu>

On 01/12/11 16:05, James Cameron wrote:
> I agree with James, it smells like hardware.
> 
> You might compare clock cycle, bit or byte counters at either end.
> 
> You might check for sensitivity to specific data patterns;

Pattern sensitivity is certainly an interesting area.  I think the ones
you've mentioned would tend to trip up poorly-designed hardware -- i.e.,
hardware that has trouble with DC restoration or noise coupled into
ground, or similar sorts of issues.  They're certainly interesting tests
to try.

I think the most prosaic cause of this sort of problem -- given the
evidence so far, which (if I recall correctly) started with OK behavior
until large data transfers were attempted -- is simple overflow.  Either
the system is just unable to keep up with the interrupt load, or
something's blocking the interrupts that do happen, or the latency into
the service routine is greater than the depth of the hardware input buffer.

An overrun would cause lost bytes in the middle of the frame, and cause
frames to be discarded as corrupt when the FCS isn't validated, and it'd
be aggravated by larger packet sizes, by a shorter interval between
packets, and by a system busy doing other things (such as talking to
disk).  All of those seem to line up well with the original problem report.

-- 
James Carlson         42.703N 71.076W         <carlsonj@workingcode.com>

  parent reply	other threads:[~2011-01-12 21:23 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-11 20:30 ifconfig ppp0 errors Slawomir Skret
2011-01-11 21:04 ` James Carlson
2011-01-11 21:57 ` Slawomir Skret
2011-01-11 22:50 ` Slawomir Skret
2011-01-11 23:30 ` James Cameron
2011-01-12  2:29 ` Paul Mackerras
2011-01-12 13:21 ` James Carlson
2011-01-12 18:40 ` Slawomir Skret
2011-01-12 19:47 ` James Carlson
2011-01-12 21:05 ` James Cameron
2011-01-12 21:23 ` James Carlson [this message]
2011-01-12 21:51 ` James Cameron
2011-01-12 22:17 ` James Carlson
2011-01-14 16:58 ` Slawomir Skret
2011-01-14 17:28 ` James Carlson

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=4D2E1BD1.7070808@workingcode.com \
    --to=carlsonj@workingcode.com \
    --cc=linux-ppp@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.