From owner-freebsd-current@FreeBSD.ORG Fri Oct 17 22:49:50 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D5E431065686 for ; Fri, 17 Oct 2008 22:49:50 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from mail.digiware.nl (www.tegenbosch28.nl [217.21.251.97]) by mx1.freebsd.org (Postfix) with ESMTP id 8C88B8FC18 for ; Fri, 17 Oct 2008 22:49:50 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from localhost (localhost.digiware.nl [127.0.0.1]) by mail.digiware.nl (Postfix) with ESMTP id 95F13173B4 for ; Sat, 18 Oct 2008 00:20:53 +0200 (CEST) X-Virus-Scanned: amavisd-new at digiware.nl Received: from mail.digiware.nl ([127.0.0.1]) by localhost (rack1.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9YnbnHSFQICs for ; Sat, 18 Oct 2008 00:20:46 +0200 (CEST) Received: from [192.168.2.10] (vaio [192.168.2.10]) by mail.digiware.nl (Postfix) with ESMTP id B581017155 for ; Sat, 18 Oct 2008 00:20:46 +0200 (CEST) Message-ID: <48F90FC1.3040503@digiware.nl> Date: Sat, 18 Oct 2008 00:20:49 +0200 From: Willem Jan Withagen Organization: Digiware Management User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Fri, 17 Oct 2008 23:00:45 +0000 Cc: Subject: Freezing or stalling current system X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Oct 2008 22:49:50 -0000 I first tought is was because I was trying to get to run a kernel under XEN on Ubuntu, but now I have the same problem on a spare dual opteron system.... What happens is that the system runs for a while especially if the network is not connected. The network on the opteron is a bge 5705 onboard chip. XEN uses the xn0 xen-device. Once the network is fired up it does not take too long for the system to "Freeze". On the XEN system I could get thing running again most of the time by just pressing ^T. That would get packets reflowing. I'm using nfs/tcp mounted disks and rsync. On the opteron system things are a little harder to get it revived. - Some of the freezes are hard. Can't break into the debugger with the keyboard. Left the system over night,but it never got back to live. - Some of the freezes are not real freezes but things just stall for a while and then continue again.... - Some freezes let me allow to break into the debugger, and then just going 'cont' gets the things going for a short while. I'm sort of assuming that the bge0: timeouts and coalesced links are due to the freezing. So my very amature conclussion is that things are "deadlocked" somewhere. But I need some guidance to be able to give more usefull info. I anyone wants to hold my hand, I'll set it up with a serial console and hook it up to another system for easier logging. --WjW