On 09/02/2019 18:54, Linus Torvalds wrote:
> On Sat, Feb 9, 2019 at 12:24 AM Sander Eikelenboom
> wrote:
>> I haven't got a reproducer so i might be hard to hit it again,
>> system is AMD and this is from the host kernel running under
>> the Xen hypervisor might it matter.
> I think this is a
On 09/02/2019 19:51, Sander Eikelenboom wrote:
> On 09/02/2019 19:48, Juergen Gross wrote:
>> On 09/02/2019 19:45, Sander Eikelenboom wrote:
>>> On 09/02/2019 09:26, Sander Eikelenboom wrote:
L.S.,
While testing a Linux 5.0-rc5-ish kernel (pull of yesterday) with some
On Sat, Feb 9, 2019 at 12:24 AM Sander Eikelenboom wrote:
>
> I haven't got a reproducer so i might be hard to hit it again,
> system is AMD and this is from the host kernel running under
> the Xen hypervisor might it matter.
I think this is a Xen bug.
In particular, there's a few poison values
On 09/02/2019 19:48, Juergen Gross wrote:
> On 09/02/2019 19:45, Sander Eikelenboom wrote:
>> On 09/02/2019 09:26, Sander Eikelenboom wrote:
>>> L.S.,
>>>
>>>
>>> While testing a Linux 5.0-rc5-ish kernel (pull of yesterday) with some
>>> additional patches for
>>> already reported other issues i
On 09/02/2019 19:45, Sander Eikelenboom wrote:
> On 09/02/2019 09:26, Sander Eikelenboom wrote:
>> L.S.,
>>
>>
>> While testing a Linux 5.0-rc5-ish kernel (pull of yesterday) with some
>> additional patches for
>> already reported other issues i came across the issue below which i haven't
>>
L.S.,
While testing a Linux 5.0-rc5-ish kernel (pull of yesterday) with some
additional patches for
already reported other issues i came across the issue below which i haven't
seen with 4.20.x
I haven't got a reproducer so i might be hard to hit it again,
system is AMD and this is from the
