All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.IGT: failure for series starting with [1/6] Revert "drm: Use a flexible array member for blob property data" (rev4)
Date: Fri, 16 Mar 2018 12:33:24 +0200	[thread overview]
Message-ID: <20180316103324.GE5453@intel.com> (raw)
In-Reply-To: <20180315232754.17606.39432@emeril.freedesktop.org>

On Thu, Mar 15, 2018 at 11:27:54PM -0000, Patchwork wrote:
> == Series Details ==
> 
> Series: series starting with [1/6] Revert "drm: Use a flexible array member for blob property data" (rev4)
> URL   : https://patchwork.freedesktop.org/series/38886/
> State : failure
> 
> == Summary ==
> 
> ---- Possible new issues:
> 
> Test kms_cursor_crc:
>         Subgroup cursor-128x128-suspend:
>                 pass       -> FAIL       (shard-apl)

<6>[  626.852771] Freezing user space processes ... 
<4>[  627.123848] hpet1: lost 7161 rtc interrupts
<4>[  628.008661] hpet1: lost 7161 rtc interrupts
<4>[  628.893790] hpet1: lost 7160 rtc interrupts
<4>[  629.779156] hpet1: lost 7161 rtc interrupts
<4>[  630.663018] hpet1: lost 7161 rtc interrupts
<4>[  631.526633] hpet1: lost 7161 rtc interrupts
<4>[  632.410351] hpet1: lost 7161 rtc interrupts
<4>[  633.294550] hpet1: lost 7161 rtc interrupts
<4>[  634.178637] hpet1: lost 7161 rtc interrupts
<4>[  635.062672] hpet1: lost 7160 rtc interrupts
<4>[  635.946840] hpet1: lost 7161 rtc interrupts
<4>[  636.832115] hpet1: lost 7161 rtc interrupts
<4>[  637.717328] hpet1: lost 7161 rtc interrupts
<4>[  638.581866] hpet1: lost 7161 rtc interrupts
<4>[  639.446595] hpet1: lost 7161 rtc interrupts
<4>[  640.332169] hpet1: lost 7161 rtc interrupts
<4>[  641.217026] hpet1: lost 7160 rtc interrupts
<3>[  646.850043] Freezing of tasks failed after 20.007 seconds (1 tasks refusing to freeze, wq_busy=0):
<6>[  646.850229] fstrim          D    0  1998   1997 0x00000004
<4>[  646.850259] Call Trace:
<4>[  646.850277]  ? __schedule+0x3c7/0xb00
<4>[  646.850289]  ? wait_for_common_io.constprop.2+0xe2/0x180
<4>[  646.850296]  schedule+0x37/0x90
<4>[  646.850303]  schedule_timeout+0x21d/0x510
<4>[  646.850311]  ? trace_hardirqs_on_caller+0xde/0x1c0
<4>[  646.850327]  ? wait_for_common_io.constprop.2+0xe2/0x180
<4>[  646.850333]  io_schedule_timeout+0x14/0x40
<4>[  646.850340]  wait_for_common_io.constprop.2+0x101/0x180
<4>[  646.850348]  ? wake_up_q+0x70/0x70
<4>[  646.850360]  submit_bio_wait+0x4a/0x60
<4>[  646.850376]  blkdev_issue_discard+0x6c/0xb0
<4>[  646.850394]  ? ext4_trim_fs+0x489/0xbe0
<4>[  646.850398]  ext4_trim_fs+0x489/0xbe0
<4>[  646.850431]  ext4_ioctl+0xc7c/0xf10
<4>[  646.850448]  do_vfs_ioctl+0x8a/0x670
<4>[  646.850455]  ? SyS_newfstat+0x29/0x40
<4>[  646.850463]  ? entry_SYSCALL_64_after_hwframe+0x52/0xb7
<4>[  646.850472]  SyS_ioctl+0x36/0x70
<4>[  646.850482]  do_syscall_64+0x65/0x1a0
<4>[  646.850490]  entry_SYSCALL_64_after_hwframe+0x42/0xb7
<4>[  646.850496] RIP: 0033:0x7fd55d4f1587
<4>[  646.850500] RSP: 002b:00007ffe19de8038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
<4>[  646.850509] RAX: ffffffffffffffda RBX: 0000000000000004 RCX: 00007fd55d4f1587
<4>[  646.850513] RDX: 00007ffe19de8040 RSI: 00000000c0185879 RDI: 0000000000000004
<4>[  646.850517] RBP: 0000557ba4f5ff90 R08: 0000557ba4f66180 R09: 0000000000000000
<4>[  646.850521] R10: 000000000000000a R11: 0000000000000246 R12: 0000557ba4f60800
<4>[  646.850526] R13: 0000000000000000 R14: 00007fd55dc09250 R15: 0000557ba4f60800
<6>[  646.850553] OOM killer enabled.
<6>[  646.850557] Restarting tasks ... done.
<6>[  646.866332] video LNXVIDEO:00: Restoring backlight state
<6>[  646.866359] PM: suspend exit

