From nobody@FreeBSD.ORG Wed Apr 21 17:45:06 1999
Return-Path: <nobody@FreeBSD.ORG>
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id 5C21615553; Wed, 21 Apr 1999 17:44:40 -0700 (PDT)
Message-Id: <19990422004440.5C21615553@hub.freebsd.org>
Date: Wed, 21 Apr 1999 17:44:40 -0700 (PDT)
From: mvp@braz.ru
Sender: nobody@FreeBSD.ORG
To: freebsd-gnats-submit@freebsd.org
Subject: DEC FDDI PCI Adapter doesn't work...
X-Send-Pr-Version: www-1.0

>Number:         11268
>Category:       i386
>Synopsis:       DEC FDDI PCI Adapter doesn't work...
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Apr 21 17:50:00 PDT 1999
>Closed-Date:    Wed Sep 15 18:25:18 PDT 1999
>Last-Modified:  Wed Sep 15 18:30:20 PDT 1999
>Originator:     Vadim Mikhailov
>Release:        3.1-19990408-STABLE, 4.0-19990418-CURRENT
>Organization:
Bratsk Aluminium Plant
>Environment:
FreeBSD mars.braz.ru 4.0-19990418-CURRENT FreeBSD 4.0-19990418-CURRENT #1: Wed Apr 21 15:57:27 IRKST 1999     mvp@mars.braz.ru:/usr/src/sys/compile/MARS  i386

>Description:
DEC FDDI PCI Adapter doesn't work under 4.0-19990418-CURRENT.
I tried also 3.1-19990408-STABLE, 4.0-19990318-CURRENT - same results.

Kernel recognizes device fpa0:

mvp@mars:/> dmesg | grep fpa
fpa0: <Digital DEFPA PCI FDDI Controller> at device 13.0 on pci0
fpa0: DEC DEFPA PCI FDDI SAS Controller   
fpa0: FDDI address 00:00:f8:63:1c:4c, FW=2.46, HW=1, SMT V7.2
fpa0: FDDI Port = S (PMD = ANSI Multi-Mode)
fpa0: interrupting at irq 14

I can configure fpa0 with ifconfig, card initializes (green light)
but ping doesn't work.
Moreover, "tcpdump -i fpa0" doesn't hear anything...
Hardware is not issue - under 3.1-RELEASE and DOS all works fine.
I inserted ethernet card 3c905b - it worked,
but what happened with fddi driver? I want to install 3.1-STABLE,
but I cannot, because I need 100mbit FDDI perfomance...

>How-To-Repeat:
Install FreeBSD 3.1-19990408-STABLE to machine with
DEC DEFPA card, and try to make it visible from network.

>Fix:



>Release-Note:
>Audit-Trail:

From: Douglas Fajardo <dfajard@dpc.com>
To: freebsd-gnats-submit@freebsd.org, mvp@braz.ru
Cc:  
Subject: Re: i386/11268: DEC FDDI PCI Adapter doesn't work...
Date: Wed, 07 Jul 1999 21:19:11 -0700

 I have had a similar experience with 3.2-19990705-STABLE.
 (Brand New Install).
 
 There was a difference, though. TCPDUMP shows network traffic recieved.
 
 After I do an ifconfig, I get "Link unavailable" followed by "Link
 Available" (this
 might be normal, I dont know)
 
 It's not a bad card - I tried a second card with identical results; the
 first was new,
     the second had been in service for over a year.
 
 FDDI loop is alive and well, with at least 5 devices in the loop.
 
 If I can provide additional information, please let me know.
 
 
 ------
 From Startup:
 
 Jul  7 16:53:28 rutile /kernel: fpa0: <Digital DEFPA PCI FDDI
 Controller> rev 0x01 int a irq 10 on pci0.13.0
 Jul  7 16:53:28 rutile /kernel: fpa0: DEC DEFPA PCI FDDI SAS Controller
 Jul  7 16:53:28 rutile /kernel: fpa0: FDDI address 00:00:f8:63:12:72,
 FW=2.46, HW=0, SMT V7.2
 Jul  7 16:53:28 rutile /kernel: fpa0: FDDI Port = S (PMD = Unshielded
 Twisted Pair)
 
 
 IFCONFIG command and resulting log entries:
 ifconfig fpa0 inet 10.30.1.120 netmask 255.255.0.0
 
 Jul  7 21:03:51 rutile /kernel: fpa0: Link Unavailable
 Jul  7 21:03:52 rutile /kernel: fpa0: Link Available
 
 
 ------
 Submitted by: Douglas Fajardo
               dfajard@hitachi-hkis.com
               Hitachi Koki Immaging Solutions
 
State-Changed-From-To: open->closed 
State-Changed-By: lile 
State-Changed-When: Wed Sep 15 18:25:18 PDT 1999 
State-Changed-Why:  
if_ether.c was broken by the token-ring arp merges.  This has 
been fixed in both -current and -stable 
>Unformatted:
