On Tue, 2024-12-10 at 10:58 +0200, Jani Nikula wrote:
On Tue, 10 Dec 2024, Sakari Ailus sakari.ailus@linux.intel.com wrote:
Hi,
... FYI 6.12.4 got a crash shortly after booting in dma_alloc_attrs - maybe triggered in ipu6_probe. Crash only happened on laptop with ipu6. All other machines are running fine.
Have you read the dmesg further than the IPU6 related warning? The IPU6 driver won't work (maybe not even probe?) but if the system crashes, it appears unlikely the IPU6 drivers would have something to do with that. Look for warnings on linked list corruption later, they seem to be coming from the i915 driver.
And the list corruption is actually happening in cpu_latency_qos_update_request(). I don't see any i915 changes in 6.12.4 that could cause it.
I guess the question is, when did it work? Did 6.12.3 work?
BR, Jani.
- 6.12.1 worked
- mainline - works (but only with i915 patch set [1] otherwise there are no graphics at all)
[1] https://patchwork.freedesktop.org/series/141911/
- 6.12.3 - crashed (i see i915 not ipu6) and again it has cpu_latency_qos_update_request+0x61/0xc0
CPU: 3 UID: 0 PID: 233674 Comm: kworker/3:1 Tainted: G W 6.12.3-stable-1 #2 b13471ff40a4c707f51ed6741af496b8675e3b0f Tainted: [W]=WARN Hardware name: Dell Inc. XPS 9320/0CR6NC, BIOS 2.16.1 09/11/2024 Workqueue: events output_poll_execute RIP: 0010:__list_add_valid_or_report+0x83/0xa0 Code: eb e9 48 89 c1 48 c7 c7 18 61 b3 ac e8 76 26 a0 ff 0f 0b eb d6 48 89 d1 48 89 c6 4c 89 c2 48 c7 c7 68 61 b3 ac e8 5d 26 a0 ff <0f> 0b eb bd 48 89 f2 48 89 c1 48 89 fe 48 c7 c7 b8 61 b3 ac e8 44 RSP: 0018:ffffa903b1a3f8a8 EFLAGS: 00010086 RAX: 0000000000000000 RBX: ffff8ac28751a0a8 RCX: 0000000000000027 RDX: ffff8ac9ef3a18c8 RSI: 0000000000000001 RDI: ffff8ac9ef3a18c0 RBP: ffff8ac283fc6ea8 R08: 0000000000000000 R09: ffffa903b1a3f728 R10: ffffffffad2a67f0 R11: 0000000000000003 R12: ffffffffad25e960 R13: ffff8ac283fc6ec0 R14: ffff8ac283fc6eb0 R15: 0000000000000000 FS: 0000000000000000(0000) GS:ffff8ac9ef380000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00002d641a8cd000 CR3: 00000006afa24000 CR4: 0000000000f52ef0 PKRU: 55555554 Call Trace: <TASK> ? __list_add_valid_or_report+0x83/0xa0 ? __warn.cold+0x93/0xf6 ? __list_add_valid_or_report+0x83/0xa0 ? report_bug+0xff/0x140 ? console_unlock+0x9d/0x140 ? handle_bug+0x58/0x90 ? exc_invalid_op+0x17/0x70 ? asm_exc_invalid_op+0x1a/0x20 ? __list_add_valid_or_report+0x83/0xa0 ? __list_add_valid_or_report+0x83/0xa0 plist_add+0xdd/0x140 pm_qos_update_target+0xa0/0x1f0 cpu_latency_qos_update_request+0x61/0xc0 intel_dp_aux_xfer+0x4c7/0x6e0 [i915 130aa22568da4be1bf6a8f4b926f812e9a4460d0] intel_dp_aux_transfer+0x10e/0x3b0 [i915 130aa22568da4be1bf6a8f4b926f812e9a4460d0] drm_dp_i2c_do_msg+0x81/0x300 [drm_display_helper f34443fa650f4fdc86a0e4b3a7e8f7fa67570a48] drm_dp_i2c_xfer+0xe4/0x2f0 [drm_display_helper f34443fa650f4fdc86a0e4b3a7e8f7fa67570a48] __i2c_transfer+0x1d5/0x540 i2c_transfer+0x5c/0xd0 drm_do_probe_ddc_edid+0xc0/0x140 ? __pfx_drm_do_probe_ddc_edid+0x10/0x10 edid_block_read+0x38/0x100 _drm_do_get_edid+0xb6/0x3a0 ? __pfx_drm_do_probe_ddc_edid+0x10/0x10 drm_edid_read_custom+0x32/0xc0 intel_dp_set_edid+0x3d4/0x3f0 [i915 130aa22568da4be1bf6a8f4b926f812e9a4460d0] intel_dp_detect+0x502/0x7b0 [i915 130aa22568da4be1bf6a8f4b926f812e9a4460d0] drm_helper_probe_detect_ctx+0x52/0x110 output_poll_execute+0x13d/0x2d0 process_one_work+0x174/0x330 worker_thread+0x252/0x390 ? __pfx_worker_thread+0x10/0x10 kthread+0xcf/0x100 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x31/0x50 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK> ---[ end trace 0000000000000000 ]--- ------------[ cut here ]------------