From owner-freebsd-sparc64@FreeBSD.ORG  Fri Mar  5 11:01:31 2004
Return-Path: <owner-freebsd-sparc64@FreeBSD.ORG>
Delivered-To: freebsd-sparc64@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 9478E16A4CE; Fri,  5 Mar 2004 11:01:31 -0800 (PST)
Received: from light.sdf.com (light.sdf.com [207.200.153.231])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id B68C043D1D; Fri,  5 Mar 2004 11:01:30 -0800 (PST)
	(envelope-from tom@sdf.com)
Received: from tom (helo=localhost)
	by light.sdf.com with local-esmtp (Exim 4.22)
	id 1AzKXM-000LW3-8W; Fri, 05 Mar 2004 10:59:08 -0800
Date: Fri, 5 Mar 2004 10:59:08 -0800 (PST)
From: Tom <tom@sdf.com>
To: Jason Mann <jason-freebsdlists@freebsd.org>
In-Reply-To: <20040305164638.GA47394@beastie.b0rken.org>
Message-ID: <20040305105639.K470@light.sdf.com>
References: <20040305164638.GA47394@beastie.b0rken.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: freebsd-sparc64@freebsd.org
Subject: Re: hme driver acting strangely
X-BeenThere: freebsd-sparc64@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting FreeBSD to the Sparc <freebsd-sparc64.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-sparc64>,
	<mailto:freebsd-sparc64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-sparc64>
List-Post: <mailto:freebsd-sparc64@freebsd.org>
List-Help: <mailto:freebsd-sparc64-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-sparc64>,
	<mailto:freebsd-sparc64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Mar 2004 19:01:31 -0000


On Fri, 5 Mar 2004, Jason Mann wrote:

> Hi folks.
>
> I'm running 5.2-RELEASE on a Sun Ultra 5 machine.
>
> It has an on-board Happy Meal ethernet interface, which is handled by the
> 'hme' driver.
>
> If I configure the interface without specifying media and mediaopt, it will
> not establish a full-duplex link with the switch, but otherwise works fine.

  The hme is relatively old hardware.  I don't believe it supports
auto-negotiation.

> If I configure the interface, explicitly specifying full-duplex for the
> mediaopt, a full-duplex link is established, however, no programs can bind
> to UDP ports on that interface. Examples of such programs are named (BIND)
> and ntpd. Logs from named are shown below.
...

  Well, that is strange.  But is probably better off.  You have a
non-managable switch, which would depend on auto-negotiation.  By
configurating static settings you are disabling auto-negotiation (assuming
the hme hardware even supports it to begin with).


Tom