Bug 92794 - [BXT] IGT not responding when executing gem_mmap_gtt
Summary: [BXT] IGT not responding when executing gem_mmap_gtt
Status: CLOSED WORKSFORME
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Rami
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-11-03 13:34 UTC by cprigent
Modified: 2015-12-08 14:15 UTC (History)
1 user (show)

See Also:
i915 platform: BXT
i915 features:


Attachments
kern.log (343.59 KB, text/plain)
2015-11-03 13:34 UTC, cprigent
no flags Details

Description cprigent 2015-11-03 13:34:26 UTC
Created attachment 119377 [details]
kern.log

BXT-P
Hardware 
Platform: Broxton P A0 Platform 
CPU Name : Intel(R) @ 1.2 GHz (family: 6, model: 92, stepping: 8) – 4 cores
SoC : BROXTON-P A0
CRB : Apollo Lake RVP Fab1
Software 
Linux distribution: Ubuntu 15.04 64 bits 
kernel 4.3.0-rc5 (26f82bd8) from https://github.com/ideak/linux.git BXT branch
commit 26f82bd872901733b739480e8899a92966ae9292
Author: Imre Deak <imre.deak@intel.com>
Date:   Tue Oct 20 16:44:03 2015 +0300
drm/i915/bxt: update bxt_defconfig
Enable Kconfig options needed for UART/eMMC.
Signed-off-by: Imre Deak <imre.deak@intel.com>
BIOS: APLKRVPA.X64.0104.R43.1510080446 
BIOS (IFWI Version): APLK_IFWI_X64_R_2015_41_5_02
CSE : 3.0.0.1044
KSC : 1.02
One HDMI monitor connected: Samsung ls24c65u

Steps:
-------
1. Execute command:
./gem_mmap_gtt
2. Wait a moment

Actual result:
--------------
2. Not all the subtests are executed. IGT is no more responding.
DUT is not crashed (responding via ssh).

Expected result:
----------------
2. All subtests are executed

Log from IGT:
--------------
./gem_mmap_gtt
IGT-Version: 1.12-NOT-GIT (x86_64) (Linux: 4.3.0-rc5-intel-bxt+ x86_64)
Subtest basic: SUCCESS (0.000s)
Subtest basic-short: SUCCESS (0.148s)
Subtest basic-copy: SUCCESS (1.008s)
Subtest basic-read: SUCCESS (0.100s)
Subtest basic-write: SUCCESS (0.508s)
Subtest basic-write-gtt: SUCCESS (1.040s)
Subtest basic-read-write: SUCCESS (0.048s)
Subtest basic-write-read: SUCCESS (0.080s)
Subtest basic-read-write-distinct: SUCCESS (0.076s)
Subtest basic-write-read-distinct: SUCCESS (0.080s)
Subtest fault-concurrent: SUCCESS (3.704s)
Subtest basic-read-no-prefault: SUCCESS (0.100s)
Subtest basic-write-no-prefault: SUCCESS (0.532s)
Subtest basic-write-gtt-no-prefault: SUCCESS (0.584s)
Test requirement not met in function test_write_cpu_read_gtt, file gem_mmap_gtt.c:433:
Test requirement: gem_has_llc(fd)
Subtest basic-write-cpu-read-gtt: SKIP (0.000s)
Subtest basic-small-bo: SUCCESS (1.060s)
Subtest basic-small-bo-tiledX: SUCCESS (0.916s)
Subtest basic-small-bo-tiledY: SUCCESS (0.908s)
Subtest big-bo: SUCCESS (1.536s)
Received signal SIGBUS.
Subtest big-bo-tiledX: CRASH (1.008s)
Received signal SIGBUS.
Subtest big-bo-tiledY: CRASH (1.432s)
Test requirement not met in function intel_require_memory, file intel_os.c:244:
Test requirement: !(total <= required)
Estimated that we need 281,474,976,718,848 bytes for the test, but only have 7,481,589,760 bytes available (RAM)
Subtest huge-bo: SKIP (0.580s)
Test requirement not met in function intel_require_memory, file intel_os.c:244:
Test requirement: !(total <= required)
Estimated that we need 281,474,976,718,848 bytes for the test, but only have 7,481,589,760 bytes available (RAM)
Subtest huge-bo-tiledX: SKIP (0.060s)
Test requirement not met in function intel_require_memory, file intel_os.c:244:
Test requirement: !(total <= required)
Estimated that we need 281,474,976,718,848 bytes for the test, but only have 7,481,589,760 bytes available (RAM)
Subtest huge-bo-tiledY: SKIP (0.060s)
Subtest basic-small-copy: SUCCESS (6.260s)
Subtest basic-small-copy-XY: SUCCESS (6.680s)

/var/log/kern.log attached

