Bug 106108 - [CI] igt@* - incomplete - ext4 issue
Summary: [CI] igt@* - incomplete - ext4 issue
Status: NEW
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: Other All
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard: ReadyForDev
Keywords:
Depends on:
Blocks:
 
Reported: 2018-04-17 17:14 UTC by Martin Peres
Modified: 2018-09-16 19:27 UTC (History)
1 user (show)

See Also:
i915 platform: KBL
i915 features: display/Other


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Peres 2018-04-17 17:14:07 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_16/fi-kbl-7567u/igt@kms_cursor_legacy@pipe-b-single-move.html

[...]
<4>[  100.756196]  __ext4_new_inode+0x3cf/0x16a0
<4>[  100.756206]  ext4_tmpfile+0x50/0x160
<4>[  100.756212]  vfs_tmpfile+0x67/0xe0
<4>[  100.756215]  path_openat+0x78e/0xb10
<4>[  100.756222]  do_filp_open+0x96/0x110
<4>[  100.756231]  ? __alloc_fd+0xe0/0x1e0
<4>[  100.756293]  ? _raw_spin_unlock+0x29/0x40
<4>[  100.756297]  ? do_sys_open+0x1b8/0x240
<4>[  100.756299]  do_sys_open+0x1b8/0x240
<4>[  100.756303]  do_syscall_64+0x6b/0x1b0
<4>[  100.756306]  entry_SYSCALL_64_after_hwframe+0x42/0xb7
<4>[  100.756307] RIP: 0033:0x7f3e33ccdc8e
<4>[  100.756308] RSP: 002b:00007ffc03aec7b0 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
<4>[  100.756310] RAX: ffffffffffffffda RBX: 0000564754458ec0 RCX: 00007f3e33ccdc8e
<4>[  100.756311] RDX: 0000000000410082 RSI: 00007f3e33d71fd1 RDI: 00000000ffffff9c
<4>[  100.756312] RBP: 00007ffc03aef180 R08: 00007ffc03aed7a0 R09: 00007f3e333152b0
<4>[  100.756313] R10: 0000000000000180 R11: 0000000000000246 R12: 00007ffc03af0e77
<4>[  100.756314] R13: 000000000000006e R14: 00005647544558c8 R15: 0000000000000000

The output is truncated because of the ftrace taking so much space...


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.