Bug 85787

Summary: [HSW]igt/kms_flip/flip-vs-modeset-vs-hang-interruptible causes system hang
Product: DRI Reporter: lu hua <huax.lu>
Component: DRM/IntelAssignee: Intel GFX Bugs mailing list <intel-gfx-bugs>
Status: CLOSED DUPLICATE QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: major    
Priority: medium CC: intel-gfx-bugs
Version: unspecified   
Hardware: All   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
dmesg none

Description lu hua 2014-11-03 06:19:31 UTC
Created attachment 108823 [details]
dmesg

==System Environment==
--------------------------
Regression: not sure 
Non-working platforms: HSW

==kernel==
--------------------------
drm-intel-nightly/203b34bf78a127a85cf89bbd8cf4decd935d780f

==Bug detailed description==
It causes system hang, It happens only one HSW machine(same as bug 85541).

output:
IGT-Version: 1.8-gab5f7ea (x86_64) (Linux: 3.18.0-rc2_drm-intel-nightly_203b34_20141103+ x86_64)
Using monotonic timestamps
Beginning flip-vs-modeset-vs-hang-interruptible on crtc 8, connector 18
  1024x768 60 1024 1048 1184 1344 768 771 777 806 0xa 0x40 65000

[  171.798475] Kernel panic - not syncing: Timeout synchronizing machine check over CPUs
[  172.822655] Shutting down cpus with NMI
[  172.833831] Kernel Offset: 0x0 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffff9fffffff)
[  172.834799] drm_kms_helper: panic occurred, switching back to text console
[  172.835760] ------------[ cut here ]------------
[  172.836716] WARNING: CPU: 5 PID: 0 at arch/x86/kernel/smp.c:124 mod_timer+0x121/0x15d()
[  172.837680] Modules linked in: netconsole configfs ip6table_filter ip6_tables ipv6 iptable_filter ip_tables ebtable_nat ebtables x_tables snd_hda_codec_realtek snd_hda_codec_hdmi snd_hda_codec_generic serio_raw pcspkr i2c_i801 lpc_ich mfd_core firewire_ohci snd_hda_intel snd_hda_controller firewire_core crc_itu_t snd_hda_codec snd_hwdep snd_pcm snd_timer snd soundcore dm_mod battery wmi acpi_cpufreq i915 button video drm_kms_helper drm cfbfillrect cfbimgblt cfbcopyarea [last unloaded: netconsole]
[  172.841882] CPU: 5 PID: 0 Comm: swapper/5 Not tainted 3.18.0-rc2_drm-intel-nightly_203b34_20141103+ #1126
[  172.842932] Hardware name:                  /DZ87KLT75K, BIOS KLZ8711D.86A.0336.2013.0516.1957 05/16/2013
[  172.843989]  0000000000000000 0000000000000009 ffffffff8178ef42 0000000000000000
[  172.845057]  ffffffff8103a8cc 0000000000000082 ffffffff8107a9ca ffffffff81be5090
[  172.846132]  ffffffff81be5090 0000000100073800 ffff8802565dc000 ffff8802565dc000
[  172.847192] Call Trace:
[  172.848229]  <#MC>  [<ffffffff8178ef42>] ? dump_stack+0x41/0x51
[  172.849278]  [<ffffffff8103a8cc>] ? warn_slowpath_common+0x78/0x90
[  172.850315]  [<ffffffff8107a9ca>] ? mod_timer+0x121/0x15d
[  172.851350]  [<ffffffff8107a9ca>] ? mod_timer+0x121/0x15d
[  172.852372]  [<ffffffff813c696b>] ? do_unblank_screen+0xca/0x169
[  172.853384]  [<ffffffff813416b5>] ? bust_spinlocks+0x11/0x28
[  172.854385]  [<ffffffff8178bb40>] ? panic+0x107/0x1e0
[  172.855369]  [<ffffffff8101db13>] ? mce_panic+0x14c/0x188
[  172.856391]  [<ffffffff8101db8f>] ? mce_timed_out+0x40/0x5a
[  172.857347]  [<ffffffff8101deec>] ? do_machine_check+0x178/0x6c6
[  172.858293]  [<ffffffff81023dc8>] ? acpi_processor_ffh_cstate_enter+0x7c/0xa8
[  172.859245]  [<ffffffff81795fc9>] ? machine_check+0x19/0x20
[  172.860188]  [<ffffffff81023dc8>] ? acpi_processor_ffh_cstate_enter+0x7c/0xa8
[  172.861130]  <<EOE>>  [<ffffffff813aae2a>] ? acpi_idle_enter_simple+0x9c/0xd9
[  172.862073]  [<ffffffff816a9d92>] ? cpuidle_enter_state+0x69/0x129
[  172.863004]  [<ffffffff81063bec>] ? cpu_startup_entry+0x1e0/0x2e8
[  172.863920]  [<ffffffff81794018>] ? _raw_spin_unlock_irqrestore+0x5/0x6
[  172.864829] ---[ end trace e5d70c89742a84e8 ]---

lspci:
00:00.0 Host bridge: Intel Corporation Haswell DRAM Controller (rev 06)
00:02.0 VGA compatible controller: Intel Corporation Haswell Integrated Graphics Controller (rev 06)
00:03.0 Audio device: Intel Corporation Haswell HD Audio Controller (rev 06)
00:14.0 USB controller: Intel Corporation Lynx Point USB xHCI Host Controller (rev 04)
00:16.0 Communication controller: Intel Corporation Lynx Point MEI Controller #1 (rev 04)
00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-V (rev 04)
00:1a.0 USB controller: Intel Corporation Lynx Point USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation Lynx Point High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation Lynx Point PCI Express Root Port #1 (rev d4)
00:1c.2 PCI bridge: Intel Corporation Lynx Point PCI Express Root Port #3 (rev d4)
00:1c.3 PCI bridge: Intel Corporation Lynx Point PCI Express Root Port #4 (rev d4)
00:1c.4 PCI bridge: Intel Corporation Lynx Point PCI Express Root Port #5 (rev d4)
00:1d.0 USB controller: Intel Corporation Lynx Point USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation Lynx Point LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation Lynx Point 6-port SATA Controller 1 [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation Lynx Point SMBus Controller (rev 04)
01:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 01)
02:00.0 PCI bridge: Integrated Technology Express, Inc. Device 8892 (rev 41)
03:02.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22A IEEE-1394a-2000 Controller (PHY/Link) [iOHCI-Lynx]
04:00.0 PCI bridge: PLX Technology, Inc. PEX 8606 6 Lane, 6 Port PCI Express Gen 2 (5.0 GT/s) Switch (rev ba)
05:07.0 PCI bridge: PLX Technology, Inc. PEX 8606 6 Lane, 6 Port PCI Express Gen 2 (5.0 GT/s) Switch (rev ba)
06:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03)

==Reproduce steps==
---------------------------- 
1. ./kms_flip --run-subtest flip-vs-modeset-vs-hang-interruptible
Comment 1 Jani Nikula 2015-01-29 14:24:46 UTC

*** This bug has been marked as a duplicate of bug 85541 ***
Comment 2 Elizabeth 2017-10-06 14:34:10 UTC
Closing old verified.

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.