Wind River Support Network

Description

The following call trace may show in dump-capture kernel  when doing kdump on Elkhart Lake.


Call Trace:
<TASK>
intel_psr_enable_locked+0x4d9/0x710 [i915]
? __might_sleep+0x49/0x80
intel_psr_update+0x124/0x150 [i915]
intel_ddi_update_pipe+0x7b/0xc0 [i915]
intel_update_crtc+0x2e7/0x370 [i915]
? _raw_spin_lock_irqsave+0x1e/0x60
skl_commit_modeset_enables+0x142/0x520 [i915]
intel_atomic_commit_tail+0x440/0x1740 [i915]
? __queue_work+0x1f8/0x450
? queue_work_on+0x2c/0x40
? intel_atomic_commit_ready+0x58/0x68 [i915]
? __i915_sw_fence_complete+0x111/0x1c0 [i915]
intel_atomic_commit+0x322/0x3a0 [i915]
drm_atomic_commit+0x47/0x60
intel_modeset_init+0x189/0x260 [i915]
i915_driver_probe+0x632/0xd20 [i915]
i915_pci_probe+0x48/0x130 [i915]
? _raw_spin_unlock_irqrestore+0x1f/0x40
local_pci_probe+0x45/0x90
pci_device_probe+0x106/0x1c0
really_probe.part.0+0xbe/0x2c0
__driver_probe_device+0x96/0x130
driver_probe_device+0x24/0xf0
__driver_attach+0xba/0x1a0
? __device_attach_driver+0x100/0x100
bus_for_each_dev+0x7c/0xd0
driver_attach+0x1e/0x30
bus_add_driver+0x12c/0x1e0
driver_register+0x95/0x100
__pci_register_driver+0x68/0x70
i915_register_pci_driver+0x23/0x30 [i915]
i915_init+0x24/0x9c [i915]
? 0xffffffffc052f000
do_one_initcall+0x4f/0x210
? kmemleak_alloc+0x26/0x40
? kmem_cache_alloc_trace+0x2fe/0x4f0
do_init_module+0x52/0x260
load_module+0x256c/0x2880
__do_sys_finit_module+0xb5/0x100
? __do_sys_finit_module+0xb5/0x100
__x64_sys_finit_module+0x18/0x20
do_syscall_64+0x40/0x90
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f37f52a62ad
Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 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 43 ab 0e 00 f7 d8 64
89 01 48
RSP: 002b:00007ffed26ce5d8 EFLAGS: 00000246 ORIG_RAX: 0000000000000139
RAX: ffffffffffffffda RBX: 000055d5b3131540 RCX: 00007f37f52a62ad
RDX: 0000000000000000 RSI: 000055d5b3036ae0 RDI: 000000000000000f
RBP: 0000000000020000 R08: 0000000000000000 R09: 000055d5b3131540
R10: 000000000000000f R11: 0000000000000246 R12: 000055d5b3036ae0
R13: 0000000000000000 R14: 0000000000000000 R15: 000055d5b3131540
</TASK>

Steps to Reproduce

1. Build project

$ /lpg-build/cdc/fast_prod/WRL10_22/WRL10_22_GIT/wrlinux-10/setup.sh --machines=xilinx-zynqmp --templates=feature/kexec,feature/kdump --accept-eula=yes --dl-layers
$ source environment-setup-x86_64-wrlinuxsdk-linux
$ source oe-init-build-env
$ bitbake wrlinux-image-std

2. Load images to the target (#29174) and boot it up with "crashkernel=512M" boot line
3. Run the following command on the board

# cat /proc/cmdline > args
# vi args # add maxcpus=1 to the command line
# cp /boot/bzImage /boot/kernel_kdump
# mv /etc/sysconfig/kdump.conf /etc/sysconfig/kdump.orig
# kexec -p /boot/kernel_kdump --append="`cat args`"
# echo c > /proc/sysrq-trigger