All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Cameron <quozl@laptop.org>
To: linux-ppp@vger.kernel.org
Subject: Re: ifconfig ppp0 errors
Date: Wed, 12 Jan 2011 21:05:44 +0000	[thread overview]
Message-ID: <20110112210544.GA3760@us.netrek.org> (raw)
In-Reply-To: <Pine.GSO.4.64.1101111527150.23601@sunfire13.eecs.tufts.edu>

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;

- all zero (00000000 repeating), 

- all ones (11111111 repeating), 

- proportion of bits set (00000001, then 00000011, then 00000111, etc), 

- full byte range sequences (00000000 through to 11111111), 

- random numbers (a file of them for cross checking), 

- long duration patterns that might cause lower frequency effects
  (00000000 repeating for 10ms, then 11111111 for 10ms, then change the
  low frequency).

You might test by excluding pppd, such as using cat, diff, and md5sum.

If you've passed all these tests already, then you should find out from
the kernel why the error count is being incremented.

-- 
James Cameron
http://quozl.linux.org.au/

  parent reply	other threads:[~2011-01-12 21:05 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 [this message]
2011-01-12 21:23 ` James Carlson
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=20110112210544.GA3760@us.netrek.org \
    --to=quozl@laptop.org \
    --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.