You are not logged in.

#1 2022-06-19 20:32:09

merlick_pl17
Member
Registered: 2022-06-19
Posts: 5

Linux kernel tainted due to boot warning kwin as ex-tainter

I wonder how I could I effectively trace what is causing this kernel warning that changes the status of my kernel as "tainted" and what I can do to clear it. It seems to be tainted by KDE Plasma Window Manager at bootstart but by the time its booted and I check dmesg it shows its untained:

sudo dmesg | grep -i taint
[   20.139928] CPU: 1 PID: 784 Comm: kwin_wayland Not tainted 5.18.5-arch1-1 #1 e9787f6018c114f5ea5c49a220d7535dfd3a932e

The code from  cat /proc/sys/kernel/tainted is 512 which is triggered by kernel warning. I run Arch Linux with linux kernel on KDE Wayland on Dell XPS 9305 machine with Secure Boot enabled. I installed Arch with Intel Xe Mesa graphics drivers. Here is more what happens in dmesg around this kernel warning event:

Jun 18 23:44:19 -xps kernel: ------------[ cut here ]------------

Jun 18 23:44:19 -xps kernel: pipe state doesn't match!

Jun 18 23:44:19 -xps kernel: WARNING: CPU: 0 PID: 795 at drivers/gpu/drm/i915/display/intel_display.c:6677 intel_atomic_commit_tail+0x184c/0x18f0 [i915]

Jun 18 23:44:19 -xps kernel: Modules linked in: xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 snd_hda_codec_hdmi cmac algif_hash xt_tcpudp nft_com>

Jun 18 23:44:19 -xps kernel: apple_mfi_fastcharge x86_pkg_temp_thermal videobuf2_common libarc4 joydev intel_powerclamp bluetooth snd_soc_core dell_smbios videodev >

Jun 18 23:44:19 -xps kernel: clk_tps68470 mac_hid intel_skl_int3472_discrete int3400_thermal intel_hid acpi_thermal_rel sparse_keymap acpi_tad acpi_pad lzo_rle pkcs>

Jun 18 23:44:19 -xps kernel: CPU: 0 PID: 795 Comm: kwin_wayland Not tainted 5.18.5-arch1-1 #1 e9787f6018c114f5ea5c49a220d7535dfd3a932e

Jun 18 23:44:19 -xps kernel: Hardware name: Dell Inc. XPS 13 9305/0MM15H, BIOS 1.5.0 03/17/2022

