Plugging in monitor crashes GPU

Using a displayport to VGA adapter, connecting to a Hitachi Starboard (pi-500) and on connect my system hangs. Dont know whats happening.

Jan 24 16:04:04 2xeon kernel: ------------[ cut here ]------------
Jan 24 16:04:04 2xeon kernel: memmove: detected field-spanning write (size 4224) of single field "sink->dc_edid.raw_edid" at drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_helpers.c:932 (size 2048)
Jan 24 16:04:04 2xeon kernel: WARNING: CPU: 74 PID: 1040 at drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_helpers.c:932 dm_helpers_read_local_edid+0x239/0x280 [amdgpu]
Jan 24 16:04:04 2xeon kernel: Modules linked in: mptcp_diag tcp_diag udp_diag raw_diag inet_diag unix_diag rfcomm snd_seq_dummy snd_hrtimer snd_seq ccm tun af_packet nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_rej>
Jan 24 16:04:04 2xeon kernel:  uvc intel_pmc_bxt videobuf2_memops snd_hda_core snd_rawmidi iTCO_vendor_support videobuf2_v4l2 cfg80211 snd_hwdep snd_seq_device videobuf2_common bluetooth kvm r8169 snd_pcm videodev aiptek snd_timer real>
Jan 24 16:04:04 2xeon kernel: CPU: 74 UID: 0 PID: 1040 Comm: kworker/74:1H Not tainted 6.12.10-1-default #1 openSUSE Tumbleweed 92f8b4bfae9b116207d57ef1371c30c09d434808
Jan 24 16:04:04 2xeon kernel: Hardware name: INTEL X99/X99, BIOS 5.11 03/06/2024
Jan 24 16:04:04 2xeon kernel: Workqueue: events_highpri dm_irq_work_func [amdgpu]
Jan 24 16:04:04 2xeon kernel: RIP: 0010:dm_helpers_read_local_edid+0x239/0x280 [amdgpu]
Jan 24 16:04:04 2xeon kernel: Code: 0f 85 8c fe ff ff b9 00 08 00 00 48 c7 c2 88 72 80 c1 48 c7 c7 f8 72 80 c1 48 89 74 24 08 c6 05 28 3f 3f 00 01 e8 57 c8 bc d5 <0f> 0b 48 8b 74 24 08 e9 5c fe ff ff 41 80 bd 70 07 00 00 00 41 b8
Jan 24 16:04:04 2xeon kernel: RSP: 0000:ffffb63bc241fc08 EFLAGS: 00210286
Jan 24 16:04:04 2xeon kernel: RAX: 0000000000000000 RBX: ffff91ba6edb2000 RCX: 0000000000000027
Jan 24 16:04:04 2xeon kernel: RDX: ffff91c97f727848 RSI: 0000000000000001 RDI: ffff91c97f727840
Jan 24 16:04:04 2xeon kernel: RBP: ffff91ba4d628800 R08: 0000000000000000 R09: ffffb63bc241fa98
Jan 24 16:04:04 2xeon kernel: R10: ffff91c97cafffa8 R11: 0000000000000003 R12: 0000000000000003
Jan 24 16:04:04 2xeon kernel: R13: ffff91ba4277a000 R14: ffff91ba4277ad58 R15: ffff91bb8768e000
Jan 24 16:04:04 2xeon kernel: FS:  0000000000000000(0000) GS:ffff91c97f700000(0000) knlGS:0000000000000000
Jan 24 16:04:04 2xeon kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jan 24 16:04:04 2xeon kernel: CR2: 00000000c9dfcc28 CR3: 0000000f1c838004 CR4: 00000000003726f0
Jan 24 16:04:04 2xeon kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Jan 24 16:04:04 2xeon kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Jan 24 16:04:04 2xeon kernel: Call Trace:
Jan 24 16:04:04 2xeon kernel:  <TASK>
Jan 24 16:04:04 2xeon kernel:  ? dm_helpers_read_local_edid+0x239/0x280 [amdgpu 145e705fb20fed36f5fe6263fd32206135db95c0]
Jan 24 16:04:04 2xeon kernel:  ? __warn.cold+0x93/0xf7
Jan 24 16:04:04 2xeon kernel:  ? dm_helpers_read_local_edid+0x239/0x280 [amdgpu 145e705fb20fed36f5fe6263fd32206135db95c0]
Jan 24 16:04:04 2xeon kernel:  ? report_bug+0xff/0x140
Jan 24 16:04:04 2xeon kernel:  ? prb_read_valid+0x1b/0x30
Jan 24 16:04:04 2xeon kernel:  ? handle_bug+0x58/0x90
Jan 24 16:04:04 2xeon kernel:  ? exc_invalid_op+0x17/0x70
Jan 24 16:04:04 2xeon kernel:  ? asm_exc_invalid_op+0x1a/0x20
Jan 24 16:04:04 2xeon kernel:  ? dm_helpers_read_local_edid+0x239/0x280 [amdgpu 145e705fb20fed36f5fe6263fd32206135db95c0]
Jan 24 16:04:04 2xeon kernel:  ? dm_helpers_read_local_edid+0x239/0x280 [amdgpu 145e705fb20fed36f5fe6263fd32206135db95c0]
Jan 24 16:04:04 2xeon kernel:  detect_link_and_local_sink+0x4e7/0x1050 [amdgpu 145e705fb20fed36f5fe6263fd32206135db95c0]
Jan 24 16:04:04 2xeon kernel:  ? dm_write_reg_func+0x47/0xb0 [amdgpu 145e705fb20fed36f5fe6263fd32206135db95c0]
Jan 24 16:04:04 2xeon kernel:  ? dm_write_reg_func+0x47/0xb0 [amdgpu 145e705fb20fed36f5fe6263fd32206135db95c0]
Jan 24 16:04:04 2xeon kernel:  ? generic_reg_update_ex+0x144/0x280 [amdgpu 145e705fb20fed36f5fe6263fd32206135db95c0]
Jan 24 16:04:04 2xeon kernel:  link_detect+0x38/0x4e0 [amdgpu 145e705fb20fed36f5fe6263fd32206135db95c0]
Jan 24 16:04:04 2xeon kernel:  ? dal_gpio_destroy_irq+0x25/0x40 [amdgpu 145e705fb20fed36f5fe6263fd32206135db95c0]
Jan 24 16:04:04 2xeon kernel:  ? query_hpd_status+0x6e/0xa0 [amdgpu 145e705fb20fed36f5fe6263fd32206135db95c0]
Jan 24 16:04:04 2xeon kernel:  handle_hpd_irq_helper+0x116/0x190 [amdgpu 145e705fb20fed36f5fe6263fd32206135db95c0]
Jan 24 16:04:04 2xeon kernel:  process_one_work+0x16b/0x320
Jan 24 16:04:04 2xeon kernel:  worker_thread+0x2da/0x410
Jan 24 16:04:04 2xeon kernel:  ? __pfx_worker_thread+0x10/0x10
Jan 24 16:04:04 2xeon kernel:  kthread+0xd2/0x100
Jan 24 16:04:04 2xeon kernel:  ? __pfx_kthread+0x10/0x10
Jan 24 16:04:04 2xeon kernel:  ret_from_fork+0x34/0x50
Jan 24 16:04:04 2xeon kernel:  ? __pfx_kthread+0x10/0x10
Jan 24 16:04:04 2xeon kernel:  ret_from_fork_asm+0x1a/0x30
Jan 24 16:04:04 2xeon kernel:  </TASK>
Jan 24 16:04:04 2xeon kernel: ---[ end trace 0000000000000000 ]---

