From owner-freebsd-net@FreeBSD.ORG  Wed Jun 16 16:14:12 2004
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 2F00E16A4CE
	for <freebsd-net@freebsd.org>; Wed, 16 Jun 2004 16:14:12 +0000 (GMT)
Received: from rms04.rommon.net (rms04.rommon.net [212.54.2.140])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 1785C43D46
	for <freebsd-net@freebsd.org>; Wed, 16 Jun 2004 16:14:11 +0000 (GMT)
	(envelope-from pete@he.iki.fi)
Received: from he.iki.fi (h86.vuokselantie10.fi [193.64.42.134])
	by rms04.rommon.net (8.12.10/8.12.9) with ESMTP id i5GGDg3v041636;
	Wed, 16 Jun 2004 19:13:44 +0300 (EEST)
	(envelope-from pete@he.iki.fi)
Message-ID: <40D071B6.2040902@he.iki.fi>
Date: Wed, 16 Jun 2004 19:13:42 +0300
From: Petri Helenius <pete@he.iki.fi>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ming fu <fming@borderware.com>
References: <40D04C08.2080703@borderware.com>
In-Reply-To: <40D04C08.2080703@borderware.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
cc: freebsd-net@freebsd.org
Subject: Re: FreeBSD em ether driver lockup
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Jun 2004 16:14:12 -0000

ming fu wrote:

>
> Is there a suggestion on how to trigger the watchdog to be called. It 
> is really time consuming to diagnose this as it takes hours or dates 
> for the em to lockup once.

Some vendors are kind enough to sell motherboards broken enough for em 
to never get interrupts. However the current driver does not fire a 
watchdog on those boards either.

Pete