Re: drm_modeset_lock oops in next

2017-04-10 Thread Maarten Lankhorst
Op 08-04-17 om 18:46 schreef Tony Lindgren: > * Maarten Lankhorst [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

Re: drm_modeset_lock oops in next

2017-04-09 Thread Tony Lindgren
* Maarten Lankhorst [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 wor

Re: drm_modeset_lock oops in next

2017-04-08 Thread Maarten Lankhorst
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 b

drm_modeset_lock oops in next

2017-04-07 Thread 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? Regards, Tony 8< -- Internal er