From owner-freebsd-stable@FreeBSD.ORG Sun Jun 1 03:57:57 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9487F1065672 for ; Sun, 1 Jun 2008 03:57:57 +0000 (UTC) (envelope-from clint@0lsen.net) Received: from belle.0lsen.net (belle.0lsen.net [75.150.32.89]) by mx1.freebsd.org (Postfix) with ESMTP id 79F5A8FC0A for ; Sun, 1 Jun 2008 03:57:57 +0000 (UTC) (envelope-from clint@0lsen.net) Received: by belle.0lsen.net (Postfix, from userid 1001) id 466AE79428; Sat, 31 May 2008 20:45:13 -0700 (PDT) Date: Sat, 31 May 2008 20:45:13 -0700 From: Clint Olsen To: stable@freebsd.org Message-ID: <20080601034513.GI29852@0lsen.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Organization: NULlsen Network X-Disclaimer: Mutt Bites! Cc: Subject: 6.X potentially has messed up sk0 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: Sun, 01 Jun 2008 03:57:57 -0000 Hi: Since upgrading from 5.4-STABLE to 6.2-RELEASE and now 6.3-STABLE, I've noticed that occasionally sk0 goes weird. I don't quite get it. I was able to connect to it via my local network, but routes to my WAN were completely hosed. So, the machine becomes unable to ping or contact anything that crosses 192.168.1.X. Taking down the interface and bringing it back up via ifconfig fixed it. However, I've seen other cases where the machine can eventually get wedged to the point that nothing can bring it back to life. So, the question is, how can I provide the FreeBSD team something tangible in the way of logs or debug information to prove this is a bug? Thanks, -Clint