On 01.12.2016 14:26, Wei Liu wrote:
This is still the same kernel log that was sent some time ago.
So, if you have built Xen with debug=y, could you try to set Xen log
level to the highest and capture "xl dmesg" when guest crashes?
It's not the guest that crashes, it's dom0. So when the host
Am 29.11.2016 um 10:08 schrieb Wei Liu :
>> http://paste.debian.net/895464/
> Entry not found -- maybe it expired... Sorry.
Here it is:
Nov 14 09:19:52 31.172.31.251 [39677.027813] BUG: unable to handle kernel
Nov 14 09:19:52 31.172.31.251 at 880002b4c06e
Nov 14
On 02.08.2016 11:20, Wei Liu wrote:
On Fri, Jul 29, 2016 at 10:17:22PM +0200, Ingo Jürgensmann wrote:
What is also interesting is that you seem to be running some sort of
ip accounting software (pmacctd) which also segfault'ed.
Yeah, it is segfaulting, because the database (in a domU VM) where
On 25.07.2016 12:23, Wei Liu wrote:
First, thank you for replying! Very much appreciated! :)
I did skim your emails. But the oops was happening in memcpy+0x6 which
indicated it came back to the origin question why would it got an
exception there.
Just by staring at the code doesn't get me
Hi!
In an effort to avoid crashes due to this bug, I installed 4.5.0-0.bpo.1-amd64
last week. The server ran in the last week quite well with activated IPv6,
but today it crashed two times within 30 mins.
Please find attached the syslog output send out via netconsole...
--
Ciao...
Hi!
After contributing to this bug on Thursday, my server kept crashing on Friday
several times, even within 5 minutes after rebooting. Really, really annoying.
However I managed to deactivate my IPv6 routing on the Xen bridge. @Jan: can
you please, if possible, if this helps for you, too?
Am 04.07.2013 um 05:42 schrieb Ben Hutchings b...@decadent.org.uk:
My understanding is that disabling scatter/gather on netfront in domU
(ethtool -K eth0 sg off) will prevent it from triggering these bugs, but
at a substantial performance impact. In practice, disabling TSO in domU
(ethtool
7 matches
Mail list logo