Date: Sun, 10 Dec 1995 04:40:21 +0200 From: Heikki Suonsivu <hsu@clinet.fi> To: FreeBSD-gnats-submit@freebsd.org Cc: jhay@mikom.csir.co.za Subject: kern/884: arnet driver does not assert DTR ? Message-ID: <199512100240.EAA25289@katiska.clinet.fi> Resent-Message-ID: <199512100250.SAA20437@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 884
>Category: kern
>Synopsis: arnet driver does not assert DTR, which is necessary for modems
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: freebsd-bugs
>State: open
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Sat Dec 9 18:50:01 PST 1995
>Last-Modified:
>Originator: Heikki Suonsivu
>Organization:
Clinet, Espoo, Finland
>Release: FreeBSD 2.2-CURRENT i386
>Environment:
We tried three environments:
Connection Speed Comments
arnet - cisco up to 2M Works
arnet - modem - modem - cisco 256 kbps Works only if cable is wired to
fake DTR.
arnet - modem - modem - arnet - Does not work, modems don't
see dtr.
>Description:
Arnet-modem-modem-arnet: Apparently arnet driver does not assert some of
the modem signals, as modem lights are not indicating them up at all, and
also they fail to work.
When the device is configured the driver starts to print these as fast as
it can:
Dec 9 05:19:24 smile /kernel: RX0 So this does happen :), stat 94, ST2 4, cda 4
00a.
Dec 9 05:19:24 smile /kernel: RX0 After reset: ST2 0.
Dec 9 05:19:24 smile /kernel: RX0 So this does happen :), stat 94, ST2 0, cda 4
028.
Dec 9 05:19:24 smile /kernel: RX0 After reset: ST2 4.
Dec 9 05:19:24 smile /kernel: RX0 So this does happen :), stat 94, ST2 4, cda 4
03c.
Dec 9 05:19:24 smile /kernel: RX0 After reset: ST2 0.
Dec 9 05:19:24 smile /kernel: RX0 So this does happen :), stat a4, ST2 0, cda 4
050.
Dec 9 05:19:24 smile /kernel: RX0 After reset: ST2 4.
Dec 9 05:19:24 smile /kernel: RX0 So this does happen :), stat 94, ST2 4, cda 4
064.
Dec 9 05:19:24 smile /kernel: RX0 After reset: ST2 0.
Dec 9 05:19:24 smile /kernel: RX0 So this does happen :), stat a4, ST2 0, cda 4
078.
We never got anything through this configuration. This is repeatable on
both 2- and 4-port arnet cards.
Arnet-modem-modem-cisco: The above messages appear sometimes, but not all
the time. DTR is faked from RTS signal:
Dec 9 18:45:11 saga /kernel: RX0 So this does happen :), stat 84, ST2 0,=
cda 426c.
Dec 9 18:45:11 saga /kernel: RX0 So this does happen :), stat 84, ST2 0,=
cda 426c.
Dec 9 18:45:11 saga /kernel: RX0 After reset: ST2 4.
Dec 9 18:45:11 saga /kernel: RX0 After reset: ST2 4.
Dec 9 18:47:12 saga /kernel: RX0 So this does happen :), stat 84, ST2 0,=
cda 424e.
Dec 9 18:47:12 saga /kernel: RX0 So this does happen :), stat 84, ST2 0,=
cda 424e.
Dec 9 18:47:12 saga /kernel: RX0 After reset: ST2 0.
Dec 9 18:47:12 saga /kernel: RX0 After reset: ST2 0.
but the link works (in fact it has been in production use for about two
weeks now).
With a cisco-arnet direct connection things work fine, probably because
ciscos don't mind DTR not being there. We got the following throughput
through a following link:
486-40 - ethernet - cisco(2501) - arnet - 486-40
-----------------------------------------> clock = 2000000 225 KB/s
<----------------------------------------- clock = 2000000 ~180 KB/s
(ftp, put/get file to /dev/null from the machine with the arnet board).
CPU usage was around 60% when receiving (seems a bit high for 16-bit
shared-memory ISA card, as 225 KBytes/s should be 1/10th to 1/20th of the
ISA bandwidth?). I don't know the reason for the speed difference; cisco
uses the same chip so the difference probably is either in driver or the
board. It should be no problem for the chip, data books promise around 7
Mbps and arnet around 5 Mbps (both cisco and arnet use the same chip).
We have only tried one port in use, not multiple ports simultaneously.
We used PPP for the connection.
>How-To-Repeat:
Connect synchronous modems which require DTR. The lack of the DTR signal
is probably the primary problem here. We tried leased line modems made by
Nokia (512k) and Martis (768k). We tried hardwiring the cables for
arnet-modem-modem-arnet connection to supply DTR, but probably did a stupid
mistake somewhere, not knowing V35 connectors too well.
>Fix:
I think this may get fixed simply by asserting DTR, but with bad luck other
signals might also be needed (RTS/CTS, maybe?)
>Audit-Trail:
>Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199512100240.EAA25289>