From owner-freebsd-xen@FreeBSD.ORG Tue Jan 7 08:20:40 2014 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B49CE19F for ; Tue, 7 Jan 2014 08:20:40 +0000 (UTC) Received: from SMTP02.CITRIX.COM (smtp02.citrix.com [66.165.176.63]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0EF441D6F for ; Tue, 7 Jan 2014 08:20:39 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.95,617,1384300800"; d="scan'208";a="88190503" Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP; 07 Jan 2014 08:20:33 +0000 Received: from [IPv6:::1] (10.80.16.47) by smtprelay.citrix.com (10.13.107.80) with Microsoft SMTP Server id 14.2.342.4; Tue, 7 Jan 2014 03:20:32 -0500 Message-ID: <52CBB8D3.8090508@citrix.com> Date: Tue, 7 Jan 2014 09:20:35 +0100 From: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Mike C. , Subject: Re: Panic with FreeBSD 10 RC2 on Netbsd Xen dom0 References: <20131218001615.GA10501@moore.morphism.de> <52B24E18.7090109@gmail.com> <52B2AC26.2020301@citrix.com> In-Reply-To: <52B2AC26.2020301@citrix.com> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-DLP: MIA2 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.17 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, 07 Jan 2014 08:20:40 -0000 On 19/12/13 09:19, Roger Pau Monné wrote: > On 19/12/13 02:38, Mike C. wrote: >> I've reported this to xen-devel I while ago. >> >> >> It worked in the first FreeBSD-10 current releases but them it stoped, I >> believe a previous issue was re-introduced somehow! >> >> NetBSD Xen backend does not support TSO/GSO at all, there was a very >> similar problem in FreeBSD 9 a while a go, and my guess is that the code >> tried to use TSO again, and leads to problems if the Dom0 is NetBSD. >> >> >> Also more recently I had problems with Windows GPLPV drivers, and the >> dev tracked the issue to the same.. however in windows DomU's if I >> disabled TSO it would work. >> In FreeBSD at least until Aplha 5, I tried to disable TSO but it still >> wouldn't work. > > By looking at relevant commits in netfront, could you try to revert > r251297 and see if that solves the problem? Also, doing a bisect of the > commits in netfront would be very helpful in order to identify the issue. Ping? Any news on this? Roger.