Re: [Intel-gfx] WARNING: at drivers/gpu/drm/i915/intel_display.c:11375 [i915] in 3.19-rc2
On Thu, 01 Jan 2015, Andrey Skvortsov andrej.skvort...@gmail.com wrote: 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. 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. [ 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: GE 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] a06b3002 813c01df 8800378afcb8 [ 12.848535] 8103f24b a06685d8 88110880 [ 12.848537] 8800c83c2d00 8800c8ccb160 8800376c1000 88011a74e000 [ 12.848539] Call Trace: [ 12.848544] [813c01df] ? dump_stack+0x4a/0x74 [ 12.848548] [8103f24b] ? warn_slowpath_common+0x9e/0xb7 [ 12.848566] [a06685d8] ? intel_crtc_set_config+0x3de/0xb36 [i915] [ 12.848568] [8103f30f] ? warn_slowpath_fmt+0x4a/0x4f [ 12.848584] [a06685d8] ? intel_crtc_set_config+0x3de/0xb36 [i915] [ 12.848586] [813c228f] ? __ww_mutex_lock+0x1c/0x91 [ 12.848598] [a0592985] ? drm_mode_set_config_internal+0x53/0xd7 [drm] [ 12.848604] [a05f6f15] ? restore_fbdev_mode+0xae/0xca [drm_kms_helper] [ 12.848608] [a05f8393] ? drm_fb_helper_restore_fbdev_mode_unlocked+0x24/0x5a [drm_kms_helper] [ 12.848627] [a06747ea] ? intel_fbdev_restore_mode+0x1b/0x41 [i915] [ 12.848632] [a0589249] ? drm_lastclose+0x3c/0x104 [drm] [ 12.848637] [a0589732] ? drm_release+0x421/0x457 [drm] [ 12.848639] [8112cd65] ? __fput+0xdb/0x177 [ 12.848642] [81054977] ? task_work_run+0x8e/0xa3 [ 12.848645] [81002814] ? do_notify_resume+0x64/0x7a [ 12.848647] [813c4267] ? int_signal+0x12/0x17 [ 12.848649] ---[ end trace da6972fb56a05968 ]--- -- Best regards, Andrey Skvortsov Secure e-mail with gnupg: See http://www.gnupg.org/ PGP Key ID: 0x57A3AEAD -- Jani Nikula, Intel Open Source Technology Center ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] new behaviors: ?2.99.917?
Chris Wilson composed on 2014-12-24 07:07 (UTC): On Wed, Dec 24, 2014 at 12:22:38AM -0500, Felix Miata wrote: 4 series onboard video rev 03 (G41) using DVI to HDMI cable on DVI motherboard connector, which Xorg reports as HDMI1 Display is 1920x1080 LCD TV, using HDMI connector #4 Rawhide kernel 3.18.1 Xorg 1.16.3RC1 xorg-x11-drv-intel-2.99.917 1-connected and unconnected absent from Xorg.0.log That's not in any -intel. You are misinterpreting verbiage in the logfile if you think that is what 2.21.15 says. Methinks you misinterpreted my comment at the time you replied. Sometime after v2.20.19 the string connected disappeared from Xorg.0.log files, while remaining all along in logs created using radeon and nouveau drivers. Since your reply, Rawhide's driver moved from v2.99.917-1 to v2.99.917-2, and the string returned to the logs. 2-EDID preferred absent from Xorg.0.log That's not used by any -intel. I see First detailed timing is preferred mode in logs generated using radeon and nouveau, and those generated using intel thru v2.20.19 and in v2.99.917-2, so absence from logs generated in the interim using intel makes me wonder why. Maybe only Xorg rather than driver is what uses it, but the difference when looking at files only from the interim period when they were absent made this the more logical place to ask. 3-EDID preferred is not used by Xorg Indeed. So if -intel does not and Xorg does not, what does? 4-video= on cmdline if present and valid is used by Xorg instead of EDID preferred Xorg inherits the current mode. This is a primary reason for the OP, a distinctly different behavior from using radeon and nouveau. I can understand the logic in it, but will be bothered by it as long as the difference among drivers remains, and would really rather it never happen that the others change to do the same as what intel started doing . It's a long tradition that the kernel cmdline options affecting framebuffer vtys (vga= pre-KMS, video= using KMS) not be inherited by Xorg. Those have quickly and easily at boot time enabled the vty rows and columns to be indirectly adjusted to provide a comfortable text size without impacting the much more elaborately configured X desktops. Current intel behavior requires an additional Xorg 'Section Device' option to get the configured DisplaySize onto the default output in place of the automagic that worked not so long ago in intel, and still can in radeon and nouveau. Logs supporting my comments: http://fm.no-ip.com/Tmp/Linux/Xorg/Igfx/ -- The wise are known for their understanding, and pleasant words are persuasive. Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
