|
[RESOLVED] Video Artifacts on Latest Versions
I am noticing video artifacts and/or corruption when using the most recent liquorix kernel versions (since 4 or 5 updates ago). The desktop will work normally for a while after booting. However, eventually I see blocks appear and disappear, stray lines, windows are not drawn correctly. This problem gets worse and worse until the computer is unusable. A reboot resolves the issue temporarily. This issue is not present on older 5.10 liquorix versions. The stock Ubuntu 5.4 kernel also works normally. The same problem occurs on both Ubuntu 18.04 and 20.04 with my setup. Details about my hardware are below. Did anything change with the intel i915 driver or its configuration within the last month or so? Any other ideas?
:: Code ::
System: Host: xxx Kernel: 5.4.0-65-generic x86_64 bits: 64 Desktop: Cinnamon 4.8.6 Distro: Linux Mint 20.1 Ulyssa Machine: Type: Desktop System: ASUS product: All Series v: N/A serial: N/A Mobo: ASUSTeK model: Z97-A v: Rev 1.xx serial: xxxx UEFI [Legacy]: American Megatrends v: 2801 date: 11/11/2015 CPU: Quad Core: Intel Core i7-4790K type: MT MCP speed: 1201 MHz min/max: 800/4500 MHz Graphics: Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics driver: i915 v: kernel Display: server: X.Org 1.20.9 driver: modesetting unloaded: fbdev,vesa resolution: 2560x1440~60Hz, 2560x1440~60Hz OpenGL: renderer: Mesa DRI Intel HD Graphics 4600 (HSW GT2) v: 4.5 Mesa 20.2.6 Network: Device-1: Intel Ethernet I218-V driver: e1000e Drives: Local Storage: total: 19.33 TiB used: 5.91 TiB (30.6%) Info: Processes: 323 Uptime: 1d 22h 59m Memory: 15.33 GiB used: 5.36 GiB (34.9%) Shell: bash inxi: 3.0.38 Back to top |
|||||
|
Bugfixes for i915 have been incrementally dripping into 5.10 stable for a while now. Here's just an example of all the i915 patches so far up to 5.10.17:
:: Code :: find ./5.10.* | grep i915
./5.10.11/drm-i915-hdcp-update-cp-property-in-update_pipe.patch ./5.10.11/drm-i915-gt-prevent-use-of-engine-wa_ctx-after-error.patch ./5.10.11/drm-i915-hdcp-get-conn-while-content_type-changed.patch ./5.10.11/drm-i915-only-enable-dfp-4-4-4-4-2-0-conversion-when-outputting-ycbcr-4-4-4.patch ./5.10.11/drm-i915-s-intel_dp_sink_dpms-intel_dp_set_power.patch ./5.10.11/drm-i915-check-for-rq-hwsp-validity-after-acquiring-rcu-lock.patch ./5.10.11/asoc-sof-intel-fix-page-fault-at-probe-if-i915-init-fails.patch ./5.10.13/drm-i915-gt-clear-cache_mode-prior-to-clearing-residuals.patch ./5.10.13/drm-i915-pmu-don-t-grab-wakeref-when-enabling-events.patch ./5.10.13/drm-i915-always-flush-the-active-worker-before-returning-from-the-wait.patch ./5.10.13/drm-i915-gt-always-try-to-reserve-ggtt-address-0x0.patch ./5.10.13/drm-i915-check-for-all-subplatform-bits.patch ./5.10.13/drm-i915-selftest-fix-potential-memory-leak.patch ./5.10.15/drm-i915-gem-drop-lru-bumping-on-display-unpinning.patch ./5.10.15/drm-i915-fix-the-mst-pbn-divider-calculation.patch ./5.10.15/drm-i915-display-prevent-double-yuv-range-correction-on-hdr-planes.patch ./5.10.15/drm-i915-power-up-combo-phy-lanes-for-for-hdmi-as-well.patch ./5.10.15/drm-i915-extract-intel_ddi_power_up_lanes.patch ./5.10.15/drm-i915-gt-close-race-between-enable_breadcrumbs-and-cancel_breadcrumbs.patch ./5.10.16/drm-i915-fix-icl-mg-phy-vswing-handling.patch ./5.10.16/drm-i915-skip-vswing-programming-for-tbt.patch ./5.10.17/drm-i915-tgl-make-sure-typec-fia-is-powered-up-when-initializing-it.patch ./5.10.17/drm-i915-fix-overlay-frontbuffer-tracking.patch ./5.10.4/drm-i915-fix-mismatch-between-misplaced-vma-check-and-vma-insert.patch ./5.10.6/drm-i915-tgl-fix-combo-phy-dpll-fractional-divider-for-38.4mhz-ref-clock.patch ./5.10.7/drm-i915-clear-the-gpu-reloc-batch.patch ./5.10.7/drm-i915-clear-the-shadow-batch.patch ./5.10.8/drm-i915-dp-track-pm_qos-per-connector.patch ./5.10.9/drm-i915-allow-the-sysadmin-to-override-security-mitigations.patch ./5.10.9/drm-i915-gt-restore-clear-residual-mitigations-for-ivybridge-baytrail.patch ./5.10.9/drm-i915-gt-limit-vfe-threads-based-on-gt.patch ./5.10.9/drm-i915-icl-fix-initing-the-dsi-dsc-power-refcount-during-hw-readout.patch ./5.10.9/drm-i915-dsi-use-unconditional-msleep-for-the-panel_on_delay-when-there-is-no-reset-deassert-mipi-sequence.patch ./5.10.9/drm-i915-backlight-fix-cpu-mode-backlight-takeover-on-lpt.patch You can try adding passing i915.mitigations=off since it was recently added. Otherwise, Con released his patch set for 5.11 already, so this week I'll upgrade Liquorix to 5.11 earlier than usual. Most likely the stable patches weren't tested well and have side effects that depend on code in newer Linux. Back to top |
|||||
|
No worries. Thanks for getting back to me so quickly! I'll continue to use 5.4 until 5.11 is ready and I'll let you know how it goes.
Back to top |
|||||
|
This problem still exists with 5.11.0-0.2. I am now testing with 5.11.0-1.1.
Back to top |
|||||
|
I can confirm the problem is the same with 5.11.0-1.1. This first started happening about 4 or 5 revisions before the last 5.10 version. Does that help pinpoint it at all? The stock Ubuntu 5.4 kernel still works normally. Let me know if there's anything I can do to help. Thanks.
Back to top |
|||||
|
Did you try passing i915.mitigations=off to your kernel parameters? Your hardware appears to be affected, the 4790k is a Haswell CPU:
:: Code :: parm: mitigations:Selectively enable security mitigations for all Intel® GPUs in the system.
auto -- enables all mitigations required for the platform [default] off -- disables all mitigations Individual mitigations can be enabled by passing a comma-separated string, e.g. mitigations=residuals to enable only clearing residuals or mitigations=auto,noresiduals to disable only the clear residual mitigation. Either '!' or 'no' may be used to switch from enabling the mitigation to disabling it. Active mitigations for Ivybridge, Baytrail, Haswell: residuals -- clear all thread-local registers between contexts Back to top |
|||||
|
So far this has not happened with i915.mitigations=off . However, it makes me think that others with the same intel CPU generation could have this issue in the future once 5.10+ becomes more mainstream and they might not know how to resolve it. Perhaps Ubuntu will disable problematic mitigations in their stock kernel. Thank you very much for your help. If you have any other suggestions, please let me know.[/code]
Back to top |
|||||
|
All times are GMT - 8 Hours
|
|||||