Date: Wed, 28 Apr 1999 06:14:05 -0700 (PDT) From: wefaqcallcenter.systemhaus.net@FreeBSD.ORG To: freebsd-gnats-submit@freebsd.org Subject: kern/11365: plip in Linux mode has trouble with some Linux Systems Message-ID: <19990428131405.9582914C08@hub.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 11365 >Category: kern >Synopsis: plip in Linux mode has trouble with some Linux Systems >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Apr 28 06:20:01 PDT 1999 >Closed-Date: >Last-Modified: >Originator: Christoph Weber-Fahr >Release: 3.1-RELEASE,2.2.7-RELEASE >Organization: O.tel.o Communications >Environment: FreeBSD hekabe.otelo-call.de 2.2.7-RELEASE FreeBSD 2.2.7-RELEASE #0: Tue Mar 2 12:00:25 CET 1999 wefa@hekabe.otelo-call.de:/usr/src/sys/compile/HEKABE i38 6 FreeBSD dido.otelo-call.de 3.1-RELEASE FreeBSD 3.1-RELEASE #1: Mon Apr 19 14:35: 09 CEST 1999 wefa@dido.otelo-call.de:/var/src/sys/compile/DIDO i386 >Description: Using plip in Linux mode (link0) is unusable with certain Linux systems. Typically the Linux System gets 'plip1 timeout', after which communication stops completely and has to be restarted by unplugging the cable and ifconfig down/up on both sides. It typically occurs as soon as I put load onto the connection On the FreeBSD side I have tested it with two systems - hekabe is an older 486/33 with 2.2.7-RELEASE, dido is a P133 with 3.1-RELEASE. The problem occurs with both. The problematic Linux machine is a Compaq 1570D Laptop. When the Compaq gets connected via plip to another, faster Linux machine, the other machine also displays 'plip timeout' messages every now and then, but the connection recovers gracefully and doesn't loose any data. I have also put FreeBSD 3.1-RELEASE onto that Compaq Laptop, in this case the problem doesn't show up at all. Also I connected the faster Linux Machine to both FreeBSD systems involved - here I didn't see any troubles as well. I suspect there is some obscure timing issue between the two plip implementations which gets triggered by the Compaq's hardware. Since it occurs when I put load onto the connection, maybe it only appears when packet length exceeds a certain value, or when packet length reaches mtu. Maybe the problemn is even known on the Linux side, and their driver has a way to recover from the error. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990428131405.9582914C08>