> Actually no need... The underlying issue was really a bug and has
> been fixed in 4.14.11.
Thanks for tracking this down & spending time looking at this Paul.
Best regards,
Alex
___
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://l
## Paul Durrant (paul.durr...@citrix.com):
> Actually no need... The underlying issue was really a bug and has
> been fixed in 4.14.11.
Oh. That explains why reverting the other patch "fixed" the problem -
I had skipped 4.14.10 and 4.14.11 - and the problem has gone away
independently of that.
Co
'Alex Braunegg'
> ; xen-devel@lists.xenproject.org
> Subject: Re: [Xen-devel] [BUG] kernel bug encountered at drivers/net/xen-
> netback/netback.c:430!
>
> I have tracked down the problem to multiple calls to the zerocopy callback for
> the same ubuf_info. I am not sure ex
I have tracked down the problem to multiple calls to the zerocopy callback for
the same ubuf_info. I am not sure exactly which patch introduced the issue but
my suspicion is that it was one of the the MSG_ZEROCOPY series (see
https://marc.info/?l=linux-netdev&m=149807997726733&w=2).
I have a can
I finally have a reliable repro and and it's trivial...
Just try to copy a large file out of a Windows VM to an SMB share (using PV
drivers in the VM). Dom0 goes bang pretty much immediately. I get another BUG
too on another CPU...
[ 1062.422497] [ cut here ]
[ 1062.4225
ts.xenproject.org
> Subject: Re: [Xen-devel] [BUG] kernel bug encountered at drivers/net/xen-
> netback/netback.c:430!
>
> ## Paul Durrant (paul.durr...@citrix.com):
>
> > > I could try a new kernel (KPTI, yay!) with that "mildly suspicious" commit
> > > cc8
## Paul Durrant (paul.durr...@citrix.com):
> > I could try a new kernel (KPTI, yay!) with that "mildly suspicious" commit
> > cc8737a5fe9051b7fa052b08c57ddb9f539c389a reverted on the weekend and
> > report back (just to rule that out - like you, I don't really believe
> > that this is the cause).
ei Liu
> Subject: Re: [Xen-devel] [BUG] kernel bug encountered at drivers/net/xen-
> netback/netback.c:430!
>
> ## Paul Durrant (paul.durr...@citrix.com):
>
> > How easy is it to trigger this? I'm assuming, from the original
> > description, that I can probably tr
## Paul Durrant (paul.durr...@citrix.com):
> How easy is it to trigger this? I'm assuming, from the original
> description, that I can probably trigger it by forcibly terminating
> a running domain and then trying to restart it.
As Alex said: in the "common cases" (like his and mine) it seems to
> How easy is it to trigger this? I'm assuming, from the original description,
> that I can probably trigger it by forcibly terminating a running domain and
> then trying to restart it.
For me the trigger was just having 2 VM's running and then within 24 hr's one
would crash with the debug data
> -Original Message-
> From: Alex Braunegg [mailto:alex.braun...@gmail.com]
> Sent: 28 December 2017 19:32
> To: 'Michael Collins' ; 'Juergen Gross'
> ; xen-devel@lists.xenproject.org
> Cc: Paul Durrant ; Wei Liu
> Subject: RE: [Xen-devel] [BUG]
/0x230 [xen_netback] RSP: c90001f67c68
> ---[ end trace 130de0b7e39d0eea ]---
>
> Best regards,
>
> Alex
>
>
>
> -Original Message-----
> From: Juergen Gross [mailto:jgr...@suse.com]
> Sent: Friday, 22 December 2017 5:47 PM
> To: Alex Braunegg; xen-devel@l
ntered at
drivers/net/xen-netback/netback.c:430!
On 22/12/17 07:40, Alex Braunegg wrote:
Hi all,
Experienced the same issue again today:
Ccing the maintainers.
Juergen
=
vif vif-2-0 vif2.0: Trying to unmap i
ubject: Re: [Xen-devel] [BUG] kernel bug encountered at
drivers/net/xen-netback/netback.c:430!
On 22/12/17 07:40, Alex Braunegg wrote:
> Hi all,
>
> Experienced the same issue again today:
Ccing the maintai
On 22/12/17 07:40, Alex Braunegg wrote:
> Hi all,
>
> Experienced the same issue again today:
Ccing the maintainers.
Juergen
>
>
> =
>
> vif vif-2-0 vif2.0: Trying to unmap invalid handle! pending_idx: 0x2f
Hi all,
Experienced the same issue again today:
=
vif vif-2-0 vif2.0: Trying to unmap invalid handle! pending_idx: 0x2f
[ cut here ]
kernel BUG at drivers/net/xen-netback/netback.c:430!
i
Hi all,
I experienced the following bug whilst using a Xen VM. What happened was
that this morning a single Xen VM suddenly terminated without cause with the
following being logged in dmesg.
Only 1 VM experienced an issue (out of 2 which were running), the other
remained up and fully functional
17 matches
Mail list logo
