On Wed, Oct 13, 2021 at 07:35:48PM +0200, Sebastian Andrzej Siewior wrote: > On 2021-10-13 14:57:34 [+0200], Daniel Vetter wrote: > > Hm there's a pile of commits there, and nothing immediately jumps to > > light. The thing is, 18 is likely way too much, since if e.g. we have a > > single new property on a plane and that pushes over the limit on all of > > them, you get iirc 3x4 already simply because we have that many planes. > > > > So would be good to know the actual culprit. > > > > Can you pls try to bisect the above range, applying the patch as a fixup > > locally (without commit, that will confuse git bisect a bit I think), so > > we know what/where went wrong? > > c7fcbf2513973 -> does not boot > c7fcbf2513973 + 2f425cf5242a0 -> boots, 18 x DRM_OBJECT_MAX_PROPERTY > 6f11f37459d8f -> boots, 0 x DRM_OBJECT_MAX_PROPERTY > 6f11f37459d8f + 2f425cf5242a0 -> boots, 18 x DRM_OBJECT_MAX_PROPERTY Just to check, you've built 6f11f37459d8f, and then you cherry-picked 2f425cf5242a0 on top (not merged), and that already got you the warning flood? I'm probably blind, but I'm really not seeing where this pile of properties is coming from. Can you pls also boot with drm.debug=0xe and attach full dmesg? Plus your .config please. Thanks, Daniel > > > I'm still confused why this isn't showing up anywhere in our intel ci ... > > > > Thanks, Daniel > > Sebastian -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch
