All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Tom Sightler" <ttsig@tuxyturvy.com>
To: "Trever L. Adams" <trever_Adams@bigfoot.com>,
	"Mark Hahn" <hahn@coffee.psychology.mcmaster.ca>
Cc: "linux Kernel" <linux-kernel@vger.kernel.org>
Subject: Re: Serial, 115Kbps, 2.2, 2.4
Date: Sun, 1 Apr 2001 20:44:22 -0400	[thread overview]
Message-ID: <003001c0bb0e$100149b0$08080808@zeusinc.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10104011432180.5518-100000@coffee.psychology.mcmaster.ca> <3AC7B54C.2010706@bigfoot.com>

Actually, I do have a similar problem that I've been unable to track down
100%.  Under 2.4.x when I run the modem on my Xircom Cardbus 10/100
Ethernet/56K Modem combo card (installed in a Dell 5000e with 650Mhz Pentium
III) I get a fair number of dropped packets at 115Kbps, enough to cause
problems and a significant speed decrease.  Simply dropping the serial port
rate to 56K seems to solve the problem.  I'm actually suspicious that the
hardware handshaking isn't working quite right, but I haven't take the time
to look at it.

I never noticed the problem under 2.2.x, but the last kernel I ran from that
era was the 2.2.16 kernel included with Redhat 7.  I've really not looked at
it very hard, backing the speed down to 56K was a good enough solution for
me for now, the Xircom has such a troublesome history that I just blamed it
on that but your report makes me more curious.

Later,
Tom



  reply	other threads:[~2001-04-02  0:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.10.10104011432180.5518-100000@coffee.psychology.mcmaster.ca>
2001-04-01 23:10 ` Serial, 115Kbps, 2.2, 2.4 Trever L. Adams
2001-04-02  0:44   ` Tom Sightler [this message]
2001-04-02  6:30     ` Paul Jakma
2001-04-01 16:35 Trever L. Adams
2001-04-01 23:53 ` Jeff Chua
2001-04-02  1:34 ` Manfred H. Winter

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='003001c0bb0e$100149b0$08080808@zeusinc.com' \
    --to=ttsig@tuxyturvy.com \
    --cc=hahn@coffee.psychology.mcmaster.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trever_Adams@bigfoot.com \
    /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.