From owner-freebsd-current@FreeBSD.ORG  Mon Oct 24 10:26:04 2005
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
X-Original-To: freebsd-current@freebsd.org
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 8595A16A41F;
	Mon, 24 Oct 2005 10:26:04 +0000 (GMT)
	(envelope-from danny@cs.huji.ac.il)
Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 1E83443D46;
	Mon, 24 Oct 2005 10:26:03 +0000 (GMT)
	(envelope-from danny@cs.huji.ac.il)
Received: from pampa.cs.huji.ac.il ([132.65.80.32])
	by cs1.cs.huji.ac.il with esmtp
	id 1ETzWk-000Nbc-Ed; Mon, 24 Oct 2005 12:26:02 +0200
X-Mailer: exmh version 2.7.0 06/18/2004 with nmh-1.0.4
To: freebsd-current@freebsd.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 24 Oct 2005 12:26:02 +0200
From: Danny Braniss <danny@cs.huji.ac.il>
Message-ID: <E1ETzWk-000Nbc-Ed@cs1.cs.huji.ac.il>
Cc: freebsd-amd64@FreeBSD.org
Subject: em/amd64 on 6.0-RC1
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Oct 2005 10:26:04 -0000


I have been running this box (an Intel SR1435VP2/Xeon-NOCOMA), of which
we have 6, under several different configurations to try and pin down
some problems, initialy I suspected am-utils, but now it's almost certain
the if_em. The problem is sometimes on i386, but always on amd64.

it seems that the problem starts right after the em is re-initialized, after
it was used via PXE to boot. Sniffing shows that the kernel sends
a GETATTR, the server responds, but the client does not see it, and
after some time it will resend, and so on ...

pinging from the server to the client works.

btw, booting off the local disk (not diskless/PXE) em works fine, though
the logs seems a bit baffling:

	...
	em0: no link ... got link
	DHCPDISCOVER on em0 to 255.255.255.255 port 67 interval 3
	DHCPDISCOVER on em0 to 255.255.255.255 port 67 interval 8
	DHCPDISCOVER on em0 to 255.255.255.255 port 67 interval 9
	DHCPOFFER from 132.65.16.10
	unknown dhcp option value 0xfc
	DHCPREQUEST on em0 to 255.255.255.255 port 67
	DHCPACK from 132.65.16.10
	unknown dhcp option value 0xfc
	bound to 132.65.16.104 -- renewal in 7200 seconds.

	lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
 	       inet6 ::1 prefixlen 128 
  	      inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 

	em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        	options=b<RXCSUM,TXCSUM,VLAN_MTU>
        	inet6 fe80::20e:cff:fe6a:8973%em0 prefixlen 64 scopeid 0x1 
        	inet 132.65.16.104 netmask 0xfffff000 broadcast 132.65.31.255
        	ether 00:0e:0c:6a:89:73
        	media: Ethernet autoselect
        	status: no carrier
	**************** HU? *************

later on, ifconfig em0 shows that all is ok.

danny