Doesn't seem particularly relevant for this series.

> 
> ---- Known issues:
> 
> Test kms_frontbuffer_tracking:
>         Subgroup fbc-1p-primscrn-cur-indfb-draw-mmap-gtt:
>                 pass       -> FAIL       (shard-apl) fdo#101623
> Test kms_vblank:
>         Subgroup pipe-b-ts-continuation-suspend:
>                 pass       -> SKIP       (shard-snb) fdo#105411
> 
> fdo#101623 https://bugs.freedesktop.org/show_bug.cgi?id=101623
> fdo#105411 https://bugs.freedesktop.org/show_bug.cgi?id=105411
> 
> shard-apl        total:3442 pass:1812 dwarn:1   dfail:0   fail:9   skip:1619 time:12935s
> shard-hsw        total:3442 pass:1768 dwarn:1   dfail:0   fail:1   skip:1671 time:11957s
> shard-snb        total:3442 pass:1355 dwarn:1   dfail:0   fail:3   skip:2083 time:7154s
> Blacklisted hosts:
> shard-kbl        total:2091 pass:1139 dwarn:17  dfail:1   fail:4   skip:929 time:5806s
> 
> == Logs ==
> 
> For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_8371/shards.html

-- 
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      reply	other threads:[~2018-03-16 10:33 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-23 19:25 [PATCH 1/6] Revert "drm: Use a flexible array member for blob property data" Ville Syrjala
2018-02-23 19:25 ` [PATCH 2/6] drm: Remove now pointelss blob->data casts Ville Syrjala
2018-03-01  8:57   ` Sharma, Shashank
2018-02-23 19:25 ` [PATCH 3/6] drm: Verify gamma/degamma LUT size Ville Syrjala
2018-03-01 13:13   ` [Intel-gfx] " Sharma, Shashank
2018-03-01 13:24     ` Ville Syrjälä
2018-03-01 14:28       ` Sharma, Shashank
2018-03-01 14:35         ` [Intel-gfx] " Ville Syrjälä
2018-03-06  7:56   ` Daniel Vetter
2018-03-15 15:22   ` [PATCH v2 " Ville Syrjala
2018-02-23 19:25 ` [PATCH 4/6] drm: Introduce drm_color_lut_size() Ville Syrjala
2018-03-06  7:54   ` Daniel Vetter
2018-03-16 14:14     ` [Intel-gfx] " Ville Syrjälä
2018-03-15 15:23   ` [PATCH v2 " Ville Syrjala
2018-02-23 19:25 ` [PATCH 5/6] drm/i915: Remove the blob->data casts Ville Syrjala
2018-03-15 17:13   ` [PATCH v2 " Ville Syrjala
2018-02-23 19:25 ` [PATCH 6/6] drm/i915: Use drm_color_lut_size() Ville Syrjala
2018-02-23 19:55 ` ✓ Fi.CI.BAT: success for series starting with [1/6] Revert "drm: Use a flexible array member for blob property data" Patchwork
2018-02-23 20:38 ` ✓ Fi.CI.IGT: " Patchwork
2018-03-01  8:49 ` [PATCH 1/6] " Sharma, Shashank
2018-03-15 15:45 ` ✗ Fi.CI.BAT: failure for series starting with [1/6] Revert "drm: Use a flexible array member for blob property data" (rev3) Patchwork
2018-03-15 18:11 ` ✗ Fi.CI.BAT: failure for series starting with [1/6] Revert "drm: Use a flexible array member for blob property data" (rev4) Patchwork
2018-03-15 20:09 ` ✓ Fi.CI.BAT: success " Patchwork
2018-03-15 23:27 ` ✗ Fi.CI.IGT: failure " Patchwork
2018-03-16 10:33   ` Ville Syrjälä [this message]

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=20180316103324.GE5453@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=intel-gfx@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.