A bug report is likely the best way forward here. FWIW, I found a similar Arch Linux topic where it was established that a bad AMD firmware release was causing the issue. Maybe you’re encountering the same tpye of issue here.

So I tried the monitor in question on my laptop with journalctl -xf and I got some non-fatal EDID errors (there were others but the only different part was the the block number)

Jan 24 20:03:20 indestructable kernel: EDID block 1 (tag 0x1e) checksum is invalid, remainder is 132

Also where do I make a bug report?

Guidance:
https://en.opensuse.org/openSUSE:Submitting_bug_reports

Bugzilla:
https://bugzilla.opensuse.org/index.cgi

Checking the driver version:
You can verify the current version of the amdgpu driver with the following command:

modinfo amdgpu | grep version

This command will display information about the amdgpu kernel module, specifically filtering for lines containing “version”. It will show you the version number of the amdgpu driver currently installed on your system.

Changing to a lower or higher kernel version could potentially solve the problem.

https://bugzilla.opensuse.org/show_bug.cgi?id=1236415

Try booting without radeon.si_support=0 amdgpu.si_support=1.

R9 390 is GCN#2. .si_support= is only for GCN#1, so probably is ignored, but that disregard could be broken. Driver maintenance for older GPU models too often doesn’t seem to get very good (any?) QA, especially involving adapter use. You may want to consider switching to a display or cable not requiring, or cable not being, an adapter.

Well, its the adapter, since when I plug in the adapter to my laptop (via its matching USB-C dock) it hangs and is unresponsive until i unplug it. But only when I use the adapter, plugging it in directly to the VGA port on my laptop (or the dock) does not cause any issues, but a mere warning in journalctl.

Not surprised to read this - always good to eliminate cables/hardware from the equation first where applicable.

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.