From: Jani Nikula <jani.nikula@linux.intel.com>
To: Sakari Kapanen <sakari.m.kapanen@student.jyu.fi>,
daniel.vetter@intel.com
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: Kernel 3.19rc6 flooding intel_check_page_flip warnings when using compton
Date: Wed, 04 Feb 2015 11:26:01 +0200 [thread overview]
Message-ID: <87h9v2xc2e.fsf@intel.com> (raw)
In-Reply-To: <54CEB859.7020003@student.jyu.fi>
On Mon, 02 Feb 2015, Sakari Kapanen <sakari.m.kapanen@student.jyu.fi> wrote:
> Dear maintainers,
>
> On an Asus Zenbook UX32VD laptop with an i5-3317U CPU and Intel HD4000
> graphics, I'm experiencing the following with the latest 3.19rc6
> mainline kernel (built from the Arch Linux AUR package:
> https://aur.archlinux.org/packages/linux-mainline/ ). The problem is
> related to the compton compositor: https://github.com/chjj/compton
Hi, a full dmesg from boot to the problem with drm.debug=14 module
parameter set might be useful. Also, you may get fastest results if you
do a git bisect from a good to bad kernel.
BR,
Jani.
>
> Booting to X goes very normally. Then, I start compton with the command
> `compton --backend glx`. As soon as I do that, the dmesg log starts
> getting filled with these warnings. This is a snippet from my journalctl
> log:
>
> 1 Feb 02 00:06:44 stroemsoe kernel: WARNING: CPU: 0 PID: 273 at
> drivers/gpu/drm/i915/intel_display.c:9705
> intel_check_page_flip+0xa2/0xf0 [i915]()
> 1421 Feb 02 00:06:44 stroemsoe kernel: WARN_ON(!in_irq())
> 1 Feb 02 00:06:44 stroemsoe kernel: Modules linked in:
> 2 Feb 02 00:06:44 stroemsoe kernel: joydev mousedev msr uvcvideo
> rtsx_usb_sdmmc videobuf2_vmalloc rtsx_usb_ms videobuf2_memops mmc_core
> memstick videobuf2_core n ls_iso8859_1 rtsx_usb v4l2_common nls_cp437
> videodev vfat fat coretemp intel_rapl media iosf_mbi
> x86_pkg_temp_thermal intel_powerclamp arc4 kvm_intel kvm iwldvm
> crct10dif_pclmul crc32_pclmul iTCO_wdt mac80211 iTCO_vendor_support
> crc32c_intel ghash_clmulni_intel snd_hda_codec_hdmi nouveau aesni_intel
> i915 aes_x86_64 snd _hda_codec_realtek glue_helper lrw gf128mul
> ablk_helper snd_hda_codec_generic cryptd iwlwifi pcspkr evdev mac_hid
> snd_hda_intel psmouse serio_raw snd_hda_contro ller snd_hda_codec
> snd_hwdep mxm_wmi snd_pcm ttm snd_timer cfg80211 snd lpc_ich soundcore
> mfd_core i2c_i801 fan int3403_thermal button i2c_algo_bit mei_me
> drm_k ms_helper mei drm battery tpm_tis
> 3 Feb 02 00:06:44 stroemsoe kernel: thermal tpm shpchp ac
> int3402_thermal i2c_core intel_gtt int3400_thermal acpi_thermal_rel
> processor sch_fq_codel overlay ext4 crc16 mbcache jbd2 sd_mod
> atkbd libps2 ahci libahci libata ehci_pci xhci_pci ehci_hcd xhci_hcd
> scsi_mod usbcore usb_common i8042 serio asus_nb_wmi asus_wmi hwm on
> video rfkill sparse_keymap wmi led_class
> 4 Feb 02 00:06:44 stroemsoe kernel: CPU: 0 PID: 273 Comm:
> irq/32-i915 Tainted: G W 3.19.0-1-mainline #1
> 5 Feb 02 00:06:44 stroemsoe kernel: Hardware name: ASUSTeK COMPUTER
> INC. UX32VD/UX32VD, BIOS UX32VD.213 11/16/2012
> 6 Feb 02 00:06:44 stroemsoe kernel: 0000000000000000
> 00000000b983161a ffff8800c88afc78 ffffffff8153537c
> 7 Feb 02 00:06:44 stroemsoe kernel: 0000000000000000
> ffff8800c88afcd0 ffff8800c88afcb8 ffffffff81075a9a
> 8 Feb 02 00:06:44 stroemsoe kernel: ffff8800c88afcb8
> ffff8800c7d99000 ffff8800c8e05000 ffff8800c8e05000
> 9 Feb 02 00:06:44 stroemsoe kernel: Call Trace:
> 10 Feb 02 00:06:44 stroemsoe kernel: [<ffffffff8153537c>]
> dump_stack+0x4c/0x6e
> 11 Feb 02 00:06:44 stroemsoe kernel: [<ffffffff81075a9a>]
> warn_slowpath_common+0x8a/0xc0
> 12 Feb 02 00:06:44 stroemsoe kernel: [<ffffffff81075b25>]
> warn_slowpath_fmt+0x55/0x70
> 13 Feb 02 00:06:44 stroemsoe kernel: [<ffffffffa0596492>]
> intel_check_page_flip+0xa2/0xf0 [i915]
> 14 Feb 02 00:06:44 stroemsoe kernel: [<ffffffffa05639d8>]
> ironlake_irq_handler+0x428/0x1000 [i915]
> 15 Feb 02 00:06:44 stroemsoe kernel: [<ffffffff810a17aa>] ?
> do_set_cpus_allowed+0x4a/0x60
> 16 Feb 02 00:06:44 stroemsoe kernel: [<ffffffff810cf810>] ?
> irq_thread_fn+0x50/0x50
> 17 Feb 02 00:06:44 stroemsoe kernel: [<ffffffff810cf83d>]
> irq_forced_thread_fn+0x2d/0x70
> 18 Feb 02 00:06:44 stroemsoe kernel: [<ffffffff810cfb67>]
> irq_thread+0x157/0x180
> 19 Feb 02 00:06:44 stroemsoe kernel: [<ffffffff810cf950>] ?
> wake_threads_waitq+0x30/0x30
> 20 Feb 02 00:06:44 stroemsoe kernel: [<ffffffff810cfa10>] ?
> irq_thread_dtor+0xc0/0xc0
> 21 Feb 02 00:06:44 stroemsoe kernel: [<ffffffff81093dea>]
> kthread+0xea/0x100
> 22 Feb 02 00:06:44 stroemsoe kernel: [<ffffffff81093d00>] ?
> kthread_create_on_node+0x1c0/0x1c0
> 23 Feb 02 00:06:44 stroemsoe kernel: [<ffffffff8153ac3c>]
> ret_from_fork+0x7c/0xb0
> 24 Feb 02 00:06:44 stroemsoe kernel: [<ffffffff81093d00>] ?
> kthread_create_on_node+0x1c0/0x1c0
> 25 Feb 02 00:06:44 stroemsoe kernel: ---[ end trace 46f2548918f46443
> ]---
>
> I get about 4-5 of them per second as long as compton is running.
> Starting compton with `--backend xrender` doesn't cause any warnings.
> I'm using the SNA AccelMethod (the default), but switching to UXA or
> Glamor didn't seem to have any effect. I haven't set any i915 specific
> kernel flags.
>
> I don't see this on the current stable 3.18.5 kernel. The first time I
> saw this was on 3.19rc3 when I tried it due to another bug in the 3.18
> series. I haven't gone through all the 3.19 release candidates, but the
> behaviour with 3.19rc6 seems identical to what I saw with 3.19rc3.
>
> Sakari Kapanen
>
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-02-04 9:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-01 23:35 Kernel 3.19rc6 flooding intel_check_page_flip warnings when using compton Sakari Kapanen
2015-02-02 7:44 ` Sakari Kapanen
2015-02-04 9:26 ` Jani Nikula [this message]
2015-02-05 10:44 ` Sakari Kapanen
2015-02-05 11:01 ` Chris Wilson
2015-02-09 17:30 ` Dave Gordon
-- strict thread matches above, loose matches on Subject: below --
2015-03-04 17:42 [4.0-rc2] WARNING at intel_check_page_flip Thomas Meyer
2015-03-04 18:32 ` Ville Syrjälä
2015-03-06 15:34 ` [PATCH] drm/i915: use in_interrupt() not in_irq() to check context Dave Gordon
2015-03-06 16:46 ` Daniel Vetter
2015-03-10 9:59 ` Jani Nikula
2015-03-06 20:20 ` shuang.he
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h9v2xc2e.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=sakari.m.kapanen@student.jyu.fi \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox