This issue also effects me.
```
May 24 21:10:24 loong0 kernel: input: Telink Wireless Receiver as
/devices/pci0000:00/0000:00:05.0/usb6/6-2/6-2:1.1/0003:248A:8327.0002/input/input4
May 24 21:10:24 loong0 kernel: hid-generic 0003:248A:8327.0002:
input,hidraw1: USB HID v1.11 Keyboard [Telink Wireless Receiver] on
usb-0000:00:05.0-2/input1
May 24 21:10:24 loong0 kernel: Console: switching to colour frame buffer
device 240x67
May 24 21:10:24 loong0 kernel: ------------[ cut here ]------------
May 24 21:10:24 loong0 kernel: loongson 0000:00:06.1: [drm]
drm_WARN_ON_ONCE(drm_drv_uses_atomic_modeset(dev))
May 24 21:10:24 loong0 kernel: WARNING: drivers/gpu/drm/drm_vblank.c:747
at drm_crtc_vblank_helper_get_vblank_timestamp_internal+0x3d4/0x450
[drm], CPU#0: kworker/0:2/230
May 24 21:10:24 loong0 kernel: Modules linked in: hid_generic usbhid hid
loongson(+) i2c_algo_bit drm_ttm_helper ttm drm_client_lib
drm_kms_helper ahci libahci xhci_pci ohci_pci xhci_hcd drm libata nvme
dwmac_loongson ehci_pci stmmac_libpci nvme_core ehci_hcd ohci_hcd stmmac
usbcore scsi_mod nvme_keyring nvme_auth pcs_xpcs zlib_deflate hkdf
phylink usb_common scsi_com>
May 24 21:10:24 loong0 kernel: CPU: 0 UID: 0 PID: 230 Comm: kworker/0:2
Not tainted 7.0.7+deb14-loong64 #1 PREEMPTLAZY Debian 7.0.7-1
May 24 21:10:24 loong0 kernel: Hardware name: Loongson
CTCI02LS3A6000C-K/CTCI02LS3A6000C-K, BIOS
Loongson-UDK2018-V4.0.05692-CTCI02202408 08/09/24 14:08:25
May 24 21:10:24 loong0 kernel: Workqueue: events
drm_fb_helper_damage_work [drm_kms_helper]
May 24 21:10:24 loong0 kernel: pc ffff800002ae2e04 ra ffff800002ae2e04
tp 900000011de4c000 sp 900000011de4fb40
May 24 21:10:24 loong0 kernel: a0 000000000000004f a1 0000000000000000
a2 0000000000000040 a3 ffffffffffffffff
May 24 21:10:24 loong0 kernel: a4 ffff800002d4cbe0 a5 900000011de4fb08
a6 2d2d2d2d2d2d2d2d a7 2d2d2d2d2d2d2d2d
May 24 21:10:24 loong0 kernel: t0 9996471fcb7d3dff t1 9996471fcb7d3dff
t2 9000000001814000 t3 0000000000000001
May 24 21:10:24 loong0 kernel: t4 40000000fffff26f t5 90000000018cf310
t6 00000000fffff26f t7 90000000018b6eb8
May 24 21:10:24 loong0 kernel: t8 000000000000003f u0 0000000000000000
s9 0000000000000000 s0 90000001061cc8b0
May 24 21:10:24 loong0 kernel: s1 ffff800002d51000 s2 0000000000000000
s3 ffff800002624900 s4 900000011de4fc24
May 24 21:10:24 loong0 kernel: s5 900000010006d0d0 s6 00000000000003cf
s7 ffffffffffffffff s8 900000011f970fc8
May 24 21:10:24 loong0 kernel: ra: ffff800002ae2e04
drm_crtc_vblank_helper_get_vblank_timestamp_internal+0x3d4/0x450 [drm]
May 24 21:10:24 loong0 kernel: ERA: ffff800002ae2e04
drm_crtc_vblank_helper_get_vblank_timestamp_internal+0x3d4/0x450 [drm]
May 24 21:10:24 loong0 kernel: CRMD: 000000b0 (PLV0 -IE -DA +PG DACF=CC
DACM=CC -WE)
May 24 21:10:24 loong0 kernel: PRMD: 00000000 (PPLV0 -PIE -PWE)
May 24 21:10:24 loong0 kernel: EUEN: 00000000 (-FPE -SXE -ASXE -BTE)
May 24 21:10:24 loong0 kernel: ECFG: 00071c1d (LIE=0,2-4,10-12 VS=7)
May 24 21:10:24 loong0 kernel: ESTAT: 000c0000 [BRK] (IS= ECode=12
EsubCode=0)
May 24 21:10:24 loong0 kernel: PRID: 0014d000 (Loongson-64bit,
Loongson-3A6000)
May 24 21:10:24 loong0 kernel: CPU: 0 UID: 0 PID: 230 Comm: kworker/0:2
Not tainted 7.0.7+deb14-loong64 #1 PREEMPTLAZY Debian 7.0.7-1
May 24 21:10:24 loong0 kernel: Hardware name: Loongson
CTCI02LS3A6000C-K/CTCI02LS3A6000C-K, BIOS
Loongson-UDK2018-V4.0.05692-CTCI02202408 08/09/24 14:08:25
May 24 21:10:24 loong0 kernel: Workqueue: events
drm_fb_helper_damage_work [drm_kms_helper]
May 24 21:10:24 loong0 kernel: Stack : 900000011de4f788 0000000000000000
9000000000238c28 900000011de4c000
May 24 21:10:24 loong0 kernel: 900000011de4f760 900000011de4f768
0000000000000000 900000011de4f8a8
May 24 21:10:24 loong0 kernel: 900000011de4f8a0 900000011de4f8a0
900000011de4f788 0000000000000024
May 24 21:10:24 loong0 kernel: 0000000000000030 900000011de4f768
9996471fcb7d3dff 900000011c1d1580
May 24 21:10:24 loong0 kernel: 900000011de4c000 90000000015f6c10
00000000ffffefff 90000000018ceeb8
May 24 21:10:24 loong0 kernel: 0000000000000000 0000000000000000
000000087ac48000 0000000000000000
May 24 21:10:24 loong0 kernel: 0000000000000000 9000000001814000
0000000000000000 90000000015f6c10
May 24 21:10:24 loong0 kernel: 00000000000002eb 0000000000000009
00000000000003cf ffffffffffffffff
May 24 21:10:24 loong0 kernel: 900000011f970fc8 0000000000000000
9000000000238c44 00007ffff27506b4
May 24 21:10:24 loong0 kernel: 00000000000000b0 0000000000000000
0000000000000000 0000000000071c1d
May 24 21:10:24 loong0 kernel: ...
May 24 21:10:24 loong0 kernel: Call Trace:
May 24 21:10:24 loong0 kernel: [<9000000000238c44>] show_stack+0x64/0x190
May 24 21:10:24 loong0 kernel: [<9000000000230ef8>] dump_stack_lvl+0x70/0x9c
May 24 21:10:24 loong0 kernel: [<900000000028f670>] __warn+0xa0/0x210
May 24 21:10:24 loong0 kernel: [<900000000125c8e8>] __report_bug+0xa8/0x1c0
May 24 21:10:24 loong0 kernel: [<900000000125caf0>] report_bug+0x40/0xd0
May 24 21:10:24 loong0 kernel: [<900000000129f9b4>] do_bp+0x254/0x420
May 24 21:10:24 loong0 kernel: [<0000000000000000>] 0x0
May 24 21:10:24 loong0 kernel: [<ffff800002ae2e04>]
drm_crtc_vblank_helper_get_vblank_timestamp_internal+0x3d4/0x450 [drm]
May 24 21:10:24 loong0 kernel: [<ffff800002ae1014>]
drm_crtc_get_last_vbltimestamp+0x64/0xb0 [drm]
May 24 21:10:24 loong0 kernel: [<ffff800002ae20a0>]
drm_update_vblank_count+0xb0/0x480 [drm]
May 24 21:10:24 loong0 kernel: [<ffff800002ae2640>]
drm_vblank_enable+0x1d0/0x230 [drm]
May 24 21:10:24 loong0 kernel: [<ffff800002ae37ec>]
drm_vblank_get+0xdc/0x160 [drm]
May 24 21:10:24 loong0 kernel: [<ffff800002ae880c>]
drm_client_modeset_wait_for_vblank+0x4c/0xb0 [drm]
May 24 21:10:24 loong0 kernel: [<ffff800002738eb4>]
drm_fb_helper_damage_work+0x84/0x240 [drm_kms_helper]
May 24 21:10:24 loong0 kernel: [<90000000002c0354>]
process_one_work+0x1a4/0x640
May 24 21:10:24 loong0 kernel: [<90000000002c1330>]
worker_thread+0x1f0/0x3c0
May 24 21:10:24 loong0 kernel: [<90000000002cce68>] kthread+0x148/0x160
May 24 21:10:24 loong0 kernel: [<900000000129fe18>]
ret_from_kernel_thread+0x28/0x290
May 24 21:10:24 loong0 kernel: [<90000000002369e8>]
ret_from_kernel_thread_asm+0x10/0x88
May 24 21:10:24 loong0 kernel:
May 24 21:10:24 loong0 kernel: ---[ end trace 0000000000000000 ]---
May 24 21:10:24 loong0 kernel: loongson 0000:00:06.1: [drm] fb0:
loongsondrmfb frame buffer device
May 24 21:10:24 loong0 kernel: random: crng init done
May 24 21:10:24 loong0 kernel: device-mapper: core:
CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will
not be recorded in the IMA log.
May 24 21:10:24 loong0 kernel: device-mapper: uevent: version 1.0.3
May 24 21:10:24 loong0 kernel: device-mapper: ioctl: 4.50.0-ioctl
(2025-04-28) initialised: [email protected]
May 24 21:10:24 loong0 kernel: PM: Image not found (code -22)
May 24 21:10:24 loong0 kernel: EXT4-fs (dm-0): orphan cleanup on readonly fs
May 24 21:10:24 loong0 kernel: EXT4-fs (dm-0): mounted filesystem
0acd0998-bf0a-4e8b-a891-552bc0306488 ro with ordered data mode. Quota
mode: none.
```
My 3A6000 NUC host has two HDMI ports. When one port is connected to a
monitor, everything is normal (without the issue mentioned above).
However, when the other port is connected to a monitor, the issue
mentioned in the log above occurs. (Even though the host can still start
normally and enter the desktop environment after `systemd journal` printed.)
Hope you guys fix it soon.
Regards,
larryw3i
