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 09:19:52 31.172.31.251 [396
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 c
On 22.07.2016 12:21, Ingo Jürgensmann wrote:
On 22.07.2016 11:03, Ingo Jürgensmann wrote:
In the meanwhile, I activated IPv6 again on Tuesday evening and today
the server crashed again some minutes ago. Here's the output from
netconsole:
... and the second subsequent crash:
... and an
On 25.07.2016 12:51, Wei Liu wrote:
[...]
> Your report and the debian report suggested that Dom0 kernel is less
> likely to be the culprit because you've tried different Dom0 kernels.
yes we did. but nothing newer than 3.16 so far, we could try that,
too.
There is a 4.5 backport kernel for Je
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 anyw
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)
Am 10.07.2016 um 00:29 schrieb Andreas Ziegler :
> In May, Ingo Jürgensmann also started experiencing this problem and
> blogged about it:
> https://blog.windfluechter.net/content/blog/2016/03/23/1721-xen-randomly-crashing-server
> https://blog.windfluechter.net/content/blog/2016/05
On 18.07.2016 18:44, Andreas Ziegler wrote:
did the information that Ingo provided (i cited his message to the list
below) maybe help in narrowing down the possible issue?
If you need additional information we can try getting it for you, as
Ingo might be able to reproduce the kernel panic, al
On 22.07.2016 11:03, Ingo Jürgensmann wrote:
In the meanwhile, I activated IPv6 again on Tuesday evening and today
the server crashed again some minutes ago. Here's the output from
netconsole:
... and the second subsequent crash:
Jul 22 11:15:04 31.172.31.251 [ 2774.896036] BUG: unab
