On Mon, 2018-06-18 at 12:33 +1000, Dave Airlie wrote:
> On 17 June 2018 at 21:02, Greg KH wrote:
> > On Sun, Jun 17, 2018 at 12:38:06PM +0200, Mike Galbraith wrote:
> >> On Sun, 2018-06-17 at 11:36 +0200, Greg KH wrote:
> >> >
> >> > And if you revert that patch, does everything work again?
> >>
On 17 June 2018 at 21:02, Greg KH wrote:
> On Sun, Jun 17, 2018 at 12:38:06PM +0200, Mike Galbraith wrote:
>> On Sun, 2018-06-17 at 11:36 +0200, Greg KH wrote:
>> >
>> > And if you revert that patch, does everything work again?
>>
>> Yes.
>
> Great, Dave, care to revert this in 4.18 so I can
On Sun, Jun 17, 2018 at 12:38:06PM +0200, Mike Galbraith wrote:
> On Sun, 2018-06-17 at 11:36 +0200, Greg KH wrote:
> >
> > And if you revert that patch, does everything work again?
>
> Yes.
Great, Dave, care to revert this in 4.18 so I can queue up that revert
in older kernels as well?
On Sun, 2018-06-17 at 11:36 +0200, Greg KH wrote:
>
> And if you revert that patch, does everything work again?
Yes.
-Mike
___
Virtualization mailing list
Virtualization@lists.linux-foundation.org
On Sat, Jun 16, 2018 at 05:39:11PM +0200, Mike Galbraith wrote:
> Greetings,
>
> Running a kernel with ATOMIC_SLEEP enabled in one of my VMs, I met the
> splat below. I tracked it back to 4.14-stable, and bisected it there.
Why does your virtual machine use a drm driver? Ah, it's a driver for