My system configuration:

                  .o+`                   ----------- 
                 `ooo/                   OS: Arch Linux x86_64 
                `+oooo:                  Host: XPS 13 9305 
               `+oooooo:                 Kernel: 5.18.5-arch1-1 
               -+oooooo+:                Uptime: 43 secs 
             `/:-:++oooo+:               Packages: 1135 (pacman) 
            `/++++/+++++++:              Shell: bash 5.1.16 
           `/++++++++++++++:             Resolution: 2560x1440 
          `/+++ooooooooooooo/`           DE: Plasma 5.25.0 
         ./ooosssso++osssssso+`          WM: kwin 
        .oossssso-````/ossssss+`         WM Theme: McSur-dark 
       -osssssso.      :ssssssso.        Theme: [Plasma], Mojave-dark-alt [GTK2/3] 
      :osssssss/        osssso+++.       Icons: McMojave-circle-dark [Plasma], McMojave-circle-dark [GTK2/3] 
     /ossssssss/        +ssssooo/-       Terminal: konsole 
   `/ossssso+/:-        -:/+osssso+-     CPU: 11th Gen Intel i5-1135G7 (8) @ 4.200GHz 
  `+sso+:-`                 `.-/+oso:    GPU: Intel TigerLake-LP GT2 [Iris Xe Graphics] 
 `++:.                           `-/+/   Memory: 1884MiB / 7674MiB 
 .`                                 `/

From Firmware Security report:

Host Security ID: HSI:2! (v1.8.1)

HSI-1
✔ CSME manufacturing mode:       Locked
✔ CSME override:                 Locked
✔ CSME v0:15.0.35.2039:          Valid
✔ Platform Debugging:            Disabled
✔ SPI BIOS region:               Locked
✔ SPI lock:                      Enabled
✔ SPI write:                     Disabled
✔ Supported CPU:                 Valid
✔ TPM empty PCRs:                Valid
✔ TPM v2.0:                      Found
✔ UEFI platform key:             Valid

HSI-2
✔ IOMMU:                         Enabled
✔ Intel BootGuard:               Enabled
✔ Intel BootGuard ACM protected: Valid
✔ Intel BootGuard OTP fuse:      Valid
✔ Intel BootGuard verified boot: Valid
✔ Platform Debugging:            Locked
✔ TPM PCR0 reconstruction:       Valid

HSI-3
✔ Intel BootGuard error policy:  Valid
✔ Pre-boot DMA protection:       Enabled
✔ Suspend-to-idle:               Enabled
✔ Suspend-to-ram:                Disabled
✘ Intel CET Enabled:             Not supported

HSI-4
✔ Intel SMAP:                    Enabled
✘ Encrypted RAM:                 Not supported

Runtime Suffix -!
✔ Linux swap:                    Encrypted
✔ fwupd plugins:                 Untainted
✘ Linux kernel:                  Tainted
✘ Linux kernel lockdown:         Disabled

This system has HSI runtime issues.
 » https://github.com/fwupd/fwupd/wiki/Host-security-ID-runtime-issues

Host Security Events
  2022-06-13 02:14:57:  ✘ Kernel is no longer tainted
  2022-06-11 09:28:26:  ✔ Secure Boot enabled
  2022-06-11 09:28:26:  ✔ Platform Debugging appeared: Disabled
  2022-06-11 09:28:26:  ✔ Supported CPU appeared: Valid
  2022-06-11 09:28:26:  ✔ Platform Debugging appeared: Locked
  2022-06-11 09:28:26:  ✔ Pre-boot DMA protection appeared: Enabled
  2022-03-19 21:45:25:  ✔ Intel DCI debugger disappeared: Disabled
  2022-03-19 21:45:25:  ✔ Intel DCI debugger disappeared: Locked
  2022-03-19 21:45:25:  ✔ Pre-boot DMA protection disappeared: Enabled
  2022-03-19 21:45:25:  ✔ TPM PCR0 reconstruction is now valid

Last edited by merlick_pl17 (2022-06-19 21:46:45)

Offline

#2 2022-06-19 20:51:39

seth
Member
Registered: 2012-09-03
Posts: 29,723

Re: Linux kernel tainted due to boot warning kwin as ex-tainter

There's some sort of kernel oops in the i915 module, the triggering process seems kwin_x11.
The kernel is Not tainted 5.18.5-arch1-1 (and tainting generally happens by out-of-tree modules, never the userspace) but most importantly all relevant context is lost by your filter selection.
The "------------[ cut here ]------------" block ends with some (surprise) "---[ end trace …" line. Post the entire segment and don't copy out of the pager (eg. redirect the journal into a file that you can open w/ a text editor)

Offline

#3 2022-06-19 21:37:24

merlick_pl17
Member
Registered: 2022-06-19
Posts: 5

Re: Linux kernel tainted due to boot warning kwin as ex-tainter

Thanks seth,

Hope this helps better:

Jun 19 13:07:17 myxps kernel: i915 0000:00:02.0: [drm] *ERROR* [CRTC:98:pipe A] mismatch in infoframes.enable (expected 0x00000000, found 0x00000004)
Jun 19 13:07:17 myxps kernel: i915 0000:00:02.0: [drm] *ERROR* mismatch in vsc dp sdp
Jun 19 13:07:17 myxps kernel: i915 0000:00:02.0: [drm] *ERROR* expected:
Jun 19 13:07:17 myxps kernel: i915 0000:00:02.0: DP SDP: VSC, revision 0, length 0
Jun 19 13:07:17 myxps kernel: i915 0000:00:02.0:     pixelformat: RGB
Jun 19 13:07:17 myxps kernel: i915 0000:00:02.0:     colorimetry: sRGB
Jun 19 13:07:17 myxps kernel: i915 0000:00:02.0:     bpc: 0
Jun 19 13:07:17 myxps kernel: i915 0000:00:02.0:     dynamic range: VESA range
Jun 19 13:07:17 myxps kernel: i915 0000:00:02.0:     content type: Not defined
Jun 19 13:07:17 myxps kernel: i915 0000:00:02.0: [drm] *ERROR* found:
Jun 19 13:07:17 myxps kernel: i915 0000:00:02.0: DP SDP: VSC, revision 4, length 14
Jun 19 13:07:17 myxps kernel: i915 0000:00:02.0:     pixelformat: RGB
Jun 19 13:07:17 myxps kernel: i915 0000:00:02.0:     colorimetry: sRGB
Jun 19 13:07:17 myxps kernel: i915 0000:00:02.0:     bpc: 0
Jun 19 13:07:17 myxps kernel: i915 0000:00:02.0:     dynamic range: VESA range
Jun 19 13:07:17 myxps kernel: i915 0000:00:02.0:     content type: Not defined
Jun 19 13:07:17 myxps kernel: ------------[ cut here ]------------
Jun 19 13:07:17 myxps kernel: pipe state doesn't match!
Jun 19 13:07:17 myxps kernel: WARNING: CPU: 1 PID: 784 at drivers/gpu/drm/i915/display/intel_display.c:6677 intel_atomic_commit_tail+0x184c/0x18f0 [i915]
Jun 19 13:07:17 myxps kernel: Modules linked in: uhid xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp nft_compat snd_hda_codec_hdmi nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables libcrc32c nfnetlink cmac algif_hash algif_skcipher snd_ctl_led af_alg snd_sof_pci_intel_tgl snd_sof_intel_hda_common spi_nor snd_hda_codec_realtek iTCO_wdt bnep intel_pmc_bxt snd_hda_codec_generic mtd iTCO_vendor_support soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci hid_multitouch snd_sof_xtensa_dsp 8250_dw snd_sof bridge snd_sof_utils snd_soc_hdac_hda mei_pxp mei_hdcp snd_hda_ext_core snd_soc_acpi_intel_match dell_wmi_sysman stp pmt_telemetry pmt_class llc iwlmvm firmware_attributes_class snd_soc_acpi soundwire_bus wmi_bmof dell_laptop dell_wmi mousedev snd_soc_core ledtrig_audio intel_rapl_msr intel_tcc_cooling mac80211 snd_compress x86_pkg_temp_thermal libarc4 intel_powerclamp dell_smbios coretemp kvm_intel dell_wmi_descriptor
Jun 19 13:07:17 myxps kernel:  ac97_bus dcdbas snd_pcm_dmaengine dell_smm_hwmon snd_hda_intel kvm snd_intel_dspcfg iwlwifi snd_intel_sdw_acpi irqbypass btusb uvcvideo snd_usb_audio snd_hda_codec btrtl intel_cstate videobuf2_vmalloc btbcm snd_usbmidi_lib videobuf2_memops intel_uncore snd_hda_core pcspkr psmouse snd_rawmidi iwlmei videobuf2_v4l2 btintel snd_seq_device snd_hwdep i2c_i801 spi_intel_pci btmtk videobuf2_common spi_intel snd_pcm i2c_smbus r8153_ecm cfg80211 videodev bluetooth cdc_acm cdc_ether snd_timer snd ecdh_generic joydev soundcore mc usbnet ucsi_acpi rfkill typec_ucsi r8152 intel_lpss_pci mei_me typec intel_lpss mei idma64 mii thunderbolt intel_vsec roles wmi hid_apple vfat i2c_hid_acpi i2c_hid apple_mfi_fastcharge fat processor_thermal_device_pci_legacy int3403_thermal processor_thermal_device intel_skl_int3472_tps68470 processor_thermal_rfim tps68470_regulator processor_thermal_mbox clk_tps68470 processor_thermal_rapl mac_hid intel_rapl_common intel_skl_int3472_discrete
Jun 19 13:07:17 myxps kernel:  int340x_thermal_zone intel_soc_dts_iosf intel_hid int3400_thermal acpi_thermal_rel acpi_pad sparse_keymap acpi_tad igen6_edac lzo_rle pkcs8_key_parser dm_multipath ipmi_devintf ipmi_msghandler crypto_user fuse zram ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 dm_crypt cbc encrypted_keys trusted asn1_encoder tee usbhid dm_mod rtsx_pci_sdmmc crct10dif_pclmul crc32_pclmul mmc_core crc32c_intel serio_raw tpm_crb ghash_clmulni_intel atkbd libps2 vivaldi_fmap aesni_intel crypto_simd tpm_tis rtsx_pci nvme xhci_pci tpm_tis_core tpm cryptd rng_core nvme_core xhci_pci_renesas i8042 serio i915 intel_gtt drm_buddy video drm_dp_helper ttm
Jun 19 13:07:17 myxps kernel: CPU: 1 PID: 784 Comm: kwin_wayland Not tainted 5.18.5-arch1-1 #1 e9787f6018c114f5ea5c49a220d7535dfd3a932e
Jun 19 13:07:17 myxps kernel: Hardware name: Dell Inc. XPS 13 9305/0MM15H, BIOS 1.5.0 03/17/2022
Jun 19 13:07:17 myxps kernel: RIP: 0010:intel_atomic_commit_tail+0x184c/0x18f0 [i915]
Jun 19 13:07:17 myxps kernel: Code: ff 80 3d bf 40 20 00 00 0f b6 d0 8d 71 41 48 c7 c7 28 50 79 c0 0f 85 8e 00 00 00 e8 fe 74 30 f8 e9 72 f9 ff ff e8 20 c2 6d f8 <0f> 0b e9 fb f5 ff ff e8 14 c2 6d f8 0f 0b 0f b6 44 24 20 e9 42 f5
Jun 19 13:07:17 myxps kernel: RSP: 0018:ffffbb9bc20dbb60 EFLAGS: 00010282
Jun 19 13:07:17 myxps kernel: RAX: 0000000000000000 RBX: ffff9a7646cb9000 RCX: 0000000000000027
Jun 19 13:07:17 myxps kernel: RDX: ffff9a77c76616a8 RSI: 0000000000000001 RDI: ffff9a77c76616a0
Jun 19 13:07:17 myxps kernel: RBP: ffff9a76430b02a8 R08: 0000000000000000 R09: ffffbb9bc20db970
Jun 19 13:07:17 myxps kernel: R10: 0000000000000003 R11: ffffffffb9ecaa08 R12: ffff9a76430b0000
Jun 19 13:07:17 myxps kernel: R13: ffff9a76430b02a0 R14: ffff9a7686206000 R15: ffff9a7646cb9000
Jun 19 13:07:17 myxps kernel: FS:  00007f872b600f40(0000) GS:ffff9a77c7640000(0000) knlGS:0000000000000000
Jun 19 13:07:17 myxps kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jun 19 13:07:17 myxps kernel: CR2: 00007f662cb31d04 CR3: 000000011dc7c006 CR4: 0000000000f70ee0
Jun 19 13:07:17 myxps kernel: PKRU: 55555554
Jun 19 13:07:17 myxps kernel: Call Trace:
Jun 19 13:07:17 myxps kernel:  <TASK>
Jun 19 13:07:17 myxps kernel:  intel_atomic_commit+0x33d/0x390 [i915 80079f9a53d89dc2e9e0bf08ab840ba6c3c6d5d2]
Jun 19 13:07:17 myxps kernel:  drm_mode_atomic_ioctl+0x9bb/0xbc0
Jun 19 13:07:17 myxps kernel:  ? drm_plane_get_damage_clips.cold+0x1c/0x1c
Jun 19 13:07:17 myxps kernel:  ? drm_atomic_set_property+0xb40/0xb40
Jun 19 13:07:17 myxps kernel:  drm_ioctl_kernel+0xc7/0x170
Jun 19 13:07:17 myxps kernel:  drm_ioctl+0x22e/0x410
Jun 19 13:07:17 myxps kernel:  ? drm_atomic_set_property+0xb40/0xb40
Jun 19 13:07:17 myxps kernel:  __x64_sys_ioctl+0x8e/0xc0
Jun 19 13:07:17 myxps kernel:  do_syscall_64+0x5c/0x90
Jun 19 13:07:17 myxps kernel:  ? syscall_exit_to_user_mode+0x26/0x50
Jun 19 13:07:17 myxps kernel:  ? do_syscall_64+0x6b/0x90
Jun 19 13:07:17 myxps kernel:  entry_SYSCALL_64_after_hwframe+0x44/0xae
Jun 19 13:07:17 myxps kernel: RIP: 0033:0x7f872fd077af
Jun 19 13:07:17 myxps kernel: Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 18 48 8b 44 24 18 64 48 2b 04 25 28 00 00
Jun 19 13:07:17 myxps kernel: RSP: 002b:00007fff93c12ed0 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
Jun 19 13:07:17 myxps kernel: RAX: ffffffffffffffda RBX: 000055a4016e4d90 RCX: 00007f872fd077af
Jun 19 13:07:17 myxps kernel: RDX: 00007fff93c12f70 RSI: 00000000c03864bc RDI: 0000000000000015
Jun 19 13:07:17 myxps kernel: RBP: 00007fff93c12f70 R08: 0000000000000007 R09: 0000000000000007
Jun 19 13:07:17 myxps kernel: R10: 000055a401749330 R11: 0000000000000246 R12: 00000000c03864bc
Jun 19 13:07:17 myxps kernel: R13: 0000000000000015 R14: 000055a4016e56f0 R15: 000055a401740b10
Jun 19 13:07:17 myxps kernel:  </TASK>
Jun 19 13:07:17 myxps kernel: ---[ end trace 0000000000000000 ]---

Entire segment:
Link

Last edited by merlick_pl17 (2022-06-19 21:43:07)

Offline

#4 2022-06-19 22:05:19

merlick_pl17
Member
Registered: 2022-06-19
Posts: 5

Re: Linux kernel tainted due to boot warning kwin as ex-tainter

I think I identified a root cause but why this triggers seems bizzare to me. Basically it happens when my docking station with my external monitor is connected to my laptop. If I boot laptop standalone, the kernel warning flag gets cleared. So simply switching DP output port is what it seems to trigger this  behavior.

This is what firmware report generates before connecting laptop to the docking station:

Runtime Suffix -!
✔ Linux kernel:                  Untainted
✔ Linux swap:                    Encrypted
✔ fwupd plugins:                 Untainted
✘ Linux kernel lockdown:         Disabled

This system has HSI runtime issues.
 » https://github.com/fwupd/fwupd/wiki/Host-security-ID-runtime-issues

Host Security Events
  2022-06-18 10:26:42:  ✔ Kernel is tainted
  2022-06-13 02:14:57:  ✘ Kernel is no longer tainted
  2022-06-11 09:28:26:  ✔ Secure Boot enabled
  2022-06-11 09:28:26:  ✔ Platform Debugging appeared: Disabled
  2022-06-11 09:28:26:  ✔ Supported CPU appeared: Valid
  2022-06-11 09:28:26:  ✔ Platform Debugging appeared: Locked
  2022-06-11 09:28:26:  ✔ Pre-boot DMA protection appeared: Enabled
  2022-03-19 21:45:25:  ✔ Intel DCI debugger disappeared: Disabled
  2022-03-19 21:45:25:  ✔ Intel DCI debugger disappeared: Locked
  2022-03-19 21:45:25:  ✔ Pre-boot DMA protection disappeared: Enabled
  2022-03-19 21:45:25:  ✔ TPM PCR0 reconstruction is now valid

This is what happens after I connect the laptop back to my docking station:

Runtime Suffix -!
✔ Linux swap:                    Encrypted
✔ fwupd plugins:                 Untainted
✘ Linux kernel:                  Tainted
✘ Linux kernel lockdown:         Disabled

This system has HSI runtime issues.
 » https://github.com/fwupd/fwupd/wiki/Host-security-ID-runtime-issues

Host Security Events
  2022-06-19 21:50:43:  ✘ Kernel is no longer tainted
  2022-06-18 10:26:42:  ✔ Kernel is tainted
  2022-06-13 02:14:57:  ✘ Kernel is no longer tainted
  2022-06-11 09:28:26:  ✔ Secure Boot enabled
  2022-06-11 09:28:26:  ✔ Platform Debugging appeared: Disabled
  2022-06-11 09:28:26:  ✔ Supported CPU appeared: Valid
  2022-06-11 09:28:26:  ✔ Platform Debugging appeared: Locked
  2022-06-11 09:28:26:  ✔ Pre-boot DMA protection appeared: Enabled
  2022-03-19 21:45:25:  ✔ Intel DCI debugger disappeared: Disabled
  2022-03-19 21:45:25:  ✔ Intel DCI debugger disappeared: Locked
  2022-03-19 21:45:25:  ✔ Pre-boot DMA protection disappeared: Enabled
  2022-03-19 21:45:25:  ✔ TPM PCR0 reconstruction is now valid
 $ systool -m i915 -av
Module = "i915"

  Attributes:
    coresize            = "3428352"
    initsize            = "0"
    initstate           = "live"
    refcnt              = "55"
    srcversion          = "4077B9649BFAA03FF035155"
    taint               = ""
    uevent              = <store method only>

  Parameters:

  Sections:

Last edited by merlick_pl17 (2022-06-19 22:24:32)

Offline

#5 2022-06-20 06:18:16

seth
Member
Registered: 2012-09-03
Posts: 29,723

Re: Linux kernel tainted due to boot warning kwin as ex-tainter

The kernel is gonna be "tainted" because of/by the warning, that's nothing to freak out about.
https://git.kernel.org/pub/scm/linux/ke … l-chktaint for actual taints

The kernel warning is likely triggered by the specific output, see eg. https://gitlab.freedesktop.org/drm/intel/-/issues/3000 for a similar bug.

Offline

#6 2022-06-20 10:44:29

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 10,140

Re: Linux kernel tainted due to boot warning kwin as ex-tainter

The report mentioned https://github.com/fwupd/fwupd/wiki/Hos … ime-issues .

I checked it and the description of "Linux Kernel Taint: Tainted" suggests (to me) proprietary and/or out-of-tree kernel modules could cause this.

merlick_pl17 wrote:

Basically it happens when my docking station with my external monitor is connected to my laptop. If I boot laptop standalone, the kernel warning flag gets cleared. So simply switching DP output port is what it seems to trigger this  behavior.

Does the docking station or monitor use DisplayLink / evdi ?


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
Did you use the guided installer ? If yes, I can't help you.

(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Offline

#7 2022-06-21 04:35:10

merlick_pl17
Member
Registered: 2022-06-19
Posts: 5

Re: Linux kernel tainted due to boot warning kwin as ex-tainter

Lone_Wolf wrote:

The report mentioned https://github.com/fwupd/fwupd/wiki/Hos … ime-issues .

I checked it and the description of "Linux Kernel Taint: Tainted" suggests (to me) proprietary and/or out-of-tree kernel modules could cause this.

merlick_pl17 wrote:

Basically it happens when my docking station with my external monitor is connected to my laptop. If I boot laptop standalone, the kernel warning flag gets cleared. So simply switching DP output port is what it seems to trigger this  behavior.

Does the docking station or monitor use DisplayLink / evdi ?

No, just universal usb-c with mDP standard. I believe its caused by specific output which these dmesg logs hint:

Jun 19 13:07:17 myxps kernel: i915 0000:00:02.0: [drm] *ERROR* mismatch in vsc dp sdp
Jun 19 13:07:17 myxps kernel: i915 0000:00:02.0: [drm] *ERROR* expected:
Jun 19 13:07:17 myxps kernel: i915 0000:00:02.0: DP SDP: VSC, revision 0, length 0
Jun 19 13:07:17 myxps kernel: i915 0000:00:02.0:     pixelformat: RGB
Jun 19 13:07:17 myxps kernel: i915 0000:00:02.0:     colorimetry: sRGB
Jun 19 13:07:17 myxps kernel: i915 0000:00:02.0:     bpc: 0
Jun 19 13:07:17 myxps kernel: i915 0000:00:02.0:     dynamic range: VESA range
Jun 19 13:07:17 myxps kernel: i915 0000:00:02.0:     content type: Not defined
Jun 19 13:07:17 myxps kernel: i915 0000:00:02.0: [drm] *ERROR* found:
Jun 19 13:07:17 myxps kernel: i915 0000:00:02.0: DP SDP: VSC, revision 4, length 14
Jun 19 13:07:17 myxps kernel: i915 0000:00:02.0:     pixelformat: RGB
Jun 19 13:07:17 myxps kernel: i915 0000:00:02.0:     colorimetry: sRGB
Jun 19 13:07:17 myxps kernel: i915 0000:00:02.0:     bpc: 0
Jun 19 13:07:17 myxps kernel: i915 0000:00:02.0:     dynamic range: VESA range
Jun 19 13:07:17 myxps kernel: i915 0000:00:02.0:     content type: Not defined

Offline

#8 2022-06-21 04:38:19

merlick_pl17
Member
Registered: 2022-06-19
Posts: 5

Re: Linux kernel tainted due to boot warning kwin as ex-tainter

seth wrote:

The kernel is gonna be "tainted" because of/by the warning, that's nothing to freak out about.
https://git.kernel.org/pub/scm/linux/ke … l-chktaint for actual taints

The kernel warning is likely triggered by the specific output, see eg. https://gitlab.freedesktop.org/drm/intel/-/issues/3000 for a similar bug.

That's very helpful. The issue seems similar, in case his it was caused by connecting to specific monitor and in my case because I switch from display 0 (internal screen) to external monitor via usb-c (which sees it at address DP4).

Offline

Board footer

Powered by FluxBB