Thursday, December 1, 2016, 2:59:36 PM, you wrote:
> 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?
>
On Thu, Dec 01, 2016 at 02:59:36PM +0100, Ingo Jürgensmann wrote:
> 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 gu
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 Tue, Nov 29, 2016 at 09:20:55PM +0100, Ingo Jürgensmann wrote:
> 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:
>
This is still the same kernel log that was sent some time ago.
So, if you have b
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 Mon, Nov 14, 2016 at 04:55:40PM +0100, Andreas Ziegler wrote:
> Hi,
>
> few months later Ingo decided again to give it a try as he really
> doesn't want to keep ipv6 disabled in 2016.
> He tried Xen 4.8 - which didn't help, the crash reappeared.
> He then managed to build Xen with debug=y and s
- Original-Nachricht --------
Betreff: Re: [Xen-devel] Kernel panic on Xen virtualisation in Debian
Von: Wei Liu
An: Ingo Jürgensmann
Datum: 2.8.2016, 14:37:58
> On Tue, Aug 02, 2016 at 12:30:30PM +0200, Ingo Jürgensmann wrote:
>> On 02.08.2016 11:20, Wei Liu wrote:
>>> On Fri, Jul 29, 2016
On Tue, Aug 02, 2016 at 12:30:30PM +0200, Ingo Jürgensmann wrote:
> 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 segfaul
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 Fri, Jul 29, 2016 at 10:17:22PM +0200, Ingo Jürgensmann wrote:
> Am 29.07.2016 um 13:45 schrieb Andreas Ziegler :
>
> > we tried with kernel 4.6 now, the crashed happened again, though.
>
> Please find attached the netconsole log of 3 from 4 crashes so far today…
What is also interesting is
On Fri, Jul 29, 2016 at 01:45:55PM +0200, Andreas Ziegler wrote:
> Hello Wei,
>
> we tried with kernel 4.6 now, the crashed happened again, though.
>
> next we want to try the Xen debug build, but we couldn't find any
> information on how to enable debug for the build, perhaps you could give
> us
[Xen-devel] Kernel panic on Xen virtualisation in Debian
Von: Wei Liu
An: Ingo Jürgensmann
Datum: 25.7.2016, 15:13:06
> On Mon, Jul 25, 2016 at 01:41:41PM +0200, Ingo Jürgensmann wrote:
>> On 25.07.2016 12:23, Wei Liu wrote:
>>
>> First, thank you for replying! Very much ap
On Mon, Jul 25, 2016 at 01:41:41PM +0200, Ingo Jürgensmann wrote:
> 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 wou
Monday, July 25, 2016, 1:27:20 PM, you wrote:
> 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,
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 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 Mon, Jul 25, 2016 at 12:42:39PM +0200, Andreas Ziegler wrote:
> > On Mon, Jul 25, 2016 at 11:38:20AM +0200, Ingo Jürgensmann wrote:
> >> 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 Tuesda
>> 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.
i have to correct myself:
we also tried 4.4 a while ago, maybe we should try
On 25/07/16 10:38, Ingo Jürgensmann wrote:
> 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
> On Mon, Jul 25, 2016 at 11:38:20AM +0200, Ingo Jürgensmann wrote:
>> 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
On Mon, Jul 25, 2016 at 11:38:20AM +0200, Ingo Jürgensmann wrote:
> 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 ou
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 another c
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: unable to han
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
Hi everyone,
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, although not reliably.
by the way, I
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/12/1723-xen-ra
: [Xen-devel] Kernel panic on Xen virtualisation in Debian
Von: Jan Prunk
An: Wei Liu
Datum: Fri, 8 Jul 2016 14:22:37 +0200
> Hello,
>
> Please also send a CC: to 804...@bugs.debian.org
> <mailto:804...@bugs.debian.org> for future reference.
> The administrator of the server i
Hello,
Please also send a CC: to 804...@bugs.debian.org for future reference.
The administrator of the server is Andreas Ziegler ,
maybe he will be able to log/reproduce the bug, I was only an initial
reporter.
Kind regards,
Jan
On Fri, Jul 8, 2016 at 1:14 PM, Wei Liu wrote:
> On Wed, Jul 06,
On Wed, Jul 06, 2016 at 03:14:15PM +0100, George Dunlap wrote:
> On Mon, Jul 4, 2016 at 7:06 PM, Jan Prunk wrote:
> > Hello !
> >
> > I am posting Xen virtualisation bug links to this e-mail address,
> > because I wasn't able to find the Xen specific bugtracker list.
> > This bug has been discover
On Mon, Jul 4, 2016 at 7:06 PM, Jan Prunk wrote:
> Hello !
>
> I am posting Xen virtualisation bug links to this e-mail address,
> because I wasn't able to find the Xen specific bugtracker list.
> This bug has been discovered in 2015 and so far it hasn't been
> resolved through the Debian/Kernel b
Hello !
I am posting Xen virtualisation bug links to this e-mail address,
because I wasn't able to find the Xen specific bugtracker list.
This bug has been discovered in 2015 and so far it hasn't been
resolved through the Debian/Kernel bug lists. I submit the
links to bug reports for you.
https:/
31 matches
Mail list logo
