Panic with FreeBSD 10 RC2 on Netbsd Xen dom0

[Mike C.]

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 at 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.