Problem could be there:
Feb 16 21:57:51 BROXTON-P kernel: [  169.727410] ------------[ cut here ]------------
Feb 16 21:57:51 BROXTON-P kernel: [  169.727552] WARNING: CPU: 0 PID: 1181 at drivers/gpu/drm/i915/i915_gem.c:1880 i915_gem_fault+0x278/0x4a0 [i915]()
Feb 16 21:57:51 BROXTON-P kernel: [  169.727561] unhandled error in i915_gem_fault: -7
Feb 16 21:57:51 BROXTON-P kernel: [  169.727568] Modules linked in: binfmt_misc cfg80211 snd_hda_codec_hdmi nls_iso8859_1 joydev hid_generic usbhid spi_pxa2xx_platform 8250_dw intel_rapl iosf_mbi i2c_designware_platform intel_powerclamp i2c_designware_core coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul snd_soc_rt286 aesni_intel snd_soc_rl6347a aes_x86_64 snd_soc_core snd_hda_intel lrw gf128mul snd_compress glue_helper snd_pcm_dmaengine snd_hda_codec ablk_helper cryptd snd_hda_core serio_raw snd_hwdep snd_pcm i915 snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device drm_kms_helper snd_timer drm xhci_pci snd fb_sys_fops xhci_hcd syscopyarea shpchp intel_lpss_pci intel_lpss sysfillrect sysimgblt soundcore i2c_hid rfkill_gpio hid int3400_thermal acpi_cpufreq int3402_thermal int3403_thermal int340x_thermal_zone acpi_thermal_rel mac_hid parport_pc ppdev lp parport autofs4 igb sdhci_pci i2c_algo_bit dca sdhci psmouse ptp mmc_core ahci pps_core libahci
Feb 16 21:57:51 BROXTON-P kernel: [  169.727859] CPU: 0 PID: 1181 Comm: gem_mmap_gtt Tainted: G     U          4.3.0-rc5-intel-bxt+ #2
Feb 16 21:57:51 BROXTON-P kernel: [  169.727868] Hardware name: Intel Corp. BROXTON P A0 PLATFORM/NOTEBOOK, BIOS APLK_IFWI_X64_R_2015_41_5_02 10/08/2015
Feb 16 21:57:51 BROXTON-P kernel: [  169.727879]  ffffffffa03b9680 ffff880274c13c50 ffffffff8138c78d ffff880274c13c98
Feb 16 21:57:51 BROXTON-P kernel: [  169.727897]  ffff880274c13c88 ffffffff81077b66 0000000000000002 ffff880272c37000
Feb 16 21:57:51 BROXTON-P kernel: [  169.727913]  00000000fffffff9 ffff880076af4000 ffff880274c13db8 ffff880274c13ce8
Feb 16 21:57:51 BROXTON-P kernel: [  169.727931] Call Trace:
Feb 16 21:57:51 BROXTON-P kernel: [  169.727959]  [<ffffffff8138c78d>] dump_stack+0x44/0x57
Feb 16 21:57:51 BROXTON-P kernel: [  169.727976]  [<ffffffff81077b66>] warn_slowpath_common+0x86/0xc0
Feb 16 21:57:51 BROXTON-P kernel: [  169.727989]  [<ffffffff81077bec>] warn_slowpath_fmt+0x4c/0x50
Feb 16 21:57:51 BROXTON-P kernel: [  169.728103]  [<ffffffffa031fff8>] i915_gem_fault+0x278/0x4a0 [i915]
Feb 16 21:57:51 BROXTON-P kernel: [  169.728127]  [<ffffffff8119988d>] __do_fault+0x3d/0xa0
Feb 16 21:57:51 BROXTON-P kernel: [  169.728142]  [<ffffffff8106816c>] ? pte_alloc_one+0x2c/0x40
Feb 16 21:57:51 BROXTON-P kernel: [  169.728155]  [<ffffffff8119ddaa>] handle_mm_fault+0xe2a/0x17d0
Feb 16 21:57:51 BROXTON-P kernel: [  169.728172]  [<ffffffff810a66eb>] ? account_system_time+0x7b/0x110
Feb 16 21:57:51 BROXTON-P kernel: [  169.728190]  [<ffffffff81062fca>] __do_page_fault+0x19a/0x430
Feb 16 21:57:51 BROXTON-P kernel: [  169.728205]  [<ffffffff81063290>] do_page_fault+0x30/0x80
Feb 16 21:57:51 BROXTON-P kernel: [  169.728224]  [<ffffffff8116d823>] ? context_tracking_user_exit+0x13/0x20
Feb 16 21:57:51 BROXTON-P kernel: [  169.728242]  [<ffffffff8173b678>] page_fault+0x28/0x30
Feb 16 21:57:51 BROXTON-P kernel: [  169.728254] ---[ end trace bda6a73d658b6497 ]---
Comment 1 cprigent 2015-11-24 17:22:30 UTC
Bug scrub:
Rami, could try to execute the subtests one by one to identify which one is/are causing some problem.
Comment 2 cprigent 2015-12-08 14:15:35 UTC
With last setup four subcases are fail.
It will be reported in another bug.

BXT-P
Hardware 
Platform: Broxton P A0 Platform 
CPU Name : Intel(R) @ 1.2 GHz (family: 6, model: 92, stepping: 8) – 4 cores
SoC : BROXTON-P A0
CRB : Apollo Lake RVP Fab1
Software 
Linux distribution: Ubuntu 15.10 64 bits
Kernel: drm-intel-nightly 4.4.0-rc2 17874a0 from http://cgit.freedesktop.org/drm-intel/
  commit 17874a0bd04949ab460431e6017860ab98e0e4d2
  Author: Ville Syrjala <ville.syrjala@linux.intel.com>
  Date:   Thu Nov 26 18:58:09 2015 +0200
  drm-intel-nightly: 2015y-11m-26d-16h-57m-42s UTC integration manifest
libdrm-2.4.65 from http://cgit.freedesktop.org/mesa/drm/
IGT 1.12 4cfcea4 from http://cgit.freedesktop.org/xorg/app/intel-gpu-tools/
Comment 3 cprigent 2015-12-08 14:15:50 UTC
So closed


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.