mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: Martin Persson <martin@cendio.se>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Problem with Linux 2.4.15-pre4 on an IBM ThinkPad
Date: Thu, 15 Nov 2001 22:57:09 +1100	[thread overview]
Message-ID: <1292.1005825429@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "15 Nov 2001 10:25:34 BST." <vwk7wsv10x.fsf@akrulino.lkpg.cendio.se>

On 15 Nov 2001 10:25:34 +0100, 
Martin Persson <martin@cendio.se> wrote:
>However (there's always a however), now I have other problems with my
>laptop. The network comes right up and everything works just fine,
>except when I try to scp files on a few Mbytes from the laptop. When I
>try that, sometimes the scp just works nicely up to 99% where it
>stalls, sometimes it continues after a few seconds, sometimes it
>stalls infinitely (or at least for more than 10 minutes, I interrupted
>it).

I would suspect the Xircom driver (RBEM56G, right?).  I have similar
symptoms with RBEM56G in a Compaq laptop, ssh hangs during bulk
transfers and is sensitive to which direction the transfer was started.
"ifconfig eth0 -promisc" a few times will usually restart the transfer,
sometimes it takes "/etc/rc.d/init.d/pcmcia restart" to fix the
problem, then wait until TCP retransmission picks up again.

I don't believe ssh is at fault, it just causes the right set of
activity to trip the driver problem.  ifconfig eth0 -promisc reloads
CSR6 on the card and the problem goes away, without me touching the ssh
transfers.

This was on my list of problems to debug (after modutils, kdb, xfs,
kbuild 2.5, ...) but I managed to trip over the Ethernet cable and
completely broke the card.  The Realport cards are more resilient than
most PCMCIA network cards but they have their limits.


      reply	other threads:[~2001-11-15 12:11 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-12 19:01 Linux 2.4.15-pre4 - merge with Alan Linus Torvalds
2001-11-12 19:18 ` Trever L. Adams
2001-11-13 11:14   ` Christoph Rohland
2001-11-12 19:26 ` Matthew Dharm
2001-11-12 20:09 ` Martin Dalecki
2001-11-12 20:42 ` Greg KH
2001-11-12 23:43 ` J . A . Magallon
2001-11-13  1:11   ` Alan Cox
2001-11-12 23:45 ` J . A . Magallon
2001-11-12 23:48 ` J . A . Magallon
2001-11-13  0:14   ` Christoph Hellwig
2001-11-13  0:25     ` J . A . Magallon
2001-11-13  0:42     ` J . A . Magallon
2001-11-13  7:43       ` Christoph Hellwig
2001-11-13  5:17 ` Keith Owens
2001-11-13 17:27   ` Chad N. Tindel
2001-11-13 17:58   ` Chad N. Tindel
2001-11-13  5:54 ` Neil Brown
2001-11-13  6:02   ` Jeff Garzik
2001-11-13  9:41     ` Alan Cox
2001-11-13  6:03 ` David S. Miller
2001-11-13  6:16   ` Keith Owens
2001-11-13  6:18   ` Keith Owens
2001-11-13  6:23   ` David S. Miller
2001-11-13  8:17     ` Jeff Garzik
2001-11-13 10:43 ` David S. Miller
2001-11-13 14:10 ` Horst von Brand
2001-11-13 15:21   ` Thorsten Kukuk
2001-11-14 12:59     ` Horst von Brand
2001-11-14  4:57   ` David S. Miller
2001-11-14  6:28     ` Thorsten Kukuk
2001-11-14  6:31     ` David S. Miller
2001-11-13 15:37 ` [PATCH] " Russell King
2001-11-15  9:25 ` Problem with Linux 2.4.15-pre4 on an IBM ThinkPad Martin Persson
2001-11-15 11:57   ` Keith Owens [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=1292.1005825429@ocs3.intra.ocs.com.au \
    --to=kaos@ocs.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin@cendio.se \
    /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

all inboxes | Powered by JetHome®