From: "Alex Braunegg" <alex.braunegg@gmail.com>
To: 'Paul Durrant' <Paul.Durrant@citrix.com>,
'Michael Collins' <mike@ark-net.org>,
'Juergen Gross' <jgross@suse.com>,
xen-devel@lists.xenproject.org
Cc: 'Wei Liu' <wei.liu2@citrix.com>
Subject: Re: [BUG] kernel bug encountered at drivers/net/xen-netback/netback.c:430!
Date: Thu, 4 Jan 2018 05:43:03 +1100 [thread overview]
Message-ID: <5a4d243d.4d78630a.2f9d0.62ad@mx.google.com> (raw)
In-Reply-To: <3f860d32831940e7aa40d97979155b6e@AMSPEX02CL03.citrite.net>
> 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 sent to console / dmesg. I didn’t have to do anything special to trigger it - nor did I try / attempt to trigger it.
When attempting to restart the crashed VM (using xl) - that’s when I got the additional xl messages & the server rebooted.
> This breaks compilation of xen-netback with older compilers.
> >From kbuild bot with gcc-4.4.7:
My Xen version (and all packages other packages including the kernel) are built / rebuilt using gcc 4.6.2 so I don’t think I am hitting this gcc issue that the patch fixed.
Best regards,
Alex
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-01-03 18:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-22 6:40 [BUG] kernel bug encountered at drivers/net/xen-netback/netback.c:430! Alex Braunegg
2017-12-22 6:47 ` Juergen Gross
2017-12-22 20:35 ` Alex Braunegg
2017-12-28 18:05 ` Michael Collins
2017-12-28 19:31 ` Alex Braunegg
2018-01-03 13:54 ` Paul Durrant
2018-01-03 18:43 ` Alex Braunegg [this message]
2018-01-03 20:33 ` Christoph Moench-Tegeder
2018-01-04 10:29 ` Paul Durrant
2018-01-07 22:19 ` 'Christoph Moench-Tegeder'
2018-01-08 9:35 ` Paul Durrant
2018-01-09 9:44 ` Paul Durrant
2018-01-10 12:52 ` Paul Durrant
2018-01-10 13:58 ` Paul Durrant
2018-01-10 17:53 ` 'Christoph Moench-Tegeder'
2018-01-10 19:55 ` Alex Braunegg
-- strict thread matches above, loose matches on Subject: below --
2017-12-20 21:03 Alex Braunegg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5a4d243d.4d78630a.2f9d0.62ad@mx.google.com \
--to=alex.braunegg@gmail.com \
--cc=Paul.Durrant@citrix.com \
--cc=jgross@suse.com \
--cc=mike@ark-net.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.