Date: Tue, 7 Jan 2014 09:20:35 +0100 From: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= <roger.pau@citrix.com> To: Mike C. <miguelmclara@gmail.com>, <freebsd-xen@freebsd.org> Subject: Re: Panic with FreeBSD 10 RC2 on Netbsd Xen dom0 Message-ID: <52CBB8D3.8090508@citrix.com> In-Reply-To: <52B2AC26.2020301@citrix.com> References: <20131218001615.GA10501@moore.morphism.de> <FD2319E7-8703-46A8-91A7-AAD491AC56FA@gmail.com> <52B24E18.7090109@gmail.com> <52B2AC26.2020301@citrix.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?52CBB8D3.8090508>