On Wed, Sep 23, 2015 at 9:18 AM, Daniel Vetter <daniel@xxxxxxxx> wrote: > Adding Jairo to track this regression. Hi, commit 721a09f7393de6c28a07516dccd654c6e995944a "drm/i915: Add primary plane to mask if it's visible" ...pending in drm-intel.git#drm-intel-fixes fixes the issue here. - sed@ - [1] http://cgit.freedesktop.org/drm-intel/commit/?h=drm-intel-fixes&id=721a09f7393de6c28a07516dccd654c6e995944a > -Daniel > > On Wed, Sep 23, 2015 at 08:23:04AM +0200, Sedat Dilek wrote: >> On Sun, Sep 13, 2015 at 9:06 AM, Sedat Dilek <sedat.dilek@xxxxxxxxx> wrote: >> > On Wed, Sep 9, 2015 at 4:42 AM, Sedat Dilek <sedat.dilek@xxxxxxxxx> wrote: >> >> [ TO INTEL DRM DRIVERS maintainers ] >> >> >> >> Hi, >> >> >> >> out of curiosity and to play with the new bindeb-pkg make-target I >> >> built pre-v4.3-rc1 (git-describe says v4.2-10463-g9a9952bbd76a) >> >> Debian-kernel packages. >> >> >> >> I see several bugs and call-traces. >> >> >> >> Two hit a warning in i915 (one snippet here, full dmesg-log and >> >> kernel-config are attached). >> >> >> >> [ 20.920943] ------------[ cut here ]------------ >> >> [ 20.920982] WARNING: CPU: 0 PID: 114 at >> >> drivers/gpu/drm/i915/intel_display.c:1377 >> >> assert_planes_disabled+0xe4/0x150 [i915]() >> >> [ 20.920983] plane A assertion failure, should be disabled but not >> >> [ 20.921023] Modules linked in: i915 mac80211 snd_hda_codec_hdmi >> >> snd_hda_codec_realtek snd_hda_codec_generic uvcvideo snd_hda_intel >> >> snd_hda_codec videobuf2_vmalloc videobuf2_memops videobuf2_core rfcomm >> >> joydev bnep v4l2_common snd_hwdep iwlwifi videodev usb_storage >> >> kvm_intel snd_hda_core parport_pc cfg80211 btusb i2c_algo_bit >> >> drm_kms_helper ppdev btrtl btbcm snd_pcm btintel kvm bluetooth >> >> snd_seq_midi psmouse snd_seq_midi_event snd_rawmidi syscopyarea >> >> snd_seq sysfillrect sysimgblt fb_sys_fops drm snd_timer snd_seq_device >> >> serio_raw samsung_laptop snd lpc_ich video soundcore wmi intel_rst >> >> mac_hid lp parport binfmt_misc hid_generic usbhid hid r8169 mii >> >> [ 20.921026] CPU: 0 PID: 114 Comm: kworker/u16:5 Not tainted >> >> 4.2.0-10463.1-iniza-small #1 >> >> [ 20.921027] Hardware name: SAMSUNG ELECTRONICS CO., LTD. >> >> 530U3BI/530U4BI/530U4BH/530U3BI/530U4BI/530U4BH, BIOS 13XK 03/28/2013 >> >> [ 20.921033] Workqueue: events_unbound async_run_entry_fn >> >> [ 20.921037] ffffffffa06a9d60 ffff8800378af718 ffffffff813df89b >> >> ffff8800378af760 >> >> [ 20.921039] ffff8800378af750 ffffffff8107cdc6 ffff8800c2000000 >> >> 0000000000000000 >> >> [ 20.921042] 0000000000000000 ffff8800bf90b000 ffff8800bf90b000 >> >> ffff8800378af7b0 >> >> [ 20.921043] Call Trace: >> >> [ 20.921046] [<ffffffff813df89b>] dump_stack+0x4b/0x70 >> >> [ 20.921050] [<ffffffff8107cdc6>] warn_slowpath_common+0x86/0xc0 >> >> [ 20.921052] [<ffffffff8107ce4c>] warn_slowpath_fmt+0x4c/0x50 >> >> [ 20.921081] [<ffffffffa0634af4>] assert_planes_disabled+0xe4/0x150 [i915] >> >> [ 20.921106] [<ffffffffa063e8bf>] intel_disable_pipe+0x4f/0x2d0 [i915] >> >> [ 20.921129] [<ffffffffa063eeb5>] ironlake_crtc_disable+0x85/0x7d0 [i915] >> >> [ 20.921151] [<ffffffffa063a9ce>] ? >> >> intel_crtc_disable_planes+0xde/0xf0 [i915] >> >> [ 20.921176] [<ffffffffa0647a58>] intel_atomic_commit+0x108/0x1370 [i915] >> >> [ 20.921192] [<ffffffffa00f1957>] ? drm_atomic_check_only+0x1d7/0x5a0 [drm] >> >> [ 20.921205] [<ffffffffa00f15c9>] ? >> >> drm_atomic_get_connector_state+0x49/0x110 [drm] >> >> [ 20.921216] [<ffffffffa00f1d57>] drm_atomic_commit+0x37/0x60 [drm] >> >> [ 20.921223] [<ffffffffa02138aa>] >> >> drm_atomic_helper_set_config+0x1ca/0x430 [drm_kms_helper] >> >> [ 20.921234] [<ffffffffa00e13c5>] >> >> drm_mode_set_config_internal+0x65/0x110 [drm] >> >> [ 20.921240] [<ffffffffa021674e>] restore_fbdev_mode+0xbe/0xe0 >> >> [drm_kms_helper] >> >> [ 20.921246] [<ffffffffa0218615>] >> >> drm_fb_helper_restore_fbdev_mode_unlocked+0x25/0x70 [drm_kms_helper] >> >> [ 20.921251] [<ffffffffa021868d>] drm_fb_helper_set_par+0x2d/0x50 >> >> [drm_kms_helper] >> >> [ 20.921280] [<ffffffffa065dfba>] intel_fbdev_set_par+0x1a/0x60 [i915] >> >> [ 20.921283] [<ffffffff8144e12e>] fbcon_init+0x53e/0x5d0 >> >> [ 20.921286] [<ffffffff814d32ca>] visual_init+0xca/0x130 >> >> [ 20.921289] [<ffffffff814d5877>] do_bind_con_driver+0x167/0x3a0 >> >> [ 20.921292] [<ffffffff814d5d5c>] do_take_over_console+0xac/0x1d0 >> >> [ 20.921294] [<ffffffff81449e27>] do_fbcon_takeover+0x57/0xb0 >> >> [ 20.921296] [<ffffffff8144ecd2>] fbcon_event_notify+0x752/0x860 >> >> [ 20.921299] [<ffffffff810a2ce5>] ? __blocking_notifier_call_chain+0x35/0x70 >> >> [ 20.921301] [<ffffffff810a2aed>] notifier_call_chain+0x5d/0x80 >> >> [ 20.921304] [<ffffffff810a2cfd>] __blocking_notifier_call_chain+0x4d/0x70 >> >> [ 20.921306] [<ffffffff810a2d36>] blocking_notifier_call_chain+0x16/0x20 >> >> [ 20.921308] [<ffffffff8145162b>] fb_notifier_call_chain+0x1b/0x20 >> >> [ 20.921311] [<ffffffff81453854>] register_framebuffer+0x204/0x330 >> >> [ 20.921317] [<ffffffffa02188e4>] >> >> drm_fb_helper_initial_config+0x234/0x3b0 [drm_kms_helper] >> >> [ 20.921344] [<ffffffffa065f15b>] intel_fbdev_initial_config+0x1b/0x20 [i915] >> >> [ 20.921346] [<ffffffff810a4807>] async_run_entry_fn+0x37/0xe0 >> >> [ 20.921349] [<ffffffff8109a8b1>] process_one_work+0x1e1/0x620 >> >> [ 20.921352] [<ffffffff8109a826>] ? process_one_work+0x156/0x620 >> >> [ 20.921353] [<ffffffff8109b589>] worker_thread+0x69/0x480 >> >> [ 20.921355] [<ffffffff8109b520>] ? cancel_delayed_work_sync+0x20/0x20 >> >> [ 20.921357] [<ffffffff810a17ea>] kthread+0x10a/0x120 >> >> [ 20.921360] [<ffffffff810a16e0>] ? kthread_create_on_node+0x200/0x200 >> >> [ 20.921364] [<ffffffff817badef>] ret_from_fork+0x3f/0x70 >> >> [ 20.921366] [<ffffffff810a16e0>] ? kthread_create_on_node+0x200/0x200 >> >> [ 20.921367] ---[ end trace 85fce5c152ff4528 ]--- >> >> >> >> Some intelgfx hardware infos (see attached Xorg.0.log)... >> >> >> >> [ 27.487] (--) intel(0): Integrated Graphics Chipset: Intel(R) HD >> >> Graphics 3000 >> >> [ 27.565] (II) intel(0): SNA initialized with Sandybridge (gen6, gt2) backend >> >> >> >> Please have a look at it. >> >> >> >> If this is a known issue, please let me know and kindly point me to a >> >> patch (patchwork preferred) or commit-id in drm-intel Git. >> >> ( Sorry, I have not checked any mailing-lists or patchwork. ) >> >> >> >> If you need more infos, logs and/or debug material please let me know >> >> and give clear instructions (especially for debugging). >> >> >> >> >> > >> > I still see this issue with Linux v4.3-rc1. >> > >> >> Hi Daniel, >> >> any progress with this reported issue? >> >> I looked into drm-intel.git#drm-intel-fixes, but see only a kernel-doc fix. >> ( I tried also some drm-intel-nightly, not the latest - and still saw >> the issue. ) >> >> This issue is still alive in Linux v4.3-rc2. >> >> What can I do to help? >> >> Please, take care of this. >> >> Thanks!. >> >> Regards, >> - Sedat - > > -- > Daniel Vetter > Software Engineer, Intel Corporation > http://blog.ffwll.ch _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/intel-gfx
