From: Ward Vandewege <ward@gnu.org>
To: Krzysztof Halasa <khc@pm.waw.pl>
Cc: Bernie Innocenti <bernie@codewiz.org>,
lkml <linux-kernel@vger.kernel.org>,
Jan Seiffert <kaffeemonster@googlemail.com>,
netdev@vger.kernel.org
Subject: Re: pc300too on a modern kernel?
Date: Tue, 23 Nov 2010 09:44:28 -0500 [thread overview]
Message-ID: <20101123144428.GA18504@countzero.vandewege.net> (raw)
In-Reply-To: <m38w0l2gzh.fsf@intrepid.localdomain>
On Mon, Nov 22, 2010 at 10:20:02PM +0100, Krzysztof Halasa wrote:
> > With this workaround applied, we're st seeing occasional clusters of
> > packet loss. We're working to graph the ping loss alongside traffic to
> > see if there's any correlation.
>
> That's interesting. I remember seeing some TX underruns at higher
> speeds, though nothing alike at 2 Mb/s. What bit rate are you using?
> Does "ifconfig hdlc0" show any errors?
This turned out to be caused by line saturation. We were not seeing this
before we upgraded to the latest kernel because we have a set of qos rules
that we forgot to install on our new box. Mea culpa...
Thanks,
Ward.
--
Ward Vandewege <ward@gnu.org>
prev parent reply other threads:[~2010-11-23 14:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100902131531.GA19028@countzero.vandewege.net>
[not found] ` <m3mxrw1lg0.fsf@intrepid.localdomain>
[not found] ` <1289421869.9336.49.camel@giskard.codewiz.org>
[not found] ` <m3sjz34mka.fsf@intrepid.localdomain>
[not found] ` <1289944619.2677.22.camel@giskard.codewiz.org>
[not found] ` <m3tyjd7za9.fsf@intrepid.localdomain>
[not found] ` <1290442675.5515.92.camel@giskard.codewiz.org>
2010-11-22 21:20 ` pc300too on a modern kernel? Krzysztof Halasa
2010-11-23 14:44 ` Ward Vandewege [this message]
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=20101123144428.GA18504@countzero.vandewege.net \
--to=ward@gnu.org \
--cc=bernie@codewiz.org \
--cc=kaffeemonster@googlemail.com \
--cc=khc@pm.waw.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).