You are not logged in.

#1 Yesterday 02:37:28

freeandeasy
Member
Registered: Yesterday
Posts: 4

Kernel Oops on AMD Framework shortly after boot

I'm running KDE 6.2.1 (wayland edition) and recently I have been getting this kernel oops on login:

WARNING: CPU: 2 PID: 1874 at drivers/gpu/drm/amd/amdgpu/../display/dc/dpp/dcn30/dcn30_dpp.c:534 dpp3_deferred_update+0x101/0x330 [amdgpu]
Modules linked in: rfcomm snd_seq_dummy snd_hrtimer uhid nf_conntrack_netbios_ns nf_conntrack_broadcast nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib ip_set qrtr bnep sunrpc binfmt_misc vfat fat snd_sof_amd_acp63 snd_sof_amd_vangogh snd_sof_amd_rembrandt snd_sof_amd_renoir snd_sof_amd_acp snd_sof_pci snd_sof_xtensa_dsp cdc_mbim cdc_wdm snd_sof intel_rapl_msr snd_hda_codec_realtek snd_sof_utils amd_atl snd_hda_codec_generic snd_pci_ps intel_rapl_common snd_amd_sdw_acpi snd_hda_scodec_component btusb mt7921e soundwire_amd edac_mce_amd btrtl soundwire_generic_allocation btintel mt7921_common soundwire_bus snd_hda_codec_hdmi btbcm mt792x_lib kvm_amd mt76_connac_lib btmtk cros_usbpd_charger leds_cros_ec cros_ec_hwmon cros_charge_control cros_ec_chardev cros_ec_sysfs led_class_multicolor gpio_cros_ec cros_usbpd_logger cros_usbpd_notify snd_soc_core mt76 snd_hda_intel bluetooth snd_compress cros_ec_dev spd5118 kvm snd_intel_dspcfg mac80211 snd_usb_audio cros_ec_lpcs ac97_bus snd_intel_sdw_acpi cros_ec
 snd_pcm_dmaengine snd_rpl_pci_acp6x snd_usbmidi_lib snd_hda_codec snd_acp_pci snd_ump snd_acp_legacy_common snd_rawmidi hid_sensor_als snd_hda_core libarc4 hid_sensor_trigger hid_sensor_iio_common snd_pci_acp6x mc snd_hwdep industrialio_triggered_buffer kfifo_buf snd_seq industrialio snd_seq_device cdc_ncm rapl wmi_bmof cfg80211 cdc_ether snd_pci_acp5x snd_pcm usbnet thunderbolt i2c_piix4 snd_rn_pci_acp3x snd_timer pcspkr snd_acp_config mii k10temp i2c_smbus snd_soc_acpi snd snd_pci_acp3x amd_pmf rfkill soundcore amdtee amd_sfh tee joydev platform_profile amd_pmc nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_masq nft_ct nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables loop nfnetlink zram dm_crypt uas usb_storage typec_displayport amdgpu amdxcp i2c_algo_bit drm_ttm_helper ttm crct10dif_pclmul drm_exec crc32_pclmul gpu_sched crc32c_intel nvme polyval_clmulni drm_suballoc_helper polyval_generic drm_buddy nvme_core drm_display_helper ghash_clmulni_intel video
 hid_multitouch sha512_ssse3 ucsi_acpi hid_sensor_hub sha256_ssse3 ccp typec_ucsi sha1_ssse3 cec sp5100_tco nvme_auth typec i2c_hid_acpi wmi i2c_hid ip6_tables ip_tables fuse i2c_dev
CPU: 2 UID: 0 PID: 1874 Comm: kworker/u64:15 Not tainted 6.11.3-arch1-1 #1
Hardware name: Framework Laptop 16 (AMD Ryzen 7040 Series)/FRANMZCP09, BIOS 03.04 07/09/2024
Workqueue: events_unbound commit_work
RIP: 0010:dpp3_deferred_update+0x101/0x330 [amdgpu]
Code: 83 78 e1 00 00 0f b6 90 a8 02 00 00 48 8b 83 70 e1 00 00 8b b0 78 04 00 00 e8 3b 21 1b 00 8b 74 24 04 85 f6 0f 84 5d 01 00 00 <0f> 0b 0f b6 83 48 96 00 00 83 e0 f7 88 83 48 96 00 00 a8 01 0f 84
RSP: 0018:ffffb59685387b80 EFLAGS: 00010202
RAX: 0000000000000066 RBX: ffff96c9939e0000 RCX: 0000000000000004
RDX: 0000000000000000 RSI: 0000000000000002 RDI: ffff96c99d580000
RBP: 0000000000000000 R08: ffffb59685387b84 R09: ffffb59685387bb8
R10: 0000000000000000 R11: 0000000000000000 R12: ffff96ca44540000
R13: ffff96c99e000000 R14: 0000000000000000 R15: ffff96c9939e0000
FS:  0000000000000000(0000) GS:ffff96d001b00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f685c3db378 CR3: 000000043642a000 CR4: 0000000000f50ef0
PKRU: 55555554
Call Trace:
 <TASK>
 ? dpp3_deferred_update+0x101/0x330 [amdgpu]
 ? __warn.cold+0x8e/0xe8
 ? dpp3_deferred_update+0x101/0x330 [amdgpu]
 ? report_bug+0xff/0x140
 ? handle_bug+0x3c/0x80
 ? exc_invalid_op+0x17/0x70
 ? asm_exc_invalid_op+0x1a/0x20
 ? dpp3_deferred_update+0x101/0x330 [amdgpu]
 ? __pfx_dpp3_deferred_update+0x10/0x10 [amdgpu]
 dc_post_update_surfaces_to_stream+0x223/0x3d0 [amdgpu]
 amdgpu_dm_atomic_commit_tail+0x2fc5/0x4430 [amdgpu]
 commit_tail+0xac/0x160
 ? srso_alias_return_thunk+0x5/0xfbef5
 process_one_work+0x176/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

This happens regardless of whether I use the linux or linux-lts packages.

Anybody else experiencing this issue? Could it be a firmware issue?

Offline

#2 Yesterday 08:16:51

yataro
Member
Registered: 2024-03-09
Posts: 74

Re: Kernel Oops on AMD Framework shortly after boot

Can you check the GPU temperature during system startup? Could be overheating

Offline

#3 Yesterday 15:28:11

freeandeasy
Member
Registered: Yesterday
Posts: 4

Re: Kernel Oops on AMD Framework shortly after boot

yataro wrote:

Can you check the GPU temperature during system startup? Could be overheating

GPU temperatures are all normal.

Booted into a distro with kernel 6.1 and GNOME and could not reproduce the kernel oops. So the issue looks like it's between the Arch kernels and KDE...

Offline

#4 Yesterday 15:32:15

freeandeasy
Member
Registered: Yesterday
Posts: 4

Re: Kernel Oops on AMD Framework shortly after boot

Update: I tried turning off Variable Refresh Rate in KDE settings and the oops no longer happens. This may be the issue, going to dig further into why this is happening...

Offline

#5 Today 00:46:58

freeandeasy
Member
Registered: Yesterday
Posts: 4

Re: Kernel Oops on AMD Framework shortly after boot

freeandeasy wrote:

Update: I tried turning off Variable Refresh Rate in KDE settings and the oops no longer happens. This may be the issue, going to dig further into why this is happening...

Okay, this was a red herring. The oops is back again. At this point, I'm kind of stumped.

Offline

Board footer

Powered by FluxBB