From owner-freebsd-stable@FreeBSD.ORG Tue Sep 5 18:33:55 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 73AA316A4DD for ; Tue, 5 Sep 2006 18:33:55 +0000 (UTC) (envelope-from barney@databus.com) Received: from mail1.acecape.com (mail1.acecape.com [66.114.74.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0789C43D49 for ; Tue, 5 Sep 2006 18:33:54 +0000 (GMT) (envelope-from barney@databus.com) Received: from pit.databus.com (pool-72-89-128-62.nycmny.fios.verizon.net [72.89.128.62]) (authenticated bits=0) by mail1.acecape.com (8.13.7/8.13.7) with ESMTP id k85IXrbb028670 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Tue, 5 Sep 2006 14:33:54 -0400 Received: from pit.databus.com (localhost [127.0.0.1]) by pit.databus.com (8.13.8/8.13.8) with ESMTP id k85IXr4K076462 for ; Tue, 5 Sep 2006 14:33:53 -0400 (EDT) (envelope-from barney@pit.databus.com) Received: (from barney@localhost) by pit.databus.com (8.13.8/8.13.8/Submit) id k85IXri3076456 for stable@freebsd.org; Tue, 5 Sep 2006 14:33:53 -0400 (EDT) (envelope-from barney) Date: Tue, 5 Sep 2006 14:33:52 -0400 From: Barney Wolff To: stable@freebsd.org Message-ID: <20060905183352.GA56243@pit.databus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.11 X-Scanned-By: MIMEDefang 2.56 on 72.89.128.62 Cc: Subject: em watchdog timeout on UP, 6-stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Sep 2006 18:33:55 -0000 Updated my Athlon-xp 6-stable system last night, got an em watchdog timeout for the first time a few hours later, during a fairly high-traffic period. System is UP but does have device apic in the config. Any chance this is the recent race condition? Workaround? ifconfig em0 down, ifconfig em0 up seemed to cure it, at least for the moment. Thanks, Barney Wolff -- Barney Wolff I never met a computer I didn't like.