On 19/12/2019 16:14, Jürgen Groß wrote:
> On 19.12.19 13:45, Sergey Dyasli wrote:
>> Hi Juergen,
>>
>> We recently did another quick test of core scheduling mode, and the following
>> failures were found:
>>
>> 1. live-patch apply failures:
>>
>> (XEN) [ 1058.751974] livepatch: lp_1_1: Timed o
On 20/12/2019 06:26, Jürgen Groß wrote:
> On 19.12.19 13:45, Sergey Dyasli wrote:
>> Hi Juergen,
>>
>> We recently did another quick test of core scheduling mode, and the following
>> failures were found:
>>
>> 1. live-patch apply failures:
>>
>> (XEN) [ 1058.751974] livepatch: lp_1_1: Timed o
On 19.12.19 13:45, Sergey Dyasli wrote:
Hi Juergen,
We recently did another quick test of core scheduling mode, and the following
failures were found:
1. live-patch apply failures:
(XEN) [ 1058.751974] livepatch: lp_1_1: Timed out on semaphore in CPU
quiesce phase 30/31
(XEN) [ 1058
On 19.12.19 13:45, Sergey Dyasli wrote:
Hi Juergen,
We recently did another quick test of core scheduling mode, and the following
failures were found:
1. live-patch apply failures:
(XEN) [ 1058.751974] livepatch: lp_1_1: Timed out on semaphore in CPU
quiesce phase 30/31
(XEN) [ 1058
On 19/12/2019 12:45, Sergey Dyasli wrote:
> 2. ACPI S5 crash:
>
> https://paste.debian.net/1121748/
cmpw $0x7fff,(%rax) with %rax as 0xc2c2c2c2c2c2c2c2
Looks like a use-after-free checking for the idle domain.
~Andrew
___
Xen-devel mailing list
Xe
Hi Juergen,
We recently did another quick test of core scheduling mode, and the following
failures were found:
1. live-patch apply failures:
(XEN) [ 1058.751974] livepatch: lp_1_1: Timed out on semaphore in CPU
quiesce phase 30/31
(XEN) [ 1058.751982] livepatch: lp_1_1 finished REPLACE