intel issueshttps://gitlab.freedesktop.org/drm/intel/-/issues2023-11-15T12:11:27Zhttps://gitlab.freedesktop.org/drm/intel/-/issues/9677igt@i915_selftest@live@ring_submission - incomplete - No warnings/errors2023-11-15T12:11:27ZTejasree Illipilliigt@i915_selftest@live@ring_submission - incomplete - No warnings/errors<!--
Please read this first: https://drm.pages.freedesktop.org/intel-docs/how-to-file-i915-bugs.html
-->
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_126202v1/fi-hsw-4770/igt@i915_selftest@live@ring_submission.html
````
Out
Starti...<!--
Please read this first: https://drm.pages.freedesktop.org/intel-docs/how-to-file-i915-bugs.html
-->
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_126202v1/fi-hsw-4770/igt@i915_selftest@live@ring_submission.html
````
Out
Starting dynamic subtest: ring_submission
Err
Starting dynamic subtest: ring_submission
Dmesg
<6> [252.465816] [IGT] i915_selftest: starting dynamic subtest ring_submission
<5> [252.591279] Setting dangerous option live_selftests - tainting kernel
````https://gitlab.freedesktop.org/drm/intel/-/issues/9616igt@gem_eio@in-flight-contexts-immediate - Dmesg-warn/Dmesg--fail - *ERROR* f...2023-11-02T09:13:16ZGundla karthikigt@gem_eio@in-flight-contexts-immediate - Dmesg-warn/Dmesg--fail - *ERROR* failed to set bcs0 head to zero ctl .*https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1435/fi-hsw-4770/igt@gem_eio@in-flight-contexts-immediate.html#dmesg-warnings592
`````````
<7> [177.876624] heartbeat *
<7> [177.876631] heartbeat Idle? no
<7> [177.876633] heartbeat IRQ: e...https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1435/fi-hsw-4770/igt@gem_eio@in-flight-contexts-immediate.html#dmesg-warnings592
`````````
<7> [177.876624] heartbeat *
<7> [177.876631] heartbeat Idle? no
<7> [177.876633] heartbeat IRQ: enabled
<7> [177.876635] heartbeat Signals:
<7> [177.876637] heartbeat [2c:5c78*] @ 510ms
<6> [177.877119] i915 0000:00:02.0: [drm] GPU HANG: ecode 7:2:9494949c, in gem_eio [5534]
<5> [177.877816] i915 0000:00:02.0: [drm] GT0: Resetting chip for stopped heartbeat on bcs0
<3> [177.981058] i915 0000:00:02.0: [drm] *ERROR* failed to set bcs0 head to zero ctl 00000000 head 00003eac tail 00000000 start 7ffa0000
<5> [177.981305] i915 0000:00:02.0: [drm] gem_eio[5534] context reset due to GPU hang
<7> [177.981350] i915 0000:00:02.0: [drm:__i915_request_reset [i915]] client gem_eio[5534]: gained 1 ban score, now 1
<7> [177.982895] i915 0000:00:02.0: [drm:i915_drop_caches_set [i915]] Dropping caches: 0x00000008 [0x00000008]
```````````https://gitlab.freedesktop.org/drm/intel/-/issues/9311igt@i915_selftest@mock - dmesg-warn - igt_mock_splintered_region too large co...2024-02-26T10:20:21ZSAI NANDANigt@i915_selftest@mock - dmesg-warn - igt_mock_splintered_region too large contiguous allocation was not rejected, i915/intel_memory_region_mock_selftests: igt_mock_splintered_region failed with error -22https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13622/re-dg2-13/igt@i915_selftest@mock@memory_region.html#dmesg-warnings16
````
<6> [835.255066] [IGT] i915_selftest: starting dynamic subtest memory_region
<5> [835.321689] Setting dangero...https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13622/re-dg2-13/igt@i915_selftest@mock@memory_region.html#dmesg-warnings16
````
<6> [835.255066] [IGT] i915_selftest: starting dynamic subtest memory_region
<5> [835.321689] Setting dangerous option mock_selftests - tainting kernel
<6> [835.346955] i915: Performing mock selftests with st_random_seed=0x989ba2db st_timeout=500
<6> [835.346958] i915: Running memory_region
<7> [835.347099] mock: [drm:intel_display_device_probe [i915]] No display ID found for device ID 0000; disabling display.
<6> [835.347455] mock: [drm] Using Transparent Hugepages
<7> [835.347704] mock: [drm:intel_uc_init_early [i915]] GT0: enable_guc=3 (guc:no submission:no huc:no slpc:no)
<6> [835.347853] mock: [drm] GT0: Incompatible option enable_guc=3 - GuC is not supported!
<6> [835.347855] mock: [drm] GT0: Incompatible option enable_guc=3 - HuC is not supported!
<6> [835.347856] mock: [drm] GT0: Incompatible option enable_guc=3 - GuC submission is N/A
<7> [835.349165] mock: [drm:engine_rename [i915]] renamed mock to rcs0
<6> [835.349339] i915: Running intel_memory_region_mock_selftests/igt_mock_reserve
<6> [835.371842] i915: Running intel_memory_region_mock_selftests/igt_mock_fill
<6> [835.418163] i915: Running intel_memory_region_mock_selftests/igt_mock_contiguous
<6> [837.888980] i915: Running intel_memory_region_mock_selftests/igt_mock_splintered_region
<3> [837.913612] igt_mock_splintered_region too large contiguous allocation was not rejected
<3> [837.920116] i915/intel_memory_region_mock_selftests: igt_mock_splintered_region failed with error -22
<7> [837.920298] intel_gt_set_wedged called from intel_gt_set_wedged_on_fini+0xd/0x30 [i915]
<6> [838.047632] [IGT] i915_selftest: finished subtest memory_region, SUCCESS
<6> [838.048150] [IGT] i915_selftest: finished subtest mock, SUCCESS
<6> [838.051521] [IGT] i915_selftest: exiting, ret=0https://gitlab.freedesktop.org/drm/intel/-/issues/9196igt@kms_universal_plane@cursor-fb-leak-pipe-d - fail - Test assertion failur...2024-02-23T05:36:46ZGundla karthikigt@kms_universal_plane@cursor-fb-leak-pipe-d - fail - Test assertion failure function cursor_leak_test_pipe, Failed assertion: count1 == count2, Last errno: 9https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13550/shard-tglu-3/igt@kms_universal_plane@cursor-fb-leak-pipe-d.html
```````
Starting subtest: cursor-fb-leak-pipe-D
(kms_universal_plane:913) CRITICAL: Test assertion failure function cur...https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13550/shard-tglu-3/igt@kms_universal_plane@cursor-fb-leak-pipe-d.html
```````
Starting subtest: cursor-fb-leak-pipe-D
(kms_universal_plane:913) CRITICAL: Test assertion failure function cursor_leak_test_pipe, file ../../../usr/src/igt-gpu-tools/tests/kms_universal_plane.c:754:
(kms_universal_plane:913) CRITICAL: Failed assertion: count1 == count2
(kms_universal_plane:913) CRITICAL: Last errno: 9, Bad file descriptor
(kms_universal_plane:913) CRITICAL: error: 1 != 2
Subtest cursor-fb-leak-pipe-D failed.
````````````https://gitlab.freedesktop.org/drm/intel/-/issues/8862Few tests - Dmesg-warn/incomplete/abort - This test caused an abort condition...2023-07-26T09:31:14ZGundla karthikFew tests - Dmesg-warn/incomplete/abort - This test caused an abort condition: Lockdep not activehttps://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1381/fi-pnv-d510/igt@kms_vblank@pipe-a-ts-continuation-dpms-suspend.html#dmesg-warnings327
`````````
Opened device: /dev/dri/card0
Starting subtest: pipe-A-ts-continuation-dpms-suspend
Begi...https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1381/fi-pnv-d510/igt@kms_vblank@pipe-a-ts-continuation-dpms-suspend.html#dmesg-warnings327
`````````
Opened device: /dev/dri/card0
Starting subtest: pipe-A-ts-continuation-dpms-suspend
Beginning pipe-A-ts-continuation-dpms-suspend on pipe A, connector VGA-1
[cmd] rtcwake: wakeup from "mem" using /dev/rtc0 at Wed Jul 12 04:51:13 2023
pipe-A-ts-continuation-dpms-suspend on pipe A, connector VGA-1: PASSED
Subtest pipe-A-ts-continuation-dpms-suspend: SUCCESS (1.901s)
Test requirement not met in function igt_require_pipe, file ../../../usr/src/igt-gpu-tools/lib/igt_kms.c:2428:
Test requirement: !(pipe >= display->n_pipes || !display->pipes[pipe].enabled)
Pipe C does not exist or not enabled
Test requirement not met in function igt_require_pipe, file ../../../usr/src/igt-gpu-tools/lib/igt_kms.c:2428:
Test requirement: !(pipe >= display->n_pipes || !display->pipes[pipe].enabled)
Pipe D does not exist or not enabled
Test requirement not met in function igt_require_pipe, file ../../../usr/src/igt-gpu-tools/lib/igt_kms.c:2428:
Test requirement: !(pipe >= display->n_pipes || !display->pipes[pipe].enabled)
Pipe E does not exist or not enabled
Test requirement not met in function igt_require_pipe, file ../../../usr/src/igt-gpu-tools/lib/igt_kms.c:2428:
Test requirement: !(pipe >= display->n_pipes || !display->pipes[pipe].enabled)
Pipe F does not exist or not enabled
Test requirement not met in function igt_require_pipe, file ../../../usr/src/igt-gpu-tools/lib/igt_kms.c:2428:
Test requirement: !(pipe >= display->n_pipes || !display->pipes[pipe].enabled)
Pipe G does not exist or not enabled
Test requirement not met in function igt_require_pipe, file ../../../usr/src/igt-gpu-tools/lib/igt_kms.c:2428:
Test requirement: !(pipe >= display->n_pipes || !display->pipes[pipe].enabled)
Pipe H does not exist or not enabled
This test caused an abort condition: Lockdep not active
```````https://gitlab.freedesktop.org/drm/intel/-/issues/6325full screen (backlight?) flicker on i7-4500U Haswell2023-01-22T11:11:23ZDominik Mierzejewskifull screen (backlight?) flicker on i7-4500U Haswell* Platform: **Intel Haswell (i7-4500U)**
* Reproducibility: **100%**
* Description: *Full screen (backlight?) flicker of the built-in display. First occurrences around 60% battery level, very occasional. Possibly correlated with storage ...* Platform: **Intel Haswell (i7-4500U)**
* Reproducibility: **100%**
* Description: *Full screen (backlight?) flicker of the built-in display. First occurrences around 60% battery level, very occasional. Possibly correlated with storage activity(?). If no suspend/resume cycle, effect starts occurring frequently below 25% battery level. Never happens when on A/C power.*
* System architecture: `x86_64`
* Kernel version: `5.18.7-200.fc36.x86_64`
* Linux distribution: **Fedora 36**
* Machine: **Sony Vaio Pro 13 (SVP1322C5E)**
* Display connector: **eDP**
* A full dmesg with debug information:
[kernel-5.18.7-i915-flicker-dmesg.txt](/uploads/c3373ff632f2d377f43effeea9cc6155/kernel-5.18.7-i915-flicker-dmesg.txt)https://gitlab.freedesktop.org/drm/intel/-/issues/5248Can't set screen scaling modes for external monitors2023-01-31T16:10:02ZNM64Can't set screen scaling modes for external monitorsRe-creation of closed issue #23 because I did not create the original issue and therefore cannot reopen it. This is key because, when issue #23 was closed, it was also stated that it should be reopened if the problem still exists.
Well...Re-creation of closed issue #23 because I did not create the original issue and therefore cannot reopen it. This is key because, when issue #23 was closed, it was also stated that it should be reopened if the problem still exists.
Well, it's been over 2 years since issue #23 was closed and it _definitely_ still exists (tested with Xubuntu 22.04 daily built 2022-03-04):
![Screenshot_2022-03-04_18-23-24](/uploads/1509a21d70823eb1be0e08f5ea8a81d1/Screenshot_2022-03-04_18-23-24.png)https://gitlab.freedesktop.org/drm/intel/-/issues/4839igt@kms_flip@flip-vs-suspend@.* - incomplete - PM: suspend entry (deep)2023-11-14T16:53:36ZSAI NANDANigt@kms_flip@flip-vs-suspend@.* - incomplete - PM: suspend entry (deep)https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11010/shard-skl6/igt@kms_flip@flip-vs-suspend@c-edp1.html
````
<7> [527.714171] [drm:drm_do_probe_ddc_edid] drm: skipping non-existent adapter i915 gmbus dpb
<7> [527.714243] i915 0000:00:0...https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11010/shard-skl6/igt@kms_flip@flip-vs-suspend@c-edp1.html
````
<7> [527.714171] [drm:drm_do_probe_ddc_edid] drm: skipping non-existent adapter i915 gmbus dpb
<7> [527.714243] i915 0000:00:02.0: [drm:intel_hdmi_set_edid [i915]] HDMI GMBUS EDID read failed, retry using GPIO bit-banging
<7> [527.715778] i915 0000:00:02.0: [drm:intel_gmbus_force_bit [i915]] enabling bit-banging on i915 gmbus dpb. force bit now 1
<7> [527.750406] [drm:drm_do_probe_ddc_edid] drm: skipping non-existent adapter i915 gmbus dpb
<7> [527.750483] i915 0000:00:02.0: [drm:intel_gmbus_force_bit [i915]] disabling bit-banging on i915 gmbus dpb. force bit now 0
<7> [527.808230] i915 0000:00:02.0: [drm:do_gmbus_xfer [i915]] GMBUS [i915 gmbus dpb] timed out, falling back to bit banging on pin 5
<7> [527.826208] i915 0000:00:02.0: [drm:drm_dp_dual_mode_detect [drm_kms_helper]] DP dual mode HDMI ID: (err -6)
<7> [527.826524] i915 0000:00:02.0: [drm:check_connector_changed [drm_kms_helper]] [CONNECTOR:112:HDMI-A-1] Same epoch counter 1
<7> [527.826741] i915 0000:00:02.0: [drm:intel_dp_detect [i915]] [CONNECTOR:118:DP-2]
<7> [527.829861] i915 0000:00:02.0: [drm:check_connector_changed [drm_kms_helper]] [CONNECTOR:118:DP-2] Same epoch counter 1
<7> [527.830032] i915 0000:00:02.0: [drm:asle_work [i915]] updating opregion backlight 255/255
<7> [527.831506] i915 0000:00:02.0: [drm:intel_panel_actually_set_backlight [i915]] set backlight level = 187
<7> [527.834442] i915 0000:00:02.0: [drm:intel_hdmi_detect [i915]] [CONNECTOR:124:HDMI-A-2]
<7> [527.888134] i915 0000:00:02.0: [drm:do_gmbus_xfer [i915]] GMBUS [i915 gmbus dpc] timed out, falling back to bit banging on pin 4
<7> [527.905167] [drm:drm_do_probe_ddc_edid] drm: skipping non-existent adapter i915 gmbus dpc
<7> [527.908077] i915 0000:00:02.0: [drm:intel_hdmi_set_edid [i915]] HDMI GMBUS EDID read failed, retry using GPIO bit-banging
<7> [527.911418] i915 0000:00:02.0: [drm:intel_gmbus_force_bit [i915]] enabling bit-banging on i915 gmbus dpc. force bit now 1
<7> [527.929477] [drm:drm_do_probe_ddc_edid] drm: skipping non-existent adapter i915 gmbus dpc
<7> [527.929551] i915 0000:00:02.0: [drm:intel_gmbus_force_bit [i915]] disabling bit-banging on i915 gmbus dpc. force bit now 0
<7> [527.984194] i915 0000:00:02.0: [drm:do_gmbus_xfer [i915]] GMBUS [i915 gmbus dpc] timed out, falling back to bit banging on pin 4
<7> [527.999092] i915 0000:00:02.0: [drm:drm_dp_dual_mode_detect [drm_kms_helper]] DP dual mode HDMI ID: (err -6)
<7> [527.999354] i915 0000:00:02.0: [drm:check_connector_changed [drm_kms_helper]] [CONNECTOR:124:HDMI-A-2] Same epoch counter 1
<6> [528.433687] PM: suspend entry (deep)
<6> [528.450609] Filesystems sync: 0.016 secondshttps://gitlab.freedesktop.org/drm/intel/-/issues/4817igt@i915_suspend@basic-s2idle-without-i915|igt@i915_suspend@basic-s3-without-...2024-01-09T11:25:00ZLAKSHMINARAYANA VUDUMigt@i915_suspend@basic-s2idle-without-i915|igt@i915_suspend@basic-s3-without-i915 - incomplete - PM: suspend entry (s2idle|deep)https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21849/shard-skl10/igt@i915_suspend@sysfs-reader.html
```
<6> [186.481914] Console: switching to colour dummy device 80x25
<6> [186.482708] [IGT] i915_suspend: executing
<6> [186.562211] ...https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21849/shard-skl10/igt@i915_suspend@sysfs-reader.html
```
<6> [186.481914] Console: switching to colour dummy device 80x25
<6> [186.482708] [IGT] i915_suspend: executing
<6> [186.562211] [IGT] i915_suspend: starting subtest sysfs-reader
<7> [187.048168] i915 0000:00:02.0: [drm:intel_backlight_device_get_brightness [i915]] get backlight PWM = 187
<7> [187.148242] i915 0000:00:02.0: [drm:intel_backlight_device_get_brightness [i915]] get backlight PWM = 187
<7> [187.595700] i915 0000:00:02.0: [drm:intel_backlight_device_get_brightness [i915]] get backlight PWM = 187
<7> [187.683227] i915 0000:00:02.0: [drm:intel_backlight_device_get_brightness [i915]] get backlight PWM = 187
<6> [188.171866] PM: suspend entry (deep)
<7> [188.191744] i915 0000:00:02.0: [drm:intel_backlight_device_get_brightness [i915]] get backlight PWM = 187
<6> [188.200114] Filesystems sync: 0.028 seconds
```https://gitlab.freedesktop.org/drm/intel/-/issues/4435igt@fbdev@pan - fail - Failed assertion: ret == expected_ret, No space left o...2024-03-19T05:41:46ZLAKSHMINARAYANA VUDUMigt@fbdev@pan - fail - Failed assertion: ret == expected_ret, No space left on device, ioctl(FBIOPAN_DISPLAY) returned ret=-1, expected 0https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_939/fi-tgl-1115g4/igt@fbdev@pan.html
```
Starting subtest: pan
(fbdev:7376) CRITICAL: Test assertion failure function pan_test, file ../tests/fbdev.c:65:
(fbdev:7376) CRITICAL: Failed asser...https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_939/fi-tgl-1115g4/igt@fbdev@pan.html
```
Starting subtest: pan
(fbdev:7376) CRITICAL: Test assertion failure function pan_test, file ../tests/fbdev.c:65:
(fbdev:7376) CRITICAL: Failed assertion: ret == expected_ret
(fbdev:7376) CRITICAL: Last errno: 28, No space left on device
(fbdev:7376) CRITICAL: ioctl(FBIOPAN_DISPLAY) returned ret=-1, expected 0
Subtest pan failed.
```https://gitlab.freedesktop.org/drm/intel/-/issues/4105[KASAN] DRM-Tip 5.14.0 use-after-free in xcs_sanitize2022-04-08T20:15:11ZTomi Sarvela[KASAN] DRM-Tip 5.14.0 use-after-free in xcs_sanitizeKASAN run of recent DRM-Tip exposed use_after_free in xcs_sanitize on following hosts:
- https://intel-gfx-ci.01.org/tree/drm-tip/kasan_280/fi-bwr-2160/igt@i915_module_load@reload-with-fault-injection.html
- https://intel-gfx-ci.01.org/t...KASAN run of recent DRM-Tip exposed use_after_free in xcs_sanitize on following hosts:
- https://intel-gfx-ci.01.org/tree/drm-tip/kasan_280/fi-bwr-2160/igt@i915_module_load@reload-with-fault-injection.html
- https://intel-gfx-ci.01.org/tree/drm-tip/kasan_280/fi-byt-clapper/igt@i915_module_load@reload-with-fault-injection.html
- https://intel-gfx-ci.01.org/tree/drm-tip/kasan_280/fi-byt-squawks/igt@i915_module_load@reload-with-fault-injection.html
- https://intel-gfx-ci.01.org/tree/drm-tip/kasan_280/fi-elk-e7500/igt@i915_module_load@reload-with-fault-injection.html
- https://intel-gfx-ci.01.org/tree/drm-tip/kasan_280/fi-hsw-4770/igt@i915_module_load@reload-with-fault-injection.html
- https://intel-gfx-ci.01.org/tree/drm-tip/kasan_280/fi-ilk-650/igt@i915_module_load@reload-with-fault-injection.html
- https://intel-gfx-ci.01.org/tree/drm-tip/kasan_280/fi-ivb-3770/igt@i915_module_load@reload-with-fault-injection.html
- https://intel-gfx-ci.01.org/tree/drm-tip/kasan_280/fi-snb-2520m/igt@i915_module_load@reload-with-fault-injection.html
- https://intel-gfx-ci.01.org/tree/drm-tip/kasan_280/fi-snb-2600/igt@i915_module_load@reload-with-fault-injection.html
Short log:
```
<7> [314.706962] i915 0000:00:02.0: [drm:intel_atomic_commit_tail [i915]] [CRTC:39:pipe A]
<7> [314.929772] i915 0000:00:02.0: [drm:drm_client_release] drm_fb_helper
<3> [315.057714] ==================================================================
<3> [315.058007] BUG: KASAN: use-after-free in xcs_sanitize+0x4a/0x110 [i915]
<3> [315.058612] Write of size 4096 at addr ffff888022db6000 by task i915_module_loa/1046
<3> [315.058770]
<3> [315.058813] CPU: 1 PID: 1046 Comm: i915_module_loa Tainted: G U 5.14.0-g8c3cd60dcfa8-kasan_280+ #1
<3> [315.059011] Hardware name: Dell Inc. OptiPlex 745 /0GW726, BIOS 2.3.1 05/21/2007
<3> [315.059208] Call Trace:
<3> [315.059271] dump_stack_lvl+0x56/0x7b
<3> [315.059364] print_address_description.constprop.10+0x41/0x60
<3> [315.059490] ? xcs_sanitize+0x4a/0x110 [i915]
<3> [315.060079] ? xcs_sanitize+0x4a/0x110 [i915]
<3> [315.060609] kasan_report.cold.15+0x83/0xdf
<3> [315.060720] ? xcs_sanitize+0x4a/0x110 [i915]
<3> [315.061251] kasan_check_range+0x1c1/0x1e0
<3> [315.061354] memset+0x1f/0x40
<3> [315.061433] xcs_sanitize+0x4a/0x110 [i915]
<3> [315.061981] gt_sanitize+0x2b2/0x680 [i915]
<3> [315.062498] ? __pm_runtime_suspend+0x183/0x2e0
<3> [315.062619] intel_gt_suspend_late+0x126/0x2c0 [i915]
<3> [315.063158] i915_gem_suspend_late+0x9d/0x450 [i915]
<3> [315.063698] ? intel_wakeref_auto+0x3ba/0x520 [i915]
<3> [315.064193] ? i915_gem_suspend+0x180/0x180 [i915]
<3> [315.064746] ? preempt_schedule_common+0x37/0xc0
<3> [315.064873] i915_gem_driver_remove+0x25/0x1f0 [i915]
<3> [315.065449] i915_driver_remove+0xb2/0xe0 [i915]
<3> [315.065954] i915_pci_remove+0x34/0x70 [i915]
<3> [315.066444] pci_device_remove+0xa3/0x1f0
<3> [315.066553] device_release_driver_internal+0x1e0/0x4a0
<3> [315.066680] driver_detach+0xbc/0x180
<3> [315.066779] bus_remove_driver+0x15b/0x2d0
<3> [315.066882] pci_unregister_driver+0x28/0x220
<3> [315.066998] i915_exit+0xb7/0x30b [i915]
<3> [315.067568] __x64_sys_delete_module+0x257/0x370
<3> [315.067682] ? __ia32_sys_delete_module+0x370/0x370
<3> [315.067809] ? lockdep_hardirqs_on+0xbf/0x130
<3> [315.067914] do_syscall_64+0x3a/0xb0
<3> [315.068002] entry_SYSCALL_64_after_hwframe+0x44/0xae
<3> [315.068112] RIP: 0033:0x7efe27e42bcb
<3> [315.068196] Code: 73 01 c3 48 8b 0d c5 82 0c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa b8 b0 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 95 82 0c 00 f7 d8 64 89 01 48
<3> [315.068536] RSP: 002b:00007ffd331acf98 EFLAGS: 00000206 ORIG_RAX: 00000000000000b0
<3> [315.068694] RAX: ffffffffffffffda RBX: 000056288f3ee6f0 RCX: 00007efe27e42bcb
<3> [315.068833] RDX: 0000000000000000 RSI: 0000000000000800 RDI: 000056288f3ee758
<3> [315.068970] RBP: 00007efe27fd7022 R08: 0000000000000000 R09: 00007efe27f0c1a0
<3> [315.069107] R10: 000056288f3b9010 R11: 0000000000000206 R12: 0000000000000000
<3> [315.069244] R13: 00007ffd331ad690 R14: 0000000000000000 R15: 0000000000000000
<3> [315.069425]
<3> [315.069467] The buggy address belongs to the page:
<4> [315.069565] page:ffffea00008b6d80 refcount:0 mapcount:0 mapping:0000000000000000 index:0x2 pfn:0x22db6
<4> [315.069578] flags: 0x4000000000000000(zone=1)
<4> [315.069594] raw: 4000000000000000 ffffea00008b6dc8 ffffea00008c1bc8 0000000000000000
<4> [315.069606] raw: 0000000000000002 0000000000000000 00000000ffffffff 0000000000000000
<4> [315.069614] page dumped because: kasan: bad access detected
<3> [315.069622]
<3> [315.069664] Memory state around the buggy address:
<3> [315.069763] ffff888022db5f00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
<3> [315.069907] ffff888022db5f80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
<3> [315.070050] >ffff888022db6000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
<3> [315.070192] ^
<3> [315.070266] ffff888022db6080: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
<3> [315.070411] ffff888022db6100: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
<3> [315.070553] ==================================================================
<4> [315.070694] Disabling lock debugging due to kernel taint
```https://gitlab.freedesktop.org/drm/intel/-/issues/4045[KASAN] DRM-Tip 5.14 stack-out-of-bounds in tick_sched_handle.isra.192021-09-10T11:40:50ZTomi Sarvela[KASAN] DRM-Tip 5.14 stack-out-of-bounds in tick_sched_handle.isra.19Recent DRM-Tip 5.14-rc7 KASAN run on CI had hit on BSW and RKL platforms.
Short log on RKL:
```
<3> [319.731364] ==================================================================
<3> [319.731434] BUG: KASAN: stack-out-of-bounds in tick...Recent DRM-Tip 5.14-rc7 KASAN run on CI had hit on BSW and RKL platforms.
Short log on RKL:
```
<3> [319.731364] ==================================================================
<3> [319.731434] BUG: KASAN: stack-out-of-bounds in tick_sched_handle.isra.19+0x10b/0x120
<3> [319.731466] Read of size 8 at addr ffffffff83c07ea0 by task swapper/0/0
<3> [319.731491]
<3> [319.731500] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G U 5.14.0-rc7-g329f62b04cd6-kasan_277+ #1
<3> [319.731536] Hardware name: ASUS System Product Name/TUF GAMING Z590-PLUS WIFI, BIOS 0811 04/06/2021
<3> [319.731568] Call Trace:
<3> [319.731579] <IRQ>
<3> [319.731590] dump_stack_lvl+0x56/0x7b
<3> [319.731609] print_address_description.constprop.10.cold.14+0xe/0x2e2
<3> [319.731637] ? tick_sched_handle.isra.19+0x10b/0x120
<3> [319.731659] ? tick_sched_handle.isra.19+0x10b/0x120
<3> [319.731681] ? tick_sched_do_timer+0xf0/0xf0
<3> [319.731700] kasan_report.cold.15+0x83/0xdf
<3> [319.731721] ? tick_sched_handle.isra.19+0x10b/0x120
<3> [319.731745] tick_sched_handle.isra.19+0x10b/0x120
<3> [319.731767] tick_sched_timer+0xac/0xd0
<3> [319.731785] __hrtimer_run_queues+0x48d/0xa20
<3> [319.731811] ? enqueue_hrtimer+0x2a0/0x2a0
<3> [319.731830] ? ktime_get_update_offsets_now+0xdb/0x2c0
<3> [319.731857] hrtimer_interrupt+0x2ec/0x790
<3> [319.731884] __sysvec_apic_timer_interrupt+0x141/0x4e0
<3> [319.731908] sysvec_apic_timer_interrupt+0x85/0xb0
<3> [319.731930] </IRQ>
<3> [319.731941] asm_sysvec_apic_timer_interrupt+0x12/0x20
<3> [319.731964] RIP: 0010:cpu_startup_entry+0x14/0x20
<3> [319.731985] Code: 0a 48 81 ff d0 13 ff 82 0f 92 c0 c3 66 2e 0f 1f 84 00 00 00 00 00 53 89 fb e8 08 f6 ff ff 89 df e8 b1 2f f5 ff e8 4c f6 ff ff <eb> f9 cc cc cc cc cc cc cc cc cc cc 48 b8 00 00 00 00 00 fc ff df
<3> [319.732056] RSP: 0018:ffffffff83c07ec8 EFLAGS: 00000296
<3> [319.732080] RAX: 0000000000000000 RBX: 0000000000000093 RCX: ffffffff82fdde5a
<3> [319.732108] RDX: 0000000000000000 RSI: 0000000000000008 RDI: ffffffff83c21500
<3> [319.732136] RBP: 1ffffffff0780fdb R08: fffffbfff07842a1 R09: fffffbfff07842a1
<3> [319.732165] R10: ffffffff83c21507 R11: fffffbfff07842a0 R12: 00000000003bb140
<3> [319.732193] R13: ffffffff83c21500 R14: 1ffffffff0780fd1 R15: 000000007505c460
<3> [319.732226] ? schedule_idle+0x5a/0x90
<3> [319.732247] ? cpu_startup_entry+0x14/0x20
<3> [319.732265] start_secondary+0x22e/0x2c0
<3> [319.732284] ? set_cpu_sibling_map+0x1340/0x1340
<3> [319.732312] ? cpu_startup_entry+0x14/0x20
<3> [319.732339] ? start_kernel+0x376/0x394
<3> [319.732361] secondary_startup_64_no_verify+0xb0/0xbb
<3> [319.732393]
<3> [319.732401] KASAN internal error: frame info validation failed; invalid marker: 16
<3> [319.732432]
<3> [319.732440] Memory state around the buggy address:
<3> [319.732461] ffffffff83c07d80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
<3> [319.732491] ffffffff83c07e00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
<3> [319.732521] >ffffffff83c07e80: 00 00 00 00 f1 01 f2 f2 f2 00 00 f1 f1 f1 f1 04
<3> [319.732551] ^
<3> [319.732569] ffffffff83c07f00: f2 f2 f2 00 00 00 00 00 00 00 00 00 00 00 00 00
<3> [319.732599] ffffffff83c07f80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
<3> [319.732629] ==================================================================
```
Full logs on two platforms:
https://intel-gfx-ci.01.org/tree/drm-tip/kasan_277/fi-bsw-cyan/igt@kms_cursor_crc@pipe-a-cursor-256x256-offscreen.html
https://intel-gfx-ci.01.org/tree/drm-tip/kasan_277/fi-rkl-guc/igt@kms_addfb_basic@unused-modifier.htmlhttps://gitlab.freedesktop.org/drm/intel/-/issues/4042[i915] GPU HANG: ecode 7:1:86ffffd, in obs2023-11-14T16:57:06ZSkybbles[i915] GPU HANG: ecode 7:1:86ffffd, in obs## Summary:
For several months now, I have been experiencing problems with my i915 graphics
device regarding hangs and chip resets in xorg, KDEnlive, plasmashell, OBS,
etc. This issue addresses a hang in OBS that happened recently in th...## Summary:
For several months now, I have been experiencing problems with my i915 graphics
device regarding hangs and chip resets in xorg, KDEnlive, plasmashell, OBS,
etc. This issue addresses a hang in OBS that happened recently in the middle of
a critical video recording session. Again, I have been experiencing these for
months now but have only been able to sufficiently document it now, and have
time to make an issue about it.
## How to reproduce:
Open OBS Studio, record from a V4L2 capture device, wait an unspecified amount
of time. Bog-standard settings; 720p, 30fps, 3.5kb/s, ultrafast, output to mp4
with H264.
## Frequency:
Very spread out and unpredictable, but usually happens after one hour of
recording. From previous testing, it happened after 82 minutes of recording.
## Which forms and features are affected?
I have only observed this happening with kernels later than 4.19 (the latest
provided by Debian Buster). I have another machine identical to this (I will
call Machine B) with the exact same hardware except for different SSD capacity
and different RAM brand and frequency.
What is even more frustrating and weird is, Machine B does not exhibit the same
problems despite having the same version of Debian, the same kernel, and same
BIOS settings. This happens even after swapping the RAM sticks. I guess I
should be thankful, though.
I will perform further testing on both machines when I have the time, since I
would like to be very sure whether this is a kernel problem or an OEM/product
defect problem.
## System information/specs:
- Architecture: x86_64
- Kernel Version: 5.10.0-8-amd64
- Linux Distribution: Debian GNU/Linux 11 (bullseye)
- Machine Model: Dell Inspiron 20 3048
- Motherboard Model: Dell 0HD5K4 A00 (full `dmidecode` is attached)
- Processor: Intel Pentium G3240T
- Memory: 2x 2GB 1333 MT/s Hynix
- GPU: Intel HD Graphics (lspci says: Intel Corporation Xeon E3-1200 v3/4th Gen
Core Processor Integrated Graphics Controller (rev 06))
- Display Connector: eDP (built-in display)
- dmesg output: (attached)
- card0/error: (attached)
- Photo: (photo of plasmashell, taken with my phone since
screenshotting is impossible on a glitched plasmashell, blurred to hide some personal things)
![IMG_20210828_212448](/uploads/7e17c6eebc22c5eed84458158003f2cb/IMG_20210828_212448.jpg)
## Notes and remarks:
I personally think this is a regression. After a lot of testing, and like I
mentioned earlier, this only occurs on kernels later than 4.19. A few months
ago, I actually compiled 5.x kernels with custom settings such as turning
mitigations off, and manually applying the DRM patch detailed in
https://patchwork.kernel.org/project/intel-gfx/patch/20210111225220.3483-1-chris@chris-wilson.co.uk/
to no avail. This problem also occurred on Liquorix kernels, although I will
have to test their latest kernels again.
I have also manually installed the nonfree firmware files in past tests (like
tgl_guc, etc) but that has not changed anything. I will try that again for this
newer kernel.
Another very frequent ecode is 0x85dffffc, which has been highlighted in
another issue. I don't have enough time or data to write another issue about
that at the moment, though.
This problem has been haunting me since February of this year, and has been
hindering my brother's first experiences with Linux. Below are issues like this
or that I have read in my attempts to solve this problem:
- https://bugzilla.redhat.com/show_bug.cgi?id=1937436
- https://gitlab.freedesktop.org/drm/intel/-/issues/2024
- https://gitlab.freedesktop.org/drm/intel/-/issues/3123
- I commented on this with details on the ecode 0x85dffffc.
- https://olegon.ru/showthread.php?t=35847
- A Russian friend helped me understand this comment, but the solution did
not work.
- https://gitlab.freedesktop.org/drm/intel/-/issues/2024
And finally, thank you, kernel devs, for your time and great efforts in fixing
bugs and improving the Linux kernel and its DRM component.[dmidecode.txt](/uploads/1dfd7361f19303d64283e66d41a05440/dmidecode.txt)[dmesg.txt](/uploads/eb1f46261cb6e18ae256537d6b2ed0a9/dmesg.txt)[card0-error.txt](/uploads/8d7631138fa7b851e13167bb86dc84ea/card0-error.txt)https://gitlab.freedesktop.org/drm/intel/-/issues/3591igt@i915_pm_rc6_residency@rc6-idle - fail - Failed assertion: 2 * phases[2].p...2023-11-21T09:03:30ZTejasree Illipilliigt@i915_pm_rc6_residency@rc6-idle - fail - Failed assertion: 2 * phases[2].power - phases[0].power <= phases[1].powerhttps://intel-gfx-ci.01.org/tree/drm-tip/drmtip_828/fi-bdw-5557u/igt@i915_pm_rc6_residency@rc6-idle.html
`````````````````````````````````````````````````````````
- Err
- Starting subtest: rc6-idle
- (i915_pm_rc6_residency:1418) CRITICA...https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_828/fi-bdw-5557u/igt@i915_pm_rc6_residency@rc6-idle.html
`````````````````````````````````````````````````````````
- Err
- Starting subtest: rc6-idle
- (i915_pm_rc6_residency:1418) CRITICAL: Test assertion failure function rc6_idle, file ../tests/i915/i915_pm_rc6_residency.c:448:
- (i915_pm_rc6_residency:1418) CRITICAL: Failed assertion: 2 * phases[2].power - phases[0].power <= phases[1].power
- (i915_pm_rc6_residency:1418) CRITICAL: Exceeded energy expectations for single busy wait load
- Used 118.5mW, min 101.4mW, max 126.4mW, expected less than 113.9mW
- Subtest rc6-idle failed.https://gitlab.freedesktop.org/drm/intel/-/issues/3441[bisected, patch attached] [drm] [i915] Flickering on build-in display since ...2024-03-07T18:59:32ZYevhen Popok[bisected, patch attached] [drm] [i915] Flickering on build-in display since kernel v4.1 (HP Elitebook Folio 1040 G1)Basically this is a duplicate of issue #306 with new information. Unfortunately I can't reopen that issue so creating a new one. Sorry about that. Please leave this issue or reopen the old one. Thanks!
----
The problem occurs with noteb...Basically this is a duplicate of issue #306 with new information. Unfortunately I can't reopen that issue so creating a new one. Sorry about that. Please leave this issue or reopen the old one. Thanks!
----
The problem occurs with notebook HP Elitebook Folio 1040 G1 which comes with processor Intel i5-4210U.
I have a few types of periodic flickering:
1. If I leave mouse cursor for a few seconds, then start moving it, there's slight flicker (like display brightness changes a bit)
2. On the top left corner sometimes appears artifacts. It's relatively easy to see with black window decorations on top of the screen. This one is showed at the attached video bellow
![VID_20190526_162622](/uploads/c17c1df58d450ef0b82299526f3a1c71/VID_20190526_162622.mp4).
Where it's not reproducible:
1) Windows and BIOS
2) With boot option `nomodeset`
Boot option like `i915.enable_psr=0`, `i915.enable_rc6=0`, `intel_idle.max_cstate=4` didn't help.
Resolution or refresh rate changes don't make any difference
3) With kernel 4.0.9. Version 4.1-rc3 has this problem. Tested on Ubuntu 16.04
I already tried new kernels (including [latest drm-tip version from Ubuntu](https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/current/amd64/) (2021-05-04 02:47). The problem persists.https://gitlab.freedesktop.org/drm/intel/-/issues/3103i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:85dffdfc, in kwin_x11 [1452]2022-05-02T13:02:45Zki915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:85dffdfc, in kwin_x11 [1452][dmesg-new.txt](/uploads/a01a213223bdb514d4310bd7b9e557c4/dmesg-new.txt)[error-i915](/uploads/7fcf850d4f52d96e4bf376bba413db02/error-i915)
Intermittent GPU HANG on Haswell Intel Pentium G3250 (2) @ 3.200GHz.
This issue manifested regular...[dmesg-new.txt](/uploads/a01a213223bdb514d4310bd7b9e557c4/dmesg-new.txt)[error-i915](/uploads/7fcf850d4f52d96e4bf376bba413db02/error-i915)
Intermittent GPU HANG on Haswell Intel Pentium G3250 (2) @ 3.200GHz.
This issue manifested regularly on Debian Stretch as well as Buster.
Cursor can be moved but not clickable. Afterward the HANG duration of 10 or 30 seconds, it came to normal again.
https://gitlab.freedesktop.org/drm/intel/-/issues/2024 This issue 2024 also affects me surely. In one instance of the HANG after #2024 is closed temporarily, I had switch to vt and reboot because xorg is completely unresponsive to any input.
In other instances of it, it came to normal again after a while.https://gitlab.freedesktop.org/drm/intel/-/issues/2858i915 GPU hang in OpenSUSE Tumbleweed after new install2022-03-22T08:11:03Zmuralitoi915 GPU hang in OpenSUSE Tumbleweed after new install-- system architecture: x86_64
-- kernel version: 5.10.1-1-default
-- openSUSE Tumbleweed version 20201226
-- Machine or mother board model: Asus Vivo PC VM42 / BIOS Version 1203 / CPU Intel(R) Celeron(R) 2957U @ 1.40GHz
-- Display conne...-- system architecture: x86_64
-- kernel version: 5.10.1-1-default
-- openSUSE Tumbleweed version 20201226
-- Machine or mother board model: Asus Vivo PC VM42 / BIOS Version 1203 / CPU Intel(R) Celeron(R) 2957U @ 1.40GHz
-- Display connector: HDMIhttps://gitlab.freedesktop.org/drm/intel/-/issues/2724igt@gem_uperptr_blits@(vma-merge|huge-split) - fail - Failed assertion: sync_...2022-10-13T05:26:18ZJaswanth kattamanchiigt@gem_uperptr_blits@(vma-merge|huge-split) - fail - Failed assertion: sync_fence_status(spin->out_fence) == 1 \n error: -5 != 1- https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_715/fi-bdw-5557u/igt@gem_userptr_blits@vma-merge.html
- ---------------------
- Starting subtest: vma-merge
- (gem_userptr_blits:1064) CRITICAL: Test assertion failure function test_vma...- https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_715/fi-bdw-5557u/igt@gem_userptr_blits@vma-merge.html
- ---------------------
- Starting subtest: vma-merge
- (gem_userptr_blits:1064) CRITICAL: Test assertion failure function test_vma_merge, file ../tests/i915/gem_userptr_blits.c:758:
- (gem_userptr_blits:1064) CRITICAL: Failed assertion: sync_fence_status(spin->out_fence) == 1
- (gem_userptr_blits:1064) CRITICAL: error: -5 != 1
- Subtest vma-merge failed.
- **** DEBUG ****
- (gem_userptr_blits:1064) DEBUG: Found huge page size: 2097152
- (gem_userptr_blits:1064) ioctl_wrappers-DEBUG: Test requirement passed: gem_has_ring(fd, ring)
- (gem_userptr_blits:1064) igt_dummyload-DEBUG: Test requirement passed: nengine
- (gem_userptr_blits:1064) CRITICAL: Test assertion failure function test_vma_merge, file ../tests/i915/gem_userptr_blits.c:758:
- (gem_userptr_blits:1064) CRITICAL: Failed assertion: sync_fence_status(spin->out_fence) == 1
- (gem_userptr_blits:1064) CRITICAL: error: -5 != 1
- (gem_userptr_blits:1064) igt_core-INFO: Stack trace:
- (gem_userptr_blits:1064) igt_core-INFO: #0 ../lib/igt_core.c:1727 __igt_fail_assert()
- (gem_userptr_blits:1064) igt_core-INFO: #1 ../tests/i915/gem_userptr_blits.c:832 __real_main2317()
- (gem_userptr_blits:1064) igt_core-INFO: #2 ../tests/i915/gem_userptr_blits.c:2317 main()
- (gem_userptr_blits:1064) igt_core-INFO: #3 ../csu/libc-start.c:344 __libc_start_main()
- (gem_userptr_blits:1064) igt_core-INFO: #4 [_start+0x2a]
- **** END ****
- Subtest vma-merge: FAIL (15.487s)
- --------------------------------------------------------https://gitlab.freedesktop.org/drm/intel/-/issues/2681igt@i915_pm_rc6_residency@rc6-(idle|fence)- warn - WARNING: Total energy used...2023-12-08T13:18:17ZLAKSHMINARAYANA VUDUMigt@i915_pm_rc6_residency@rc6-(idle|fence)- warn - WARNING: Total energy used while idle: .*mJhttps://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9307/shard-tglb2/igt@i915_pm_rc6_residency@rc6-idle.html
```
Out
IGT-Version: 1.25-g8cffaebec (x86_64) (Linux: 5.10.0-rc3-CI-CI_DRM_9307+ x86_64)
Starting subtest: rc6-idle
Total energy us...https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9307/shard-tglb2/igt@i915_pm_rc6_residency@rc6-idle.html
```
Out
IGT-Version: 1.25-g8cffaebec (x86_64) (Linux: 5.10.0-rc3-CI-CI_DRM_9307+ x86_64)
Starting subtest: rc6-idle
Total energy used for normal: 60.7mJ (20.2mW)
Total energy used for boost: 50.5mJ (16.8mW)
Total energy used for once: 61.0mJ (20.3mW)
Subtest rc6-idle: SUCCESS (12.214s)
Err
Starting subtest: rc6-idle
(i915_pm_rc6_residency:1480) WARNING: Total energy used while idle: 36.9mJ
Subtest rc6-idle: SUCCESS (12.214s)
```https://gitlab.freedesktop.org/drm/intel/-/issues/2415igt@gem_tiled_blits@interruptible - dmesg-fail/incomplete - general protectio...2022-04-08T20:15:11ZLAKSHMINARAYANA VUDUMigt@gem_tiled_blits@interruptible - dmesg-fail/incomplete - general protection fault, probably for non-canonical address.*PREEMPT SMP PTIhttps://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8943/shard-hsw2/igt@gem_tiled_blits@interruptible.html#dmesg-warnings20
```
<6> [69.847736] [IGT] gem_tiled_blits: starting subtest interruptible
<4> [71.885973] general protection fault, p...https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8943/shard-hsw2/igt@gem_tiled_blits@interruptible.html#dmesg-warnings20
```
<6> [69.847736] [IGT] gem_tiled_blits: starting subtest interruptible
<4> [71.885973] general protection fault, probably for non-canonical address 0x1ad998badadad80: 0000 [#1] PREEMPT SMP PTI
<4> [71.885988] CPU: 6 PID: 1092 Comm: gem_tiled_blits Not tainted 5.9.0-rc2-CI-CI_DRM_8943+ #1
<4> [71.885997] Hardware name: MSI MS-7924/Z97M-G43(MS-7924), BIOS V1.12 02/15/2016
<4> [71.886010] RIP: 0010:kfree+0x6e/0x6b0
<4> [71.886016] Code: 01 d8 0f 82 4a 06 00 00 49 bc 00 00 00 80 7f 77 00 00 49 01 c4 48 b8 00 00 00 00 00 ea ff ff 49 c1 ec 0c 49 c1 e4 06 49 01 c4 <49> 8b 44 24 08 48 8d 50 ff a8 01 4c 0f 45 e2 49 8b 54 24 08 48 8d
<4> [71.886033] RSP: 0018:ffffc900006eba00 EFLAGS: 00010203
<4> [71.886039] RAX: ffffea0000000000 RBX: 6b6b6b6b6b6b6b6b RCX: 0000000000000000
<4> [71.886046] RDX: 0000000000000001 RSI: ffffffff8264e240 RDI: ffff8884051ab208
<4> [71.886053] RBP: ffffc900006eba48 R08: 0000000000000004 R09: 0000000000000001
<4> [71.886060] R10: 00000000859da96f R11: 0000000051d70783 R12: 01ad998badadad80
<4> [71.886067] R13: 0000000000000005 R14: 0000000000000002 R15: ffffc900006ebb08
<4> [71.886074] FS: 00007f6edf2b9300(0000) GS:ffff888410700000(0000) knlGS:0000000000000000
<4> [71.886082] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
<4> [71.886088] CR2: 00007f6ede7e35c0 CR3: 0000000404666006 CR4: 00000000001706e0
<4> [71.886095] Call Trace:
<4> [71.886103] ? _raw_spin_unlock_irqrestore+0x47/0x60
<4> [71.886189] eb_relocate_parse_slow+0x4d4/0x6a0 [i915]
<4> [71.886276] i915_gem_do_execbuffer+0xf68/0x22c0 [i915]
<4> [71.886291] ? __lock_acquire+0x913/0x1f40
<4> [71.886343] ? i915_gem_execbuffer2_ioctl+0x9d/0x220 [i915]
<4> [71.886350] ? lock_acquire+0xb5/0x3c0
<4> [71.886355] ? __might_fault+0x39/0x90
<4> [71.886414] i915_gem_execbuffer2_ioctl+0xed/0x220 [i915]
<4> [71.886490] ? i915_gem_execbuffer_ioctl+0x300/0x300 [i915]
<4> [71.886497] drm_ioctl_kernel+0xb0/0xf0
<4> [71.886501] drm_ioctl+0x305/0x3c0
<4> [71.886546] ? i915_gem_execbuffer_ioctl+0x300/0x300 [i915]
<4> [71.886554] ? syscall_enter_from_user_mode+0x1b/0x220
<4> [71.886558] ? syscall_enter_from_user_mode+0x1b/0x220
<4> [71.886565] __x64_sys_ioctl+0x71/0xb0
<4> [71.886570] do_syscall_64+0x33/0x80
<4> [71.886575] entry_SYSCALL_64_after_hwframe+0x44/0xa9
<4> [71.886579] RIP: 0033:0x7f6ede50c5d7
<4> [71.886583] Code: b3 66 90 48 8b 05 b1 48 2d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 81 48 2d 00 f7 d8 64 89 01 48
<4> [71.886593] RSP: 002b:00007ffcf0547f18 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
<4> [71.886599] RAX: ffffffffffffffda RBX: 00000000ffffffff RCX: 00007f6ede50c5d7
<4> [71.886604] RDX: 00007ffcf0547f70 RSI: 00000000c0406469 RDI: 0000000000000006
<4> [71.886609] RBP: 00007ffcf0547f70 R08: 0000000000000000 R09: 0000000000000000
<4> [71.886613] R10: 0000000000000000 R11: 0000000000000246 R12: 00000000c0406469
<4> [71.886618] R13: 0000000000000006 R14: 0000000000000000 R15: 000055e14eb41f18
<4> [71.886625] Modules linked in: snd_hda_codec_hdmi i915 mei_hdcp x86_pkg_temp_thermal coretemp snd_hda_codec_realtek crct10dif_pclmul snd_hda_codec_generic crc32_pclmul ledtrig_audio ghash_clmulni_intel snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_hwdep snd_hda_core r8169 realtek snd_pcm mei_me lpc_ich mei prime_numbers
````