| Summary: | [CI] igt@* - fail - rtcwake failed - Freezing of tasks failed after 20.001 seconds (1 tasks refusing to freeze, wq_busy=0): fstrim D 0 3100 3099 0x00000004 | ||
|---|---|---|---|
| Product: | DRI | Reporter: | Martin Peres <martin.peres> |
| Component: | IGT | Assignee: | Tomi Sarvela <tomi.p.sarvela> |
| Status: | CLOSED WORKSFORME | QA Contact: | |
| Severity: | critical | ||
| Priority: | high | CC: | intel-gfx-bugs, petri.latvala, tomi.p.sarvela |
| Version: | DRI git | ||
| Hardware: | Other | ||
| OS: | All | ||
| See Also: |
https://bugs.freedesktop.org/show_bug.cgi?id=102899 https://bugs.freedesktop.org/show_bug.cgi?id=102901 https://bugs.freedesktop.org/show_bug.cgi?id=103077 |
||
| Whiteboard: | ReadyForDev | ||
| i915 platform: | HSW | i915 features: | |
|
Description
Martin Peres
2017-08-16 13:43:26 UTC
Also seen on SandyBridge. Current statistics are 100% reproducible (SNB will appear in an hour): https://intel-gfx-ci.01.org/cibuglog/index.html%3Faction_failures_history=210.html Based on the logs in the bug description from Martin, the hibernation got interrupted due to: PM: Swap header not found! So could you try recreating the swap area or otherwise make it sure the hibernation image can be saved? Using a swapfile not swap partition. Did it really get all the way to the end of writing (or just creating) the hibernation image before checking it had somewhere to save that image? (In reply to Chris Wilson from comment #5) > Using a swapfile not swap partition. > > Did it really get all the way to the end of writing (or just creating) the > hibernation image before checking it had somewhere to save that image? AFAICS it did write all the pages, but failed to update some metadata in the end which is in the swapheader. So I'm guessing it's just corrupted swap area and would need to be recreated. This test also is failing on GLK QA
Tests List:
igt@drv_suspend@debugfs-reader-hibernate
====================================================
Output
====================================================
. . .
**** DEBUG ****
(drv_suspend:12371) igt-core-DEBUG: Test requirement passed: !igt_run_in_simulation()
(drv_suspend:12371) igt-aux-DEBUG: Test requirement passed: (power_dir = open("/sys/power", O_RDONLY)) >= 0
(drv_suspend:12371) igt-aux-DEBUG: Test requirement passed: get_supported_suspend_states(power_dir) & (1 << state)
(drv_suspend:12371) igt-aux-DEBUG: Test requirement passed: test == SUSPEND_TEST_NONE || faccessat(power_dir, "pm_test", R_OK | W_OK, 0) == 0
(drv_suspend:12371) igt-aux-DEBUG: Test requirement passed: ret == 0
(drv_suspend:12371) igt-aux-CRITICAL: Test assertion failure function suspend_via_rtcwake, file igt_aux.c:769:
(drv_suspend:12371) igt-aux-CRITICAL: Failed assertion: ret == 0
(drv_suspend:12371) igt-aux-CRITICAL: rtcwake failed with 256
Check dmesg for further details.
(drv_suspend:12371) igt-core-INFO: Stack trace:
(drv_suspend:12371) igt-core-INFO: #0 [__igt_fail_assert+0x101]
(drv_suspend:12371) igt-core-INFO: #1 [igt_system_suspend_autoresume+0x5ae]
(drv_suspend:12371) igt-core-INFO: #2 [<unknown>+0x5ae]
**** END ****
. . .
This is my configuration:
====================================================
Graphic Stack
====================================================
Component: drm
tag: libdrm-2.4.81-55-g76418c2
commit: 76418c244d4c52a8dd20809e3e8b4e70501fc76f
Component: cairo
tag: 1.15.6-38-g1220e3c
commit: 1220e3c6b8f94a00ac7afee15f21e6782655d97c
Component: intel-gpu-tools
tag: intel-gpu-tools-1.19-312-gda197b5
commit: da197b5f3cb516aaaea72d0d60b0f5c1c81081dd
Component: piglit
tag: piglit-v1
commit: 2753955998d7deb90f681cf4cb1253c4519dfd1d
======================================
Software
======================================
kernel version : 4.14.0-rc1-drm-tip-ww38-commit-ab2e3a0+
hostname : GLK-1-GLKRVP1DDR405
architecture : x86_64
os version : Ubuntu 16.10
os codename : yakkety
kernel driver : i915
bios revision : 60.34
bios release date : 08/09/2017
ksc : 1.41
hardware acceleration : disabled
swap partition : enabled on (/dev/sda3)
======================================
Graphic drivers
======================================
libdrm : 2.4.83
cairo : 1.15.9
intel-gpu-tools (tag) : intel-gpu-tools-1.19-289-gc718ba8
intel-gpu-tools (commit) : c718ba8
======================================
Hardware
======================================
platform : Geminilake
motherboard model : Geminilake
motherboard id : GLKRVP1DDR4(05)
form factor : Hand Held
manufacturer : IntelCorp.
cpu family : Other
cpu family id : 6
cpu information : Genuine Intel(R) CPU @ 1.10GHz
gpu card : Intel Corporation Device 3185 (rev 03) (prog-if 00 [VGA controller])
memory ram : 7.6 GB
max memory ram : 16 GB
cpu thread : 2
cpu core : 2
cpu model : 122
cpu stepping : 1
socket : Other
hard drive : 223GiB (240GB)
current cd clock frequency : 316800 kHz
maximum cd clock frequency : 316800 kHz
displays connected : eDP-1 DP-1 HDMI-A-2
======================================
Firmware
======================================
dmc fw loaded : yes
dmc version : 1.4
guc fw loaded : SUCCESS
guc version wanted : 10.56
guc version found : 10.56
huc fw loaded : yes
======================================
kernel parameters
======================================
quiet splash drm.debug=0xe i915.enable_guc_submission=2 i915.enable_guc_loading=2 i915.alpha_support=1 resume=/dev/sda3
After 4.14.0-rc1 KBL-shards either have the rtcwake failed with 256 or incompletes. Some incomplete runs with pstore: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3102/shard-kbl4/igt@gem_exec_suspend@basic-S4.html https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3104/shard-kbl2/igt@gem_exec_suspend@basic-S4.html https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3108/shard-kbl5/igt@gem_exec_suspend@basic-S4.html https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3109/shard-kbl5/igt@gem_exec_suspend@basic-S4.html https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3112/shard-kbl4/igt@gem_exec_suspend@basic-S4.html https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3116/shard-kbl5/igt@gem_exec_suspend@basic-S4.html The backtraces are not identical, but they all have: "e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang:" This test also is failing on GLK QA
Tests List:
igt@drv_suspend@debugfs-reader-hibernate
igt@drv_suspend@forcewake-hibernate
====================================================
Output
====================================================
. . .
**** DEBUG ****
(drv_suspend:12546) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
(drv_suspend:12546) igt-core-DEBUG: Test requirement passed: !igt_run_in_simulation()
(drv_suspend:12546) igt-aux-DEBUG: Test requirement passed: (power_dir = open("/sys/power", O_RDONLY)) >= 0
(drv_suspend:12546) igt-aux-DEBUG: Test requirement passed: get_supported_suspend_states(power_dir) & (1 << state)
(drv_suspend:12546) igt-aux-DEBUG: Test requirement passed: test == SUSPEND_TEST_NONE || faccessat(power_dir, "pm_test", R_OK | W_OK, 0) == 0
(drv_suspend:12546) igt-aux-DEBUG: Test requirement passed: ret == 0
(drv_suspend:12546) igt-aux-CRITICAL: Test assertion failure function suspend_via_rtcwake, file igt_aux.c:769:
(drv_suspend:12546) igt-aux-CRITICAL: Failed assertion: ret == 0
(drv_suspend:12546) igt-aux-CRITICAL: Last errno: 2, No such file or directory
(drv_suspend:12546) igt-aux-CRITICAL: rtcwake failed with 256
Check dmesg for further details.
(drv_suspend:12546) igt-core-INFO: Stack trace:
(drv_suspend:12546) igt-core-INFO: #0 [__igt_fail_assert+0x101]
(drv_suspend:12546) igt-core-INFO: #1 [igt_system_suspend_autoresume+0x5ae]
(drv_suspend:12546) igt-core-INFO: #2 [<unknown>+0x5ae]
**** END ****
. . .
This is my configuration:
======================================
Graphic stack
======================================
Component: drm
tag: libdrm-2.4.81-56-g7c71188
commit: 7c71188610b4ceba0339c2bc884320bcb749adee
Component: cairo
tag: 1.15.6-42-gdccbed7
commit: dccbed7d78d32bd3b912e8810379451dd94e6a1f
Component: intel-gpu-tools
tag: intel-gpu-tools-1.19-332-g0a91a5e
commit: 0a91a5e9624d41d23b79e2540eda111cb56d42d9
Component: piglit
tag: piglit-v1
commit: 95e2f51a28b6cf7ff77d84e1234121c98f10ef64
======================================
Software
======================================
kernel version : 4.14.0-rc2-drm-tip-ww39-commit-d76cbbc+
hostname : GLK-2-GLKRVP1DDR405
architecture : x86_64
os version : Ubuntu 16.10
os codename : yakkety
kernel driver : i915
bios revision : 62.30
bios release date : 08/22/2017
ksc : 1.41
hardware acceleration : disabled
swap partition : enabled on (/dev/sda3)
======================================
Graphic drivers
======================================
grep: /opt/X11R7/var/log/Xorg.0.log: No such file or directory
libdrm : 2.4.83
cairo : 1.15.9
intel-gpu-tools (tag) : intel-gpu-tools-1.19-332-g0a91a5e
intel-gpu-tools (commit) : 0a91a5e
======================================
Hardware
======================================
. . .
======================================
Firmware
======================================
dmc fw loaded : yes
dmc version : 1.4
guc fw loaded : SUCCESS
guc version wanted : 10.56
guc version found : 10.56
huc fw loaded : yes
======================================
kernel parameters
======================================
quiet drm.debug=0xe pci=pcie_bus_safe i915.alpha_support=1 i915.enable_guc_loading=2 i915.enable_guc_submission=2 intel_iommu=igfx_off auto panic=1 nmi_watchdog=panic resume=/dev/sda3 fastboot
High as not being BAT... The pattern with e1000e related incompletes for KBL-shards has stopped since 4.14.-0-rc2. CI_DRM_3253 GLK-shards dmesg-fail: (drv_suspend:2655) igt-core-WARNING: [cmd] rtcwake: write error (drv_suspend:2655) igt-aux-CRITICAL: Test assertion failure function suspend_via_rtcwake, file igt_aux.c:809: (drv_suspend:2655) igt-aux-CRITICAL: Failed assertion: ret == 0 (drv_suspend:2655) igt-aux-CRITICAL: rtcwake failed with 1 Check dmesg for further details. from dmesg: [ 224.209920] [drm:intel_dp_sink_crc [i915]] *ERROR* Panel is unable to calculate any CRC after 6 vblanks https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3253/shard-glkb4/igt@drv_suspend@debugfs-reader-hibernate.html Also, KBL-shards: igt@kms_flip@vblank-vs-suspend (kms_flip:1361) igt-core-WARNING: [cmd] rtcwake: [cmd] write error (kms_flip:1361) igt-aux-CRITICAL: Test assertion failure function suspend_via_rtcwake, file igt_aux.c:809: (kms_flip:1361) igt-aux-CRITICAL: Failed assertion: ret == 0 (kms_flip:1361) igt-aux-CRITICAL: Last errno: 25, Inappropriate ioctl for device (kms_flip:1361) igt-aux-CRITICAL: rtcwake failed with 1 Check dmesg for further details. Subtest vblank-vs-suspend failed. https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3260/shard-kbl7/igt@kms_flip@vblank-vs-suspend.html (In reply to Marta Löfstedt from comment #8) > After 4.14.0-rc1 KBL-shards either have the rtcwake failed with 256 or > incompletes. > > Some incomplete runs with pstore: > > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3102/shard-kbl4/ > igt@gem_exec_suspend@basic-S4.html > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3104/shard-kbl2/ > igt@gem_exec_suspend@basic-S4.html > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3108/shard-kbl5/ > igt@gem_exec_suspend@basic-S4.html > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3109/shard-kbl5/ > igt@gem_exec_suspend@basic-S4.html > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3112/shard-kbl4/ > igt@gem_exec_suspend@basic-S4.html > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3116/shard-kbl5/ > igt@gem_exec_suspend@basic-S4.html > > The backtraces are not identical, but they all have: > "e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang:" To clarify here is a run where don't get incomplete but hit the failure described in the first entry for this bug: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3107/shard-kbl2/igt@drv_suspend@debugfs-reader-hibernate.html However, I have now discussed with Imre and according to him this bug requires the association with the backtrace that is included in the kernel bugzilla bug and/or? the string "[ 680.783120] fstrim D 0 1612 1611 0x00000004" Also, the links from the original entry in this bug is dead. Also, comments 11 to 14 are referring to results where the fstrim issue is not reproduced and should be disregarded. CI_DRM_3269 APL-shards igt@gem_workarounds@hibernate-resume-fd <3>[ 1334.253813] PM: Cannot find swap device, try swapon -a. <3>[ 1334.253856] PM: Cannot get swap writer (gem_workarounds:6731) igt-core-WARNING: [cmd] rtcwake: write error (gem_workarounds:6731) igt-aux-CRITICAL: Test assertion failure function suspend_via_rtcwake, file igt_aux.c:809: (gem_workarounds:6731) igt-aux-CRITICAL: Failed assertion: ret == 0 (gem_workarounds:6731) igt-aux-CRITICAL: rtcwake failed with 1 Check dmesg for further details. Subtest hibernate-resume-fd failed. https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3269/shard-apl4/igt@gem_workarounds@hibernate-resume-fd.html The fstrim issue is no longer reproduced I will close this bug. rtcwake issues related to swap are should be filed on bug 103375 Fstrim issue is back: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4207/shard-hsw8/igt@drv_suspend@forcewake.html <6>[ 644.741804] Freezing user space processes ... <3>[ 664.748049] Freezing of tasks failed after 20.006 seconds (1 tasks refusing to freeze, wq_busy=0): <6>[ 664.748077] fstrim D 0 4613 4612 0x00000004 <4>[ 664.748086] Call Trace: <4>[ 664.748092] ? __schedule+0x3c3/0xaf0 <4>[ 664.748096] ? wait_for_common_io.constprop.2+0xe2/0x180 <4>[ 664.748099] schedule+0x37/0x90 <4>[ 664.748101] schedule_timeout+0x21f/0x520 <4>[ 664.748105] ? trace_hardirqs_on_caller+0xde/0x1c0 <4>[ 664.748110] ? wait_for_common_io.constprop.2+0xe2/0x180 <4>[ 664.748112] io_schedule_timeout+0x14/0x40 <4>[ 664.748114] wait_for_common_io.constprop.2+0x101/0x180 <4>[ 664.748117] ? wake_up_q+0x70/0x70 <4>[ 664.748122] submit_bio_wait+0x4a/0x60 <4>[ 664.748127] blkdev_issue_discard+0x6c/0xb0 <4>[ 664.748133] ? ext4_trim_fs+0x489/0xbe0 <4>[ 664.748135] ext4_trim_fs+0x489/0xbe0 <4>[ 664.748145] ext4_ioctl+0xc7c/0xf10 <4>[ 664.748151] do_vfs_ioctl+0x8a/0x670 <4>[ 664.748154] ? entry_SYSCALL_64_fastpath+0x5/0x8f <4>[ 664.748156] ? trace_hardirqs_on_caller+0xde/0x1c0 <4>[ 664.748160] SyS_ioctl+0x36/0x70 <4>[ 664.748163] entry_SYSCALL_64_fastpath+0x22/0x8f <4>[ 664.748165] RIP: 0033:0x7fc5d2008587 <4>[ 664.748166] RSP: 002b:00007ffd499589c8 EFLAGS: 00000246 https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4207/shard-hsw2/igt@drv_suspend@sysfs-reader.html <6>[ 600.885325] Freezing user space processes ... <3>[ 620.893284] Freezing of tasks failed after 20.007 seconds (1 tasks refusing to freeze, wq_busy=0): <6>[ 620.893324] fstrim D 0 2954 2953 0x00000004 <4>[ 620.893337] Call Trace: <4>[ 620.893347] ? __schedule+0x3c3/0xaf0 <4>[ 620.893355] ? wait_for_common_io.constprop.2+0xe2/0x180 <4>[ 620.893359] schedule+0x37/0x90 <4>[ 620.893363] schedule_timeout+0x21f/0x520 <4>[ 620.893369] ? trace_hardirqs_on_caller+0xde/0x1c0 <4>[ 620.893378] ? wait_for_common_io.constprop.2+0xe2/0x180 <4>[ 620.893382] io_schedule_timeout+0x14/0x40 <4>[ 620.893386] wait_for_common_io.constprop.2+0x101/0x180 <4>[ 620.893391] ? wake_up_q+0x70/0x70 <4>[ 620.893400] submit_bio_wait+0x4a/0x60 <4>[ 620.893409] blkdev_issue_discard+0x6c/0xb0 <4>[ 620.893420] ? ext4_trim_fs+0x489/0xbe0 <4>[ 620.893423] ext4_trim_fs+0x489/0xbe0 <4>[ 620.893441] ext4_ioctl+0xc7c/0xf10 <4>[ 620.893451] do_vfs_ioctl+0x8a/0x670 <4>[ 620.893456] ? entry_SYSCALL_64_fastpath+0x5/0x8f <4>[ 620.893460] ? trace_hardirqs_on_caller+0xde/0x1c0 <4>[ 620.893466] SyS_ioctl+0x36/0x70 <4>[ 620.893472] entry_SYSCALL_64_fastpath+0x22/0x8f <4>[ 620.893475] RIP: 0033:0x7fe76d208587 <4>[ 620.893477] RSP: 002b:00007fffd45fa068 EFLAGS: 00000246 <6>[ 620.893492] OOM killer enabled. <6>[ 620.893494] Restarting tasks ... done. <6>[ 620.896660] video LNXVIDEO:00: Restoring backlight state <6>[ 620.896667] PM: suspend exit Based on the latest comment on https://bugzilla.kernel.org/show_bug.cgi?id=196691 the proposed solution is to make the trim/discard operation more fine-grained by setting discard_max_bytes. Adding CI people, and changing the component accordingly. CI should be now done, to be followed. Imre, does this setting persist over suspend? (In reply to Jani Saarinen from comment #23) > Imre, does this setting persist over suspend? /sys/block/<dev>/queue/discard_max_bytes ? I would assume it doesn't but you can easily check it by reading out after suspend and comparing it what you have set it to. (In reply to Imre Deak from comment #24) > (In reply to Jani Saarinen from comment #23) > > Imre, does this setting persist over suspend? > > /sys/block/<dev>/queue/discard_max_bytes ? I would assume it doesn't but you Err, I'd assume it does persist. > can easily check it by reading out after suspend and comparing it what you > have set it to. https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4297/shard-apl4/igt@drv_suspend@debugfs-reader.html <3>[ 599.936578] Freezing of tasks failed after 20.007 seconds (1 tasks refusing to freeze, wq_busy=0): <6>[ 599.936811] fstrim D 0 2170 2169 0x00000004 <4>[ 599.936836] Call Trace: <4>[ 599.936852] ? __schedule+0x3c7/0xb00 <4>[ 599.936865] ? wait_for_common_io.constprop.2+0xe2/0x180 <4>[ 599.936872] schedule+0x37/0x90 <4>[ 599.936878] schedule_timeout+0x21d/0x510 <4>[ 599.936886] ? trace_hardirqs_on_caller+0xde/0x1c0 <4>[ 599.936940] ? wait_for_common_io.constprop.2+0xe2/0x180 <4>[ 599.936946] io_schedule_timeout+0x14/0x40 <4>[ 599.936953] wait_for_common_io.constprop.2+0x101/0x180 <4>[ 599.936961] ? wake_up_q+0x70/0x70 <4>[ 599.936973] submit_bio_wait+0x4a/0x60 <4>[ 599.936988] blkdev_issue_discard+0x6c/0xb0 <4>[ 599.937005] ? ext4_trim_fs+0x489/0xbe0 <4>[ 599.937009] ext4_trim_fs+0x489/0xbe0 <4>[ 599.937042] ext4_ioctl+0xc7c/0xf10 <4>[ 599.937059] do_vfs_ioctl+0x8a/0x670 <4>[ 599.937065] ? SyS_newfstat+0x29/0x40 <4>[ 599.937074] ? entry_SYSCALL_64_after_hwframe+0x52/0xb7 <4>[ 599.937083] SyS_ioctl+0x36/0x70 <4>[ 599.937093] do_syscall_64+0x65/0x1a0 <4>[ 599.937101] entry_SYSCALL_64_after_hwframe+0x42/0xb7 <4>[ 599.937108] RIP: 0033:0x7f36ed006587 <4>[ 599.937112] RSP: 002b:00007ffe74ab3a58 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 <4>[ 599.937121] RAX: ffffffffffffffda RBX: 0000000000000004 RCX: 00007f36ed006587 <4>[ 599.937125] RDX: 00007ffe74ab3a60 RSI: 00000000c0185879 RDI: 0000000000000004 <4>[ 599.937129] RBP: 000055fbc4a25f90 R08: 000055fbc4a2c180 R09: 0000000000000000 <4>[ 599.937133] R10: 000000000000000a R11: 0000000000000246 R12: 000055fbc4a26800 <4>[ 599.937138] R13: 0000000000000000 R14: 00007f36ed71e250 R15: 000055fbc4a26800 <6>[ 599.937165] OOM killer enabled. <6>[ 599.937169] Restarting tasks ... done. https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3852/shard-hsw1/igt@kms_vblank@pipe-c-ts-continuation-dpms-suspend.html <7>[ 695.011079] [drm:intel_runtime_suspend [i915]] Device suspended <3>[ 695.719398] Freezing of tasks failed after 20.001 seconds (1 tasks refusing to freeze, wq_busy=0): <6>[ 695.719448] fstrim D 0 3100 3099 0x00000004 <4>[ 695.719459] Call Trace: <4>[ 695.719467] ? __schedule+0x3c7/0xb00 <4>[ 695.719475] ? wait_for_common_io.constprop.2+0xe2/0x180 <4>[ 695.719478] schedule+0x37/0x90 <4>[ 695.719483] schedule_timeout+0x21d/0x510 <4>[ 695.719487] ? trace_hardirqs_on_caller+0xde/0x1c0 <4>[ 695.719496] ? wait_for_common_io.constprop.2+0xe2/0x180 <4>[ 695.719500] io_schedule_timeout+0x14/0x40 <4>[ 695.719504] wait_for_common_io.constprop.2+0x101/0x180 <4>[ 695.719509] ? wake_up_q+0x70/0x70 <4>[ 695.719516] submit_bio_wait+0x4a/0x60 <4>[ 695.719526] blkdev_issue_discard+0x6c/0xb0 <4>[ 695.719536] ? ext4_trim_fs+0x489/0xbe0 <4>[ 695.719538] ext4_trim_fs+0x489/0xbe0 <4>[ 695.719558] ext4_ioctl+0xc7c/0xf10 <4>[ 695.719567] do_vfs_ioctl+0x8a/0x670 <4>[ 695.719571] ? SyS_newfstat+0x29/0x40 <4>[ 695.719577] ? entry_SYSCALL_64_after_hwframe+0x52/0xb7 <4>[ 695.719582] SyS_ioctl+0x36/0x70 <4>[ 695.719588] do_syscall_64+0x65/0x1a0 <4>[ 695.719593] entry_SYSCALL_64_after_hwframe+0x42/0xb7 <4>[ 695.719596] RIP: 0033:0x7fc4502e5587 <4>[ 695.719598] RSP: 002b:00007ffdc5d77548 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 <4>[ 695.719603] RAX: ffffffffffffffda RBX: 0000000000000004 RCX: 00007fc4502e5587 <4>[ 695.719605] RDX: 00007ffdc5d77550 RSI: 00000000c0185879 RDI: 0000000000000004 <4>[ 695.719608] RBP: 000055e347ebbf90 R08: 000055e347ec2180 R09: 0000000000000000 <4>[ 695.719610] R10: 000000000000000a R11: 0000000000000246 R12: 000055e347ebc800 <4>[ 695.719612] R13: 0000000000000000 R14: 00007fc4509fd250 R15: 000055e347ebc800 I will close and archive this again since it hasn't been seen since: IGT_4317: 2018-03-02 / 238 runs ago |
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.