From owner-freebsd-xen@FreeBSD.ORG Tue Dec 21 04:21:38 2010 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8DB7A106564A for ; Tue, 21 Dec 2010 04:21:38 +0000 (UTC) (envelope-from joovke@joovke.com) Received: from one.digitalpacific.com.au (one.digitalpacific.com.au [203.19.59.9]) by mx1.freebsd.org (Postfix) with ESMTP id 1D3858FC15 for ; Tue, 21 Dec 2010 04:21:37 +0000 (UTC) X-ClientAddr: 150.101.205.12 Received: from [127.0.0.1] (eth525.nsw.adsl.internode.on.net [150.101.205.12]) (authenticated bits=0) by one.digitalpacific.com.au (8.13.8/8.13.8) with ESMTP id oBL3eKcI024929 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for ; Tue, 21 Dec 2010 14:40:22 +1100 Message-ID: <4D0F78A6.4070204@joovke.com> Date: Tue, 21 Dec 2010 02:39:18 +1100 From: Alex User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: freebsd-xen@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DigitalPacific-MailScanner-Information: Please contact support@digitalpacific.com.au for more information X-DigitalPacific-MailScanner-ID: oBL3eKcI024929 X-DigitalPacific-MailScanner: Found to be clean X-DigitalPacific-MailScanner-From: joovke@joovke.com X-Spam-Status: No Subject: Re: lockups/freezes/pauses - 8.1-release/amd64 + XEN X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Dec 2010 04:21:38 -0000 Found something interesting from an email sent by the daily cron: Name Mtu Network Address Ipkts Ierrs Idrop Opkts Oerrs Coll re0 1500 00:16:3e:f0:8b:6c 160763 0 0 12053 0 12024 Uptime is about a day, 12024 collisions. That couldnt be good! Houston we have a problem. Now whether this is a bug with the re() driver or a side effect of something else, I dont know.