Hi,
this warning does not exist in 3.19-rc1, but it happens every boot in 3.19-rc2. If you need any other information or data, I would be glad to help to debug it.
[ 12.848428] ------------[ cut here ]------------ [ 12.848479] WARNING: CPU: 1 PID: 328 at drivers/gpu/drm/i915/intel_display.c:11375 intel_crtc_set_config+0x3de/0xb36 [i915]() [ 12.848482] WARN_ON(!set->fb && (set->num_connectors != 0)) [ 12.848484] Modules linked in: i915(E) drm_kms_helper(E) drm(E) snd_hda_intel(E) snd_hda_controller(E) i2c_algo_bit(E) snd_hda_codec(E) i2c_core(E) xhci_pci(E) xhci_hcd(E) ehci_pci(E) ehci_hcd(E) usbcore(E) snd_hwdep(E) snd_pcm_oss(E) snd_mixer_oss(E) snd_pcm(E) snd_seq_midi(E) snd_rawmidi(E) snd_seq_midi_event(E) snd_seq(E) snd_timer(E) snd_seq_device(E) snd(E) video(E) battery(E) ppdev(E) parport_pc(E) usb_common(E) serio_raw(E) lpc_ich(E) evdev(E) mfd_core(E) soundcore(E) button(E) acpi_cpufreq(E) processor(E) coretemp(E) lp(E) parport(E) ext3(E) jbd(E) mbcache(E) sd_mod(E) ata_generic(E) btrfs(E) ata_piix(E) pata_via(E) libata(E) raid6_pq(E) thermal(E) scsi_mod(E) fan(E) thermal_sys(E) r8169(E) mii(E) xor(E) zlib_deflate(E) crc32c_generic(E) libcrc32c(E) [ 12.848531] CPU: 1 PID: 328 Comm: plymouthd Tainted: G E 3.19.0-rc2-noiommu- #122 [ 12.848532] Hardware name: System manufacturer System Product Name/P8H67-M PRO, BIOS 3904 04/27/2013 [ 12.848533] 0000000000000000 ffffffffa06b3002 ffffffff813c01df ffff8800378afcb8 [ 12.848535] ffffffff8103f24b 0000000000000000 ffffffffa06685d8 ffff880000110880 [ 12.848537] ffff8800c83c2d00 ffff8800c8ccb160 ffff8800376c1000 ffff88011a74e000 [ 12.848539] Call Trace: [ 12.848544] [<ffffffff813c01df>] ? dump_stack+0x4a/0x74 [ 12.848548] [<ffffffff8103f24b>] ? warn_slowpath_common+0x9e/0xb7 [ 12.848566] [<ffffffffa06685d8>] ? intel_crtc_set_config+0x3de/0xb36 [i915] [ 12.848568] [<ffffffff8103f30f>] ? warn_slowpath_fmt+0x4a/0x4f [ 12.848584] [<ffffffffa06685d8>] ? intel_crtc_set_config+0x3de/0xb36 [i915] [ 12.848586] [<ffffffff813c228f>] ? __ww_mutex_lock+0x1c/0x91 [ 12.848598] [<ffffffffa0592985>] ? drm_mode_set_config_internal+0x53/0xd7 [drm] [ 12.848604] [<ffffffffa05f6f15>] ? restore_fbdev_mode+0xae/0xca [drm_kms_helper] [ 12.848608] [<ffffffffa05f8393>] ? drm_fb_helper_restore_fbdev_mode_unlocked+0x24/0x5a [drm_kms_helper] [ 12.848627] [<ffffffffa06747ea>] ? intel_fbdev_restore_mode+0x1b/0x41 [i915] [ 12.848632] [<ffffffffa0589249>] ? drm_lastclose+0x3c/0x104 [drm] [ 12.848637] [<ffffffffa0589732>] ? drm_release+0x421/0x457 [drm] [ 12.848639] [<ffffffff8112cd65>] ? __fput+0xdb/0x177 [ 12.848642] [<ffffffff81054977>] ? task_work_run+0x8e/0xa3 [ 12.848645] [<ffffffff81002814>] ? do_notify_resume+0x64/0x7a [ 12.848647] [<ffffffff813c4267>] ? int_signal+0x12/0x17 [ 12.848649] ---[ end trace da6972fb56a05968 ]---
On Thu, 01 Jan 2015, Andrey Skvortsov andrej.skvortzov@gmail.com wrote:
Hmm, at a glance I can't find a commit that could be the culprit. Can you bisect between rc1 and rc2 to find the bad commit?
Thanks, Jani.
On Fri, Jan 02, 2015 at 09:42:01AM +0200, Jani Nikula wrote:
Sorry, my first message was not fully correct. As I tested this more, it happens unfortunately not every boot. And this is not a regression, because it happened couple of times with 3.19-rc1 too.
This warning seems to depend on the previously booted kernel. If I boot the same kernel every time, it occurs very seldom. To reproduce the warning I booted v3.19-rc2 and v3.19-rc1-g08b022a965 one after another many times. In this case the warning happens with probability around 50%.
On Fri, Jan 02, 2015 at 08:27:29PM +0530, Sudip Mukherjee wrote:
Sorry, my first message was not fully correct. As I tried to bisect this, I noticed that this warning happens unfortunately not every boot. And I noticed another strange behavior. If the same kernel is always booted, the warning happens very seldom. To make it appear more frequently I booted v3.19-rc2 and v3.19-rc1-g08b022a9655bf one after another many times. In this case it happens with probability around 50% during the boot.
my config is attached.
dri-devel@lists.freedesktop.org