Re: drm_modeset_lock oops in next

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



* Maarten Lankhorst <maarten.lankhorst@xxxxxxxxxxxxxxx> [170408 01:55]:
> Hey,
> 
> Op 07-04-17 om 17:56 schreef Tony Lindgren:
> > Hi,
> >
> > Looks like current next now oopses at least for omapdrm
> > when starting X. Reverting commit d20afeb3e2f9 ("Merge
> > remote-tracking branch 'drm-misc/for-linux-next'") makes
> > things work again.
> >
> > Any ideas what might be causing the oops below?
> Looks like fallout from the acquire_ctx patches?
> 
> Could you test the below?

Yes thanks Daniel Vetter already posted a similar fix as
"[PATCH] drm: Only take cursor locks when the cursor plane exists".

Regards,

Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux