From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jani Nikula Subject: Re: drm: i915: "plane B assertion failure, should be off on pipe B but is still active" Date: Tue, 01 Jul 2014 12:17:56 +0300 Message-ID: <87egy5h1yz.fsf@intel.com> References: <1404140703.2978.13.camel@x41> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1404140703.2978.13.camel@x41> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: Paul Bolle , Daniel Vetter , David Airlie Cc: intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org List-Id: intel-gfx@lists.freedesktop.org On Mon, 30 Jun 2014, Paul Bolle wrote: > Kernels v3.16-rc2 and v3.16-rc3 trigger a new (for me) warning. (I never > booted v3.16-rc1). Machine is a, rather outdated, ThinkPad X41 (ie, > single core i686). > > WARNING: CPU: 0 PID: 221 at drivers/gpu/drm/i915/intel_display.c:1274 assert_planes_disabled+0xf9/0x100 [i915]() > plane B assertion failure, should be off on pipe B but is still active > Modules linked in: tg3 i915(+) i2c_algo_bit drm_kms_helper ptp drm ata_generic pata_acpi yenta_socket i2c_core pps_core video > CPU: 0 PID: 221 Comm: systemd-udevd Not tainted 3.16.0-0.rc3.1.local0.fc20.i686 #1 > Hardware name: IBM 2525FAG/2525FAG, BIOS 74ET64WW (2.09 ) 12/14/2006 > c0c87907 add7c490 00000000 f652b9ac c09fdab7 f652b9ec f652b9dc c045008e > f830c6cc f652ba0c 000000dd f830c634 000004fa f82b4d59 f82b4d59 f6728000 > 00000001 f65a8c00 f652b9f8 c04500ee 00000009 f652b9ec f830c6cc f652ba0c > Call Trace: > [] dump_stack+0x41/0x52 > [] warn_slowpath_common+0x7e/0xa0 > [] ? assert_planes_disabled+0xf9/0x100 [i915] > [] ? assert_planes_disabled+0xf9/0x100 [i915] > [] warn_slowpath_fmt+0x3e/0x60 > [] assert_planes_disabled+0xf9/0x100 [i915] > [] intel_disable_pipe+0x26/0xb0 [i915] > [] ? gen4_read8+0xc0/0xc0 [i915] > [] i9xx_crtc_disable+0x93/0x3d0 [i915] > [] intel_modeset_setup_hw_state+0x7ac/0xbc0 [i915] > [] ? gen4_read8+0xc0/0xc0 [i915] > [] ? drm_modeset_lock_all_crtcs+0x3c/0x50 [drm] > [] intel_modeset_init+0x734/0x1220 [i915] > [] ? i915_enable_pipestat+0xab/0x120 [i915] > [] ? i915_irq_postinstall+0x104/0x110 [i915] > [] ? drm_irq_install+0xa9/0x170 [drm] > [] i915_driver_load+0xa76/0xe70 [i915] > [] ? i915_switcheroo_set_state+0x90/0x90 [i915] > [] ? cleanup_uevent_env+0x10/0x10 > [] ? sysfs_add_file+0x23/0x30 > [] ? get_device+0x14/0x30 > [] ? klist_class_dev_get+0x12/0x20 > [] ? klist_node_init+0x2e/0x50 > [] ? klist_add_tail+0x27/0x30 > [] ? device_add+0x1d6/0x5a0 > [] ? drm_sysfs_device_add+0xba/0x100 [drm] > [] drm_dev_register+0x8e/0xe0 [drm] > [] drm_get_pci_dev+0x79/0x1c0 [drm] > [] i915_pci_probe+0x35/0x60 [i915] > [] pci_device_probe+0x6f/0xc0 > [] ? sysfs_create_link+0x25/0x40 > [] driver_probe_device+0x93/0x3a0 > [] ? sysfs_create_dir_ns+0x37/0x80 > [] ? pci_match_device+0xc1/0xe0 > [] __driver_attach+0x71/0x80 > [] ? __device_attach+0x40/0x40 > [] bus_for_each_dev+0x57/0xa0 > [] driver_attach+0x1e/0x20 > [] ? __device_attach+0x40/0x40 > [] bus_add_driver+0x157/0x230 > [] ? 0xf7fc7fff > [] ? 0xf7fc7fff > [] driver_register+0x59/0xe0 > [] ? __kmalloc_track_caller+0x46/0x1f0 > [] __pci_register_driver+0x32/0x40 > [] drm_pci_init+0xe5/0x110 [drm] > [] ? 0xf7fc7fff > [] i915_init+0x88/0x8a [i915] > [] ? 0xf7fc7fff > [] do_one_initcall+0xc2/0x1f0 > [] ? 0xf7fc7fff > [] ? kfree+0xdd/0x120 > [] ? __vunmap+0x8f/0xe0 > [] ? __vunmap+0x8f/0xe0 > [] ? __vunmap+0x8f/0xe0 > [] load_module+0x1a92/0x23b0 > [] ? copy_module_from_fd.isra.46+0x109/0x1a0 > [] SyS_finit_module+0x8d/0xd0 > [] ? vm_mmap_pgoff+0x93/0xb0 > [] sysenter_do_call+0x12/0x16 > > Feel free to prod me for further details. This does not ring any bells to me (but that doesn't prove anything). A bisect result would be awesome. BR, Jani. -- Jani Nikula, Intel Open Source Technology Center