On Sun, Mar 03 2019 at 12:06pm -0500,
Alexander Duyck wrote:
> On Sat, Mar 2, 2019 at 7:48 PM Mike Snitzer wrote:
> >
> > On Sat, Mar 02 2019 at 6:34pm -0500,
> > Alexander Duyck wrote:
> >
> > > So I have been seeing an issue with an intermittent boot hang on my
> > > x86 KVM VM with the late
On Sun, Mar 03 2019 at 12:06pm -0500,
Alexander Duyck wrote:
> Thanks. The behavior of it has me wondering if we are looking at
> something like an uninitialized data issue or something like that
> since as I mentioned I don't see this occur on every boot, just on
> most of them. So every now and
On Sat, Mar 2, 2019 at 7:48 PM Mike Snitzer wrote:
>
> On Sat, Mar 02 2019 at 6:34pm -0500,
> Alexander Duyck wrote:
>
> > So I have been seeing an issue with an intermittent boot hang on my
> > x86 KVM VM with the latest linux-next and have bisected it down to the
> > following commit:
> > 1efa
On Sat, Mar 02 2019 at 6:34pm -0500,
Alexander Duyck wrote:
> So I have been seeing an issue with an intermittent boot hang on my
> x86 KVM VM with the latest linux-next and have bisected it down to the
> following commit:
> 1efa3bb79d3de8ca1b7f6770313a1fc0bebe25c7 is the first bad commit
> comm
So I have been seeing an issue with an intermittent boot hang on my
x86 KVM VM with the latest linux-next and have bisected it down to the
following commit:
1efa3bb79d3de8ca1b7f6770313a1fc0bebe25c7 is the first bad commit
commit 1efa3bb79d3de8ca1b7f6770313a1fc0bebe25c7
Author: Mike Snitzer
Date:
5 matches
Mail list logo