lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <2810b938-7df7-408e-9775-6f20d1694176@gmail.com>
Date: Thu, 15 Aug 2024 02:45:44 -0300
From: "Renan W. P." <renanwilliamprado@...il.com>
To: jani.nikula@...ux.intel.com, joonas.lahtinen@...ux.intel.com,
 rodrigo.vivi@...el.com, intel-gfx@...ts.freedesktop.org,
 intel-xe@...ts.freedesktop.org, tursulin@...ulin.net, airlied@...il.com,
 daniel@...ll.ch, dri-devel@...ts.freedesktop.org,
 linux-kernel@...r.kernel.org
Subject: A huge warning in dmesg pointing to
 drivers/gpu/drm/i915/display/intel_tc.c

Hello, mainteners,

[1.] One line summary of the problem:

A huge warning in dmesg pointing to drivers/gpu/drm/i915/display/intel_tc.c

[2.] Full description of the problem/report:

I can't identify any factual problems beyond a warning in dmesg triggered at every boot, i.e., I have seen no features affected. The dmesg output is located in the log files in the attachment.
I am facing this warning in LENOVO 82MG/LNVNB161216, BIOS H4CN35WW(V2.04) 04/12/2024 (Lenovo Ganing 3i). I have tried two new kernel versions fromwww.kernel.org  site, the Kernel 6.10.5 and 6.1.105.
Additionally, I have used Debian at least since kernel version 6.1.22. All kernels present warnings in the same file with slightly different outputs in dmesg. I am compiling the kernel with the config-6.1.105 file in the attachment.

[3.] Keywords (i.e., modules, networking, kernel):

Modules

[4.] Kernel information:

The issue is present in Kernel 6.10.5 and 6.1.105, but the warning might be present since 6.1.22.

[4.1.] Kernel version (from /proc/version):

