On Mon, Dec 2, 2013 at 10:53 AM, Paul Bolle <[email protected]> wrote: > On Mon, 2013-12-02 at 08:33 +0100, Daniel Vetter wrote: >> On Sun, Dec 1, 2013 at 5:57 PM, Paul Bolle <[email protected]> wrote: >> > The WARNING is now gone during suspend and resume (having tested that >> > thoroughly - ie, twice). But I still see it at boot. Is there a related >> > fix for that WARNING during boot? >> >> Hm, I've never seen it during boot. Can you please boot with >> drm.debug=0xe and attach the dmesg with the WARN? > > Sure. > > This generated quite a bit of debug messages so I only copied the > WARNING and the drm (related) messages immediately preceding it. Please > feel free to prod again if that's insufficient.
Yeah, the beginning of the drm message would are wanted since I need to know what exactly your hardware claims to support ;-) But the backtrace confirms my first hunch for now ... Just want to confirm before sending out a patch with commit message. -Daniel -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
