Date: Fri, 19 Nov 1999 22:40:17 -0800 (PST) From: gshapiro+freebsd@gshapiro.net To: FreeBSD-gnats-submit@freebsd.org Subject: i386/15003: 3.3-STABLE: 3C574 gives bogus ethernet address Message-ID: <199911200640.dAK6eHH90651@horsey.gshapiro.net>
next in thread | raw e-mail | index | archive | help
>Number: 15003
>Category: i386
>Synopsis: 3C574 (ep0) reads bogus ethernet address
>Confidential: no
>Severity: serious
>Priority: high
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Fri Nov 19 22:50:00 PST 1999
>Closed-Date:
>Last-Modified:
>Originator: Gregory Neil Shapiro
>Release: FreeBSD 3.3-STABLE i386
>Organization:
>Environment:
From /sys/i386/conf/MONKEYBOY:
device ep0 at isa? port 0x300 net irq 11
From /etc/pccard.conf:
# 3Com Megahertz 3CXE574B* 10/100 Mbps LAN PC Card
card "3Com" "Megahertz 574B"
config 0x1 "ep0" 11
insert echo 3Com Megahertz 574B Ethernet card inserted
insert /etc/pccard_ether -r ep0
remove echo 3Com Megahertz 574B Ethernet card removed
remove /etc/pccard_ether_remove ep0
>Description:
The latest 3.3-STABLE has begun supporting my PCMCIA Ethernet card (3Com
Megahertz 3CXE574B) using /sys/i386/isa/if_ep.c with the commit of change
1.78.2.4 with one slight problem. The Ethernet address is read as:
Nov 14 13:21:48 monkeyboy /kernel: Card inserted, slot 1
Nov 14 13:21:58 monkeyboy /kernel: ep0: [*UTP*] address 02:01:02:01:02:01
What I find interesting about the bogus Ethernet address is the number 0201
is also the ID number for the new card in the source:
case 0x0201: /* 3C574BT */
To make this more interesting, before 3.3-STABLE had this support I was
using the patch committed to 4.0-CURRENT in commits 1.86 and 1.87 and the
card worked fine, including getting the proper Ethernet address.
It appears that the MFC of the changes broken part of it. In the
4.0-CURRENT code, the epb->prod_id == 0x4b57, in the 3.3-STABLE code, it's
0x0201 which shouldn't happen as the product ID is in the card.
Although the card works fine beyond the bogus Ethernet address, if more
than one of us shows up to a USENIX or IETF with this card, there will be
Ethernet address conflicts. Any chance this can be fixed before 3.3-STABLE
goes into code slush state in preparation for 3.4?
>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?199911200640.dAK6eHH90651>