Linux version 6.10.5 (renan@...ian) (gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC Thu Aug 15 01:06:09 -03 2024

[4.2.] Kernel .config file:

In the config-6.1.105 file in the attachment

[5.] Most recent kernel version which did not have the bug:

This computer is "new". I bought it two months ago, and I have not seem this warning not occuring.

[6.] Output of Oops.. message (if applicable) with symbolic information
      resolved (see Documentation/admin-guide/bug-hunting.rst) :

[    2.237704] ------------[ cut here ]------------
[    2.237706] i915 0000:00:02.0: drm_WARN_ON(val == 0xffffffff)
[    2.237721] WARNING: CPU: 7 PID: 217 at drivers/gpu/drm/i915/display/intel_tc.c:737 tgl_tc_phy_init+0x103/0x130 [i915]
[    2.237969] Modules linked in: i915(+) joydev hid_generic usbhid hid nvme nvme_core t10_pi crc64_rocksoft crc64 crc_t10dif crct10dif_generic i2c_algo_bit cec rc_core drm_buddy ttm drm_display_helper xhci_pci xhci_hcd drm_kms_helper crct10dif_pclmul usbcore evdev crct10dif_common crc32c_intel serio_raw drm usb_common vmd video wmi fan
[    2.238002] CPU: 7 PID: 217 Comm: (udev-worker) Tainted: G        W          6.10.5 #1
[    2.238007] Hardware name: LENOVO 82MG/LNVNB161216, BIOS H4CN35WW(V2.04) 04/12/2024
[    2.238010] RIP: 0010:tgl_tc_phy_init+0x103/0x130 [i915]
[    2.238241] Code: 48 8b 6f 50 48 85 ed 75 03 48 8b 2f e8 76 62 ac d8 48 c7 c1 e8 94 c5 c0 48 89 ea 48 c7 c7 62 a7 c7 c0 48 89 c6 e8 bd a0 2e d8 <0f> 0b 48 8b 3b e8 e3 7d f9 ff 89 c1 89 c5 c1 e9 1f c1 ed 1f 8d 14
[    2.238248] RSP: 0018:ffffb95e40a53608 EFLAGS: 00010286
[    2.238252] RAX: 0000000000000000 RBX: ffff8e8f919e7000 RCX: c0000000fffdffff
[    2.238256] RDX: 0000000000000000 RSI: 00000000fffdffff RDI: 0000000000000001
[    2.238259] RBP: ffff8e8f81bf6d30 R08: 0000000000000000 R09: 0000000000000003
[    2.238262] R10: ffffb95e40a53498 R11: ffff8e952f7fffe8 R12: ffff8e8f813ec000
[    2.238266] R13: ffff8e8f813ec618 R14: 000fffffffe00000 R15: ffff8e8f813ec000
[    2.238269] FS:  00007f4ce50158c0(0000) GS:ffff8e952e780000(0000) knlGS:0000000000000000
[    2.238274] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[    2.238278] CR2: 000055b901674008 CR3: 0000000102c70004 CR4: 0000000000770ef0
[    2.238281] PKRU: 55555554
[    2.238284] Call Trace:
[    2.238286]  <TASK>
[    2.238289]  ? __warn+0x7c/0x120
[    2.238295]  ? tgl_tc_phy_init+0x103/0x130 [i915]
[    2.238520]  ? report_bug+0x160/0x190
[    2.238527]  ? prb_read_valid+0x17/0x20
[    2.238532]  ? handle_bug+0x41/0x70
[    2.238538]  ? exc_invalid_op+0x13/0x60
[    2.238543]  ? asm_exc_invalid_op+0x16/0x20
[    2.238551]  ? tgl_tc_phy_init+0x103/0x130 [i915]
[    2.238777]  ? tgl_tc_phy_init+0x103/0x130 [i915]
[    2.238991]  intel_tc_port_init+0x17e/0x220 [i915]
[    2.239208]  intel_ddi_init+0x9fa/0x11d0 [i915]
[    2.239435]  ? __pfx_intel_ddi_init+0x10/0x10 [i915]
[    2.239657]  intel_bios_for_each_encoder+0x31/0x50 [i915]
[    2.239929]  intel_setup_outputs+0x4e0/0xc20 [i915]
[    2.240194]  intel_display_driver_probe_nogem+0x139/0x220 [i915]
[    2.240453]  i915_driver_probe+0x63b/0xba0 [i915]
[    2.240654]  local_pci_probe+0x3e/0x90
[    2.240661]  pci_device_probe+0xc3/0x240
[    2.240667]  really_probe+0xd3/0x380
[    2.240673]  ? __pfx___driver_attach+0x10/0x10
[    2.240678]  __driver_probe_device+0x78/0x150
[    2.240684]  driver_probe_device+0x1f/0x90
[    2.240689]  __driver_attach+0xce/0x1c0
[    2.240694]  bus_for_each_dev+0x81/0xd0
[    2.240699]  bus_add_driver+0x10e/0x240
[    2.240704]  driver_register+0x55/0x100
[    2.240710]  i915_init+0x1e/0xc0 [i915]
[    2.240904]  ? __pfx_i915_init+0x10/0x10 [i915]
[    2.241092]  do_one_initcall+0x54/0x320
[    2.241099]  do_init_module+0x60/0x240
[    2.241103]  init_module_from_file+0x86/0xc0
[    2.241108]  idempotent_init_module+0x120/0x310
[    2.241113]  __x64_sys_finit_module+0x5a/0xb0
[    2.241117]  do_syscall_64+0x7e/0x190
[    2.241121]  ? vm_mmap_pgoff+0x12d/0x1c0
[    2.241128]  ? ksys_mmap_pgoff+0x153/0x1f0
[    2.241135]  ? syscall_exit_to_user_mode+0x73/0x200
[    2.241140]  ? do_syscall_64+0x8a/0x190
[    2.241145]  ? syscall_exit_to_user_mode+0x73/0x200
[    2.241150]  ? do_syscall_64+0x8a/0x190
[    2.241156]  ? vfs_read+0x292/0x370
[    2.241162]  ? syscall_exit_to_user_mode+0x73/0x200
[    2.241167]  ? do_syscall_64+0x8a/0x190
[    2.241172]  ? syscall_exit_to_user_mode+0x73/0x200
[    2.241177]  ? do_syscall_64+0x8a/0x190
[    2.241181]  ? do_syscall_64+0x8a/0x190
[    2.241185]  ? clear_bhb_loop+0x45/0xa0
[    2.241189]  ? clear_bhb_loop+0x45/0xa0
[    2.241192]  ? clear_bhb_loop+0x45/0xa0
[    2.241195]  entry_SYSCALL_64_after_hwframe+0x76/0x7e
[    2.241202] RIP: 0033:0x7f4ce5723719
[    2.241205] Code: 08 89 e8 5b 5d c3 66 2e 0f 1f 84 00 00 00 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d b7 06 0d 00 f7 d8 64 89 01 48
[    2.241212] RSP: 002b:00007ffe5dcb5ed8 EFLAGS: 00000246 ORIG_RAX: 0000000000000139
[    2.241217] RAX: ffffffffffffffda RBX: 000055df22026c20 RCX: 00007f4ce5723719
[    2.241221] RDX: 0000000000000000 RSI: 00007f4ce58b6efd RDI: 0000000000000013
[    2.241224] RBP: 00007f4ce58b6efd R08: 0000000000000000 R09: 000000000000000a
[    2.241228] R10: 0000000000000013 R11: 0000000000000246 R12: 0000000000020000
[    2.241231] R13: 0000000000000000 R14: 000055df22023820 R15: 000000000000000a
[    2.241236]  </TASK>
[    2.241238] ---[ end trace 0000000000000000 ]---


[7.] A small shell script or example program which triggers the
      problem (if possible)

Not possible

[8.] Environment
[8.1.] Software (add the output of the ver_linux script here)

[8.2.] Processor information (from /proc/cpuinfo):

In file cpuinfo.log in the attachments

[8.3.] Module information (from /proc/modules):

In file modules.log in the attachments

[8.4.] Loaded driver and hardware information (/proc/ioports, /proc/iomem)

In files ioports.log and iomen.log in the attachments

[8.5.] PCI information ('lspci -vvv' as root):

In file "sudo lspci -vvv".log in the attachments

[8.6.] SCSI information (from /proc/scsi/scsi):

File does not exist

[8.7.] Other information that might be relevant to the problem
        (please look in /proc and include all information that you
        think to be relevant):

Not applicable

[X.] Other notes, patches, fixes, workarounds:

No known workarounds in the web was found

Content of type "text/html" skipped

View attachment "dmesg-6.10.5-v2.log" of type "text/x-log" (232539 bytes)

View attachment "dmesg-6.1.105-v2.log" of type "text/x-log" (213822 bytes)

View attachment "config-6.1.105" of type "text/plain" (259442 bytes)

View attachment "cpuinfo.log" of type "text/x-log" (14472 bytes)

View attachment "xrandr --verbose.log" of type "text/x-log" (21023 bytes)

View attachment "modules.log" of type "text/x-log" (12956 bytes)

View attachment "iomen.log" of type "text/x-log" (4009 bytes)

View attachment "ioports.log" of type "text/x-log" (951 bytes)

View attachment "sudo lspci -vvv.log" of type "text/x-log" (57164 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