Date: Tue, 07 Jan 2014 12:30:05 +0000 From: "Mike C." <miguelmclara@gmail.com> To: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= <roger.pau@citrix.com>, freebsd-xen@freebsd.org Subject: Re: Panic with FreeBSD 10 RC2 on Netbsd Xen dom0 Message-ID: <6153b6b3-8ea9-4dc8-b039-7ab678e33b5e@email.android.com> In-Reply-To: <52CBB8D3.8090508@citrix.com> References: <20131218001615.GA10501@moore.morphism.de> <FD2319E7-8703-46A8-91A7-AAD491AC56FA@gmail.com> <52B24E18.7090109@gmail.com> <52B2AC26.2020301@citrix.com> <52CBB8D3.8090508@citrix.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Without network reverting to previous commits to test is painful. I tried some before not that one specifically but I do know for sure that somewhere before that release it was working. I have to find some time to make a IMG with that release from my laptop, sadly the laptop is just going to repair because I'm having disk read issues so I won't be able to do it this week, maybe someone else can try? >From the commit however it does seems like the code assumes tso features are available? but I'm not that much of a coder just guessing. That would explain however why even if I disable tso in the domu it still fails. Sorry if the feedback is not much helpful at this time and thanks for following up on this. "Roger Pau Monné" <roger.pau@citrix.com> wrote: >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. -- Sent from my Android device with K-9 Mail. Please excuse my brevity. From owner-freebsd-xen@FreeBSD.ORG Tue Jan 7 14:28:04 2014 Return-Path: <owner-freebsd-xen@FreeBSD.ORG> Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 581CD3A8 for <freebsd-xen@freebsd.org>; Tue, 7 Jan 2014 14:28:04 +0000 (UTC) Received: from mail-ee0-f43.google.com (mail-ee0-f43.google.com [74.125.83.43]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id DC73C1CFF for <freebsd-xen@freebsd.org>; Tue, 7 Jan 2014 14:28:03 +0000 (UTC) Received: by mail-ee0-f43.google.com with SMTP id c13so108051eek.30 for <freebsd-xen@freebsd.org>; Tue, 07 Jan 2014 06:27:55 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=oJrmNayZ7gcSCDVuYE0I7/7StUnf4uKZIdoVqCdk1rs=; b=O92EWoPkEUSSOLddrIBEKBpPdZWE3ni2CeknH9N2FcZ7gVuwlh+DaCDNKKQ7V8Ghu2 Dx6D4qRpBXp4nov20X0PHgvVb+WLlE3YMXP7yqPczHA0ebHBOoZb2FQKtb9772+ThTQX Rlz9A6hjjjUjiUqJjap3nZX+JiMC1GLdBJZ7wNtUtQNiDTxFsQid77CtJLZj5kbS9TwF JWVMv4xwilWZiHol+kSs9KiVrqzB3sya59MiX4PH6COMMjBNwDJCb6+Jp7x9cbEjf2Hm uuykgvGVA3rwoiQLPnVBXpgbG2Kb0o0VZRiJ+ddHjlQpd3R4opB/HTHG4SEFSYz/kkQa P7vw== X-Gm-Message-State: ALoCoQmCOtZRitCdjelSDdGkz1CTNu6EKkhijmuWmyqAYGdhy5X2owyUp4HWroRFN9uHqHRQ5alw X-Received: by 10.14.99.66 with SMTP id w42mr90958eef.63.1389104875724; Tue, 07 Jan 2014 06:27:55 -0800 (PST) Received: from [10.80.2.139] ([185.25.64.249]) by mx.google.com with ESMTPSA id 7sm35571011eee.12.2014.01.07.06.27.54 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 07 Jan 2014 06:27:54 -0800 (PST) Message-ID: <52CC0EE8.6060205@linaro.org> Date: Tue, 07 Jan 2014 14:27:52 +0000 From: Julien Grall <julien.grall@linaro.org> User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20131104 Icedove/17.0.10 MIME-Version: 1.0 To: =?UTF-8?B?Um9nZXIgUGF1IE1vbm7DqQ==?= <roger.pau@citrix.com> Subject: Re: [Xen-devel] [PATCH v9 15/19] xen: create a Xen nexus to use in PV/PVH References: <1388677433-49525-1-git-send-email-roger.pau@citrix.com> <1388677433-49525-16-git-send-email-roger.pau@citrix.com> <52C9D4CA.6070403@linaro.org> <52CA78DE.9060502@citrix.com> <52CA9481.4090703@linaro.org> <52CBBB05.6020104@citrix.com> In-Reply-To: <52CBBB05.6020104@citrix.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Cc: jhb@freebsd.org, xen-devel@lists.xen.org, julien.grall@citrix.com, freebsd-xen@freebsd.org, freebsd-current@freebsd.org, kib@freebsd.org, gibbs@freebsd.org 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 <freebsd-xen.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-xen>, <mailto:freebsd-xen-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-xen/>; List-Post: <mailto:freebsd-xen@freebsd.org> List-Help: <mailto:freebsd-xen-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-xen>, <mailto:freebsd-xen-request@freebsd.org?subject=subscribe> X-List-Received-Date: Tue, 07 Jan 2014 14:28:04 -0000 On 01/07/2014 08:29 AM, Roger Pau Monné wrote: > On 06/01/14 12:33, Julien Grall wrote: >> >> >> On 01/06/2014 09:35 AM, Roger Pau Monné wrote: >>> On 05/01/14 22:55, Julien Grall wrote: >>>> >>>> >>>> On 01/02/2014 03:43 PM, Roger Pau Monne wrote: >>>>> Introduce a Xen specific nexus that is going to be in charge for >>>>> attaching Xen specific devices. >>>> >>>> Now that we have a xenpv bus, do we really need a specific nexus for >>>> Xen? >>>> We should be able to use the identify callback of xenpv to create the >>>> bus. >>>> >>>> The other part of this patch can be merged in the patch #14 "Introduce >>>> xenpv bus and a dummy pvcpu device". >>> >>> On x86 at least we need the Xen specific nexus, or we will fall back to >>> use the legacy nexus which is not what we really want. >>> >> >> Oh right, in any case can we use the identify callback of xenpv to add >> the bus? > > AFAICT this kind of bus devices don't have a identify routine, and they > are usually added manually from the specific nexus, see acpi or legacy. > Could you add the device on ARM when you detect that you are running as > a Xen guest, or in the generic ARM nexus if Xen is detected? Is there any reason to not add identify callback? If it's possible, I would like to avoid as much as possible #ifdef XENHVM in ARM code. -- Julien Grall
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6153b6b3-8ea9-4dc8-b039-7ab678e33b5e>