From owner-freebsd-xen@FreeBSD.ORG Sat Mar 13 21:41:32 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 C66E81065672 for ; Sat, 13 Mar 2010 21:41:32 +0000 (UTC) (envelope-from robert@ml.erje.net) Received: from smtp-vbr12.xs4all.nl (smtp-vbr12.xs4all.nl [194.109.24.32]) by mx1.freebsd.org (Postfix) with ESMTP id 593B08FC1D for ; Sat, 13 Mar 2010 21:41:32 +0000 (UTC) Received: from xykert.erje.net (erje.net [80.126.62.176]) by smtp-vbr12.xs4all.nl (8.13.8/8.13.8) with ESMTP id o2DLTlJE072422 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Sat, 13 Mar 2010 22:29:48 +0100 (CET) (envelope-from robert@ml.erje.net) Received: from ismet.erje.net (ismet.erje.net [IPv6:2001:888:1f33::8e45:5e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by xykert.erje.net (PostFix 2.6.5) with ESMTPS id 5B8A392E70D for ; Sat, 13 Mar 2010 22:29:31 +0100 (CET) Received: (from robert@localhost) by ismet.erje.net (8.14.3/8.14.3/Submit) id o2DLTVCl008162 for freebsd-xen@freebsd.org; Sat, 13 Mar 2010 22:29:31 +0100 (CET) (envelope-from robert@ml.erje.net) X-Authentication-Warning: ismet.erje.net: robert set sender to robert@ml.erje.net using -f Date: Sat, 13 Mar 2010 22:29:30 +0100 From: Robert Joosten To: freebsd-xen@freebsd.org Message-ID: <20100313212930.GF2160@ismet.erje.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.20 (2009-06-14) X-erje-MailScanner-Information: support@erje.net X-erje-MailScanner-ID: 5B8A392E70D.91F17 X-erje-MailScanner: Ok found to be clean X-Spam-Status: No X-Virus-Scanned: by XS4ALL Virus Scanner Subject: problemreports here or file PR ? (was: Re: Kernel panics on 9-CURRENT) 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: Sat, 13 Mar 2010 21:41:32 -0000 Hi, > My 9-CURRENT XEN box periodically panics on intensive net load, for > example on doing csup ports. Previously I was using 8-STABLE, and kernel > panics too, but currently I can't provide a report for this. Hmm, my 8stable doesn't even start (old P4 hardware, vanilla debian lenny x86), where both 8.0rel and 9 do (all images were created on the same buildbox...). My 9 also crashes, it's quite reproducable with csup. I still need to compile the latest xen manually, maybe things are already fixed up. But now a more household question: do we need to report crashes here, or should we file a PR ? And in which category are we expected to dump backtraces ? I would opt a new category called 'xen' 8-) Any insight would be helpful. This specific dev box will be taken into use (jail server, because xen doens't prove to be ready as of yet) soon, but I have an, even older hahaha, box ready to continue fiddling with xen exclusively. Regards, Robert