| Summary: | [BDW Regression]ARNING: CPU: 0 PID: 1215 at drivers/gpu/drm/drm_irq.c:1159 drm_wait_one_vblank+0x3b/0x16d [drm] while clean boot system | ||||||
|---|---|---|---|---|---|---|---|
| Product: | DRI | Reporter: | lu hua <huax.lu> | ||||
| Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||
| Status: | CLOSED FIXED | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||
| Severity: | normal | ||||||
| Priority: | high | CC: | adrian.sandu, christophe.prigent, intel-gfx-bugs, tjaalton | ||||
| Version: | unspecified | ||||||
| Hardware: | All | ||||||
| OS: | Linux (All) | ||||||
| Whiteboard: | |||||||
| i915 platform: | BDW | i915 features: | display/Other | ||||
| Attachments: |
|
||||||
|
Description
lu hua
2015-05-11 07:15:04 UTC
This bug still exist on the latest drm-intel-next-fixes_41d232 branch kernel, but It has go away on the latest drm-intel-nightly branch kernel. I see the same thing on an Dell XPS 13 (9343) with 4.2rc4: [ 1.669648] ------------[ cut here ]------------ [ 1.669659] WARNING: CPU: 1 PID: 54 at drivers/gpu/drm/drm_irq.c:1162 drm_wait_one_vblank+0x16e/0x1c0 [drm]() [ 1.669660] vblank not available on crtc 0, ret=-22 [ 1.669692] Modules linked in: pcspkr evdev input_leds mac_hid serio_raw i2c_i801 lpc_ich rtsx_pci_ms memstick shpchp mei_me mei btusb btrtl btb cm btintel bluetooth rfkill dell_led i915 snd_hda_codec_realtek snd_hda_codec_generic drm_kms_helper snd_hda_intel drm snd_hda_codec snd_hda_core s nd_hwdep intel_gtt i2c_algo_bit fan thermal wmi battery int3403_thermal snd_soc_rt286 snd_soc_rl6347a snd_soc_core snd_compress snd_pcm_dmaengine s nd_pcm snd_timer snd i2c_hid(+) soundcore hid int3400_thermal video i2c_designware_platform dw_dmac i2c_designware_core dw_dmac_core snd_soc_sst_ac pi processor_thermal_device gpio_lynxpoint 8250_dw intel_soc_dts_iosf tpm_crb i2c_core int3402_thermal spi_pxa2xx_platform int340x_thermal_zone tpm iosf_mbi acpi_thermal_rel acpi_pad ac button processor sch_fq_codel ip_tables [ 1.669703] x_tables ext4 crc16 mbcache jbd2 sd_mod rtsx_pci_sdmmc atkbd libps2 ahci libahci libata scsi_mod xhci_pci ehci_pci ehci_hcd xhci_hc d rtsx_pci usbcore usb_common i8042 serio sdhci_acpi sdhci led_class mmc_core [ 1.669706] CPU: 1 PID: 54 Comm: kworker/u8:1 Not tainted 4.2.0-rc4-mainline #1 [ 1.669707] Hardware name: Dell Inc. XPS 13 9343/0TRX4F, BIOS A04 05/15/2015 [ 1.669712] Workqueue: events_unbound async_run_entry_fn [ 1.669714] 0000000000000000 0000000056d893f3 ffff8800d9bd76e8 ffffffff81565fb9 [ 1.669716] 0000000000000000 ffff8800d9bd7740 ffff8800d9bd7728 ffffffff810737a6 [ 1.669718] 0000000100000000 ffff8800d90de800 ffff8800d90de800 0000000000000000 [ 1.669719] Call Trace: [ 1.669724] [<ffffffff81565fb9>] dump_stack+0x4c/0x6e [ 1.669726] [<ffffffff810737a6>] warn_slowpath_common+0x86/0xc0 [ 1.669729] [<ffffffff81073835>] warn_slowpath_fmt+0x55/0x70 [ 1.669735] [<ffffffffa04643fe>] drm_wait_one_vblank+0x16e/0x1c0 [drm] [ 1.669766] [<ffffffffa05a5cc2>] intel_finish_crtc_commit+0x162/0x170 [i915] [ 1.669770] [<ffffffffa04df1c0>] drm_atomic_helper_commit_planes+0x170/0x200 [drm_kms_helper] [ 1.669796] [<ffffffffa05a6eed>] __intel_set_mode+0x8ad/0xb80 [i915] [ 1.669821] [<ffffffffa05addb9>] intel_crtc_set_config+0x2c9/0x600 [i915] [ 1.669828] [<ffffffffa046c9f6>] drm_mode_set_config_internal+0x66/0x100 [drm] [ 1.669832] [<ffffffffa04e24f2>] restore_fbdev_mode+0xc2/0xf0 [drm_kms_helper] [ 1.669835] [<ffffffffa04e4459>] drm_fb_helper_restore_fbdev_mode_unlocked+0x29/0x70 [drm_kms_helper] [ 1.669837] [<ffffffffa04e44c2>] drm_fb_helper_set_par+0x22/0x40 [drm_kms_helper] [ 1.669860] [<ffffffffa05bc63a>] intel_fbdev_set_par+0x1a/0x60 [i915] [ 1.669863] [<ffffffff8131c6e8>] fbcon_init+0x538/0x5c0 [ 1.669866] [<ffffffff81395aee>] visual_init+0xce/0x130 [ 1.669868] [<ffffffff8139761e>] do_bind_con_driver+0x1be/0x3e0 [ 1.669870] [<ffffffff81397b79>] do_take_over_console+0x149/0x1a0 [ 1.669873] [<ffffffff8156515e>] ? printk+0x55/0x6b [ 1.669875] [<ffffffff8131c7c7>] do_fbcon_takeover+0x57/0xb0 [ 1.669876] [<ffffffff81320980>] fbcon_event_notify+0x660/0x760 [ 1.669878] [<ffffffff810920de>] notifier_call_chain+0x4e/0x80 [ 1.669880] [<ffffffff8109249b>] __blocking_notifier_call_chain+0x4b/0x70 [ 1.669881] [<ffffffff810924d6>] blocking_notifier_call_chain+0x16/0x20 [ 1.669884] [<ffffffff8132677b>] fb_notifier_call_chain+0x1b/0x20 [ 1.669885] [<ffffffff81328975>] register_framebuffer+0x215/0x350 [ 1.669889] [<ffffffffa04e473f>] drm_fb_helper_initial_config+0x25f/0xb20 [drm_kms_helper] [ 1.669908] [<ffffffffa05bd0eb>] intel_fbdev_initial_config+0x1b/0x20 [i915] [ 1.669910] [<ffffffff81093c1c>] async_run_entry_fn+0x4c/0x160 [ 1.669912] [<ffffffff8108b49b>] process_one_work+0x14b/0x440 [ 1.669914] [<ffffffff8108b7d8>] worker_thread+0x48/0x4a0 [ 1.669917] [<ffffffff8108b790>] ? process_one_work+0x440/0x440 [ 1.669919] [<ffffffff81091378>] kthread+0xd8/0xf0 [ 1.669921] [<ffffffff810912a0>] ? kthread_worker_fn+0x170/0x170 [ 1.669923] [<ffffffff8156b89f>] ret_from_fork+0x3f/0x70 [ 1.669925] [<ffffffff810912a0>] ? kthread_worker_fn+0x170/0x170 [ 1.669926] ---[ end trace 69072b58e579403f ]--- tested -next 07-31, where this one doesn't occur, but v4.2-rc6 is still affected Can you test http://lists.freedesktop.org/archives/intel-gfx/2015-August/073406.html and http://lists.freedesktop.org/archives/intel-gfx/2015-August/073405.html ? I tried test these on 4.2rc5. The "cleaner" patch gives a similar backtrace to before. The other one doesn't apply cleanly to 4.2rc5 or 4.2rc6. The chunk at 13267 in intel_display.c changes a line that doesn't exist. Is there another patch needed before this? sorry, I get it, you wanted both patches at once... With both patches applied it does seem to solve the issue. Thanks! The patches have been applied, closing. Thanks for the report. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.