All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 99426] gem_mmap_gtt swap tests are too long - perf: interrupt took too long
Date: Mon, 16 Jan 2017 13:58:37 +0000	[thread overview]
Message-ID: <bug-99426-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2925 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=99426

            Bug ID: 99426
           Summary: gem_mmap_gtt swap tests are too long - perf: interrupt
                    took too long
           Product: DRI
           Version: unspecified
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: IGT
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: christophe.prigent@intel.com

Tested on BDW, SNB, SKL, IVB, HSW, BYT with SW config:

Kernel: 4.10.0-rc3 ea7e3e5 branch drm-tip from
https://cgit.freedesktop.org/drm-tip
  commit ea7e3e5c99e316fb6876399f9b32b2372e45c4af
  Author: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
  Date:   Mon Jan 9 16:46:47 2017 +0200
  drm-tip: 2017y-01m-09d-14h-45m-54s UTC integration manifest

libdrm-2.4.74-21 geebefaf from git://anongit.freedesktop.org/mesa/drm
mesa: mesa-13.0.2 c9e993b from git://anongit.freedesktop.org/mesa/mesa
cairo 1.15.4 9fe6683 from git://anongit.freedesktop.org/cairo
xorg-server-1.19.0-38 9d32b71 from git://git.freedesktop.org/git/xorg/xserver
xf86-video-intel 2.99.917-747 028c946 from
git://git.freedesktop.org/git/xorg/driver/xf86-video-intel
libva-1.7.2-45 acbc209 from git://git.freedesktop.org/git/vaapi/libva 
vaapi-intel-driver: 1.7.2-216 70770f9 from
git://git.freedesktop.org/git/vaapi/intel-driver
intel-gpu-tools-1.17 e2eefcc from
http://anongit.freedesktop.org/git/xorg/app/intel-gpu-tools.git

Steps:
-------
1. Execute IGT test manually (no timeout is used):
./gem_mmap_gtt --r swap-copy
2. Wait 100 hours

Actual results:
----------------
2. Test is still not finished after 100 hours (IGT is still running - DUT is
not freezed)
dmesg shows the same logs on all platforms, example on SKL:
[  151.322722] [IGT] gem_mmap_gtt: executing
[  151.353973] [IGT] gem_mmap_gtt: starting subtest swap-copy
[  151.354090] gem_mmap_gtt (31952): drop_caches: 4
[ 4843.205005] perf: interrupt took too long (2540 > 2500), lowering
kernel.perf_event_max_sample_rate to 78500
[ 6383.794279] perf: interrupt took too long (3202 > 3175), lowering
kernel.perf_event_max_sample_rate to 62250
[ 9271.093175] perf: interrupt took too long (4037 > 4002), lowering
kernel.perf_event_max_sample_rate to 49500
[14046.280647] perf: interrupt took too long (5090 > 5046), lowering
kernel.perf_event_max_sample_rate to 39250
[22889.758381] perf: interrupt took too long (6365 > 6362), lowering
kernel.perf_event_max_sample_rate to 31250
[50315.915256] perf: interrupt took too long (7982 > 7956), lowering
kernel.perf_event_max_sample_rate to 25000

Expected results:
-----------------
2. Test is not so long

Info:
-----
I can't attach dmesg due to its size
There is no log from IGT

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 4434 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2017-01-16 13:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-16 13:58 bugzilla-daemon [this message]
2018-07-04 16:10 ` [Bug 99426] gem_mmap_gtt swap tests are too long - perf: interrupt took too long bugzilla-daemon
2019-11-12  7:35 ` bugzilla-daemon

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=bug-99426-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.