5.15 kernel, DIsplay not work

[usstlf]

5.15 kernel, DIsplay not work. no signal in display, but hdmi can show everything.

[penk]

@usstlf hi, thanks for the report, can you tell me which kernel package do you use? I'd like to reproduce.

[penk]

Reproducible with 5.15.30-v8+ after sudo rpi-update.

Linux raspberrypi 5.15.30-v8+ #1536 SMP PREEMPT Mon Mar 28 13:53:14 BST 2022 aarch64 GNU/Linux

dmesg:

...
[    8.297284] CPU: 3 PID: 7 Comm: kworker/u8:0 Tainted: G         C        5.15.30-v8+ #1536
[    8.297295] Hardware name: Raspberry Pi Compute Module 4 Rev 1.0 (DT)
[    8.297304] Workqueue: events_unbound deferred_probe_work_func
[    8.297320] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[    8.297330] pc : of_drm_find_panel+0x80/0xd0 [drm]
[    8.297449] lr : of_drm_find_panel+0x54/0xd0 [drm]
[    8.297531] sp : ffffffc00963b8e0
[    8.297537] x29: ffffffc00963b8e0 x28: 0000000000000000 x27: ffffff8047187a00
[    8.297550] x26: ffffff8044e17480 x25: ffffff8047187a00 x24: 0000000000000000
[    8.297563] x23: 0000000000000000 x22: 0000000000000000 x21: ffffffc000c849f8
[    8.297575] x20: ffffff807fc1dcf8 x19: ffffff8043a66080 x18: 0000000000000001
[    8.297586] x17: ffffffc076b87000 x16: ffffffc009604000 x15: ffffffffffffffff
[    8.297598] x14: ffffff0000000000 x13: ffffffffffffffff x12: 000000000000000c
[    8.297610] x11: 0000000000000003 x10: 0101010101010101 x9 : ffffffc000c6078c
[    8.297622] x8 : 7f7f7f7f7f7f7f7f x7 : fefefeff646c606d x6 : ffffffc00963b810
[    8.297633] x5 : 0000000000000001 x4 : 0000000000000000 x3 : ffffffc000c849f8
[    8.297645] x2 : ffffff80401cbc80 x1 : ffffffc000c84a18 x0 : fffffffffffffbff
[    8.297657] Call trace:
[    8.297662]  of_drm_find_panel+0x80/0xd0 [drm]
[    8.297744]  drm_of_find_panel_or_bridge+0x70/0xf0 [drm]
[    8.297826]  vc4_dsi_bind+0x3ac/0x7d0 [vc4]
[    8.297859]  component_bind_all+0x108/0x278
[    8.297870]  vc4_drm_bind+0x1d8/0x2f8 [vc4]
[    8.297899]  try_to_bring_up_master+0x170/0x1d8
[    8.297907]  __component_add+0xb0/0x180
[    8.297915]  component_add+0x1c/0x28
[    8.297922]  vc4_dsi_host_attach+0x88/0x148 [vc4]
[    8.297951]  mipi_dsi_attach+0x30/0x48
[    8.297958]  ili9881c_dsi_probe+0xd4/0x120 [panel_ilitek_ili9881c]
[    8.297970]  mipi_dsi_drv_probe+0x28/0x38
[    8.297977]  really_probe+0xc0/0x318
[    8.297985]  __driver_probe_device+0x80/0xe8
[    8.297993]  driver_probe_device+0x88/0x118
[    8.298000]  __device_attach_driver+0x98/0xe8
[    8.298008]  bus_for_each_drv+0x84/0xd8
[    8.298018]  __device_attach+0xf0/0x150
[    8.298025]  device_initial_probe+0x1c/0x28
[    8.298032]  bus_probe_device+0xa4/0xb0
[    8.298039]  deferred_probe_work_func+0x90/0xc8
[    8.298047]  process_one_work+0x1f8/0x4a0
[    8.298057]  worker_thread+0x50/0x480
[    8.298064]  kthread+0x140/0x158
[    8.298072]  ret_from_fork+0x10/0x20
[    8.298085] Code: eb01001f d1008013 540001a0 f85e0000 (f9412800) 
[    8.298094] ---[ end trace bceeed67386d8d12 ]---

5.15.32-dmesg.txt

[penk]

Related discussion in the forum: https://forums.raspberrypi.com/viewtopic.php?t=328071

[penk]

@usstlf turns out it was the driver bug, I can confirm the fix in this post
https://forums.raspberrypi.com/viewtopic.php?p=1989016#p1989016

[penk]

And here: https://github.com/raspberrypi/linux/pull/4969/files

[usstlf]

thanks a lot. I will update the driver and rebuild ther kernel and have a try.