On 28/02/2019 11:13, Marc Zyngier wrote:
> On 28/02/2019 08:49, Marc Zyngier wrote:
>> On Thu, 28 Feb 2019 08:16:05 +,
>> Greg KH wrote:
>>
>> Hi both,
>>
>>>
>>> On Wed, Feb 27, 2019 at 04:36:39PM -0800, Daniel Verkamp wrote:
Hello,
In my testing of crosvm[1] with Linux 4.4.175
On 28/02/2019 08:49, Marc Zyngier wrote:
> On Thu, 28 Feb 2019 08:16:05 +,
> Greg KH wrote:
>
> Hi both,
>
>>
>> On Wed, Feb 27, 2019 at 04:36:39PM -0800, Daniel Verkamp wrote:
>>> Hello,
>>>
>>> In my testing of crosvm[1] with Linux 4.4.175, I am observing failures
>>> on a 'kevin' Chromebo
On Thu, 28 Feb 2019 08:16:05 +,
Greg KH wrote:
Hi both,
>
> On Wed, Feb 27, 2019 at 04:36:39PM -0800, Daniel Verkamp wrote:
> > Hello,
> >
> > In my testing of crosvm[1] with Linux 4.4.175, I am observing failures
> > on a 'kevin' Chromebook (RK3399) device - the guest kernel does not
> >
On Wed, Feb 27, 2019 at 04:36:39PM -0800, Daniel Verkamp wrote:
> Hello,
>
> In my testing of crosvm[1] with Linux 4.4.175, I am observing failures
> on a 'kevin' Chromebook (RK3399) device - the guest kernel does not
> even get to the point of printing its first messages, and the host
> seems to
Hello,
In my testing of crosvm[1] with Linux 4.4.175, I am observing failures
on a 'kevin' Chromebook (RK3399) device - the guest kernel does not
even get to the point of printing its first messages, and the host
seems to be spinning at 100% CPU in KVM_RUN.
I narrowed this down to the 4.4 stable
