On pátek 15. července 2016 4:17 Felix Miata wrote:
BTW, "DWARF2 unwinder stuck" is near the tail of the Call Trace that occurs on every 13.2, 42.1 and TW boot on Intel video host gx780. The search intent was to find some kind of clue to making these oopses stop happening, but I'm having no luck figuring out where to start.
The "unwinder stuck" message has nothing to do with the WARN_ON check you are hitting. Unwinder is the code that tries to present your kernel stack in a human readable form _after_ the problem happened. The message means it has trouble to follow the call chain. As it happened this high on the stack, it's not really a problem and it doesn't hinder investigating the bug at all. The interesting parts of the log would rather be
[ 16.041826] WARNING: CPU: 0 PID: 66 at ../drivers/gpu/drm/i915/intel_display.c:12802 intel_modeset_check_state+0x67e/0x870 [i915]() [ 16.041827] pipe state doesn't match!
and
[ 16.041908] [<ffffffffa0478c5e>] intel_modeset_check_state+0x67e/0x870 [i915] [ 16.041937] [<ffffffffa0483fef>] intel_atomic_commit+0x4af/0x6d0 [i915] [ 16.041956] [<ffffffffa0331107>] drm_atomic_commit+0x37/0x60 [drm] [ 16.041964] [<ffffffffa03bda6f>] restore_fbdev_mode+0x22f/0x260 [drm_kms_helper] [ 16.041971] [<ffffffffa03bfc33>] drm_fb_helper_restore_fbdev_mode_unlocked+0x33/0x80 [drm_kms_helper] [ 16.041976] [<ffffffffa03bfcad>] drm_fb_helper_set_par+0x2d/0x50 [drm_kms_helper] [ 16.041998] [<ffffffffa049897a>] intel_fbdev_set_par+0x1a/0x60 [i915] [ 16.042002] [<ffffffff813ef8f0>] fbcon_init+0x570/0x5f0
I would suggest to google for "i915 pipe state doesn't match". Michal Kubeček -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org