[Bug 119211] amdgpu disables fan by default
https://bugzilla.kernel.org/show_bug.cgi?id=119211 Stas Sergeev (st...@yandex.ru) changed: What|Removed |Added Kernel Version|4.5.5 |6.7.7 --- Comment #18 from Stas Sergeev (st...@yandex.ru) --- I figured out something very interesting regarding this bug. Writing 2 to pwm1_enable causes the fan to rotate for about 10 seconds. Note that the old value of pwm1_enable is also 2, so it doesn't change, but the mere fact of writing has an effect! And this is not all! Now if you periodically READ from pwm1, then the fan doesn't stop! I can do: while :; do cat /sys/class/hwmon/hwmon0/pwm1; sleep 1; done And with this, the fan keeps rotating forever! But if you stop that script for something like 10 seconds, then the fan stops and pwm1 reads always return 0. You need to start again by writing 2 to pwm1_enable (even if there is already 2!), and quickly start reading from pwm1, and you have your fan finally rotating. :) A bit of a hand-written fancontrol script. :) Alex Deucher can you make any sense out of that? -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218617] Linux Kernel Bug Report: "Scheduling while atomic" Kernel Panic and System Freeze on NVIDIA RTX 2000 Ada Generation Laptop GPU
https://bugzilla.kernel.org/show_bug.cgi?id=218617 --- Comment #2 from Sarah S. (sarah.salzst...@gmail.com) --- Thank you for letting me know! Sincerely, Sarah S. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218617] Linux Kernel Bug Report: "Scheduling while atomic" Kernel Panic and System Freeze on NVIDIA RTX 2000 Ada Generation Laptop GPU
https://bugzilla.kernel.org/show_bug.cgi?id=218617 Artem S. Tashkinov (a...@gmx.com) changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WILL_NOT_FIX --- Comment #1 from Artem S. Tashkinov (a...@gmx.com) --- If it's an open source NVIDIA module, you report your bug here: https://github.com/NVIDIA/open-gpu-kernel-modules/issues If it's a closed source NVIDIA driver, you report your bug here: https://forums.developer.nvidia.com/c/gpu-graphics/linux/148 Unfortunately kernel developer can't and won't help you with out of tree modules. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218617] New: Linux Kernel Bug Report: "Scheduling while atomic" Kernel Panic and System Freeze on NVIDIA RTX 2000 Ada Generation Laptop GPU
https://bugzilla.kernel.org/show_bug.cgi?id=218617 Bug ID: 218617 Summary: Linux Kernel Bug Report: "Scheduling while atomic" Kernel Panic and System Freeze on NVIDIA RTX 2000 Ada Generation Laptop GPU Product: Drivers Version: 2.5 Hardware: Intel OS: Linux Status: NEW Severity: blocking Priority: P3 Component: Video(DRI - non Intel) Assignee: drivers_video-...@kernel-bugs.osdl.org Reporter: sarah.salzst...@gmail.com Regression: No Created attachment 306013 --> https://bugzilla.kernel.org/attachment.cgi?id=306013=edit Relevant dmesg output Dear Linux Kernel Development Team, I am writing to report a critical issue I have been encountering with the Linux kernel, specifically related to my NVIDIA RTX 2000 Ada Generation Laptop GPU, installed in a Lenovo ThinkPad P1 Gen 6. The problem manifests as a "scheduling while atomic" kernel bug, followed by a complete system freeze. Description of the Problem: Randomly during system operation, the kernel gives the error message "scheduling while atomic". This error occurs seemingly at random intervals and under varying system loads. Subsequently, at some point, the system becomes unresponsive and necessitates a hard reboot to regain functionality. Steps to Reproduce: - The error occurs randomly during system operation. - The system becomes unresponsive, leading to a complete freeze. System Information: - GPU: NVIDIA Corporation AD107GLM [RTX 2000 Ada Generation Laptop GPU] (rev a1) Linux Distribution: Gentoo Linux - Kernel Version: 6.8.1 (Also affects kernel versions 6.7.x, 6.6.x, and 6.1.x) Additional Information: The issue persists across multiple kernel versions, indicating it is not specific to a particular kernel release. I have examined the system logs and have identified the occurrence of the "scheduling while atomic" error as the primary issue leading to the kernel panic and subsequent system freeze. No specific system activity or workload triggers the error; it happens seemingly at random. I have ensured that the GPU drivers are up to date and have attempted to reinstall them without resolving the issue, but no matter which NVIDIA driver version I install, the bug consistently persists. Attached Logs: Attached the relevant portion of the dmesg output showing the BUG. This issue severely affects the usability and stability of my system, and I kindly request your assistance in resolving it promptly. If there are any additional diagnostic steps or information required from my end, please let me know, and I will gladly provide it. Thank you for your attention to this matter. Sincerely, Sarah S. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218569] Early KMS Resolution Issue on MST dock connected 4K Monitor
https://bugzilla.kernel.org/show_bug.cgi?id=218569 --- Comment #2 from Emre (ereno...@gmail.com) --- OK, I don't have windows on this laptop. I can try another windows laptop but that has thunderbolt and I dont know if behavior would be the same in windows. I had an impression this was sth to do with MST rather than amdgpu since amdgpu can drive hdmi port just fine, but anyway I will open a bug report in the drm as well. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218569] Early KMS Resolution Issue on MST dock connected 4K Monitor
https://bugzilla.kernel.org/show_bug.cgi?id=218569 Artem S. Tashkinov (a...@gmx.com) changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |ANSWERED --- Comment #1 from Artem S. Tashkinov (a...@gmx.com) --- 1. Would be great if you tested Windows and confirmed it's not an issue there. 2. One you've done that, probably it's worth posting here: https://gitlab.freedesktop.org/drm/amd/-/issues Pretty much no one is subscribed to this bugzilla component. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218569] New: Early KMS Resolution Issue on MST dock connected 4K Monitor
https://bugzilla.kernel.org/show_bug.cgi?id=218569 Bug ID: 218569 Summary: Early KMS Resolution Issue on MST dock connected 4K Monitor Product: Drivers Version: 2.5 Hardware: All OS: Linux Status: NEW Severity: normal Priority: P3 Component: Video(DRI - non Intel) Assignee: drivers_video-...@kernel-bugs.osdl.org Reporter: ereno...@gmail.com Regression: No My laptop, a Thinkpad P14s Gen2 AMD has two usb-c and an hdmi port. I use one USB-C port to connect to Thinkpad Dock Type 40B0 which has an internal MST hub. The Dock has 2xDP connectors and 1xHDMI. The dock is connected to a 4K TV (LG C2), using a DP to HDMI cable. The system works fine when Wayland or Xorg starts and displays 3840x2160@60hz. I noticed a lot of monitor sync loss when changing modes. At UEFI boot it's at 1280x1024, then at kernel boot it switches to 1920x1080 and monitor loses signal during this transition, then SDDM or GDM starts it switches to 3840x2160, and when I login to KDE, it loses signal again for a few seconds then shows the desktop again at 3840x2160@60. So this is a nuisance for losing monitor sync but not effecting normal operation. I then tried to use the HDMI port on the laptop. I unplugged the cable from the dock and plugged a separate HDMI cable directly to the port on the Laptop. Then I noticed it was fully smooth. After UEFI, mode immediately switched to 3840x2160@60 with early kms and then SDDM launched without losing any signal. Then logging into desktop also is smooth and does not lose any signal. So I concluded something is wrong when one uses a Monitor connected to a Dock with MST Hub function, connected to a USB-C port on the laptop (no-Thunderbolt). Problems are: 1) When using the MST docking station, early kms does not switch to native 4K resolution (3840x2160@60hz). I tried feeding an EDID at kernel command line, it did not work. 2) Monitor loses signal sync when switching modes when using Dock. Does not happen when using HDMI port on laptop. This does not happen if I use a simpler usb-c hub without MST support. So a simple usb-c hub with one HDMI port out works fine. Problematic setup: Laptop --usb-c-- dock_with_mst -- dp2hdmi cable -- hdmi_port_on_4K_Monitor Working setup: Laptop -- hdmi -- hdmi_port_on_4K_Monitor Kernel Version: Linux: 6.7.8-arch1-1 bug reported to Arch as well but I'm directed to report upstream: https://gitlab.archlinux.org/archlinux/packaging/packages/linux/-/issues/32 Steps to reproduce: 1) Use any recent kernel and use any docking station with an MST hub. 2) Connect a monitor to the docking station. 3) Connect Dock to the laptop using USB-C port (no thunderbolt support, ie amd laptop) 4) Use early kms by adding amdgpu to mkinitcpio.conf modules section 5) Watch monitor resolution using Monitor functions while booting -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218549] [REGRESSION] in 6.7.5, amdgpu: amdgpu_device_ip_resume failed (-62).
https://bugzilla.kernel.org/show_bug.cgi?id=218549 Alexander Goomenyuk (emerg.reanima...@gmail.com) changed: What|Removed |Added Status|RESOLVED|CLOSED --- Comment #5 from Alexander Goomenyuk (emerg.reanima...@gmail.com) --- @Artem S. Tashkinov Thanks for quick response! Just for sake of completeness, here is the link to corresponding issue: https://gitlab.freedesktop.org/drm/amd/-/issues/3230 -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218549] [REGRESSION] in 6.7.5, amdgpu: amdgpu_device_ip_resume failed (-62).
https://bugzilla.kernel.org/show_bug.cgi?id=218549 Artem S. Tashkinov (a...@gmx.com) changed: What|Removed |Added Status|NEW |RESOLVED Kernel Version||6.7.5 Resolution|--- |ANSWERED Regression|No |Yes --- Comment #4 from Artem S. Tashkinov (a...@gmx.com) --- amdgpu bug tracker is here: https://gitlab.freedesktop.org/drm/amd/-/issues Please post there. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218549] [REGRESSION] in 6.7.5, amdgpu: amdgpu_device_ip_resume failed (-62).
https://bugzilla.kernel.org/show_bug.cgi?id=218549 --- Comment #3 from Alexander Goomenyuk (emerg.reanima...@gmail.com) --- Created attachment 305947 --> https://bugzilla.kernel.org/attachment.cgi?id=305947=edit modinfo amdgpu, 6.7.5, failure -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218549] [REGRESSION] in 6.7.5, amdgpu: amdgpu_device_ip_resume failed (-62).
https://bugzilla.kernel.org/show_bug.cgi?id=218549 --- Comment #2 from Alexander Goomenyuk (emerg.reanima...@gmail.com) --- Created attachment 305946 --> https://bugzilla.kernel.org/attachment.cgi?id=305946=edit modinfo amdgpu, 6.7.3, working -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218549] [REGRESSION] in 6.7.5, amdgpu: amdgpu_device_ip_resume failed (-62).
https://bugzilla.kernel.org/show_bug.cgi?id=218549 --- Comment #1 from Alexander Goomenyuk (emerg.reanima...@gmail.com) --- Created attachment 305945 --> https://bugzilla.kernel.org/attachment.cgi?id=305945=edit dmesg 6.7.3, working -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218549] New: [REGRESSION] in 6.7.5, amdgpu: amdgpu_device_ip_resume failed (-62).
https://bugzilla.kernel.org/show_bug.cgi?id=218549 Bug ID: 218549 Summary: [REGRESSION] in 6.7.5, amdgpu: amdgpu_device_ip_resume failed (-62). Product: Drivers Version: 2.5 Hardware: All OS: Linux Status: NEW Severity: normal Priority: P3 Component: Video(DRI - non Intel) Assignee: drivers_video-...@kernel-bugs.osdl.org Reporter: emerg.reanima...@gmail.com Regression: No Created attachment 305944 --> https://bugzilla.kernel.org/attachment.cgi?id=305944=edit dmesg 6.7.5, failure AMDGPU initialisation fails at boot time. --- This is a regression in 6.7.5 and 6.7.6 comparing to 6.7.3; --- # dmesg 6.7.3 [ 176.620376] amdgpu :06:00.0: amdgpu: RAS: optional ras ta ucode is not available [ 176.626377] amdgpu :06:00.0: amdgpu: RAP: optional rap ta ucode is not available [ 176.626379] amdgpu :06:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available [ 176.626381] amdgpu :06:00.0: amdgpu: SMU is resuming... [ 176.629079] amdgpu :06:00.0: amdgpu: SMU is resumed successfully! # demsg 6.7.5 [ 100.704263] amdgpu :06:00.0: amdgpu: RAS: optional ras ta ucode is not available [ 100.716580] amdgpu :06:00.0: amdgpu: RAP: optional rap ta ucode is not available [ 100.716584] amdgpu :06:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available [ 100.716589] amdgpu :06:00.0: amdgpu: SMU is resuming... [ 104.056259] amdgpu :06:00.0: amdgpu: SMU: I'm not done with your previous command: SMN_C2PMSG_66:0x0006 SMN_C2PMSG_82:0x [ 104.056263] amdgpu :06:00.0: amdgpu: Failed to enable requested dpm features! [ 104.056264] amdgpu :06:00.0: amdgpu: Failed to setup smc hw! [ 104.056265] [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block failed -62 [ 104.056623] amdgpu :06:00.0: amdgpu: amdgpu_device_ip_resume failed (-62). -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218483] Blank screen on Cezanne/Barcelo APU with amdgpu.seamless=1
https://bugzilla.kernel.org/show_bug.cgi?id=218483 Artem S. Tashkinov (a...@gmx.com) changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |ANSWERED --- Comment #1 from Artem S. Tashkinov (a...@gmx.com) --- please report here instead: https://gitlab.freedesktop.org/drm/amd/-/issues -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218483] Blank screen on Cezanne/Barcelo APU with amdgpu.seamless=1
https://bugzilla.kernel.org/show_bug.cgi?id=218483 Luya Tshimbalanga (l...@fedoraproject.org) changed: What|Removed |Added Kernel Version||6.7.4 -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218483] New: Blank screen on Cezanne/Barcelo APU with amdgpu.seamless=1
https://bugzilla.kernel.org/show_bug.cgi?id=218483 Bug ID: 218483 Summary: Blank screen on Cezanne/Barcelo APU with amdgpu.seamless=1 Product: Drivers Version: 2.5 Hardware: AMD OS: Linux Status: NEW Severity: normal Priority: P3 Component: Video(DRI - non Intel) Assignee: drivers_video-...@kernel-bugs.osdl.org Reporter: l...@fedoraproject.org Regression: No Created attachment 305856 --> https://bugzilla.kernel.org/attachment.cgi?id=305856=edit Boot report The screen goes blank when enabling "amdgpu.seamless=1" for a seamless boot as tested on Cezanne/Barcelo APU as found on laptops like Dell Inspiron 14 7425 with the following error: "Feb 11 13:43:37 kernel: amdgpu :04:00.0: [drm] *ERROR* [CRTC:73:crtc-0] flip_done timed out" Tested on kernel 6.7.4-200 -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 213145] AMDGPU resets, timesout and crashes after "*ERROR* Waiting for fences timed out!"
https://bugzilla.kernel.org/show_bug.cgi?id=213145 fichterfran...@gmail.com changed: What|Removed |Added CC||fichterfran...@gmail.com --- Comment #34 from fichterfran...@gmail.com --- Hello, With my mini pc ryzen 5 6600H (six core) processor : 11 vendor_id : AuthenticAMD cpu family : 25 model : 68 model name : AMD Ryzen 5 6600H with Radeon Graphics stepping: 1 microcode : 0xa404102 cpu MHz : 400.000 cache size : 512 KB physical id : 0 siblings: 12 core id : 5 cpu cores : 6 apicid : 11 initial apicid : 11 fpu : yes fpu_exception : yes cpuid level : 16 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid aperfmperf rapl pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 x2apic movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_llc mwaitx cpb cat_l3 cdp_l3 hw_pstate ssbd mba ibrs ibpb stibp vmmcall fsgsbase bmi1 avx2 smep bmi2 erms invpcid cqm rdt_a rdseed adx smap clflushopt clwb sha_ni xsaveopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local clzero irperf xsaveerptr rdpru wbnoinvd cppc arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif v_spec_ctrl umip pku ospke vaes vpclmulqdq rdpid overflow_recov succor smca fsrm bugs: sysret_ss_attrs spectre_v1 spectre_v2 spec_store_bypass srso bogomips: 6587.56 TLB size: 2560 4K pages clflush size: 64 cache_alignment : 64 address sizes : 48 bits physical, 48 bits virtual power management: ts ttp tm hwpstate cpb eff_freq_ro [13] [14] cat /etc/debian_version trixie/sid cat /etc/debian_version trixie/sid Feb 3 21:38:50 debser kernel: [drm] PCIE GART of 1024M enabled (table at 0x00F4FFC0). Feb 3 21:38:50 debser kernel: [drm] PSP is resuming... Feb 3 21:38:50 debser kernel: [drm] reserve 0xa0 from 0xf4fe00 for PSP TMR Feb 3 21:38:51 debser kernel: [drm] DMUB hardware initialized: version=0x043C Feb 3 21:38:51 debser kernel: [drm] kiq ring mec 2 pipe 1 q 0 Feb 3 21:38:51 debser kernel: [drm] VCN decode and encode initialized successfully(under DPG Mode). Feb 3 21:38:51 debser kernel: [drm] JPEG decode initialized successfully. Feb 3 21:38:51 debser kernel: [drm] Skip scheduling IBs! Feb 3 21:38:51 debser kernel: [drm] Skip scheduling IBs! Feb 3 21:38:51 debser kernel: [drm] Skip scheduling IBs! Feb 3 21:38:51 debser kernel: [drm] Skip scheduling IBs! Feb 3 21:38:51 debser kernel: [drm] Skip scheduling IBs! Feb 3 21:38:51 debser kernel: [drm] Skip scheduling IBs! Feb 3 21:38:51 debser kernel: [drm] Skip scheduling IBs! Feb 3 21:38:51 debser kernel: [drm] Skip scheduling IBs! Feb 3 21:38:51 debser kernel: [drm] Skip scheduling IBs! Feb 3 21:38:51 debser kernel: [drm] Skip scheduling IBs! Feb 3 21:38:51 debser kernel: [drm] Skip scheduling IBs! Feb 3 21:38:51 debser kernel: [drm] Skip scheduling IBs! Feb 3 21:38:51 debser kernel: [drm] Skip scheduling IBs! Feb 3 21:38:51 debser kernel: [drm] Skip scheduling IBs! Feb 3 21:38:51 debser kernel: [drm] Skip scheduling IBs! Feb 3 21:38:51 debser kernel: [drm] Skip scheduling IBs! Feb 3 21:38:51 debser kernel: [drm] Skip scheduling IBs! Feb 3 21:38:51 debser kernel: [drm] Skip scheduling IBs! Feb 3 21:38:51 debser kernel: [drm] Skip Feb 3 21:38:50 debser kernel: [drm] PCIE GART of 1024M enabled (table at 0x00F4FFC0). Feb 3 21:38:50 debser kernel: [drm] PSP is resuming... Feb 3 21:38:50 debser kernel: [drm] reserve 0xa0 from 0xf4fe00 for PSP TMR Feb 3 21:38:51 debser kernel: [drm] DMUB hardware initialized: version=0x043C Feb 3 21:38:51 debser kernel: [drm] kiq ring mec 2 pipe 1 q 0 Feb 3 21:38:51 debser kernel: [drm] VCN decode and encode initialized successfully(under DPG Mode). Feb 3 21:38:51 debser kernel: [drm] JPEG decode initialized successfully. Feb 3 21:38:51 debser kernel: [drm] Skip scheduling IBs! Feb 3 21:38:51 debser kernel: [drm] Skip scheduling IBs! Feb 3 21:38:51 debser kernel: [drm] Skip scheduling IBs! Feb 3 21:38:51 debser kernel: [drm] Skip scheduling IBs! Feb 3 21:38:51 debser kernel: [drm] Skip scheduling IBs! Feb 3 21:38:51 debser kernel: [drm] Skip scheduling IBs! Feb 3 21:38:51 debser kernel: [drm] Skip scheduling IBs! Feb 3 21:38:51 debser kernel: [drm] Skip scheduling IBs! Feb 3 21:38:51 debser kernel: [drm] Skip scheduling IBs! Feb 3 21:38:51 debser kernel: [drm] Skip scheduling IBs! Feb 3
[Bug 218435] UBSAN: array-index-out-of-bounds in radeon_atombios.c:2620:43
https://bugzilla.kernel.org/show_bug.cgi?id=218435 Artem S. Tashkinov (a...@gmx.com) changed: What|Removed |Added Status|NEW |RESOLVED Kernel Version||6.5.0-15-generic ||#15~22.04.1-Ubuntu Resolution|--- |WILL_NOT_FIX --- Comment #2 from Artem S. Tashkinov (a...@gmx.com) --- This kernel release is no longer supported. Take it to your vendor: https://bugs.launchpad.net/ubuntu -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218435] UBSAN: array-index-out-of-bounds in radeon_atombios.c:2620:43
https://bugzilla.kernel.org/show_bug.cgi?id=218435 --- Comment #1 from Sergey Belyashov (sergey.belyas...@gmail.com) --- Created attachment 305790 --> https://bugzilla.kernel.org/attachment.cgi?id=305790=edit dmesg output -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218435] New: UBSAN: array-index-out-of-bounds in radeon_atombios.c:2620:43
https://bugzilla.kernel.org/show_bug.cgi?id=218435 Bug ID: 218435 Summary: UBSAN: array-index-out-of-bounds in radeon_atombios.c:2620:43 Product: Drivers Version: 2.5 Hardware: All OS: Linux Status: NEW Severity: normal Priority: P3 Component: Video(DRI - non Intel) Assignee: drivers_video-...@kernel-bugs.osdl.org Reporter: sergey.belyas...@gmail.com Regression: No Created attachment 305789 --> https://bugzilla.kernel.org/attachment.cgi?id=305789=edit Kernel config Part of kernel log: ... [2.391350] ATOM BIOS: 87829JEB.SGH [2.391375] radeon :01:00.0: VRAM: 1024M 0x - 0x3FFF (1024M used) [2.391379] radeon :01:00.0: GTT: 1024M 0x4000 - 0x7FFF [2.391383] [drm] Detected VRAM RAM=1024M, BAR=256M [2.391384] [drm] RAM width 128bits DDR [2.391471] [drm] radeon: 1024M of VRAM memory ready [2.391474] [drm] radeon: 1024M of GTT memory ready. [2.391487] [drm] Loading RV730 Microcode [2.391827] [drm] Internal thermal controller with fan control [2.391829] [2.391835] fbcon: Taking over console [2.391840] UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-BV4m5T/linux-hwe-6.5-6.5.0/drivers/gpu/drm/radeon/radeon_atombios.c:2620:43 [2.391847] index 1 is out of range for type 'UCHAR [1]' [2.391850] CPU: 0 PID: 113 Comm: systemd-udevd Tainted: G I 6.5.0-15-generic #15~22.04.1-Ubuntu [2.391853] Hardware name: Dell Inc. OptiPlex 380 /0HN7XN, BIOS A07 06/13/2012 [2.391855] Call Trace: [2.391857] [2.391861] dump_stack_lvl+0x48/0x70 [2.391868] dump_stack+0x10/0x20 [2.391871] __ubsan_handle_out_of_bounds+0xc6/0x110 [2.391877] radeon_atombios_parse_power_table_4_5+0x3c6/0x3e0 [radeon] [2.392018] radeon_atombios_get_power_modes+0x205/0x210 [radeon] [2.392099] radeon_pm_init_dpm+0x8e/0x2f0 [radeon] [2.392202] radeon_pm_init+0xdf/0x120 [radeon] [2.392304] rv770_init+0x1fa/0x3d0 [radeon] [2.392406] radeon_device_init+0x57e/0xaf0 [radeon] [2.392485] radeon_driver_load_kms+0xcc/0x300 [radeon] [2.392565] drm_dev_register+0x10e/0x240 [drm] [2.392652] radeon_pci_probe+0xec/0x180 [radeon] [2.392730] local_pci_probe+0x47/0xb0 [2.392734] pci_call_probe+0x55/0x190 [2.392737] pci_device_probe+0x84/0x120 [2.392740] really_probe+0x1cc/0x430 [2.392743] __driver_probe_device+0x8c/0x190 [2.392746] driver_probe_device+0x24/0xd0 [2.392748] __driver_attach+0x10b/0x210 [2.392750] ? __pfx___driver_attach+0x10/0x10 [2.392753] bus_for_each_dev+0x8d/0xf0 [2.392757] driver_attach+0x1e/0x30 [2.392760] bus_add_driver+0x127/0x240 [2.392763] driver_register+0x5e/0x130 [2.392766] ? __pfx_radeon_module_init+0x10/0x10 [radeon] [2.392843] __pci_register_driver+0x62/0x70 [2.392846] radeon_module_init+0x4c/0xff0 [radeon] [2.392924] do_one_initcall+0x5e/0x340 [2.392929] do_init_module+0x68/0x260 [2.392933] load_module+0xb85/0xcd0 [2.392937] ? security_kernel_post_read_file+0x75/0x90 [2.392940] ? security_kernel_post_read_file+0x75/0x90 [2.392943] init_module_from_file+0x96/0x100 [2.392946] ? init_module_from_file+0x96/0x100 [2.392950] idempotent_init_module+0x11c/0x2b0 [2.392954] __x64_sys_finit_module+0x64/0xd0 [2.392958] do_syscall_64+0x5b/0x90 [2.392961] ? do_syscall_64+0x67/0x90 [2.392964] ? do_syscall_64+0x67/0x90 [2.392966] ? do_syscall_64+0x67/0x90 [2.392969] ? sysvec_call_function_single+0x4b/0xd0 [2.392972] entry_SYSCALL_64_after_hwframe+0x6e/0xd8 [2.392977] RIP: 0033:0x7ff88150588d [2.392984] 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 73 b5 0f 00 f7 d8 64 89 01 48 [2.392986] RSP: 002b:7ffef9db25b8 EFLAGS: 0246 ORIG_RAX: 0139 [2.392990] RAX: ffda RBX: 5590544f1df0 RCX: 7ff88150588d [2.392992] RDX: RSI: 7ff88169d441 RDI: 0016 [2.392993] RBP: 0002 R08: R09: 0002 [2.392995] R10: 0016 R11: 0246 R12: 7ff88169d441 [2.392997] R13: 5590544f4030 R14: 5590544f5c10 R15: 5590544f6ff0 [2.392999] [2.393021] [2.394165] [drm] radeon: dpm initialized [2.395090] [drm] GART: num cpu pages 262144, num gpu pages 262144 [2.425952] [drm] PCIE GART of 1024M enabled (table at 0x0014C000). [2.426006] radeon :01:00.0: WB enabled [2.426010] radeon
[Bug 198551] amdgpu error on shutdown or gpu intense game
https://bugzilla.kernel.org/show_bug.cgi?id=198551 Artem S. Tashkinov (a...@gmx.com) changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |OBSOLETE --- Comment #7 from Artem S. Tashkinov (a...@gmx.com) --- If you still experience this under 6.6.13 or 6.7.1 please file a bug report here: https://gitlab.freedesktop.org/drm/amd/-/issues -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 198551] amdgpu error on shutdown or gpu intense game
https://bugzilla.kernel.org/show_bug.cgi?id=198551 CassiRunnells (troy28...@outlook.com) changed: What|Removed |Added CC||troy28...@outlook.com --- Comment #6 from CassiRunnells (troy28...@outlook.com) --- Ensure that you are using the latest version of the AMDGPU driver. Visit the official AMD website and download the latest driver for your GPU.Check if there are any available updates for your Linux kernel. A newer kernel might include improvements and fixes for GPU-related issues.(https://ricepuritytest2024.com/) -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218368] amdgpu crashes on loading on both kernel-6.6.9 and kernel-6.1.69 at cold boot
https://bugzilla.kernel.org/show_bug.cgi?id=218368 Artem S. Tashkinov (a...@gmx.com) changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |ANSWERED --- Comment #4 from Artem S. Tashkinov (a...@gmx.com) --- Please report here instead: https://gitlab.freedesktop.org/drm/amd/-/issues -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218368] amdgpu crashes on loading on both kernel-6.6.9 and kernel-6.1.69 at cold boot
https://bugzilla.kernel.org/show_bug.cgi?id=218368 --- Comment #3 from nvaert1986 (nvaert1...@hotmail.com) --- P.S.: The GPU is a Sapphire (AMD) Radeon 7900 XTX, I figured that might be useful information. If any other information is required, then please let me know. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218368] amdgpu crashes on loading on both kernel-6.6.9 and kernel-6.1.69 at cold boot
https://bugzilla.kernel.org/show_bug.cgi?id=218368 --- Comment #2 from nvaert1986 (nvaert1...@hotmail.com) --- Jan 11 18:20:27 pc02 kernel: WARNING: CPU: 24 PID: 468 at 0xc06b26f1 Jan 11 18:20:27 pc02 kernel: Modules linked in: amdgpu(+) drm_ttm_helper snd_hda_codec_hdmi ttm amdxcp drm_exec gpu_sched i2c_algo_bit kvm_amd drm_buddy snd_hda_intel mt7921e drm_suballoc_helper snd_intel_dspcfg mt7921_common drm_display_helper mt792x_lib snd_hda_codec cec mt76_connac_lib igc snd_hda_core mt> Jan 11 18:20:27 pc02 kernel: CPU: 24 PID: 468 Comm: (udev-worker) Tainted: G W O 6.6.9-gentoo #2 Jan 11 18:20:27 pc02 kernel: Hardware name: ASUS System Product Name/ROG STRIX X670E-A GAMING WIFI, BIOS 1807 12/14/2023 Jan 11 18:20:27 pc02 kernel: RIP: 0010:0xc06b26f1 Jan 11 18:20:27 pc02 kernel: Code: c0 74 33 48 8b 4e 10 48 83 39 00 74 29 89 d1 48 8d 04 88 8b 08 85 c9 74 11 f0 ff 08 74 07 31 c0 e9 14 eb 60 cf e9 9f fd ff ff <0f> 0b b8 ea ff ff ff e9 03 eb 60 cf b8 ea ff ff ff e9 f9 ea 60 cf Jan 11 18:20:27 pc02 kernel: RSP: 0018:b7a6028bfb38 EFLAGS: 00010246 Jan 11 18:20:27 pc02 kernel: RAX: 9db705a29f8c RBX: 9db717219098 RCX: Jan 11 18:20:27 pc02 kernel: RDX: 0003 RSI: 9db7172278f0 RDI: 9db71720 Jan 11 18:20:27 pc02 kernel: RBP: 9db7172100f8 R08: R09: 9dc63d897b40 Jan 11 18:20:27 pc02 kernel: R10: 0003 R11: 9050ef28 R12: 9db7172104c8 Jan 11 18:20:27 pc02 kernel: R13: 9db717200010 R14: 9db71720 R15: ff01 Jan 11 18:20:27 pc02 kernel: FS: 7ff1f6fa5340() GS:9dc63dc0() knlGS: Jan 11 18:20:27 pc02 kernel: CS: 0010 DS: ES: CR0: 80050033 Jan 11 18:20:27 pc02 kernel: CR2: 7f657532049c CR3: 0001141f6000 CR4: 00f50ee0 Jan 11 18:20:27 pc02 kernel: PKRU: 5554 Jan 11 18:20:27 pc02 kernel: Call Trace: Jan 11 18:20:27 pc02 kernel: Jan 11 18:20:27 pc02 kernel: ? 0x8f18ee7f Jan 11 18:20:27 pc02 kernel: ? 0xc06b26f1 Jan 11 18:20:27 pc02 kernel: ? 0x8fc8705e Jan 11 18:20:27 pc02 kernel: ? 0x8fcaba9a Jan 11 18:20:27 pc02 kernel: ? 0x8fcabb77 Jan 11 18:20:27 pc02 kernel: ? 0x8fe0120a Jan 11 18:20:27 pc02 kernel: ? 0xc06b26f1 Jan 11 18:20:27 pc02 kernel: ? 0x8fcc1205 Jan 11 18:20:27 pc02 kernel: 0xc063a3d7 Jan 11 18:20:27 pc02 kernel: 0xc06267f1 Jan 11 18:20:27 pc02 kernel: ? 0x8f1b88a9 Jan 11 18:20:27 pc02 kernel: 0xc062c1a1 Jan 11 18:20:27 pc02 kernel: 0xc0623824 Jan 11 18:20:27 pc02 kernel: 0x8f6b8754 Jan 11 18:20:27 pc02 kernel: 0x8f7f82ce Jan 11 18:20:27 pc02 kernel: ? 0x8f7f8760 Jan 11 18:20:27 pc02 kernel: 0x8f7f84ce Jan 11 18:20:27 pc02 kernel: 0x8f7f858a Jan 11 18:20:27 pc02 kernel: 0x8f7f87e3 Jan 11 18:20:27 pc02 kernel: 0x8f7f6390 Jan 11 18:20:27 pc02 kernel: 0x8f7f75d7 Jan 11 18:20:27 pc02 kernel: 0x8f7f9414 Jan 11 18:20:27 pc02 kernel: ? 0xc0d8a000 Jan 11 18:20:27 pc02 kernel: 0x8f000723 Jan 11 18:20:27 pc02 kernel: 0x8f20ee3b Jan 11 18:20:27 pc02 kernel: 0x8f210fd1 Jan 11 18:20:27 pc02 kernel: 0x8f21112c Jan 11 18:20:27 pc02 kernel: 0x8f211351 Jan 11 18:20:27 pc02 kernel: 0x8fcab7c4 Jan 11 18:20:27 pc02 kernel: 0x8fe000c7 Jan 11 18:20:27 pc02 kernel: RIP: 0033:0x7ff1f7b4eca9 Jan 11 18:20:27 pc02 kernel: Code: 08 89 e8 5b 5d c3 66 2e 0f 1f 84 00 00 00 00 00 90 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 2f e1 0c 00 f7 d8 64 89 01 48 Jan 11 18:20:27 pc02 kernel: RSP: 002b:7ffd84d4f018 EFLAGS: 0246 ORIG_RAX: 0139 Jan 11 18:20:27 pc02 kernel: RAX: ffda RBX: 5641b982ad80 RCX: 7ff1f7b4eca9 Jan 11 18:20:27 pc02 kernel: RDX: RSI: 7ff1f7c3b2df RDI: 0017 Jan 11 18:20:27 pc02 kernel: RBP: R08: R09: Jan 11 18:20:27 pc02 kernel: R10: 0050 R11: 0246 R12: 7ff1f7c3b2df Jan 11 18:20:27 pc02 kernel: R13: 0002 R14: 5641b9844ba0 R15: Jan 11 18:20:27 pc02 kernel: Jan 11 18:20:27 pc02 kernel: ---[ end trace ]--- Jan 11 18:20:27 pc02 kernel: [ cut here ] Jan 11 18:20:27 pc02 kernel: WARNING: CPU: 24 PID: 468 at 0xc06b26f1 Jan 11 18:20:27 pc02 kernel: Modules linked in: amdgpu(+) drm_ttm_helper snd_hda_codec_hdmi ttm amdxcp drm_exec gpu_sched i2c_algo_bit kvm_amd drm_buddy snd_hda_intel mt7921e drm_suballoc_helper snd_intel_dspcfg mt7921_common drm_display_helper mt792x_lib snd_hda_codec cec mt76_connac_lib igc snd_hda_core mt> Jan 11 18:20:27 pc02 kernel: CPU: 24 PID: 468 Comm: (udev-worker)
[Bug 218368] amdgpu crashes on loading on both kernel-6.6.9 and kernel-6.1.69 at cold boot
https://bugzilla.kernel.org/show_bug.cgi?id=218368 --- Comment #1 from nvaert1986 (nvaert1...@hotmail.com) --- an 11 18:20:27 pc02 kernel: [drm] failed to load ucode UNKNOWN UCODE(0xE) Jan 11 18:20:27 pc02 kernel: [drm] psp gfx command LOAD_IP_FW(0x6) failed and response status is (0x0) Jan 11 18:20:27 pc02 kernel: [drm:0xc06c23d5] *ERROR* Fail to stop psp ring Jan 11 18:20:27 pc02 kernel: [drm:0xc06bde91] *ERROR* PSP firmware loading failed Jan 11 18:20:27 pc02 kernel: [drm:0xc06246b5] *ERROR* hw_init of IP block failed -22 Jan 11 18:20:27 pc02 kernel: amdgpu :03:00.0: amdgpu: amdgpu_device_ip_init failed Jan 11 18:20:27 pc02 kernel: amdgpu :03:00.0: amdgpu: Fatal error during GPU init Jan 11 18:20:27 pc02 kernel: amdgpu :03:00.0: amdgpu: amdgpu: finishing device. Jan 11 18:20:27 pc02 kernel: [ cut here ] Jan 11 18:20:27 pc02 kernel: WARNING: CPU: 24 PID: 468 at 0xc06b26f1 Jan 11 18:20:27 pc02 kernel: Modules linked iJan 11 18:20:27 pc02 kernel: 0xc0623824 Jan 11 18:20:27 pc02 kernel: 0x8f6b8754 Jan 11 18:20:27 pc02 kernel: 0x8f7f82ce Jan 11 18:20:27 pc02 kernel: ? 0x8f7f8760 Jan 11 18:20:27 pc02 kernel: 0x8f7f84ce Jan 11 18:20:27 pc02 kernel: 0x8f7f858a Jan 11 18:20:27 pc02 kernel: 0x8f7f87e3 Jan 11 18:20:27 pc02 kernel: 0x8f7f6390 Jan 11 18:20:27 pc02 kernel: 0x8f7f75d7 Jan 11 18:20:27 pc02 kernel: 0x8f7f9414 Jan 11 18:20:27 pc02 kernel: ? 0xc0d8a000 Jan 11 18:20:27 pc02 kernel: 0x8f000723 Jan 11 18:20:27 pc02 kernel: 0x8f20ee3b Jan 11 18:20:27 pc02 kernel: 0x8f210fd1 Jan 11 18:20:27 pc02 kernel: 0x8f21112c Jan 11 18:20:27 pc02 kernel: 0x8f211351 Jan 11 18:20:27 pc02 kernel: 0x8fcab7c4 Jan 11 18:20:27 pc02 kernel: 0x8fe000c7 Jan 11 18:20:27 pc02 kernel: RIP: 0033:0x7ff1f7b4eca9 Jan 11 18:20:27 pc02 kernel: Code: 08 89 e8 5b 5d c3 66 2e 0f 1f 84 00 00 00 00 00 90 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 2f e1 0c 00 f7 d8 64 89 01 48 Jan 11 18:20:27 pc02 kernel: RSP: 002b:7ffd84d4f018 EFLAGS: 0246 ORIG_RAX: 0139 Jan 11 18:20:27 pc02 kernel: RAX: ffda RBX: 5641b982ad80 RCX: 7ff1f7b4eca9 Jan 11 18:20:27 pc02 kernel: RDX: RSI: 7ff1f7c3b2df RDI: 0017 Jan 11 18:20:27 pc02 kernel: RBP: R08: R09: Jan 11 18:20:27 pc02 kernel: R10: 0050 R11: 0246 R12: 7ff1f7c3b2df Jan 11 18:20:27 pc02 kernel: R13: 0002 R14: 5641b9844ba0 R15: Jan 11 18:20:27 pc02 kernel: Jan 11 18:20:27 pc02 kernel: ---[ end trace ]--- Jan 11 18:20:27 pc02 kernel: [ cut here ] n: amdgpu(+) drm_ttm_helper snd_hda_codec_hdmi ttm amdxcp drm_exec gpu_sched i2c_algo_bit kvm_amd drm_buddy snd_hda_intel mt7921e drm_suballoc_helper snd_intel_dspcfg mt7921_common drm_display_helper mt792x_lib snd_hda_codec cec mt76_connac_lib igc snd_hda_core mt> Jan 11 18:20:27 pc02 kernel: CPU: 24 PID: 468 Comm: (udev-worker) Tainted: G O 6.6.9-gentoo #2 Jan 11 18:20:27 pc02 kernel: Hardware name: ASUS System Product Name/ROG STRIX X670E-A GAMING WIFI, BIOS 1807 12/14/2023 Jan 11 18:20:27 pc02 kernel: RIP: 0010:0xc06b26f1 Jan 11 18:20:27 pc02 kernel: Code: c0 74 33 48 8b 4e 10 48 83 39 00 74 29 89 d1 48 8d 04 88 8b 08 85 c9 74 11 f0 ff 08 74 07 31 c0 e9 14 eb 60 cf e9 9f fd ff ff <0f> 0b b8 ea ff ff ff e9 03 eb 60 cf b8 ea ff ff ff e9 f9 ea 60 cf Jan 11 18:20:27 pc02 kernel: RSP: 0018:b7a6028bfb38 EFLAGS: 00010246 Jan 11 18:20:27 pc02 kernel: RAX: 9db705a29f80 RBX: 9db717218580 RCX: Jan 11 18:20:27 pc02 kernel: RDX: RSI: 9db7172278f0 RDI: 9db71720 Jan 11 18:20:27 pc02 kernel: RBP: 9db7172100e8 R08: R09: 9dc63d897b40 Jan 11 18:20:27 pc02 kernel: R10: 0003 R11: 9050ef28 R12: 9db7172104c8 Jan 11 18:20:27 pc02 kernel: R13: 9db717200010 R14: 9db71720 R15: ff01 Jan 11 18:20:27 pc02 kernel: FS: 7ff1f6fa5340() GS:9dc63dc0() knlGS: Jan 11 18:20:27 pc02 kernel: CS: 0010 DS: ES: CR0: 80050033 Jan 11 18:20:27 pc02 kernel: CR2: 7f657532049c CR3: 0001141f6000 CR4: 00f50ee0 Jan 11 18:20:27 pc02 kernel: PKRU: 5554 Jan 11 18:20:27 pc02 kernel: Call Trace: Jan 11 18:20:27 pc02 kernel: Jan 11 18:20:27 pc02 kernel: ? 0x8f18ee7f Jan 11 18:20:27 pc02 kernel: ? 0xc06b26f1 Jan 11 18:20:27 pc02 kernel: ? 0x8fc8705e Jan 11 18:20:27 pc02 kernel: ? 0x8fcaba9a Jan 11 18:20:27 pc02 kernel: ? 0x8fcabb77 Jan 11 18:20:27 pc02 kernel: ? 0x8fe0120a Jan 11 18:20:27 pc02 kernel: ?
[Bug 218368] New: amdgpu crashes on loading on both kernel-6.6.9 and kernel-6.1.69 at cold boot
https://bugzilla.kernel.org/show_bug.cgi?id=218368 Bug ID: 218368 Summary: amdgpu crashes on loading on both kernel-6.6.9 and kernel-6.1.69 at cold boot Product: Drivers Version: 2.5 Hardware: All OS: Linux Status: NEW Severity: normal Priority: P3 Component: Video(DRI - non Intel) Assignee: drivers_video-...@kernel-bugs.osdl.org Reporter: nvaert1...@hotmail.com Regression: No The amdgpu driver crashes frequently whenever I cold boot my system. The issue has not occurred so far when rebooting the system. I can see the screen (when efifb is running) and then as soon as amdgpu is loaded my screen goes blank. I press ctrl - alt - del to reboot the system. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218347] Crash. amdgpu : drm:amdgpu_cs_ioctl : Failed to initialize parser -125
https://bugzilla.kernel.org/show_bug.cgi?id=218347 Alex Deucher (alexdeuc...@gmail.com) changed: What|Removed |Added CC||alexdeuc...@gmail.com --- Comment #4 from Alex Deucher (alexdeuc...@gmail.com) --- (In reply to Rik from comment #3) > Are you sure? Because in the help I read: Yes, per: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/MAINTAINERS#n18009 RADEON and AMDGPU DRM DRIVERS M: Alex Deucher M: Christian König M: Pan, Xinhui L: amd-...@lists.freedesktop.org S: Supported B: https://gitlab.freedesktop.org/drm/amd/-/issues C: irc://irc.oftc.net/radeon T: git https://gitlab.freedesktop.org/agd5f/linux.git F: Documentation/gpu/amdgpu/ F: drivers/gpu/drm/amd/ F: drivers/gpu/drm/ci/xfails/amd* F: drivers/gpu/drm/radeon/ F: include/uapi/drm/amdgpu_drm.h F: include/uapi/drm/radeon_drm.h -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 203201] [mgag200] Unable to do mmap call on mgadrmfb device - Returns -EINVAL
https://bugzilla.kernel.org/show_bug.cgi?id=203201 Roland Kletzing (devz...@web.de) changed: What|Removed |Added CC||devz...@web.de --- Comment #1 from Roland Kletzing (devz...@web.de) --- apparently the patch has never got merged, apparently it seems Dave Airlie did not find it useful enough https://yhbt.net/lore/all/CAPM=9tzmt3hdopdwphrr07sw-3iu6ohnky6noo3e_21vyf6...@mail.gmail.com/ -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 111271] Black stripe on screen with MGAG200 (PowerEdge R320) and modesetting
https://bugzilla.kernel.org/show_bug.cgi?id=111271 Roland Kletzing (devz...@web.de) changed: What|Removed |Added CC||devz...@web.de --- Comment #8 from Roland Kletzing (devz...@web.de) --- there has been major rework in mgag200 since your report, could you perhaps retry with recent 6.1 or 6.6 kernel how that behaves? also mind that there is a patch on the way to get merged soon which fixes an issue cause by the driver rework https://bugzilla.kernel.org/show_bug.cgi?id=217790 -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218347] Crash. amdgpu : drm:amdgpu_cs_ioctl : Failed to initialize parser -125
https://bugzilla.kernel.org/show_bug.cgi?id=218347 --- Comment #3 from Rik (riks...@gmail.com) --- Are you sure? Because in the help I read: Video(DRI - Intel) intel-gfx-b...@lists.freedesktop.org Please file new drm/i915 bugs at https://bugs.freedesktop.org. Product: DRI. Component: DRM/Intel. Video(DRI - non Intel) drivers_video-dri DRI video This is not an DRI Intel so I thought the right place was here. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218347] Crash. amdgpu : drm:amdgpu_cs_ioctl : Failed to initialize parser -125
https://bugzilla.kernel.org/show_bug.cgi?id=218347 Artem S. Tashkinov (a...@gmx.com) changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |ANSWERED --- Comment #2 from Artem S. Tashkinov (a...@gmx.com) --- Please report here instead: https://gitlab.freedesktop.org/drm/amd/-/issues -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218347] Crash. amdgpu : drm:amdgpu_cs_ioctl : Failed to initialize parser -125
https://bugzilla.kernel.org/show_bug.cgi?id=218347 Rik (riks...@gmail.com) changed: What|Removed |Added Kernel Version|Debian 6.1.0-17 |Debian 6.1.0-17 (= upstream ||6.1.69-1) -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218347] Crash. amdgpu : drm:amdgpu_cs_ioctl : Failed to initialize parser -125
https://bugzilla.kernel.org/show_bug.cgi?id=218347 Rik (riks...@gmail.com) changed: What|Removed |Added Kernel Version||Debian 6.1.0-17 -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218347] Crash. amdgpu : drm:amdgpu_cs_ioctl : Failed to initialize parser -125
https://bugzilla.kernel.org/show_bug.cgi?id=218347 --- Comment #1 from Rik (riks...@gmail.com) --- Created attachment 305678 --> https://bugzilla.kernel.org/attachment.cgi?id=305678=edit systemctl -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218347] New: Crash. amdgpu : drm:amdgpu_cs_ioctl : Failed to initialize parser -125
https://bugzilla.kernel.org/show_bug.cgi?id=218347 Bug ID: 218347 Summary: Crash. amdgpu : drm:amdgpu_cs_ioctl : Failed to initialize parser -125 Product: Drivers Version: 2.5 Hardware: i386 OS: Linux Status: NEW Severity: blocking Priority: P3 Component: Video(DRI - non Intel) Assignee: drivers_video-...@kernel-bugs.osdl.org Reporter: riks...@gmail.com Regression: No Created attachment 305677 --> https://bugzilla.kernel.org/attachment.cgi?id=305677=edit dmesg Yesterday I've apt update Debian 12 and with the update I got kernel 6.1.0.-16 --> 6.1.0.-17. This morning while I was scrolling rapidly a long page of code inside Netbeans 20, I foud myself at login. I DOUBT IT'S MERE COINCIDENCE: I've been working ok for months with the same exact hw/sw config and after a couple of hour such incident. I can see the culprit in log: after [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! a cascade of errors brough me to the crash-->login losing everything that was not yet saved. Graphics: Device-1: AMD Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] driver: amdgpu v: kernel Display: x11 server: X.Org v: 1.21.1.7 driver: X: loaded: amdgpu unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: amdgpu resolution: 1: 1440x2560~60Hz 2: 1440x2560~60Hz API: OpenGL v: 4.6 Mesa 22.3.6 renderer: AMD Radeon RX 570 Series (polaris10 LLVM 15.0.6 DRM 3.49 6.1.0-17-amd64) -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 205089] amdgpu : drm:amdgpu_cs_ioctl : Failed to initialize parser -125
https://bugzilla.kernel.org/show_bug.cgi?id=205089 Rik (riks...@gmail.com) changed: What|Removed |Added CC||riks...@gmail.com --- Comment #61 from Rik (riks...@gmail.com) --- Yesterday I've apt update Debian 12 and with the update I got 6.1.0.-16 --> 6.1.0.-17. This morning while I was scrolling rapidly a long page of code inside Netbeans 20, I find myself at login. I DOUBT IT'S MERE COINCIDENCE because I've been working ok for months with the same exact hw/sw config I can see the culprit in log: Jan 05 09:50:44 kernel: amdgpu :01:00.0: amdgpu: GPU fault detected: 147 0x0802 for process Xorg pid 1130 thread Xorg:cs0 pid 1605 That triggered a cascade of problems this way Jan 05 09:50:44 kernel: amdgpu :01:00.0: amdgpu: GPU fault detected: 147 0x0802 for process Xorg pid 1130 thread Xorg:cs0 pid 1605 Jan 05 09:50:44 kernel: amdgpu :01:00.0: amdgpu: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x0800 Jan 05 09:50:44 kernel: amdgpu :01:00.0: amdgpu: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0C008002 Jan 05 09:50:44 kernel: amdgpu :01:00.0: amdgpu: VM fault (0x02, vmid 6, pasid 32769) at page 2048, read from 'TC0' (0x54433000) (8) Jan 05 09:50:54 kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=158350, emitted seq=158352 Jan 05 09:50:54 kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 1130 thread Xorg:cs0 pid 1605 Jan 05 09:50:54 kernel: amdgpu :01:00.0: amdgpu: GPU reset begin! Jan 05 09:50:54 kernel: amdgpu: cp is busy, skip halt cp Jan 05 09:50:55 kernel: amdgpu: rlc is busy, skip halt rlc Jan 05 09:50:55 kernel: amdgpu :01:00.0: amdgpu: BACO reset Jan 05 09:50:55 kernel: amdgpu :01:00.0: amdgpu: GPU reset succeeded, trying to resume Jan 05 09:50:55 kernel: [drm] PCIE GART of 256M enabled (table at 0x00F40090). Jan 05 09:50:55 kernel: [drm] VRAM is lost due to GPU reset! Jan 05 09:50:55 kernel: [drm] UVD and UVD ENC initialized successfully. Jan 05 09:50:55 kernel: [drm] VCE initialized successfully. Jan 05 09:50:55 kernel: amdgpu :01:00.0: amdgpu: recover vram bo from shadow start Jan 05 09:50:55 kernel: amdgpu :01:00.0: amdgpu: recover vram bo from shadow done Jan 05 09:50:55 kernel: [drm] Skip scheduling IBs! Jan 05 09:50:55 kernel: [drm] Skip scheduling IBs! Jan 05 09:50:55 kernel: amdgpu :01:00.0: amdgpu: GPU reset(2) succeeded! Jan 05 09:50:55 kernel: [drm] Skip scheduling IBs! Jan 05 09:50:55 kernel: [drm] Skip scheduling IBs! Jan 05 09:50:55 kernel: [drm] Skip scheduling IBs! Jan 05 09:50:55 kernel: [drm] Skip scheduling IBs! Jan 05 09:50:55 kernel: [drm] Skip scheduling IBs! Jan 05 09:50:55 kernel: [drm] Skip scheduling IBs! Jan 05 09:50:55 kernel: [drm] Skip scheduling IBs! Jan 05 09:50:55 kernel: [drm] Skip scheduling IBs! Jan 05 09:50:55 kernel: [drm] Skip scheduling IBs! Jan 05 09:50:55 kernel: [drm] Skip scheduling IBs! Jan 05 09:50:55 kernel: [drm] Skip scheduling IBs! Jan 05 09:50:55 kernel: [drm] Skip scheduling IBs! Jan 05 09:50:55 kernel: [drm] Skip scheduling IBs! Jan 05 09:50:55 kernel: [drm] Skip scheduling IBs! Jan 05 09:50:55 kernel: [drm] Skip scheduling IBs! Jan 05 09:50:55 kernel: [drm] Skip scheduling IBs! Jan 05 09:50:55 kernel: [drm] Skip scheduling IBs! Jan 05 09:50:55 kernel: [drm] Skip scheduling IBs! Jan 05 09:50:55 kernel: [drm] Skip scheduling IBs! Jan 05 09:50:55 kernel: [drm] Skip scheduling IBs! Jan 05 09:50:55 kernel: [drm] Skip scheduling IBs! Jan 05 09:50:55 kernel: [drm] Skip scheduling IBs! Jan 05 09:50:55 kernel: [drm] Skip scheduling IBs! Jan 05 09:50:55 kernel: [drm] Skip scheduling IBs! Jan 05 09:50:55 kernel: [drm] Skip scheduling IBs! Jan 05 09:50:55 kernel: [drm] Skip scheduling IBs! Jan 05 09:50:55 kernel: [drm] Skip scheduling IBs! Jan 05 09:50:55 kernel: [drm] Skip scheduling IBs! Jan 05 09:50:55 kernel: [drm] Skip scheduling IBs! Jan 05 09:50:55 kernel: [drm] Skip scheduling IBs! Jan 05 09:50:55 kernel: [drm] Skip scheduling IBs! Jan 05 09:50:55 kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! Jan 05 09:50:55 pulseaudio[3356]: X11 I/O error handler called Jan 05 09:50:55 pulseaudio[3356]: X11 I/O error exit handler called, preparing to tear down X11 modules Jan 05 09:50:55 polkitd[1078]: Unregistered Authentication Agent for unix-session:4 (system bus name :1.44, object path /org/mate/PolicyKit1/AuthenticationAgent, locale en_GB.UTF-8) (disconnected from bus) Jan 05 09:50:55 at-spi-bus-launcher[3480]: X connection to :0 broken (explicit kill or server shutdown). Jan 05 09:50:55 lightdm[2844]: pam_unix(lightdm:session): session closed for user rik Jan 05 09:50:55 systemd-logind[920]: Session 4 logged out. Waiting for processes to exit. Jan 05 09:50:55 firefox[4100]: Exiting due
[Bug 198551] amdgpu error on shutdown or gpu intense game
https://bugzilla.kernel.org/show_bug.cgi?id=198551 Kenna Anna (kenaann...@gmail.com) changed: What|Removed |Added CC||kenaann...@gmail.com --- Comment #5 from Kenna Anna (kenaann...@gmail.com) --- Encountering occasional shutdown errors, particularly during GPU-intensive tasks like playing CS:GO on my Radeon R5 M255. This results in system freezes, prompting a hard reset. Exploring potential solutions, such as updating GPU drivers or addressing potential overheating issues, could prove beneficial. For more insights into experiences like these, you can check out (https://ricepurity-test.org/) -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 213145] AMDGPU resets, timesout and crashes after "*ERROR* Waiting for fences timed out!"
https://bugzilla.kernel.org/show_bug.cgi?id=213145 mikkk (mikk...@gmail.com) changed: What|Removed |Added CC||mikk...@gmail.com --- Comment #33 from mikkk (mikk...@gmail.com) --- Also getting gfx_0.0.0 timeout error on brand new Lenovo ThinkPad T14 Gen 4 AMD Ryzen™ 7 PRO 7840U w/ Radeon™ 780M Graphics × 16 on Debian. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 213983] WARNING: CPU: 3 PID: 520 at drivers/gpu/drm/ttm/ttm_bo.c:409 ttm_bo_release+0x7a/0x803 [ttm]
https://bugzilla.kernel.org/show_bug.cgi?id=213983 --- Comment #9 from Andimewi (andim...@gmx.net) --- Remains in 6.5.0-14 Sometimes system freezes! [12068.780248] WARNING: CPU: 11 PID: 2001 at drivers/gpu/drm/ttm/ttm_bo.c:326 ttm_bo_release+0x299/0x2c0 [ttm] [12068.780285] Modules linked in: bnep bluetooth ecdh_generic ecc veth snd_seq_dummy snd_hrtimer xt_nat xt_tcpudp xt_conntrack nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user xfrm_algo xt_addrtype nft_compat nf_tables nfnetlink br_netfilter bridge stp llc overlay dm_crypt cfg80211 binfmt_misc joydev input_leds intel_rapl_msr intel_rapl_common snd_hda_codec_realtek edac_mce_amd snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_seq_midi nls_iso8859_1 snd_seq_midi_event snd_rawmidi kvm snd_seq snd_seq_device snd_timer irqbypass snd rapl wmi_bmof k10temp ccp soundcore i2c_piix4 gpio_amdpt mac_hid msr dm_multipath parport_pc ppdev lp parport efi_pstore dmi_sysfs ip_tables x_tables autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear amdgpu amdxcp iommu_v2 [12068.780551] drm_buddy gpu_sched hid_generic radeon video i2c_algo_bit drm_suballoc_helper drm_ttm_helper ttm drm_display_helper cec crct10dif_pclmul rc_core crc32_pclmul usbhid polyval_clmulni polyval_generic hid ghash_clmulni_intel aesni_intel drm_kms_helper crypto_simd nvme r8169 cryptd drm xhci_pci nvme_core realtek ahci xhci_pci_renesas libahci nvme_common wmi [12068.780653] CPU: 11 PID: 2001 Comm: Xorg Not tainted 6.5.0-14-generic #14-Ubuntu [12068.780662] Hardware name: Micro-Star International Co., Ltd. MS-7A39/B350M GAMING PRO (MS-7A39), BIOS 2.P3 07/16/2022 [12068.780667] RIP: 0010:ttm_bo_release+0x299/0x2c0 [ttm] [12068.780695] Code: 48 8b 7b 90 e8 88 4c d0 e9 e9 e1 fd ff ff c7 43 2c 00 00 00 00 48 8b 7b 08 e8 a3 53 00 00 e9 5d ff ff ff 0f 0b e9 b0 fd ff ff <0f> 0b e9 9e fd ff ff be 03 00 00 00 e8 a6 e7 3c e9 e9 21 ff ff ff [12068.780702] RSP: 0018:b92b0317fc80 EFLAGS: 00010202 [12068.780710] RAX: RBX: 9769c40919e0 RCX: [12068.780716] RDX: 0001 RSI: RDI: 9769c40919e0 [12068.780721] RBP: b92b0317fce0 R08: R09: [12068.780725] R10: R11: R12: [12068.780730] R13: 9769d24646e0 R14: 9769c4091878 R15: 976a3b8423c0 [12068.780735] FS: 7f37d2401ac0() GS:976ceecc() knlGS: [12068.780741] CS: 0010 DS: ES: CR0: 80050033 [12068.780747] CR2: 7f37b6e29c00 CR3: 00012f15 CR4: 003506e0 [12068.780753] Call Trace: [12068.780759] [12068.780768] ? show_regs+0x6d/0x80 [12068.780781] ? __warn+0x89/0x160 [12068.780792] ? ttm_bo_release+0x299/0x2c0 [ttm] [12068.780822] ? report_bug+0x17e/0x1b0 [12068.780837] ? handle_bug+0x51/0xa0 [12068.780848] ? exc_invalid_op+0x18/0x80 [12068.780857] ? asm_exc_invalid_op+0x1b/0x20 [12068.780874] ? ttm_bo_release+0x299/0x2c0 [ttm] [12068.780902] ? srso_return_thunk+0x5/0x10 [12068.780911] ? __call_rcu_common.constprop.0+0xa0/0x2b0 [12068.780925] ttm_bo_put+0x3c/0x70 [ttm] [12068.780952] radeon_bo_unref+0x1e/0x40 [radeon] [12068.781083] radeon_gem_object_free+0x34/0x60 [radeon] [12068.781220] drm_gem_object_free+0x1d/0x40 [drm] [12068.781337] drm_gem_dmabuf_release+0x46/0x70 [drm] [12068.781446] dma_buf_release+0x3e/0xa0 [12068.781457] __dentry_kill+0x100/0x190 [12068.781467] dput+0x19d/0x320 [12068.781476] __fput+0x150/0x2c0 [12068.781487] fput+0xe/0x20 [12068.781494] task_work_run+0x61/0xa0 [12068.781504] exit_to_user_mode_loop+0x100/0x130 [12068.781516] exit_to_user_mode_prepare+0xa5/0xb0 [12068.781526] syscall_exit_to_user_mode+0x29/0x60 [12068.781536] do_syscall_64+0x68/0x90 [12068.781543] ? syscall_exit_to_user_mode+0x37/0x60 [12068.781550] ? srso_return_thunk+0x5/0x10 [12068.781558] ? do_syscall_64+0x68/0x90 [12068.781564] ? srso_return_thunk+0x5/0x10 [12068.781579] ? radeon_drm_ioctl+0x70/0x90 [radeon] [12068.781697] ? srso_return_thunk+0x5/0x10 [12068.781735] ? exit_to_user_mode_prepare+0x91/0xb0 [12068.781745] ? srso_return_thunk+0x5/0x10 [12068.781753] ? syscall_exit_to_user_mode+0x37/0x60 [12068.781761] ? srso_return_thunk+0x5/0x10 [12068.781768] ? do_syscall_64+0x68/0x90 [12068.781776] entry_SYSCALL_64_after_hwframe+0x6e/0xd8 [12068.781784] RIP: 0033:0x7f37d27238ef [12068.781828] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 18 48 8b 44 24 18 64 48 2b 04 25 28 00 00 [12068.781834] RSP: 002b:7ffd3f5be970 EFLAGS: 0246 ORIG_RAX: 0010 [12068.781842] RAX: RBX: 55e2463fe9a0
[Bug 218292] Built in Screen (Laptop) won't wake up from sleep (AMD Graphics)
https://bugzilla.kernel.org/show_bug.cgi?id=218292 --- Comment #7 from m...@bewi.at --- (In reply to Bagas Sanjaya from comment #6) > (In reply to mail from comment #4) > > > > > > > Info for my System: > > > > > > > > Graphics Platform: X11 > > > > Processors: 16 × AMD Ryzen 7 PRO 7840U w/ Radeon 780M Graphics > > > > Memory: 30,1 GiB of RAM > > > > Graphics Processor: AMD Radeon Graphics > > > > > > What amdgpu model? > > > > > > > Manufacturer: LENOVO > > > > Product Name: 21F80041GE > > > > System Version: ThinkPad T14s Gen 4 > > > > > > > > > > Confused... > > > > I'm also confused. ;-) Did you mean this? > > > > > > [root@xyz user]# lspci -k | grep -EA2 'VGA|3D' > > pcilib: Error reading /sys/bus/pci/devices/:00:08.3/label: Operation > not > > permitted > > c3:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] > > Phoenix1 (rev dd) > > Subsystem: Lenovo Phoenix1 > > Kernel driver in use: amdgpu > > > > I mean I'd like to know what gpu chipset is (hint: see laptop specification). Sorry i mean that i have posted this on the first post. Here is the data: CPU: AMD Ryzen 7 PRO 7840U Graphics: AMD Radeon 780M Chipset: AMD SoC (System on Chip) platform https://psref.lenovo.com/syspool/Sys/PDF/ThinkPad/ThinkPad_T14s_Gen_4_AMD/ThinkPad_T14s_Gen_4_AMD_Spec.PDF Thank you for your help. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218292] Built in Screen (Laptop) won't wake up from sleep (AMD Graphics)
https://bugzilla.kernel.org/show_bug.cgi?id=218292 --- Comment #6 from Bagas Sanjaya (bagasdo...@gmail.com) --- (In reply to mail from comment #4) > > > > > Info for my System: > > > > > > Graphics Platform: X11 > > > Processors: 16 × AMD Ryzen 7 PRO 7840U w/ Radeon 780M Graphics > > > Memory: 30,1 GiB of RAM > > > Graphics Processor: AMD Radeon Graphics > > > > What amdgpu model? > > > > > Manufacturer: LENOVO > > > Product Name: 21F80041GE > > > System Version: ThinkPad T14s Gen 4 > > > > > > > Confused... > > I'm also confused. ;-) Did you mean this? > > > [root@xyz user]# lspci -k | grep -EA2 'VGA|3D' > pcilib: Error reading /sys/bus/pci/devices/:00:08.3/label: Operation not > permitted > c3:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] > Phoenix1 (rev dd) > Subsystem: Lenovo Phoenix1 > Kernel driver in use: amdgpu > I mean I'd like to know what gpu chipset is (hint: see laptop specification). -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218292] Built in Screen (Laptop) won't wake up from sleep (AMD Graphics)
https://bugzilla.kernel.org/show_bug.cgi?id=218292 --- Comment #5 from m...@bewi.at --- Sorry i forgot to say. I don't tried the 6.5 Kernel. v6.1. works. v6.6. doesn't work. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218292] Built in Screen (Laptop) won't wake up from sleep (AMD Graphics)
https://bugzilla.kernel.org/show_bug.cgi?id=218292 --- Comment #4 from m...@bewi.at --- (In reply to Bagas Sanjaya from comment #1) > (In reply to mail from comment #0) > > Hello all! > > > > I’ve a problem with the wake up from screen sleep (not whole computer > sleeo, > > only display) and latest kernels. When the computer screen goes to sleep it > > won’t wake up anymore. No mouse cursor nor i can change to tty (Strg + Alt > + > > F1 …). The journals logs are also empty and only a hard reset helps. I’ve > > tested it with the lastest Linux Kernel 6.6.6 and 6.6.7. Funnily if the > > whole computer goes to sleep (for example Sleep, Hybrid Sleep or > Hibernate), > > and i disable Screen Sleep before, the screen wakes up. The problem exists > > only when the screen goes to sleep. With older kernels (i don't know the > > exact version, i think before 6.6.x) it does work. I've tested the same > > behaviour on OpenSUSE Tumbleweed and Arch Linux. Also i changed to Wayland, > > but the same problem. > > > > Does waking up from sleep work on v6.5.y? v6.1.y? Also, can you attach > full dmesg (from both v6.6.y and working kernel)? First of all thank you for the reply. I've attached the logs. I hope i made it correctly. > > > Info for my System: > > > > Graphics Platform: X11 > > Processors: 16 × AMD Ryzen 7 PRO 7840U w/ Radeon 780M Graphics > > Memory: 30,1 GiB of RAM > > Graphics Processor: AMD Radeon Graphics > > What amdgpu model? > > > Manufacturer: LENOVO > > Product Name: 21F80041GE > > System Version: ThinkPad T14s Gen 4 > > > > Confused... I'm also confused. ;-) Did you mean this? [root@xyz user]# lspci -k | grep -EA2 'VGA|3D' pcilib: Error reading /sys/bus/pci/devices/:00:08.3/label: Operation not permitted c3:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Phoenix1 (rev dd) Subsystem: Lenovo Phoenix1 Kernel driver in use: amdgpu Thanks again. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218292] Built in Screen (Laptop) won't wake up from sleep (AMD Graphics)
https://bugzilla.kernel.org/show_bug.cgi?id=218292 --- Comment #3 from m...@bewi.at --- Created attachment 305635 --> https://bugzilla.kernel.org/attachment.cgi?id=305635=edit dmesg6.6.x_not_working -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218292] Built in Screen (Laptop) won't wake up from sleep (AMD Graphics)
https://bugzilla.kernel.org/show_bug.cgi?id=218292 --- Comment #2 from m...@bewi.at --- Created attachment 305634 --> https://bugzilla.kernel.org/attachment.cgi?id=305634=edit dmesg6.1.x_working -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218292] Built in Screen (Laptop) won't wake up from sleep (AMD Graphics)
https://bugzilla.kernel.org/show_bug.cgi?id=218292 Bagas Sanjaya (bagasdo...@gmail.com) changed: What|Removed |Added CC||bagasdo...@gmail.com --- Comment #1 from Bagas Sanjaya (bagasdo...@gmail.com) --- (In reply to mail from comment #0) > Hello all! > > I’ve a problem with the wake up from screen sleep (not whole computer sleeo, > only display) and latest kernels. When the computer screen goes to sleep it > won’t wake up anymore. No mouse cursor nor i can change to tty (Strg + Alt + > F1 …). The journals logs are also empty and only a hard reset helps. I’ve > tested it with the lastest Linux Kernel 6.6.6 and 6.6.7. Funnily if the > whole computer goes to sleep (for example Sleep, Hybrid Sleep or Hibernate), > and i disable Screen Sleep before, the screen wakes up. The problem exists > only when the screen goes to sleep. With older kernels (i don't know the > exact version, i think before 6.6.x) it does work. I've tested the same > behaviour on OpenSUSE Tumbleweed and Arch Linux. Also i changed to Wayland, > but the same problem. > Does waking up from sleep work on v6.5.y? v6.1.y? Also, can you attach full dmesg (from both v6.6.y and working kernel)? > Info for my System: > > Graphics Platform: X11 > Processors: 16 × AMD Ryzen 7 PRO 7840U w/ Radeon 780M Graphics > Memory: 30,1 GiB of RAM > Graphics Processor: AMD Radeon Graphics What amdgpu model? > Manufacturer: LENOVO > Product Name: 21F80041GE > System Version: ThinkPad T14s Gen 4 > Confused... -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218292] New: Built in Screen (Laptop) won't wake up from sleep (AMD Graphics)
https://bugzilla.kernel.org/show_bug.cgi?id=218292 Bug ID: 218292 Summary: Built in Screen (Laptop) won't wake up from sleep (AMD Graphics) Product: Drivers Version: 2.5 Hardware: All OS: Linux Status: NEW Severity: normal Priority: P3 Component: Video(DRI - non Intel) Assignee: drivers_video-...@kernel-bugs.osdl.org Reporter: m...@bewi.at Regression: No Hello all! I’ve a problem with the wake up from screen sleep (not whole computer sleeo, only display) and latest kernels. When the computer screen goes to sleep it won’t wake up anymore. No mouse cursor nor i can change to tty (Strg + Alt + F1 …). The journals logs are also empty and only a hard reset helps. I’ve tested it with the lastest Linux Kernel 6.6.6 and 6.6.7. Funnily if the whole computer goes to sleep (for example Sleep, Hybrid Sleep or Hibernate), and i disable Screen Sleep before, the screen wakes up. The problem exists only when the screen goes to sleep. With older kernels (i don't know the exact version, i think before 6.6.x) it does work. I've tested the same behaviour on OpenSUSE Tumbleweed and Arch Linux. Also i changed to Wayland, but the same problem. Info for my System: Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 PRO 7840U w/ Radeon 780M Graphics Memory: 30,1 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 21F80041GE System Version: ThinkPad T14s Gen 4 Maybe someone have an idea. Thank you very much. Best regards! -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218274] AMD r9 m380, 2015,27 imac - amdgpu wont work
https://bugzilla.kernel.org/show_bug.cgi?id=218274 Artem S. Tashkinov (a...@gmx.com) changed: What|Removed |Added Status|NEW |RESOLVED CC||a...@gmx.com Resolution|--- |ANSWERED --- Comment #2 from Artem S. Tashkinov (a...@gmx.com) --- Please report here instead: https://gitlab.freedesktop.org/drm/amd/-/issues -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218274] AMD r9 m380, 2015,27 imac - amdgpu wont work
https://bugzilla.kernel.org/show_bug.cgi?id=218274 Pukurasa (pukur...@gmail.com) changed: What|Removed |Added Kernel Version||6.6.6 -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218274] AMD r9 m380, 2015,27 imac - amdgpu wont work
https://bugzilla.kernel.org/show_bug.cgi?id=218274 --- Comment #1 from Pukurasa (pukur...@gmail.com) --- Kernel 6.6 and up, havn`t used anything earlier than that -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218274] New: AMD r9 m380, 2015,27 imac - amdgpu wont work
https://bugzilla.kernel.org/show_bug.cgi?id=218274 Bug ID: 218274 Summary: AMD r9 m380, 2015,27 imac - amdgpu wont work Product: Drivers Version: 2.5 Hardware: All OS: Linux Status: NEW Severity: high Priority: P3 Component: Video(DRI - non Intel) Assignee: drivers_video-...@kernel-bugs.osdl.org Reporter: pukur...@gmail.com Regression: No I`v tried adding amdgpu.cik_support=1 params to kernel, tried blacklisting radeon drivers, tried using nobara linux patched kernel to enable amdgpu for si/cik cards. All of those methods end up PC being stuck on boot, it will throw some artfacts on black screen and will not load into KDE LOGS from journalctl that seem related to gpu: dec 16 02:05:27 fedora kernel: PCI: Using ACPI for IRQ routing dec 16 02:05:27 fedora kernel: PCI: pci_cache_line_size set to 64 bytes dec 16 02:05:27 fedora kernel: e820: reserve RAM buffer [mem 0x00058000-0x0005] dec 16 02:05:27 fedora kernel: e820: reserve RAM buffer [mem 0x0009e000-0x0009] dec 16 02:05:27 fedora kernel: e820: reserve RAM buffer [mem 0x7de65018-0x7fff] dec 16 02:05:27 fedora kernel: e820: reserve RAM buffer [mem 0x7de77018-0x7fff] dec 16 02:05:27 fedora kernel: e820: reserve RAM buffer [mem 0x83e01000-0x83ff] dec 16 02:05:27 fedora kernel: e820: reserve RAM buffer [mem 0x84e48000-0x87ff] dec 16 02:05:27 fedora kernel: e820: reserve RAM buffer [mem 0x8507e000-0x87ff] dec 16 02:05:27 fedora kernel: e820: reserve RAM buffer [mem 0x8ac7f000-0x8bff] dec 16 02:05:27 fedora kernel: e820: reserve RAM buffer [mem 0x8b00-0x8bff] dec 16 02:05:27 fedora kernel: e820: reserve RAM buffer [mem 0x66f00-0x66fff] dec 16 02:05:27 fedora kernel: pci :01:00.0: vgaarb: setting as boot VGA device dec 16 02:05:27 fedora kernel: pci :01:00.0: vgaarb: bridge control possible dec 16 02:05:27 fedora kernel: pci :01:00.0: vgaarb: VGA device added: decodes=io+mem,owns=none,locks=none dec 16 02:05:27 fedora kernel: vgaarb: loaded --- dec 16 02:05:27 fedora kernel: ACPI: video: [Firmware Bug]: ACPI(GFX0) defines _DOD but not _DOS dec 16 02:05:27 fedora kernel: ACPI: video: Video Device [GFX0] (multi-head: yes rom: no post: no) dec 16 02:05:27 fedora kernel: input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:01/LNXVIDEO:00/input/input8 dec 16 02:05:27 fedora systemd[1]: Mounted sys-kernel-config.mount - Kernel Configuration File System. dec 16 02:05:27 fedora systemd[1]: Reached target sysinit.target - System Initialization. dec 16 02:05:27 fedora kernel: tg3 :03:00.0 enp3s0f0: renamed from eth0 dec 16 02:05:27 fedora kernel: [drm] radeon kernel modesetting enabled. dec 16 02:05:27 fedora kernel: radeon :01:00.0: CIK support disabled by module param dec 16 02:05:28 fedora kernel: BTRFS: device label fedora devid 1 transid 19386 /dev/sda6 scanned by (udev-worker) (384) dec 16 02:05:28 fedora systemd[1]: Found device dev-disk-by\x2duuid-0f85a4ef\x2d0d63\x2d4701\x2dace8\x2d7b12e7af2d68.device - APPLE_HDD_ST1000DM003 fedora. dec 16 02:05:28 fedora systemd[1]: Reached target initrd-root-device.target - Initrd Root Device. dec 16 02:05:30 fedora kernel: [drm] amdgpu kernel modesetting enabled. dec 16 02:05:30 fedora kernel: amdgpu: Virtual CRAT table created for CPU dec 16 02:05:30 fedora kernel: amdgpu: Topology: Add CPU node dec 16 02:05:30 fedora kernel: [drm] initializing kernel modesetting (BONAIRE 0x1002:0x6640 0x106B:0x014B 0x80). dec 16 02:05:30 fedora kernel: [drm] register mmio base: 0x9250 dec 16 02:05:30 fedora kernel: [drm] register mmio size: 262144 dec 16 02:05:30 fedora kernel: [drm] add ip block number 0 dec 16 02:05:30 fedora kernel: [drm] add ip block number 1 dec 16 02:05:30 fedora kernel: [drm] add ip block number 2 dec 16 02:05:30 fedora kernel: [drm] add ip block number 3 dec 16 02:05:30 fedora kernel: [drm] add ip block number 4 dec 16 02:05:30 fedora kernel: [drm] add ip block number 5 dec 16 02:05:30 fedora kernel: [drm] add ip block number 6 dec 16 02:05:30 fedora kernel: [drm] add ip block number 7 dec 16 02:05:30 fedora kernel: [drm] add ip block number 8 dec 16 02:05:30 fedora kernel: amdgpu :01:00.0: amdgpu: Fetched VBIOS from VFCT dec 16 02:05:30 fedora kernel: amdgpu: ATOM BIOS: 113-C6005T-009 dec 16 02:05:30 fedora kernel: kfd kfd: amdgpu: BONAIRE not supported in kfd dec 16 02:05:30 fedora kernel: amdgpu :01:00.0: vgaarb: deactivate vga console dec 16 02:05:30 fedora kernel: amdgpu :01:00.0: amdgpu: Trusted Memory Zone (TMZ) feature not supported dec 16 02:05:30 fedora kernel: [drm] PCIE gen 3 link speeds already enabled dec 16 02:05:30 fedora kernel: [drm] vm size is 128 GB, 2 levels, block size is 10-bit, fragment size is 9-bit dec 16 02:05:30 fedora kernel: amdgpu
[Bug 218250] Regression nouveau driver
https://bugzilla.kernel.org/show_bug.cgi?id=218250 --- Comment #4 from Jaime Pérez (19.jaime...@gmail.com) --- Created attachment 305589 --> https://bugzilla.kernel.org/attachment.cgi?id=305589=edit dmesg wo commit -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218250] Regression nouveau driver
https://bugzilla.kernel.org/show_bug.cgi?id=218250 Artem S. Tashkinov (a...@gmx.com) changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |ANSWERED --- Comment #3 from Artem S. Tashkinov (a...@gmx.com) --- Please report here instead: https://gitlab.freedesktop.org/drm/nouveau/-/issues/ -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218250] Regression nouveau driver
https://bugzilla.kernel.org/show_bug.cgi?id=218250 --- Comment #2 from Jaime Pérez (19.jaime...@gmail.com) --- No graphical env [ 439.049257] [ cut here ] [ 439.049262] WARNING: CPU: 5 PID: 67651 at include/drm/ttm/ttm_resource.h:313 nouveau_ttm_fini+0x216/0x2c0 [nouveau] [ 439.049609] Modules linked in: nouveau(E+) rfcomm snd_seq_dummy snd_hrtimer xt_nat xt_tcpudp veth xt_conntrack nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user xfrm_algo xt_addrtype nft_compat nf_tables nfnetlink br_netfilter bridge stp llc ccm overlay cmac algif_hash algif_skcipher af_alg bnep binfmt_misc nls_iso8859_1 snd_hda_codec_hdmi snd_ctl_led snd_hda_codec_realtek snd_hda_codec_generic snd_soc_avs ledtrig_audio snd_soc_hda_codec snd_hda_ext_core snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec snd_hda_core snd_hwdep snd_pcm intel_rapl_msr intel_rapl_common intel_tcc_cooling x86_pkg_temp_thermal snd_seq_midi intel_powerclamp snd_seq_midi_event ath10k_pci snd_rawmidi coretemp uvcvideo btusb videobuf2_vmalloc btrtl ath10k_core btintel snd_seq uvc ath rtsx_usb_ms videobuf2_memops kvm_intel btbcm btmtk mei_pxp mei_hdcp memstick snd_seq_device videobuf2_v4l2 kvm mac80211 bluetooth snd_timer [ 439.049740] videodev snd acer_wmi videobuf2_common ecdh_generic rapl intel_cstate intel_wmi_thunderbolt mc wmi_bmof joydev sparse_keymap ecc soundcore ee1004 mei_me cfg80211 libarc4 mei intel_pch_thermal acpi_pad hid_multitouch input_leds mac_hid serio_raw msr parport_pc ppdev lp parport efi_pstore dmi_sysfs ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq libcrc32c dm_mirror dm_region_hash dm_log rtsx_usb_sdmmc rtsx_usb usbhid i915 drm_gpuvm mxm_wmi drm_exec gpu_sched drm_buddy i2c_algo_bit drm_ttm_helper ttm drm_display_helper hid_generic cec rc_core i2c_hid_acpi i2c_hid crct10dif_pclmul crc32_pclmul drm_kms_helper ghash_clmulni_intel hid sha512_ssse3 i2c_i801 r8169 sha256_ssse3 intel_lpss_pci nvme sha1_ssse3 realtek ahci intel_lpss i2c_smbus video drm nvme_core xhci_pci libahci idma64 xhci_pci_renesas wmi pinctrl_sunrisepoint aesni_intel crypto_simd cryptd [last unloaded: nouveau] [ 439.049875] CPU: 5 PID: 67651 Comm: insmod Tainted: GW E 6.7.0-rc1+ #170 [ 439.049881] Hardware name: Acer Aspire VX5-591G/Wish_KLS, BIOS V1.06 07/07/2017 [ 439.049884] RIP: 0010:nouveau_ttm_fini+0x216/0x2c0 [nouveau] [ 439.050230] Code: 41 5c 41 5d 41 5e 41 5f 5d 31 c0 31 d2 31 c9 31 f6 31 ff c3 cc cc cc cc be 02 00 00 00 4c 89 ef e8 1f 9d e7 ff e9 bb fe ff ff <0f> 0b e9 0c ff ff ff 0f 0b e9 46 fe ff ff be 03 00 00 00 48 89 55 [ 439.050235] RSP: 0018:c900092c37e0 EFLAGS: 00010206 [ 439.050240] RAX: 888123879ab0 RBX: 888123879ab0 RCX: 8881920f9838 [ 439.050244] RDX: 888123879a80 RSI: RDI: [ 439.050247] RBP: c900092c3818 R08: R09: [ 439.050250] R10: R11: R12: 888123603800 [ 439.050253] R13: 88811d1ccc50 R14: 88811d1cc000 R15: [ 439.050256] FS: 7fbb9318b040() GS:5ed4() knlGS: [ 439.050260] CS: 0010 DS: ES: CR0: 80050033 [ 439.050264] CR2: 7fc0c587dec4 CR3: 00011e104002 CR4: 003706f0 [ 439.050268] Call Trace: [ 439.050271] [ 439.050275] ? show_regs+0x6d/0x80 [ 439.050284] ? __warn+0x89/0x160 [ 439.050292] ? nouveau_ttm_fini+0x216/0x2c0 [nouveau] [ 439.050626] ? report_bug+0x17e/0x1b0 [ 439.050634] ? handle_bug+0x46/0x90 [ 439.050641] ? exc_invalid_op+0x18/0x80 [ 439.050646] ? asm_exc_invalid_op+0x1b/0x20 [ 439.050655] ? nouveau_ttm_fini+0x216/0x2c0 [nouveau] [ 439.050966] ? kfree+0x78/0x120 [ 439.050975] nouveau_drm_device_init+0x1a2/0x9b0 [nouveau] [ 439.051347] ? pci_enable_device_flags+0x27/0x180 [ 439.051356] ? drmm_add_final_kfree+0x26/0x70 [drm] [ 439.051494] nouveau_drm_probe+0x137/0x280 [nouveau] [ 439.051867] local_pci_probe+0x44/0xb0 [ 439.051876] pci_device_probe+0xc5/0x280 [ 439.051885] really_probe+0x1c9/0x430 [ 439.051893] __driver_probe_device+0x8c/0x190 [ 439.051900] driver_probe_device+0x24/0xd0 [ 439.051906] __driver_attach+0x10b/0x210 [ 439.051912] ? __pfx___driver_attach+0x10/0x10 [ 439.051918] bus_for_each_dev+0x8a/0xf0 [ 439.051925] driver_attach+0x1e/0x30 [ 439.051930] bus_add_driver+0x127/0x240 [ 439.051937] driver_register+0x5e/0x130 [ 439.051945] ? __pfx_nouveau_drm_init+0x10/0x10 [nouveau] [ 439.052209] __pci_register_driver+0x62/0x70 [ 439.052217] nouveau_drm_init+0x177/0xff0 [nouveau] [ 439.052452] do_one_initcall+0x5b/0x340 [ 439.052463] do_init_module+0x68/0x260 [ 439.052469] load_module+0x21a9/0x2510 [ 439.052485] init_module_from_file+0x97/0xe0 [ 439.052489] ? init_module_from_file+0x97/0xe0 [ 439.052498] idempotent_init_module+0x11c/0x2b0 [
[Bug 218250] Regression nouveau driver
https://bugzilla.kernel.org/show_bug.cgi?id=218250
Bagas Sanjaya (bagasdo...@gmail.com) changed:
What|Removed |Added
CC||bagasdo...@gmail.com
--- Comment #1 from Bagas Sanjaya (bagasdo...@gmail.com) ---
(In reply to Jaime Pérez from comment #0)
> Created attachment 305577 [details]
> dmesg
>
> ae1aadb1eb8d3cbc52e42bee71d67bd4a71f9f07 is the first bad commit
> commit ae1aadb1eb8d3cbc52e42bee71d67bd4a71f9f07
> Author: Dave Airlie
> Date: Thu Nov 16 00:39:33 2023 +1000
>
> nouveau: don't fail driver load if no display hw present.
>
> If we get back ENODEV don't fail load. There are nvidia devices
> that don't have display blocks and the driver should work on those.
>
> Fixes: 15740541e8f0 ("drm/nouveau/devinit/tu102-: prepare for GSP-RM")
> Link: https://gitlab.freedesktop.org/drm/nouveau/-/issues/270
> Signed-off-by: Dave Airlie
> Signed-off-by: Danilo Krummrich
> Link:
> https://patchwork.freedesktop.org/patch/msgid/20231115143933.261287-1-
> airl...@gmail.com
>
> drivers/gpu/drm/nouveau/nouveau_display.c | 5 +
> 1 file changed, 5 insertions(+)
What problem?
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
[Bug 218250] Regression nouveau driver
https://bugzilla.kernel.org/show_bug.cgi?id=218250 Jaime Pérez (19.jaime...@gmail.com) changed: What|Removed |Added Bisected commit-id||ae1aadb1eb8d3cbc52e42bee71d ||67bd4a71f9f07 Kernel Version||6.7.0-rc1+ Regression|No |Yes -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218250] New: Regression nouveau driver
https://bugzilla.kernel.org/show_bug.cgi?id=218250
Bug ID: 218250
Summary: Regression nouveau driver
Product: Drivers
Version: 2.5
Hardware: All
OS: Linux
Status: NEW
Severity: blocking
Priority: P3
Component: Video(DRI - non Intel)
Assignee: drivers_video-...@kernel-bugs.osdl.org
Reporter: 19.jaime...@gmail.com
Regression: No
Created attachment 305577
--> https://bugzilla.kernel.org/attachment.cgi?id=305577=edit
dmesg
ae1aadb1eb8d3cbc52e42bee71d67bd4a71f9f07 is the first bad commit
commit ae1aadb1eb8d3cbc52e42bee71d67bd4a71f9f07
Author: Dave Airlie
Date: Thu Nov 16 00:39:33 2023 +1000
nouveau: don't fail driver load if no display hw present.
If we get back ENODEV don't fail load. There are nvidia devices
that don't have display blocks and the driver should work on those.
Fixes: 15740541e8f0 ("drm/nouveau/devinit/tu102-: prepare for GSP-RM")
Link: https://gitlab.freedesktop.org/drm/nouveau/-/issues/270
Signed-off-by: Dave Airlie
Signed-off-by: Danilo Krummrich
Link:
https://patchwork.freedesktop.org/patch/msgid/20231115143933.261287-1-airl...@gmail.com
drivers/gpu/drm/nouveau/nouveau_display.c | 5 +
1 file changed, 5 insertions(+)
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
[Bug 218241] amdgpu: MODE2 reset
https://bugzilla.kernel.org/show_bug.cgi?id=218241 Artem S. Tashkinov (a...@gmx.com) changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |ANSWERED --- Comment #1 from Artem S. Tashkinov (a...@gmx.com) --- Please report here instead: https://gitlab.freedesktop.org/drm/amd/-/issues -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218241] New: amdgpu: MODE2 reset
https://bugzilla.kernel.org/show_bug.cgi?id=218241 Bug ID: 218241 Summary: amdgpu: MODE2 reset Product: Drivers Version: 2.5 Kernel Version: 6.6.5 Hardware: AMD OS: Linux Status: NEW Severity: normal Priority: P3 Component: Video(DRI - non Intel) Assignee: drivers_video-...@kernel-bugs.osdl.org Reporter: support...@protonmail.com Regression: No Created attachment 305568 --> https://bugzilla.kernel.org/attachment.cgi?id=305568=edit dmesg output I compiled and installed Kernel 6.6.5 today and got a short black screen. I attached the dmesg output. Because i saw changes in DRM, amdgpu in the changelog, and i never had a reset under 6.6.4 and many Kernel versions before, i think, it's releated to these changes. Hardware: AMD Ryzen 7 5700U with Radeon Graphics -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 209129] HW related error message under Gnome important tab
https://bugzilla.kernel.org/show_bug.cgi?id=209129 Ken Sharp (imwellcushtymel...@gmail.com) changed: What|Removed |Added CC||imwellcushtymel...@gmail.co ||m --- Comment #15 from Ken Sharp (imwellcushtymel...@gmail.com) --- I've opened a bug report at Launchpad for this but cannot say for certain there is a kernel bug here. https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2045951 -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218221] Nouveau GSP fail on command cli:0xc1d0000
https://bugzilla.kernel.org/show_bug.cgi?id=218221 --- Comment #5 from airl...@gmail.com --- Yes I'd file that against mesa, I don't think we are quite there with zink support yet, trying to push on it a bit. On Tue, 5 Dec 2023 at 21:42, wrote: > > https://bugzilla.kernel.org/show_bug.cgi?id=218221 > > --- Comment #3 from marc barbier (mmarc...@gmail.com) --- > (In reply to airlied from comment #2) > > Can't remember my bz, but all those errors are fine, I've sent patches > > to clean them up so we don't report them in dmesg anymore. > > > > On Tue, 5 Dec 2023 at 01:12, wrote: > > > > > > https://bugzilla.kernel.org/show_bug.cgi?id=218221 > > > > > > Bug ID: 218221 > > >Summary: Nouveau GSP fail on command cli:0xc1d > > >Product: Drivers > > >Version: 2.5 > > > Hardware: All > > > OS: Linux > > > Status: NEW > > > Severity: normal > > > Priority: P3 > > > Component: Video(DRI - non Intel) > > > Assignee: drivers_video-...@kernel-bugs.osdl.org > > > Reporter: mmarc...@gmail.com > > > Regression: No > > > > > > Running Linux 6.7.0-rc3 on Gentoo Linux > > > > > > I'm using a 3070(laptop) with the command line argument > > > nouveau.config=NvGspRm=1 > > > > > > I have confirmed that the Gsp firmware in present in my system, and I'm > > > running > > > mesa 23.3.0 > > > > > > This should allow the nouveau kernel driver to call the GSP firmware for > > > tasks > > > such as reclocking. > > > > > > As my system is a laptop my main GPU is an integrated radeon gpu so > > starting > > > Xorg doesn't require nouveau to work. > > > > > > Once X11 is started I can try to launch vulkan applications which causes > > the > > > following errors to appear in the kernel log. > > > > > > > dmesg > > > [ 17.007772] nouveau :01:00.0: gsp:msg fn:4123 len:0x24/0x4 res:0x0 > > > resp:0x0 > > > [ 17.010650] nouveau :01:00.0: gsp:msg fn:4108 len:0x38/0x18 > res:0x0 > > > resp:0x0 > > > [ 17.010945] nouveau :01:00.0: gsp:msg fn:4108 len:0x40/0x20 > res:0x0 > > > resp:0x0 > > > [15217.991692] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 > > ctrl > > > cmd:0x00731341 failed: 0x > > > [15217.992913] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 > > ctrl > > > cmd:0x00731341 failed: 0x > > > [15217.994155] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 > > ctrl > > > cmd:0x00731341 failed: 0x > > > [15217.995408] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 > > ctrl > > > cmd:0x00731341 failed: 0x > > > [15217.996738] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 > > ctrl > > > cmd:0x00731341 failed: 0x > > > [15217.997859] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 > > ctrl > > > cmd:0x00731341 failed: 0x > > > [15217.999154] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 > > ctrl > > > cmd:0x00731341 failed: 0x > > > [15218.000392] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 > > ctrl > > > cmd:0x00731341 failed: 0x > > > [15218.001799] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 > > ctrl > > > cmd:0x00731341 failed: 0x > > > [15218.003055] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 > > ctrl > > > cmd:0x00731341 failed: 0x > > > [15218.004271] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 > > ctrl > > > cmd:0x00731341 failed: 0x > > > [15218.005615] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 > > ctrl > > > cmd:0x00731341 failed: 0x > > > [15218.007023] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 > > ctrl > > > cmd:0x00731341 failed: 0x > > > [15218.008281] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 > > ctrl > > > cmd:0x00731341 failed: 0x > > > [15218.009543] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 > > ctrl > > > cmd:0x00731341 failed: 0x > > > [15218.010843] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 > > ctrl > > > cmd:0x00731341 failed: 0x > > > [15218.012054] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 > > ctrl > > > cmd:0x00731341 failed: 0x > > > [15218.013295] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 > > ctrl > > > cmd:0x00731341 failed: 0x > > > [15218.014570] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 > > ctrl > > > cmd:0x00731341 failed: 0x > > > [15218.015841] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 > > ctrl > > > cmd:0x00731341 failed: 0x > > > [15218.017084] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 > > ctrl > > > cmd:0x00731341 failed: 0x > > > [15218.018206] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 > > ctrl > > > cmd:0x00731341 failed: 0x > > > [15218.019532] nouveau :01:00.0: gsp:
[Bug 218221] Nouveau GSP fail on command cli:0xc1d0000
https://bugzilla.kernel.org/show_bug.cgi?id=218221 marc barbier (mmarc...@gmail.com) changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |CODE_FIX --- Comment #4 from marc barbier (mmarc...@gmail.com) --- I just compiled rc4 and the errors no longer shows. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218221] Nouveau GSP fail on command cli:0xc1d0000
https://bugzilla.kernel.org/show_bug.cgi?id=218221 --- Comment #3 from marc barbier (mmarc...@gmail.com) --- (In reply to airlied from comment #2) > Can't remember my bz, but all those errors are fine, I've sent patches > to clean them up so we don't report them in dmesg anymore. > > On Tue, 5 Dec 2023 at 01:12, wrote: > > > > https://bugzilla.kernel.org/show_bug.cgi?id=218221 > > > > Bug ID: 218221 > >Summary: Nouveau GSP fail on command cli:0xc1d > >Product: Drivers > >Version: 2.5 > > Hardware: All > > OS: Linux > > Status: NEW > > Severity: normal > > Priority: P3 > > Component: Video(DRI - non Intel) > > Assignee: drivers_video-...@kernel-bugs.osdl.org > > Reporter: mmarc...@gmail.com > > Regression: No > > > > Running Linux 6.7.0-rc3 on Gentoo Linux > > > > I'm using a 3070(laptop) with the command line argument > > nouveau.config=NvGspRm=1 > > > > I have confirmed that the Gsp firmware in present in my system, and I'm > > running > > mesa 23.3.0 > > > > This should allow the nouveau kernel driver to call the GSP firmware for > > tasks > > such as reclocking. > > > > As my system is a laptop my main GPU is an integrated radeon gpu so > starting > > Xorg doesn't require nouveau to work. > > > > Once X11 is started I can try to launch vulkan applications which causes > the > > following errors to appear in the kernel log. > > > > > dmesg > > [ 17.007772] nouveau :01:00.0: gsp:msg fn:4123 len:0x24/0x4 res:0x0 > > resp:0x0 > > [ 17.010650] nouveau :01:00.0: gsp:msg fn:4108 len:0x38/0x18 res:0x0 > > resp:0x0 > > [ 17.010945] nouveau :01:00.0: gsp:msg fn:4108 len:0x40/0x20 res:0x0 > > resp:0x0 > > [15217.991692] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 > ctrl > > cmd:0x00731341 failed: 0x > > [15217.992913] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 > ctrl > > cmd:0x00731341 failed: 0x > > [15217.994155] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 > ctrl > > cmd:0x00731341 failed: 0x > > [15217.995408] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 > ctrl > > cmd:0x00731341 failed: 0x > > [15217.996738] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 > ctrl > > cmd:0x00731341 failed: 0x > > [15217.997859] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 > ctrl > > cmd:0x00731341 failed: 0x > > [15217.999154] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 > ctrl > > cmd:0x00731341 failed: 0x > > [15218.000392] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 > ctrl > > cmd:0x00731341 failed: 0x > > [15218.001799] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 > ctrl > > cmd:0x00731341 failed: 0x > > [15218.003055] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 > ctrl > > cmd:0x00731341 failed: 0x > > [15218.004271] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 > ctrl > > cmd:0x00731341 failed: 0x > > [15218.005615] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 > ctrl > > cmd:0x00731341 failed: 0x > > [15218.007023] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 > ctrl > > cmd:0x00731341 failed: 0x > > [15218.008281] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 > ctrl > > cmd:0x00731341 failed: 0x > > [15218.009543] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 > ctrl > > cmd:0x00731341 failed: 0x > > [15218.010843] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 > ctrl > > cmd:0x00731341 failed: 0x > > [15218.012054] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 > ctrl > > cmd:0x00731341 failed: 0x > > [15218.013295] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 > ctrl > > cmd:0x00731341 failed: 0x > > [15218.014570] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 > ctrl > > cmd:0x00731341 failed: 0x > > [15218.015841] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 > ctrl > > cmd:0x00731341 failed: 0x > > [15218.017084] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 > ctrl > > cmd:0x00731341 failed: 0x > > [15218.018206] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 > ctrl > > cmd:0x00731341 failed: 0x > > [15218.019532] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 > ctrl > > cmd:0x00731341 failed: 0x > > [15218.020804] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 > ctrl > > cmd:0x00731341 failed: 0x > > [15218.022064] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 > ctrl > > cmd:0x00731341 failed: 0x > > [15218.023324] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 > ctrl > > cmd:0x00731341 failed: 0x > > [15218.024644] nouveau :01:00.0: gsp: cli:0xc1d2
[Bug 218221] Nouveau GSP fail on command cli:0xc1d0000
https://bugzilla.kernel.org/show_bug.cgi?id=218221 --- Comment #2 from airl...@gmail.com --- Can't remember my bz, but all those errors are fine, I've sent patches to clean them up so we don't report them in dmesg anymore. On Tue, 5 Dec 2023 at 01:12, wrote: > > https://bugzilla.kernel.org/show_bug.cgi?id=218221 > > Bug ID: 218221 >Summary: Nouveau GSP fail on command cli:0xc1d >Product: Drivers >Version: 2.5 > Hardware: All > OS: Linux > Status: NEW > Severity: normal > Priority: P3 > Component: Video(DRI - non Intel) > Assignee: drivers_video-...@kernel-bugs.osdl.org > Reporter: mmarc...@gmail.com > Regression: No > > Running Linux 6.7.0-rc3 on Gentoo Linux > > I'm using a 3070(laptop) with the command line argument > nouveau.config=NvGspRm=1 > > I have confirmed that the Gsp firmware in present in my system, and I'm > running > mesa 23.3.0 > > This should allow the nouveau kernel driver to call the GSP firmware for > tasks > such as reclocking. > > As my system is a laptop my main GPU is an integrated radeon gpu so starting > Xorg doesn't require nouveau to work. > > Once X11 is started I can try to launch vulkan applications which causes the > following errors to appear in the kernel log. > > > dmesg > [ 17.007772] nouveau :01:00.0: gsp:msg fn:4123 len:0x24/0x4 res:0x0 > resp:0x0 > [ 17.010650] nouveau :01:00.0: gsp:msg fn:4108 len:0x38/0x18 res:0x0 > resp:0x0 > [ 17.010945] nouveau :01:00.0: gsp:msg fn:4108 len:0x40/0x20 res:0x0 > resp:0x0 > [15217.991692] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 ctrl > cmd:0x00731341 failed: 0x > [15217.992913] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 ctrl > cmd:0x00731341 failed: 0x > [15217.994155] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 ctrl > cmd:0x00731341 failed: 0x > [15217.995408] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 ctrl > cmd:0x00731341 failed: 0x > [15217.996738] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 ctrl > cmd:0x00731341 failed: 0x > [15217.997859] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 ctrl > cmd:0x00731341 failed: 0x > [15217.999154] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 ctrl > cmd:0x00731341 failed: 0x > [15218.000392] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 ctrl > cmd:0x00731341 failed: 0x > [15218.001799] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 ctrl > cmd:0x00731341 failed: 0x > [15218.003055] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 ctrl > cmd:0x00731341 failed: 0x > [15218.004271] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 ctrl > cmd:0x00731341 failed: 0x > [15218.005615] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 ctrl > cmd:0x00731341 failed: 0x > [15218.007023] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 ctrl > cmd:0x00731341 failed: 0x > [15218.008281] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 ctrl > cmd:0x00731341 failed: 0x > [15218.009543] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 ctrl > cmd:0x00731341 failed: 0x > [15218.010843] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 ctrl > cmd:0x00731341 failed: 0x > [15218.012054] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 ctrl > cmd:0x00731341 failed: 0x > [15218.013295] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 ctrl > cmd:0x00731341 failed: 0x > [15218.014570] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 ctrl > cmd:0x00731341 failed: 0x > [15218.015841] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 ctrl > cmd:0x00731341 failed: 0x > [15218.017084] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 ctrl > cmd:0x00731341 failed: 0x > [15218.018206] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 ctrl > cmd:0x00731341 failed: 0x > [15218.019532] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 ctrl > cmd:0x00731341 failed: 0x > [15218.020804] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 ctrl > cmd:0x00731341 failed: 0x > [15218.022064] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 ctrl > cmd:0x00731341 failed: 0x > [15218.023324] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 ctrl > cmd:0x00731341 failed: 0x > [15218.024644] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 ctrl > cmd:0x00731341 failed: 0x > [15218.025870] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 ctrl > cmd:0x00731341 failed: 0x > [15218.027143] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 ctrl > cmd:0x00731341 failed: 0x > [15218.028388] nouveau
[Bug 218221] Nouveau GSP fail on command cli:0xc1d0000
https://bugzilla.kernel.org/show_bug.cgi?id=218221 marc barbier (mmarc...@gmail.com) changed: What|Removed |Added Kernel Version||6.7.0-rc3 -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218221] Nouveau GSP fail on command cli:0xc1d0000
https://bugzilla.kernel.org/show_bug.cgi?id=218221 --- Comment #1 from marc barbier (mmarc...@gmail.com) --- Created attachment 305539 --> https://bugzilla.kernel.org/attachment.cgi?id=305539=edit dmesg log -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218221] New: Nouveau GSP fail on command cli:0xc1d0000
https://bugzilla.kernel.org/show_bug.cgi?id=218221 Bug ID: 218221 Summary: Nouveau GSP fail on command cli:0xc1d Product: Drivers Version: 2.5 Hardware: All OS: Linux Status: NEW Severity: normal Priority: P3 Component: Video(DRI - non Intel) Assignee: drivers_video-...@kernel-bugs.osdl.org Reporter: mmarc...@gmail.com Regression: No Running Linux 6.7.0-rc3 on Gentoo Linux I'm using a 3070(laptop) with the command line argument nouveau.config=NvGspRm=1 I have confirmed that the Gsp firmware in present in my system, and I'm running mesa 23.3.0 This should allow the nouveau kernel driver to call the GSP firmware for tasks such as reclocking. As my system is a laptop my main GPU is an integrated radeon gpu so starting Xorg doesn't require nouveau to work. Once X11 is started I can try to launch vulkan applications which causes the following errors to appear in the kernel log. > dmesg [ 17.007772] nouveau :01:00.0: gsp:msg fn:4123 len:0x24/0x4 res:0x0 resp:0x0 [ 17.010650] nouveau :01:00.0: gsp:msg fn:4108 len:0x38/0x18 res:0x0 resp:0x0 [ 17.010945] nouveau :01:00.0: gsp:msg fn:4108 len:0x40/0x20 res:0x0 resp:0x0 [15217.991692] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 ctrl cmd:0x00731341 failed: 0x [15217.992913] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 ctrl cmd:0x00731341 failed: 0x [15217.994155] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 ctrl cmd:0x00731341 failed: 0x [15217.995408] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 ctrl cmd:0x00731341 failed: 0x [15217.996738] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 ctrl cmd:0x00731341 failed: 0x [15217.997859] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 ctrl cmd:0x00731341 failed: 0x [15217.999154] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 ctrl cmd:0x00731341 failed: 0x [15218.000392] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 ctrl cmd:0x00731341 failed: 0x [15218.001799] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 ctrl cmd:0x00731341 failed: 0x [15218.003055] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 ctrl cmd:0x00731341 failed: 0x [15218.004271] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 ctrl cmd:0x00731341 failed: 0x [15218.005615] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 ctrl cmd:0x00731341 failed: 0x [15218.007023] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 ctrl cmd:0x00731341 failed: 0x [15218.008281] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 ctrl cmd:0x00731341 failed: 0x [15218.009543] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 ctrl cmd:0x00731341 failed: 0x [15218.010843] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 ctrl cmd:0x00731341 failed: 0x [15218.012054] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 ctrl cmd:0x00731341 failed: 0x [15218.013295] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 ctrl cmd:0x00731341 failed: 0x [15218.014570] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 ctrl cmd:0x00731341 failed: 0x [15218.015841] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 ctrl cmd:0x00731341 failed: 0x [15218.017084] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 ctrl cmd:0x00731341 failed: 0x [15218.018206] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 ctrl cmd:0x00731341 failed: 0x [15218.019532] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 ctrl cmd:0x00731341 failed: 0x [15218.020804] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 ctrl cmd:0x00731341 failed: 0x [15218.022064] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 ctrl cmd:0x00731341 failed: 0x [15218.023324] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 ctrl cmd:0x00731341 failed: 0x [15218.024644] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 ctrl cmd:0x00731341 failed: 0x [15218.025870] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 ctrl cmd:0x00731341 failed: 0x [15218.027143] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 ctrl cmd:0x00731341 failed: 0x [15218.028388] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 ctrl cmd:0x00731341 failed: 0x [15218.029801] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 ctrl cmd:0x00731341 failed: 0x [15218.031055] nouveau :01:00.0: gsp: cli:0xc1d2 obj:0x0073 ctrl cmd:0x00731341 failed: 0x Running ZINK also inform me that DRI3 is not available. > MESA_LOADER_DRIVER_OVERRIDE=zink glxgears WARNING: NVK is not a conformant Vulkan
[Bug 218168] amdgpu: kfd_topology.c warning: the frame size of 1408 bytes is larger than 1024 bytes
https://bugzilla.kernel.org/show_bug.cgi?id=218168 --- Comment #5 from Felix Kuehling (felix.kuehl...@amd.com) --- There are two patches that didn't make it into Linux 6.6 that reduce the stack size in kfd_topology_add_device. Can you check if those fix the problem? commit aa5a9b2ccda2fa834fddb4bd30a2ab831598f551 Author: Alex Deucher Date: Tue Sep 26 12:00:23 2023 -0400 drm/amdkfd: drop struct kfd_cu_info I think this was an abstraction back from when kfd supported both radeon and amdgpu. Since we just support amdgpu now, there is no more need for this and we can use the amdgpu structures directly. This also avoids having the kfd_cu_info structures on the stack when inlining which can blow up the stack. Cc: Arnd Bergmann Acked-by: Arnd Bergmann Reviewed-by: Felix Kuehling Acked-by: Christian König Signed-off-by: Alex Deucher commit 1f3b515578a1d73926993629a06a7f3b60535b59 Author: Alex Deucher Date: Thu Sep 21 10:32:09 2023 -0400 drm/amdkfd: reduce stack size in kfd_topology_add_device() kfd_topology.c:2082:1: warning: the frame size of 1440 bytes is larger than 1024 bytes Link: https://gitlab.freedesktop.org/drm/amd/-/issues/2866 Cc: Arnd Bergmann Acked-by: Arnd Bergmann Acked-by: Christian König Reviewed-by: Felix Kuehling Signed-off-by: Alex Deucher Regards, Felix On 2023-11-20 10:36, Hamza Mahfooz wrote: > + amd-gfx > + Felix > > On 11/20/23 10:16, bugzilla-dae...@kernel.org wrote: >> https://bugzilla.kernel.org/show_bug.cgi?id=218168 >> >> Bug ID: 218168 >> Summary: amdgpu: kfd_topology.c warning: the frame size >> of 1408 >> bytes is larger than 1024 bytes >> Product: Drivers >> Version: 2.5 >> Hardware: All >> OS: Linux >> Status: NEW >> Severity: normal >> Priority: P3 >> Component: Video(DRI - non Intel) >> Assignee: drivers_video-...@kernel-bugs.osdl.org >> Reporter: bluesun...@gmail.com >> Regression: No >> >> Trying to compile Linux 6.6.2 with GCC 13.2.1 and CONFIG_WERROR=y: >> >> [...] >> drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_topology.c: In function >> 'kfd_topology_add_device': >> drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_topology.c:2082:1: error: >> the frame >> size of 1408 bytes is larger than 1024 bytes >> [-Werror=frame-larger-than=] >> 2082 | } >> | ^ >> cc1: all warnings being treated as errors >> [...] >> -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218168] amdgpu: kfd_topology.c warning: the frame size of 1408 bytes is larger than 1024 bytes
https://bugzilla.kernel.org/show_bug.cgi?id=218168 Artem S. Tashkinov (a...@gmx.com) changed: What|Removed |Added URL||https://gitlab.freedesktop. ||org/drm/amd/-/issues/2866 -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218168] amdgpu: kfd_topology.c warning: the frame size of 1408 bytes is larger than 1024 bytes
https://bugzilla.kernel.org/show_bug.cgi?id=218168 --- Comment #4 from Artem S. Tashkinov (a...@gmx.com) --- Fixed by https://gitlab.freedesktop.org/drm/amd/uploads/26580b07cb9c763a0b840b9d705e0338/0001-drm-amdkfd-reduce-stack-size-in-kfd_topology_add_dev.patch -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218168] amdgpu: kfd_topology.c warning: the frame size of 1408 bytes is larger than 1024 bytes
https://bugzilla.kernel.org/show_bug.cgi?id=218168 Artem S. Tashkinov (a...@gmx.com) changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |ANSWERED --- Comment #2 from Artem S. Tashkinov (a...@gmx.com) --- Please report here: https://gitlab.freedesktop.org/drm/amd/-/issues -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218168] amdgpu: kfd_topology.c warning: the frame size of 1408 bytes is larger than 1024 bytes
https://bugzilla.kernel.org/show_bug.cgi?id=218168 --- Comment #1 from hamza.mahf...@amd.com --- + amd-gfx + Felix On 11/20/23 10:16, bugzilla-dae...@kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=218168 > > Bug ID: 218168 > Summary: amdgpu: kfd_topology.c warning: the frame size of 1408 > bytes is larger than 1024 bytes > Product: Drivers > Version: 2.5 >Hardware: All > OS: Linux > Status: NEW >Severity: normal >Priority: P3 > Component: Video(DRI - non Intel) >Assignee: drivers_video-...@kernel-bugs.osdl.org >Reporter: bluesun...@gmail.com > Regression: No > > Trying to compile Linux 6.6.2 with GCC 13.2.1 and CONFIG_WERROR=y: > > [...] > drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_topology.c: In function > 'kfd_topology_add_device': > drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_topology.c:2082:1: error: the frame > size of 1408 bytes is larger than 1024 bytes [-Werror=frame-larger-than=] > 2082 | } >| ^ > cc1: all warnings being treated as errors > [...] > -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218168] New: amdgpu: kfd_topology.c warning: the frame size of 1408 bytes is larger than 1024 bytes
https://bugzilla.kernel.org/show_bug.cgi?id=218168 Bug ID: 218168 Summary: amdgpu: kfd_topology.c warning: the frame size of 1408 bytes is larger than 1024 bytes Product: Drivers Version: 2.5 Hardware: All OS: Linux Status: NEW Severity: normal Priority: P3 Component: Video(DRI - non Intel) Assignee: drivers_video-...@kernel-bugs.osdl.org Reporter: bluesun...@gmail.com Regression: No Trying to compile Linux 6.6.2 with GCC 13.2.1 and CONFIG_WERROR=y: [...] drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_topology.c: In function 'kfd_topology_add_device': drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_topology.c:2082:1: error: the frame size of 1408 bytes is larger than 1024 bytes [-Werror=frame-larger-than=] 2082 | } | ^ cc1: all warnings being treated as errors [...] -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218141] fb: trapped write at 0000006000 on channel -1 [3fed0000 unknown] engine 06 [BAR] client 04 [PFIFO_WRITE] subclient 00 [FB] reason 00000002 [PAGE_NOT_PRESENT]
https://bugzilla.kernel.org/show_bug.cgi?id=218141 --- Comment #1 from sander44 (ionut_n2...@yahoo.com) --- Created attachment 305402 --> https://bugzilla.kernel.org/attachment.cgi?id=305402=edit dmesg nouveau -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218141] fb: trapped write at 0000006000 on channel -1 [3fed0000 unknown] engine 06 [BAR] client 04 [PFIFO_WRITE] subclient 00 [FB] reason 00000002 [PAGE_NOT_PRESENT]
https://bugzilla.kernel.org/show_bug.cgi?id=218141 sander44 (ionut_n2...@yahoo.com) changed: What|Removed |Added Kernel Version||6.6.1 -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218141] New: fb: trapped write at 0000006000 on channel -1 [3fed0000 unknown] engine 06 [BAR] client 04 [PFIFO_WRITE] subclient 00 [FB] reason 00000002 [PAGE_NOT_PRESENT]
https://bugzilla.kernel.org/show_bug.cgi?id=218141 Bug ID: 218141 Summary: fb: trapped write at 006000 on channel -1 [3fed unknown] engine 06 [BAR] client 04 [PFIFO_WRITE] subclient 00 [FB] reason 0002 [PAGE_NOT_PRESENT] Product: Drivers Version: 2.5 Hardware: All OS: Linux Status: NEW Severity: normal Priority: P3 Component: Video(DRI - non Intel) Assignee: drivers_video-...@kernel-bugs.osdl.org Reporter: ionut_n2...@yahoo.com Regression: No Hi Kernel Team, I notice today this: nouveau :65:00.0: fb: trapped write at 006000 on channel -1 [3fed unknown] engine 06 [BAR] client 04 [PFIFO_WRITE] subclient 00 [FB] reason 0002 [PAGE_NOT_PRESENT] Kernel: 6.6.1-vanilla Sporadic nouveau driver have issue with performance. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218134] Null pointer when rearranging screen layout in XFCE.
https://bugzilla.kernel.org/show_bug.cgi?id=218134 Artem S. Tashkinov (a...@gmx.com) changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |ANSWERED -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218134] Null pointer when rearranging screen layout in XFCE.
https://bugzilla.kernel.org/show_bug.cgi?id=218134 --- Comment #4 from Gerhard Mack (gm...@innerfire.net) --- I have opened the bug report as requested (https://gitlab.freedesktop.org/drm/amd/-/issues/2981) I also found this while I was digging in the logs and it was just prior to the crash: [ T8277] [drm] enabling link 2 failed: 15 [T735019] [drm] DM_MST: starting TM on aconnector: c46ac3ce [id: 90] [T735019] [drm] DM_MST: DP14, 4-lane link detected [ T1964] [drm] Downstream port present 1, type 0 [ T1964] [drm] Downstream port present 1, type 0 -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218134] Null pointer when rearranging screen layout in XFCE.
https://bugzilla.kernel.org/show_bug.cgi?id=218134 Bagas Sanjaya (bagasdo...@gmail.com) changed: What|Removed |Added CC||bagasdo...@gmail.com --- Comment #3 from Bagas Sanjaya (bagasdo...@gmail.com) --- (In reply to Gerhard Mack from comment #0) > If I attempt to change my screen layout in XFCE, I get a kernel NULL pointer > crash. This is very reproduceable. > > [ 50.275982] BUG: kernel NULL pointer dereference, address: > 0008 > [ 50.275988] #PF: supervisor read access in kernel mode > [ 50.275989] #PF: error_code(0x) - not-present page > [ 50.275991] PGD 0 P4D 0 > [ 50.275993] Oops: [#1] PREEMPT SMP NOPTI > [ 50.275995] CPU: 18 PID: 1931 Comm: Xorg Not tainted 6.6.1 #106 > d284c8807aa68b715e3e2f475c4079807a0b5cb5 > [ 50.275997] Hardware name: To Be Filled By O.E.M. B550 Taichi/B550 > Taichi, BIOS P3.20 09/27/2023 > [ 50.275999] RIP: 0010:drm_dp_atomic_find_time_slots+0x57/0x1e0 > [drm_display_helper] > [ 50.276007] Code: 0f 87 9d 01 00 00 48 8b 85 28 05 00 00 31 d2 48 63 80 > 88 00 00 00 41 3b 44 24 28 7d 0d 48 6b c0 28 49 03 44 24 30 48 8b 50 18 <48> > 8b 42 08 48 89 ee 48 89 df 8b 88 90 00 00 00 b8 01 00 00 00 d3 > [ 50.276008] RSP: 0018:ad10544b76d8 EFLAGS: 00010286 > [ 50.276010] RAX: 9409ea510ca0 RBX: 940994c46900 RCX: > 0002 > [ 50.276011] RDX: RSI: 940996bd0578 RDI: > 9409b11b7b00 > [ 50.276012] RBP: 94099317b800 R08: ad10544b7a58 R09: > 0001 > [ 50.276012] R10: R11: R12: > 9409b11b7b00 > [ 50.276013] R13: 940996bd0578 R14: 0224 R15: > 94c46900 > [ 50.276014] FS: 7f4296208ac0() GS:94187ee8() > knlGS: > [ 50.276015] CS: 0010 DS: ES: CR0: 80050033 > [ 50.276016] CR2: 0008 CR3: 00010612e000 CR4: > 00f50ee0 > [ 50.276017] PKRU: 5554 > [ 50.276018] Call Trace: > [ 50.276020] > [ 50.276021] ? __die_body+0x15/0x54 > [ 50.276026] ? page_fault_oops+0x323/0x36d > [ 50.276030] ? post_alloc_hook+0x9/0x50 > [ 50.276033] ? prep_new_page+0x2c/0x41 > [ 50.276035] ? get_page_from_freelist+0x6c4/0x7f6 > [ 50.276036] ? exc_page_fault+0x159/0x4f9 > [ 50.276039] ? asm_exc_page_fault+0x26/0x30 > [ 50.276043] ? drm_dp_atomic_find_time_slots+0x57/0x1e0 > [drm_display_helper 13cd3e40727f81da5f41f67251f92c3e185bfce2] > [ 50.276047] ? drm_dp_atomic_find_time_slots+0x21/0x1e0 > [drm_display_helper 13cd3e40727f81da5f41f67251f92c3e185bfce2] > [ 50.276051] compute_mst_dsc_configs_for_link+0x29b/0x7fd [amdgpu > 98fd76f1aa24e802b0010b76204b9775aacb3c0c] > [ 50.276121] ? free_tail_page_prepare+0xc0/0xdb > [ 50.276123] ? free_unref_page_commit+0x29/0xeb > [ 50.276127] compute_mst_dsc_configs_for_state+0x119/0x1a8 [amdgpu > 98fd76f1aa24e802b0010b76204b9775aacb3c0c] > [ 50.276178] amdgpu_dm_atomic_check+0x9ba/0xd9e [amdgpu > 98fd76f1aa24e802b0010b76204b9775aacb3c0c] > [ 50.276229] ? kmem_cache_debug_flags+0x5/0x11 > [ 50.276232] ? amdgpu_dm_connector_atomic_duplicate_state+0x24/0xa4 > [amdgpu 98fd76f1aa24e802b0010b76204b9775aacb3c0c] > [ 50.276280] ? kmem_cache_debug_flags+0x5/0x11 > [ 50.276281] ? slab_post_alloc_hook+0x70/0x17f > [ 50.276284] ? slab_pre_alloc_hook.constprop.0+0x49/0x14c > [ 50.276286] ? amdgpu_dm_connector_atomic_duplicate_state+0x24/0xa4 > [amdgpu 98fd76f1aa24e802b0010b76204b9775aacb3c0c] > [ 50.276344] ? __kmem_cache_alloc_node+0x10b/0x137 > [ 50.276345] drm_atomic_check_only+0x6df/0x812 > [ 50.276349] ? __drm_connector_put_safe+0x11/0x49 > [ 50.276351] drm_atomic_commit+0x6a/0xc1 > [ 50.276352] ? __drm_printfn_seq_file+0x17/0x17 > [ 50.276355] ? __drm_printfn_seq_file+0x17/0x17 > [ 50.276356] drm_atomic_connector_commit_dpms+0xc1/0xda > [ 50.276358] drm_mode_obj_set_property_ioctl+0xff/0x293 > [ 50.276361] ? drm_connector_set_obj_prop+0x63/0x63 > [ 50.276362] drm_connector_property_set_ioctl+0x36/0x51 > [ 50.276364] drm_ioctl_kernel+0xe9/0x13c > [ 50.276366] drm_ioctl+0x278/0x3a4 > [ 50.276368] ? drm_connector_set_obj_prop+0x63/0x63 > [ 50.276369] ? rpm_resume+0x8b/0x3eb > [ 50.276372] amdgpu_drm_ioctl+0x4a/0x79 [amdgpu > 98fd76f1aa24e802b0010b76204b9775aacb3c0c] > [ 50.276414] vfs_ioctl+0x1d/0x2b > [ 50.276418] __do_sys_ioctl+0x67/0x8a > [ 50.276420] do_syscall_64+0x82/0xa3 > [ 50.276422] ? syscall_exit_to_user_mode+0x34/0x37 > [ 50.276424] ? do_syscall_64+0x9c/0xa3 > [ 50.276425] ? vfs_ioctl+0x1d/0x2b > [ 50.276426] ? __do_sys_ioctl+0x78/0x8a > [ 50.276428] ? exit_to_user_mode_prepare+0x15/0x108 > [ 50.276430] ? syscall_exit_to_user_mode+0x34/0x37 > [ 50.276432] ? do_syscall_64+0x9c/0xa3 > [ 50.276433] ?
[Bug 218133] kernel panic when opening spotify/firefox 6.5.0.10.12 ubuntu 23.10 vega 64
https://bugzilla.kernel.org/show_bug.cgi?id=218133 Alex Deucher (alexdeuc...@gmail.com) changed: What|Removed |Added CC||alexdeuc...@gmail.com --- Comment #3 from Alex Deucher (alexdeuc...@gmail.com) --- The warnings are harmless (they are just variable sized arrays) and have already been adjusted in 6.7. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218134] Null pointer when rearranging screen layout in XFCE.
https://bugzilla.kernel.org/show_bug.cgi?id=218134 --- Comment #2 from Gerhard Mack (gm...@innerfire.net) --- I have discovered this happens when there are two monitors plugged into my displayport switch. If I run monitor 4 on hdmi directly, the crash stops happening. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218134] Null pointer when rearranging screen layout in XFCE.
https://bugzilla.kernel.org/show_bug.cgi?id=218134 Gerhard Mack (gm...@innerfire.net) changed: What|Removed |Added CC||gm...@innerfire.net --- Comment #1 from Gerhard Mack (gm...@innerfire.net) --- CPU is AMD Ryzen 9 5950X 16-Core Processor (32 threads) GPU is an Rx580 0d:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] (rev e7) -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218134] New: Null pointer when rearranging screen layout in XFCE.
https://bugzilla.kernel.org/show_bug.cgi?id=218134 Bug ID: 218134 Summary: Null pointer when rearranging screen layout in XFCE. Product: Drivers Version: 2.5 Hardware: All OS: Linux Status: NEW Severity: normal Priority: P3 Component: Video(DRI - non Intel) Assignee: drivers_video-...@kernel-bugs.osdl.org Reporter: gm...@innerfire.net Regression: No If I attempt to change my screen layout in XFCE, I get a kernel NULL pointer crash. This is very reproduceable. [ 50.275982] BUG: kernel NULL pointer dereference, address: 0008 [ 50.275988] #PF: supervisor read access in kernel mode [ 50.275989] #PF: error_code(0x) - not-present page [ 50.275991] PGD 0 P4D 0 [ 50.275993] Oops: [#1] PREEMPT SMP NOPTI [ 50.275995] CPU: 18 PID: 1931 Comm: Xorg Not tainted 6.6.1 #106 d284c8807aa68b715e3e2f475c4079807a0b5cb5 [ 50.275997] Hardware name: To Be Filled By O.E.M. B550 Taichi/B550 Taichi, BIOS P3.20 09/27/2023 [ 50.275999] RIP: 0010:drm_dp_atomic_find_time_slots+0x57/0x1e0 [drm_display_helper] [ 50.276007] Code: 0f 87 9d 01 00 00 48 8b 85 28 05 00 00 31 d2 48 63 80 88 00 00 00 41 3b 44 24 28 7d 0d 48 6b c0 28 49 03 44 24 30 48 8b 50 18 <48> 8b 42 08 48 89 ee 48 89 df 8b 88 90 00 00 00 b8 01 00 00 00 d3 [ 50.276008] RSP: 0018:ad10544b76d8 EFLAGS: 00010286 [ 50.276010] RAX: 9409ea510ca0 RBX: 940994c46900 RCX: 0002 [ 50.276011] RDX: RSI: 940996bd0578 RDI: 9409b11b7b00 [ 50.276012] RBP: 94099317b800 R08: ad10544b7a58 R09: 0001 [ 50.276012] R10: R11: R12: 9409b11b7b00 [ 50.276013] R13: 940996bd0578 R14: 0224 R15: 94c46900 [ 50.276014] FS: 7f4296208ac0() GS:94187ee8() knlGS: [ 50.276015] CS: 0010 DS: ES: CR0: 80050033 [ 50.276016] CR2: 0008 CR3: 00010612e000 CR4: 00f50ee0 [ 50.276017] PKRU: 5554 [ 50.276018] Call Trace: [ 50.276020] [ 50.276021] ? __die_body+0x15/0x54 [ 50.276026] ? page_fault_oops+0x323/0x36d [ 50.276030] ? post_alloc_hook+0x9/0x50 [ 50.276033] ? prep_new_page+0x2c/0x41 [ 50.276035] ? get_page_from_freelist+0x6c4/0x7f6 [ 50.276036] ? exc_page_fault+0x159/0x4f9 [ 50.276039] ? asm_exc_page_fault+0x26/0x30 [ 50.276043] ? drm_dp_atomic_find_time_slots+0x57/0x1e0 [drm_display_helper 13cd3e40727f81da5f41f67251f92c3e185bfce2] [ 50.276047] ? drm_dp_atomic_find_time_slots+0x21/0x1e0 [drm_display_helper 13cd3e40727f81da5f41f67251f92c3e185bfce2] [ 50.276051] compute_mst_dsc_configs_for_link+0x29b/0x7fd [amdgpu 98fd76f1aa24e802b0010b76204b9775aacb3c0c] [ 50.276121] ? free_tail_page_prepare+0xc0/0xdb [ 50.276123] ? free_unref_page_commit+0x29/0xeb [ 50.276127] compute_mst_dsc_configs_for_state+0x119/0x1a8 [amdgpu 98fd76f1aa24e802b0010b76204b9775aacb3c0c] [ 50.276178] amdgpu_dm_atomic_check+0x9ba/0xd9e [amdgpu 98fd76f1aa24e802b0010b76204b9775aacb3c0c] [ 50.276229] ? kmem_cache_debug_flags+0x5/0x11 [ 50.276232] ? amdgpu_dm_connector_atomic_duplicate_state+0x24/0xa4 [amdgpu 98fd76f1aa24e802b0010b76204b9775aacb3c0c] [ 50.276280] ? kmem_cache_debug_flags+0x5/0x11 [ 50.276281] ? slab_post_alloc_hook+0x70/0x17f [ 50.276284] ? slab_pre_alloc_hook.constprop.0+0x49/0x14c [ 50.276286] ? amdgpu_dm_connector_atomic_duplicate_state+0x24/0xa4 [amdgpu 98fd76f1aa24e802b0010b76204b9775aacb3c0c] [ 50.276344] ? __kmem_cache_alloc_node+0x10b/0x137 [ 50.276345] drm_atomic_check_only+0x6df/0x812 [ 50.276349] ? __drm_connector_put_safe+0x11/0x49 [ 50.276351] drm_atomic_commit+0x6a/0xc1 [ 50.276352] ? __drm_printfn_seq_file+0x17/0x17 [ 50.276355] ? __drm_printfn_seq_file+0x17/0x17 [ 50.276356] drm_atomic_connector_commit_dpms+0xc1/0xda [ 50.276358] drm_mode_obj_set_property_ioctl+0xff/0x293 [ 50.276361] ? drm_connector_set_obj_prop+0x63/0x63 [ 50.276362] drm_connector_property_set_ioctl+0x36/0x51 [ 50.276364] drm_ioctl_kernel+0xe9/0x13c [ 50.276366] drm_ioctl+0x278/0x3a4 [ 50.276368] ? drm_connector_set_obj_prop+0x63/0x63 [ 50.276369] ? rpm_resume+0x8b/0x3eb [ 50.276372] amdgpu_drm_ioctl+0x4a/0x79 [amdgpu 98fd76f1aa24e802b0010b76204b9775aacb3c0c] [ 50.276414] vfs_ioctl+0x1d/0x2b [ 50.276418] __do_sys_ioctl+0x67/0x8a [ 50.276420] do_syscall_64+0x82/0xa3 [ 50.276422] ? syscall_exit_to_user_mode+0x34/0x37 [ 50.276424] ? do_syscall_64+0x9c/0xa3 [ 50.276425] ? vfs_ioctl+0x1d/0x2b [ 50.276426] ? __do_sys_ioctl+0x78/0x8a [ 50.276428] ? exit_to_user_mode_prepare+0x15/0x108 [ 50.276430] ? syscall_exit_to_user_mode+0x34/0x37 [ 50.276432] ? do_syscall_64+0x9c/0xa3 [ 50.276433] ? syscall_exit_to_user_mode+0x34/0x37 [ 50.276435] ? do_syscall_64+0x9c/0xa3 [ 50.276436] ? do_syscall_64+0x9c/0xa3 [
[Bug 218133] kernel panic when opening spotify/firefox 6.5.0.10.12 ubuntu 23.10 vega 64
https://bugzilla.kernel.org/show_bug.cgi?id=218133 Artem S. Tashkinov (a...@gmx.com) changed: What|Removed |Added Kernel Version|Linux version |6.5.0-10-generic Ubuntu |6.5.0-10-generic| --- Comment #2 from Artem S. Tashkinov (a...@gmx.com) --- If you can reproduce the issue in vanilla 6.5.11 or 6.6.1 then report to https://gitlab.freedesktop.org/drm/amd/-/issues -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218133] kernel panic when opening spotify/firefox 6.5.0.10.12 ubuntu 23.10 vega 64
https://bugzilla.kernel.org/show_bug.cgi?id=218133 Artem S. Tashkinov (a...@gmx.com) changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |ANSWERED --- Comment #1 from Artem S. Tashkinov (a...@gmx.com) --- Please report on https://bugs.launchpad.net/ubuntu -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218133] kernel panic when opening spotify/firefox 6.5.0.10.12 ubuntu 23.10 vega 64
https://bugzilla.kernel.org/show_bug.cgi?id=218133 Michael Pollind (mpoll...@gmail.com) changed: What|Removed |Added Kernel Version||Linux version ||6.5.0-10-generic -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218133] kernel panic when opening spotify/firefox 6.5.0.10.12 ubuntu 23.10 vega 64
https://bugzilla.kernel.org/show_bug.cgi?id=218133 Michael Pollind (mpoll...@gmail.com) changed: What|Removed |Added Summary|kernel panic when opening |kernel panic when opening |spotify/firefox 6.5.0.10.12 |spotify/firefox 6.5.0.10.12 |ubuntu 23.10|ubuntu 23.10 vega 64 -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218133] kernel panic when opening spotify/firefox 6.5.0.10.12 ubuntu 23.10
https://bugzilla.kernel.org/show_bug.cgi?id=218133 Michael Pollind (mpoll...@gmail.com) changed: What|Removed |Added Summary|kernel panic when opening |kernel panic when opening |spotify 6.5.0.10.12 ubuntu |spotify/firefox 6.5.0.10.12 |23.10 |ubuntu 23.10 -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218133] New: kernel panic when opening spotify 6.5.0.10.12 ubuntu 23.10
https://bugzilla.kernel.org/show_bug.cgi?id=218133 Bug ID: 218133 Summary: kernel panic when opening spotify 6.5.0.10.12 ubuntu 23.10 Product: Drivers Version: 2.5 Hardware: AMD OS: Linux Status: NEW Severity: normal Priority: P3 Component: Video(DRI - non Intel) Assignee: drivers_video-...@kernel-bugs.osdl.org Reporter: mpoll...@gmail.com Regression: No this problem does not happen when I downgrade my kernel to 6.3.7. Linux version 6.5.0-10-generic (buildd@lcy02-amd64-118) (x86_64-linux-gnu-gcc-13 (Ubuntu 13.2.0-4ubuntu3) 13.2.0, GNU ld (GNU Binutils for Ubuntu) 2.41) #10-Ubuntu SMP PREEMPT_DYNAMIC Fri Oct 13 13:49:38 UTC 2023 - Nov 10 20:31:06 michaelpollind kernel: UBSAN: array-index-out-of-bounds in /build/linux-UiLXaH/linux-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/vega10_processpptables.c:361:55 Nov 10 20:31:06 michaelpollind kernel: index 2 is out of range for type 'ATOM_Vega10_MM_Dependency_Record [1]' Nov 10 20:31:06 michaelpollind kernel: CPU: 10 PID: 343 Comm: (udev-worker) Not tainted 6.5.0-10-generic #10-Ubuntu Nov 10 20:31:06 michaelpollind kernel: Hardware name: Gigabyte Technology Co., Ltd. X670E AORUS MASTER/X670E AORUS MASTER, BIOS F13d 09/14/2023 Nov 10 20:31:06 michaelpollind kernel: Call Trace: Nov 10 20:31:06 michaelpollind kernel: Nov 10 20:31:06 michaelpollind kernel: dump_stack_lvl+0x48/0x70 Nov 10 20:31:06 michaelpollind kernel: dump_stack+0x10/0x20 Nov 10 20:31:06 michaelpollind kernel: __ubsan_handle_out_of_bounds+0xc6/0x110 Nov 10 20:31:06 michaelpollind kernel: init_powerplay_extended_tables+0x6e7/0xab0 [amdgpu] Nov 10 20:31:06 michaelpollind kernel: vega10_pp_tables_initialize+0x156/0x4e0 [amdgpu] Nov 10 20:31:06 michaelpollind kernel: hwmgr_hw_init+0x78/0x1e0 [amdgpu] Nov 10 20:31:06 michaelpollind kernel: pp_hw_init+0x16/0x50 [amdgpu] Nov 10 20:31:06 michaelpollind kernel: amdgpu_device_ip_init+0x48b/0x900 [amdgpu] Nov 10 20:31:06 michaelpollind kernel: amdgpu_device_init+0x975/0x1160 [amdgpu] Nov 10 20:31:06 michaelpollind kernel: amdgpu_driver_load_kms+0x1a/0x1c0 [amdgpu] Nov 10 20:31:06 michaelpollind kernel: amdgpu_pci_probe+0x175/0x490 [amdgpu] Nov 10 20:31:06 michaelpollind kernel: local_pci_probe+0x44/0xb0 Nov 10 20:31:06 michaelpollind kernel: pci_call_probe+0x55/0x190 Nov 10 20:31:06 michaelpollind kernel: pci_device_probe+0x84/0x120 Nov 10 20:31:06 michaelpollind kernel: ? srso_alias_return_thunk+0x5/0x7f Nov 10 20:31:06 michaelpollind kernel: really_probe+0x1c4/0x410 Nov 10 20:31:06 michaelpollind kernel: __driver_probe_device+0x8c/0x180 Nov 10 20:31:06 michaelpollind kernel: driver_probe_device+0x24/0xd0 Nov 10 20:31:06 michaelpollind kernel: __driver_attach+0x10b/0x210 Nov 10 20:31:06 michaelpollind kernel: ? __pfx___driver_attach+0x10/0x10 Nov 10 20:31:06 michaelpollind kernel: bus_for_each_dev+0x8a/0xf0 Nov 10 20:31:06 michaelpollind kernel: driver_attach+0x1e/0x30 Nov 10 20:31:06 michaelpollind kernel: bus_add_driver+0x127/0x240 Nov 10 20:31:06 michaelpollind kernel: driver_register+0x5e/0x130 Nov 10 20:31:06 michaelpollind kernel: ? __pfx_amdgpu_init+0x10/0x10 [amdgpu] Nov 10 20:31:06 michaelpollind kernel: __pci_register_driver+0x62/0x70 Nov 10 20:31:06 michaelpollind kernel: amdgpu_init+0x69/0xff0 [amdgpu] Nov 10 20:31:06 michaelpollind kernel: do_one_initcall+0x5b/0x340 Nov 10 20:31:06 michaelpollind kernel: do_init_module+0x91/0x290 Nov 10 20:31:06 michaelpollind kernel: load_module+0xba1/0xcf0 Nov 10 20:31:06 michaelpollind kernel: ? vfree+0xff/0x2d0 Nov 10 20:31:06 michaelpollind kernel: init_module_from_file+0x96/0x100 Nov 10 20:31:06 michaelpollind kernel: ? init_module_from_file+0x96/0x100 Nov 10 20:31:06 michaelpollind kernel: idempotent_init_module+0x11c/0x2b0 Nov 10 20:31:06 michaelpollind kernel: __x64_sys_finit_module+0x64/0xd0 Nov 10 20:31:06 michaelpollind kernel: do_syscall_64+0x59/0x90 Nov 10 20:31:06 michaelpollind kernel: ? exit_to_user_mode_prepare+0x9b/0xb0 Nov 10 20:31:06 michaelpollind kernel: ? srso_alias_return_thunk+0x5/0x7f Nov 10 20:31:06 michaelpollind kernel: ? syscall_exit_to_user_mode+0x37/0x60 Nov 10 20:31:06 michaelpollind kernel: ? srso_alias_return_thunk+0x5/0x7f Nov 10 20:31:06 michaelpollind kernel: ? do_syscall_64+0x68/0x90 Nov 10 20:31:06 michaelpollind kernel: ? srso_alias_return_thunk+0x5/0x7f Nov 10 20:31:06 michaelpollind kernel: ? do_syscall_64+0x68/0x90 Nov 10 20:31:06 michaelpollind kernel: entry_SYSCALL_64_after_hwframe+0x6e/0xd8 Nov 10 20:31:06 michaelpollind kernel: RIP: 0033:0x7f0dac788c7d Nov 10 20:31:06 michaelpollind kernel: Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 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 6b 81 0d 00 f7 d8 64 89 01 48 Nov 10 20:31:06 michaelpollind kernel: RSP:
[Bug 217872] RIP: 0010:amdgpu_vm_pde_update [amdgpu]
https://bugzilla.kernel.org/show_bug.cgi?id=217872 b...@duck.com changed: What|Removed |Added CC||b...@duck.com --- Comment #2 from b...@duck.com --- (In reply to Alex Deucher from comment #1) > Likely a duplicate of: > https://gitlab.freedesktop.org/drm/amd/-/issues/2761 > If so, fixed in: > https://cgit.freedesktop.org/drm/drm-misc/commit/?h=drm-misc- > fixes=e2884fe84a83c562346eb9d92783a3576ce67177 Unfortunately it doesn't seem to be fixed. https://gitlab.freedesktop.org/drm/amd/-/issues/2623 -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 201957] amdgpu: ring gfx timeout
https://bugzilla.kernel.org/show_bug.cgi?id=201957 Mario Limonciello (AMD) (mario.limoncie...@amd.com) changed: What|Removed |Added CC||mario.limoncie...@amd.com --- Comment #99 from Mario Limonciello (AMD) (mario.limoncie...@amd.com) --- #98 The amdgpu.mcbp=0 will only help GFX9 products. For GFX10 this is a different problem, please open at AMD Gitlab. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 201957] amdgpu: ring gfx timeout
https://bugzilla.kernel.org/show_bug.cgi?id=201957 --- Comment #98 from jeremy boyd (j...@jerdboyd.com) --- (In reply to jeremy boyd from comment #97) > Hello, I'm having this same issue with my thinkpad z16 laptop, Ryzen 6850H > and Radeon RX 6500M graphics card. > > I do not use the laptop for gaming but for audio and video editing. I have > not had trouble with any video editing software but I can easily reproduce > the issue by loading up Ardour or Mixbus32C and either leaving it alone or > working. After 15 minutes the screen freezes although audio will continue > for a time. At this point Ardour or Mixbus will close and I can continue > using the machine. If I load up either program again it will fail again, > usually within a couple minutes and the whole laptop will freeze up until I > ctrl-alt-F2 to get to a terminal prompt. > > The issue always happens when Im recording audio with an HDMI device > attached and 90% of the time without HDMI > > I will attempt to set this kernel parameter amdgpu.mcbp=0 and report back. I can confirm that this did not solve my problem. I tested my system out for several hours with no issue and thought that perhaps it had been solved but while doing a libreoffice presentation with my audio software running it happened again. here is the error from journalctl Oct 22 09:40:01 fedora kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=433823, emitted seq=433825 Oct 22 09:40:01 fedora kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 2189 thread Xorg:cs0 pid 2319 Oct 22 09:40:01 fedora kernel: amdgpu :67:00.0: amdgpu: GPU reset begin! Oct 22 09:40:02 fedora kernel: amdgpu :67:00.0: amdgpu: MODE2 reset Oct 22 09:40:02 fedora kernel: amdgpu :67:00.0: amdgpu: GPU reset succeeded, trying to resume -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218015] amdgpu powerplay: Spontaneous changes to power_dpm_force_performance_level
https://bugzilla.kernel.org/show_bug.cgi?id=218015 Roman Žilka (roman.zi...@gmail.com) changed: What|Removed |Added URL||https://gitlab.freedesktop. ||org/drm/amd/-/issues/2931 -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218015] amdgpu powerplay: Spontaneous changes to power_dpm_force_performance_level
https://bugzilla.kernel.org/show_bug.cgi?id=218015 --- Comment #5 from Roman Žilka (roman.zi...@gmail.com) --- Thanks, I passed the info on. https://gitlab.freedesktop.org/drm/amd/-/issues/2931 -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 201957] amdgpu: ring gfx timeout
https://bugzilla.kernel.org/show_bug.cgi?id=201957 jeremy boyd (j...@jerdboyd.com) changed: What|Removed |Added CC||j...@jerdboyd.com --- Comment #97 from jeremy boyd (j...@jerdboyd.com) --- Hello, I'm having this same issue with my thinkpad z16 laptop, Ryzen 6850H and Radeon RX 6500M graphics card. I do not use the laptop for gaming but for audio and video editing. I have not had trouble with any video editing software but I can easily reproduce the issue by loading up Ardour or Mixbus32C and either leaving it alone or working. After 15 minutes the screen freezes although audio will continue for a time. At this point Ardour or Mixbus will close and I can continue using the machine. If I load up either program again it will fail again, usually within a couple minutes and the whole laptop will freeze up until I ctrl-alt-F2 to get to a terminal prompt. The issue always happens when Im recording audio with an HDMI device attached and 90% of the time without HDMI I will attempt to set this kernel parameter amdgpu.mcbp=0 and report back. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 215631] Some Desktop oriented mode setting drivers are missing DRM PRIME support
https://bugzilla.kernel.org/show_bug.cgi?id=215631 bluescreen_aven...@verizon.net changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |CODE_FIX --- Comment #2 from bluescreen_aven...@verizon.net --- I think 6b85aa68d9d5a27556b8b1015e7e515a371e77de 71e801b9b44f86ce8c816b06960c705f901c50e5 71a7974ac7019afeec105a54447ae1dc7216cbb3 resolve this -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218015] amdgpu powerplay: Spontaneous changes to power_dpm_force_performance_level
https://bugzilla.kernel.org/show_bug.cgi?id=218015 --- Comment #4 from Alex Deucher (alexdeuc...@gmail.com) --- UMDs (e.g., mesa) can change the power profile as well. E.g., if they want to capture an SQ trace, etc. It's likely that is the cause. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218015] amdgpu powerplay: Spontaneous changes to power_dpm_force_performance_level
https://bugzilla.kernel.org/show_bug.cgi?id=218015 Artem S. Tashkinov (a...@gmx.com) changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |ANSWERED --- Comment #3 from Artem S. Tashkinov (a...@gmx.com) --- Please report here instead: https://gitlab.freedesktop.org/drm/amd/-/issues 6.1.x is really not the best kernel to use with this card. You should try something fresher, i.e. 6.5.7. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 218015] amdgpu powerplay: Spontaneous changes to power_dpm_force_performance_level
https://bugzilla.kernel.org/show_bug.cgi?id=218015 --- Comment #2 from Roman Žilka (roman.zi...@gmail.com) --- Created attachment 305226 --> https://bugzilla.kernel.org/attachment.cgi?id=305226=edit lspci -vv -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
