[Bug 219468] Screen flickering on Radeon 680M - 6.12
https://bugzilla.kernel.org/show_bug.cgi?id=219468 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 refile 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 219468] Screen flickering on Radeon 680M - 6.12
https://bugzilla.kernel.org/show_bug.cgi?id=219468 --- Comment #3 from Joungmin Lee (leejm...@gmail.com) --- System info from inxi System: Host: leej-zenbook Kernel: 6.12.0-rc6-1-llvm-241014 arch: x86_64 bits: 64 compiler: clang v: 19.1.3 clocksource: tsc avail: acpi_pm parameters: BOOT_IMAGE=/root/boot/vmlinuz-linux-6.12.0-rc6-1-llvm-241014 root=UUID=ff2c684d-f559-4a51-9ae2-b27098fadb5f rw rootflags=subvol=root loglevel=3 quiet splash Desktop: KDE Plasma v: 6.2.2 tk: Qt v: N/A wm: kwin_wayland dm: SDDM Distro: Arch Linux Machine: Type: Laptop System: ASUSTeK product: Zenbook 15 UM3504DA_UM3504DA v: 1.0 serial: RBN0CX03S725478 Mobo: ASUSTeK model: UM3504DA v: 1.0 serial: RB46NBCX002FT6MB uuid: dda31f15-6388-bd4b-b4ea-cc1e6f3dd3e9 UEFI: American Megatrends LLC. v: UM3504DA.312 date: 05/13/2024 CPU: Info: model: AMD Ryzen 7 7735U with Radeon Graphics socket: FP7 bits: 64 type: MT MCP arch: Zen 3+ gen: 3 level: v3 note: check built: 2022 process: TSMC n6 (7nm) family: 0x19 (25) model-id: 0x44 (68) stepping: 1 microcode: 0xA404102 Topology: cpus: 1x dies: 1 clusters: 1 cores: 8 threads: 16 tpc: 2 smt: enabled cache: L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB L3: 16 MiB desc: 1x16 MiB Speed (MHz): avg: 400 min/max: 400/4819 boost: enabled base/boost: 2700/4800 scaling: driver: amd-pstate-epp governor: powersave volts: 1.2 V ext-clock: 100 MHz cores: 1: 400 2: 400 3: 400 4: 400 5: 400 6: 400 7: 400 8: 400 9: 400 10: 400 11: 400 12: 400 13: 400 14: 400 15: 400 16: 400 bogomips: 86261 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm Vulnerabilities: Type: gather_data_sampling status: Not affected Type: itlb_multihit status: Not affected Type: l1tf status: Not affected Type: mds status: Not affected Type: meltdown status: Not affected Type: mmio_stale_data status: Not affected Type: reg_file_data_sampling status: Not affected Type: retbleed status: Not affected Type: spec_rstack_overflow status: Vulnerable: Safe RET, no microcode Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization Type: spectre_v2 mitigation: Retpolines; IBPB: conditional; IBRS_FW; STIBP: always-on; RSB filling; PBRSB-eIBRS: Not affected; BHI: Not affected Type: srbds status: Not affected Type: tsx_async_abort status: Not affected Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Rembrandt [Radeon 680M] vendor: ASUSTeK driver: amdgpu v: kernel arch: RDNA-2 code: Navi-2x process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 4 speed: 16 GT/s lanes: 16 ports: active: eDP-1 empty: DP-1, DP-2, DP-3, DP-4, DP-5, DP-6, HDMI-A-1, Writeback-1 bus-ID: 73:00.0 chip-ID: 1002:1681 class-ID: 0300 temp: 44.0 C Device-2: Shinetech USB2.0 FHD UVC WebCam driver: uvcvideo type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 5-1:2 chip-ID: 3277:0033 class-ID: fe01 serial: 200901010001 Display: unspecified server: X.Org v: 24.1.4 with: Xwayland v: 24.1.4 compositor: kwin_wayland driver: X: loaded: amdgpu unloaded: modesetting alternate: fbdev,vesa dri: radeonsi gpu: amdgpu display-ID: :1 screens: 1 Screen-1: 0 s-res: 2880x1620 s-dpi: 96 s-size: 762x429mm (30.00x16.89") s-diag: 874mm (34.43") Monitor-1: eDP-1 model: Samsung 0x4180 built: 2021 res: 2880x1620 hz: 120 dpi: 213 gamma: 1.2 size: 344x194mm (13.54x7.64") diag: 395mm (15.5") ratio: 16:9 modes: max: 2880x1620 min: 640x480 API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi device: 1 drv: swrast gbm: drv: radeonsi surfaceless: drv: radeonsi x11: drv: radeonsi inactive: wayland API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.2.6-arch1.1 glx-v: 1.4 direct-render: yes renderer: AMD Radeon Graphics (radeonsi rembrandt LLVM 18.1.8 DRM 3.59 6.12.0-rc6-1-llvm-241014) device-ID: 1002:1681 memory: 500 MiB unified: no API: Vulkan v: 1.3.295 layers: N/A device: 0 type: integrated-gpu name: AMD Radeon Graphics (RADV REMBRANDT) driver: mesa radv v: 24.2.6-arch1.1 device-ID: 1002:1681 surfaces: xcb,xlib -- 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 219468] Screen flickering on Radeon 680M - 6.12
https://bugzilla.kernel.org/show_bug.cgi?id=219468 Joungmin Lee (leejm...@gmail.com) changed: What|Removed |Added Kernel Version||6.12 --- Comment #2 from Joungmin Lee (leejm...@gmail.com) --- Video clips taken. https://youtu.be/WfS5tWvqiYc https://youtu.be/vVnlvhUzIvY -- 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 219468] Screen flickering on Radeon 680M - 6.12
https://bugzilla.kernel.org/show_bug.cgi?id=219468 --- Comment #1 from Joungmin Lee (leejm...@gmail.com) --- Created attachment 307142 --> https://bugzilla.kernel.org/attachment.cgi?id=307142&action=edit kernel configuration kernel config -- 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 219468] New: Screen flickering on Radeon 680M - 6.12
https://bugzilla.kernel.org/show_bug.cgi?id=219468 Bug ID: 219468 Summary: Screen flickering on Radeon 680M - 6.12 Product: Drivers Version: 2.5 Hardware: AMD OS: Linux Status: NEW Severity: low Priority: P3 Component: Video(DRI - non Intel) Assignee: drivers_video-...@kernel-bugs.osdl.org Reporter: leejm...@gmail.com Regression: No Created attachment 307141 --> https://bugzilla.kernel.org/attachment.cgi?id=307141&action=edit dmesg Random screen flickering is observed after upgrading to 6.12 (from rc1), which was not observed in 6.11 kernels. The phenomenon is more notable when trying to scroll the screen with mouse. Seen on a machine running KDE Plasma 6.2 (w/ wayland) on Arch Linux. Other WMs have not been tested. My English is not so good for describing the problem exactly. So I link two clips where the display was taken. I could identify nothing special from dmesg. The dmesg and kernel configuration are attached. -- 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 206225] nouveau: Screen distortion and lockup on resume
https://bugzilla.kernel.org/show_bug.cgi?id=206225 lukasz.wojnilow...@gmail.com changed: What|Removed |Added CC||lukasz.wojnilow...@gmail.co ||m --- Comment #13 from lukasz.wojnilow...@gmail.com --- We have 2024 and https://nouveau.freedesktop.org/KernelModuleParameters.html (updated in 2024) still recommends using nouveau.config=PCRYPT=0 instead of nouveau.config=cipher=0. I believe that correct names can be taken at https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/nouveau/nvkm/engine from the directory names. -- 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 68701] On boot, console freeze after "conflicting fb hw usage nouveau fb vs..." with 3.13-rc8
https://bugzilla.kernel.org/show_bug.cgi?id=68701 William (wj...@mypostoffice.co.uk) changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |OBSOLETE --- Comment #3 from William (wj...@mypostoffice.co.uk) --- As this is a very old report and the hardware is gone, so would be impossible to test, the bug should be closed. -- 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 214071] amdgpu idle power draw too high at +75Hz
https://bugzilla.kernel.org/show_bug.cgi?id=214071 Artem S. Tashkinov (a...@gmx.com) changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |ANSWERED --- Comment #5 from Artem S. Tashkinov (a...@gmx.com) --- AMD's bug tracker is 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 203033] nouveau hung task
https://bugzilla.kernel.org/show_bug.cgi?id=203033 Matteo Croce (rootki...@yahoo.it) changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |OBSOLETE -- 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 204241] amdgpu fails to resume from suspend
https://bugzilla.kernel.org/show_bug.cgi?id=204241 Artem S. Tashkinov (a...@gmx.com) changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |ANSWERED --- Comment #80 from Artem S. Tashkinov (a...@gmx.com) --- If you're still affected, please try kernels 6.10.11 or 6.11. If the bug is reproducible, please file a new one 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 209939] radeontop causes kernel panic
https://bugzilla.kernel.org/show_bug.cgi?id=209939 Janpieter Sollie (janpieter.sol...@edpnet.be) changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |OBSOLETE -- 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 204241] amdgpu fails to resume from suspend
https://bugzilla.kernel.org/show_bug.cgi?id=204241 John_H_Smith (derfab...@gmail.com) changed: What|Removed |Added CC||derfab...@gmail.com --- Comment #79 from John_H_Smith (derfab...@gmail.com) --- Are there any updates on the status of this bug as I cannot see anything since 1,5 Years? The issue still exists. -- 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 195159] nouveau incorrect ACPI usgage results in ACPI Error : AE_AML_PACKAGE_LIMIT
https://bugzilla.kernel.org/show_bug.cgi?id=195159 Artem S. Tashkinov (a...@gmx.com) changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WILL_NOT_FIX --- Comment #14 from Artem S. Tashkinov (a...@gmx.com) --- The nouveau project is severely underfunded and understaffed, so don't expect this bug report to be fixed any time soon or ever. Also, it makes sense to file it where it should belong: 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 195159] nouveau incorrect ACPI usgage results in ACPI Error : AE_AML_PACKAGE_LIMIT
https://bugzilla.kernel.org/show_bug.cgi?id=195159 Yury Puchalski (p...@aikipooh.name) changed: What|Removed |Added CC||p...@aikipooh.name --- Comment #13 from Yury Puchalski (p...@aikipooh.name) --- I think it's the right place to discuss:) Using gentoo, kernel 6.6.38, and 5.15.41 had it the same. It's Dell Precision M4800, integrated intel card, and additional nvidia. I'm using nouveau driver, nvidia setup as primaryGPU for X. The usual line is there. [4.295646] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20230628/nsarguments-61) But then, what's very bad, I get temporary freezes regularly. Sometimes it's every 10-15 seconds, sometimes it doesn't happen for prolonged time. Sep 9 20:00:05 dell kernel: ACPI: \x5c_SB_.PCI0.PEG0.PEGP: failed to evaluate _DSM Sep 9 20:00:40 dell kernel: ACPI: \x5c_SB_.PCI0.PEG0.PEGP: failed to evaluate _DSM Sep 9 20:01:10 dell kernel: ACPI: \x5c_SB_.PCI0.PEG0.PEGP: failed to evaluate _DSM Sep 9 20:01:32 dell kernel: ACPI: \x5c_SB_.PCI0.PEG0.PEGP: failed to evaluate _DSM Sep 9 20:03:52 dell kernel: ACPI: \x5c_SB_.PCI0.PEG0.PEGP: failed to evaluate _DSM Sep 9 20:04:22 dell kernel: ACPI: \x5c_SB_.PCI0.PEG0.PEGP: failed to evaluate _DSM Sep 9 20:04:56 dell kernel: ACPI: \x5c_SB_.PCI0.PEG0.PEGP: failed to evaluate _DSM Sep 9 20:06:35 dell kernel: ACPI: \x5c_SB_.PCI0.PEG0.PEGP: failed to evaluate _DSM Sep 9 20:09:55 dell kernel: ACPI: \x5c_SB_.PCI0.PEG0.PEGP: failed to evaluate _DSM Sep 9 20:10:34 dell kernel: ACPI: \x5c_SB_.PCI0.PEG0.PEGP: failed to evaluate _DSM Every such message is followed by: Sep 9 20:12:43 dell kernel: nouveau :01:00.0: Enabling HDA controller These freezes result in music hiccups, mouse pointer not moving for 2-3 seconds. What can I do to sweep them under the carpet? acpi=off? -- 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 206309] Experimental amdgpu w/ Dell E6540 with HD 8790M (MARS XTX), massive performance improvement after ACPI suspend
https://bugzilla.kernel.org/show_bug.cgi?id=206309 --- Comment #6 from Travis Juntara (changhaitra...@gmail.com) --- I ended up upgrading to a slightly newer dell business laptop with an AMD GPU (with none of these issues) and getting rid of my Latitude E6540. As such, I can't really help test anymore. I also can't remember who set this ticket status to be "Resolved - WILL_NOT_FIX", but hesitate to re-open in case it wasn't me. If you want to pursue this further, you'll want to open up a new ticket. -- 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 206309] Experimental amdgpu w/ Dell E6540 with HD 8790M (MARS XTX), massive performance improvement after ACPI suspend
https://bugzilla.kernel.org/show_bug.cgi?id=206309 --- Comment #5 from jerbear3.14...@gmail.com --- It's a Linux bug! I finally set aside a day to waste on Windows installation to check whether it behaves the same way. Windows 10 repeatedly crashed and bricked itself because of course it did. It works perfectly on Windows 8.1 with the official graphics driver on Dell's website. https://dl.dell.com/FOLDER02868143M/5/AMD-FirePro-Graphics-Driver_CWRN6_WIN_14.502.1005_A02_02.EXE Memory Clock (MHz)/Shader Clock (MHz): Idle: 150/300 Battery: 600/400 AC: 1000/900 On Xubuntu 23.10 it's more like: Idle: 150/300 Battery: 150/300 AC: 1000/900 (but it drops down to 150/300 after unplugging, and requires a reboot to bring it back up) I've gone through 2 official 130W Dell chargers and 2 90W Targus universal chargers. Linux exhibits the power management bug regardless. I have never tried a docking station. uname -a gives: Linux 6.5.0-44-generic #44-Ubuntu SMP PREEMPT_DYNAMIC Fri Jun 7 15:10:09 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux The only reprieve I've found is to follow these steps: 1. Boot with the laptop plugged in. If using a 90W charger and this is a cold start (as opposed to a reboot), need to reboot as soon as it finishes booting. 2. echo -n high > /sys/class/drm/card1/device/power_dpm_force_performance_level 3. Pray 4. Unplug 5. Now for some reason, there's a small chance that the clock speeds stick high and don't drop. If not, start over from step 1. If yes, then typically (but not always) I can repeatedly unplug+plug safely up until it's time to shut down. Problems I've encountered with this method include: - Low success rate - Runs hotter/harms battery life - If I'm working unplugged, I need to manually lower the clock speeds down to 600/400. If I forget and leave it at 1000/900 and try to do anything graphically intense, the battery can't provide enough power and the entire laptop shuts down immediately. You can see that Windows does this automatically when unplugged. All in all, this is a nightmare for a game developer who needs maximum GPU performance. I live in constant fear of bumping the power cord out or needing to switch rooms. I'm happy to provide any additional information, but glancing at the amdgpu source code it seems a little over my head! -- 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 211807] [drm:drm_dp_mst_dpcd_read] *ERROR* mstb 000000004e6288dd port 3: DPCD read on addr 0x60 for 1 bytes NAKed
https://bugzilla.kernel.org/show_bug.cgi?id=211807 Feicop1 (bofomol...@givehit.com) changed: What|Removed |Added CC||bofomol...@givehit.com --- Comment #29 from Feicop1 (bofomol...@givehit.com) --- You have clear goals in all of our Papa's games. You might be putting money aside for a new car or a park ticket. You can only reach your goal by making money and helping other people. At the order desk, you will first take orders. Then, get the right items together and get them ready at the grill, mix, or build station. The last steps are different for each place. Help people in the neighborhood and at baseball games! https://papasgames.pro -- 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 219152] 6.11 regression: AMD 7950x iGPU fails to initialize (with bisect)
https://bugzilla.kernel.org/show_bug.cgi?id=219152 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 219152] New: 6.11 regression: AMD 7950x iGPU fails to initialize (with bisect)
https://bugzilla.kernel.org/show_bug.cgi?id=219152
Bug ID: 219152
Summary: 6.11 regression: AMD 7950x iGPU fails to initialize
(with bisect)
Product: Drivers
Version: 2.5
Hardware: AMD
OS: Linux
Status: NEW
Severity: blocking
Priority: P3
Component: Video(DRI - non Intel)
Assignee: drivers_video-...@kernel-bugs.osdl.org
Reporter: saverio.p...@gmail.com
Regression: No
I've found a regression in the 6.11 kernel, caused by the commit 3af2c80ae2
("drm/amdgpu: refine gfx10 firmware loading").
On boot, the iGPU fails to initialize:
[drm:amdgpu_device_init [amdgpu]] *ERROR* early_init of IP block
failed -22
amdgpu: Fatal error during GPU init
amdgpu: amdgpu: finishing device.
Reverting the commit fixes the issue.
--
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 219117] amdgpu: amdgpu_device_ip_init failed
https://bugzilla.kernel.org/show_bug.cgi?id=219117 Jean-Christophe Guillain (jean-christo...@guillain.net) changed: What|Removed |Added Resolution|ANSWERED|CODE_FIX --- Comment #3 from Jean-Christophe Guillain (jean-christo...@guillain.net) --- Hello Tim ! I confirm that your patch fixed the issue. Thank you very much, jC -- 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 219117] amdgpu: amdgpu_device_ip_init failed
https://bugzilla.kernel.org/show_bug.cgi?id=219117 Tim Huang (tim.hu...@amd.com) changed: What|Removed |Added CC||tim.hu...@amd.com --- Comment #2 from Tim Huang (tim.hu...@amd.com) --- Hello, Thanks Jean for reporting this issue. It should be the same issue with this one https://gitlab.freedesktop.org/drm/amd/-/issues/3502. Here is the fix patch https://gitlab.freedesktop.org/agd5f/linux/-/commit/f1127b0b6ef8d451eddfecb67e4289ce763b2f9e. Thanks. Tim Huang -- 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 219117] amdgpu: amdgpu_device_ip_init failed
https://bugzilla.kernel.org/show_bug.cgi?id=219117 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 219118] Linux 6.10.x [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout VM fault / GPU fault detected
https://bugzilla.kernel.org/show_bug.cgi?id=219118 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 219118] New: Linux 6.10.x [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout VM fault / GPU fault detected
https://bugzilla.kernel.org/show_bug.cgi?id=219118 Bug ID: 219118 Summary: Linux 6.10.x [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout VM fault / GPU fault detected 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: mjevans1...@gmail.com Regression: No I'm not sure if this should be filed under Console/Framebuffers, Video(DRI - non Intel), or Video(Other). I thought I'd created the bug in the correct location, https://gitlab.freedesktop.org/drm/amd/-/issues/3510 but no maintainer has commented or otherwise notably interacted with the report. Initially I thought it was just an MPV bug since VLC didn't trigger the issue https://github.com/mpv-player/mpv/issues/14600 . It looks like a developer's personal(?) drm-fixes-6.11 branch cherry picked the commit that appeared to fix the issue completely for my test cases: https://gitlab.freedesktop.org/agd5f/linux/-/commit/f3572db3c049b4d32bb5ba77ad5305616c44c7c1 However that isn't for the earlier 6.10.x series which also needs the fix, unless it's dead. This appears to be a Swiss cheese sort of bug situation. If software requests/provides contiguous buffers then the error results are more subtle, such as momentary video corruption if the kernel's access isn't out of bounds but rather rarely scrambled. It's only when both the userspace and driver don't enforce contiguous buffer segments that out of bounds accesses result in a GPU reset and consequently terminated userspace. ArchLinux (rolling release) Linux 6.10.1-arch1-1 #1 (closed) SMP PREEMPT_DYNAMIC Wed, 24 Jul 2024 22:25:43 + x86_64 GNU/Linux amdgpu + OpenGL version string: 4.6 (Compatibility Profile) Mesa 24.1.4-arch1.2 ArchLinux current stable builds [ 1766.321165] amdgpu :01:00.0: amdgpu: GPU fault detected: 147 0x0a22c802 [ 1766.321171] amdgpu :01:00.0: amdgpu: for process plasmashell pid 2961 thread plasmashel:cs0 pid 3007 [ 1766.321172] amdgpu :01:00.0: amdgpu: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00101F44 [ 1766.321174] amdgpu :01:00.0: amdgpu: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0B0C8002 [ 1766.321175] amdgpu :01:00.0: amdgpu: VM fault (0x02, vmid 5, pasid 32772) at page 1056580, write from 'TC3' (0x54433300) (200) [ 1766.321237] amdgpu :01:00.0: amdgpu: GPU fault detected: 147 0x07f2a002 [ 1766.321238] amdgpu :01:00.0: amdgpu: for process plasmashell pid 2961 thread plasmashel:cs0 pid 3007 [ 1766.321239] amdgpu :01:00.0: amdgpu: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x0010120C [ 1766.321240] amdgpu :01:00.0: amdgpu: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0B020002 [ 1766.321241] amdgpu :01:00.0: amdgpu: VM fault (0x02, vmid 5, pasid 32772) at page 1053196, write from 'CB2' (0x43423200) (32) [ 1766.321244] amdgpu :01:00.0: amdgpu: GPU fault detected: 147 0x07b29002 [ 1766.321245] amdgpu :01:00.0: amdgpu: for process plasmashell pid 2961 thread plasmashel:cs0 pid 3007 [ 1766.321247] amdgpu :01:00.0: amdgpu: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00101237 [ 1766.321247] amdgpu :01:00.0: amdgpu: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0B010002 [ 1766.321248] amdgpu :01:00.0: amdgpu: VM fault (0x02, vmid 5, pasid 32772) at page 1053239, write from 'CB3' (0x43423300) (16) [ 1766.321255] amdgpu :01:00.0: amdgpu: GPU fault detected: 147 0x0772e002 [ 1766.321256] amdgpu :01:00.0: amdgpu: for process plasmashell pid 2961 thread plasmashel:cs0 pid 3007 [ 1766.321257] amdgpu :01:00.0: amdgpu: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00101200 [ 1766.321258] amdgpu :01:00.0: amdgpu: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0B0A0002 [ 1766.321258] amdgpu :01:00.0: amdgpu: VM fault (0x02, vmid 5, pasid 32772) at page 1053184, write from 'CB4' (0x43423400) (160) [ 1766.321262] amdgpu :01:00.0: amdgpu: GPU fault detected: 147 0x0772d002 [ 1766.321263] amdgpu :01:00.0: amdgpu: for process plasmashell pid 2961 thread plasmashel:cs0 pid 3007 [ 1766.321264] amdgpu :01:00.0: amdgpu: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00101232 [ 1766.321264] amdgpu :01:00.0: amdgpu: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0B0A0002 [ 1766.321265] amdgpu :01:00.0: amdgpu: VM fault (0x02, vmid 5, pasid 32772) at page 1053234, write from 'CB4' (0x43423400) (160) [ 1766.321268] amdgpu :01:00.0: amdgpu: GPU fault detected: 147 0x07729002 [ 1766.321269] amdgpu :01:00.0: amdgpu: for process plasmashell pid 2961 thread plasmashel:cs0 pid 3007 [ 1766.321271] amdgpu :01:00.0: amdgpu: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x0010123A [ 1766.321271] amdgpu :01:00.0: amdgpu: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0B050002 [ 1766.321272] amdgpu :01:00.0: amdgpu: VM fault (0x02, vmid 5, pasid 32772) at pa
[Bug 219117] New: amdgpu: amdgpu_device_ip_init failed
https://bugzilla.kernel.org/show_bug.cgi?id=219117 Bug ID: 219117 Summary: amdgpu: amdgpu_device_ip_init failed Product: Drivers Version: 2.5 Kernel Version: 6.11.0-rc1 Hardware: All OS: Linux Status: NEW Severity: blocking Priority: P3 Component: Video(DRI - non Intel) Assignee: drivers_video-...@kernel-bugs.osdl.org Reporter: jean-christo...@guillain.net Regression: Yes Bisected 064d92436b6924937ef414894d9174fa4465f788 commit-id: Hello ! Since the last kernel RC (6.11-rc1), the boot process hangs on my computer after a GPU error : Jul 30 10:18:10 youpi kernel: amdgpu :00:01.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring gfx test failed (-110) Jul 30 10:18:10 youpi kernel: [drm:amdgpu_device_init [amdgpu]] *ERROR* hw_init of IP block failed -110 Jul 30 10:18:10 youpi kernel: amdgpu :00:01.0: amdgpu: amdgpu_device_ip_init failed Jul 30 10:18:10 youpi kernel: amdgpu :00:01.0: amdgpu: Fatal error during GPU init Jul 30 10:18:10 youpi kernel: amdgpu :00:01.0: amdgpu: amdgpu: finishing device. Jul 30 10:18:10 youpi kernel: [ cut here ] Jul 30 10:18:10 youpi kernel: WARNING: CPU: 0 PID: 186 at drivers/gpu/drm/amd/amdgpu/amdgpu_irq.c:631 amdgpu_irq_put+0x45/0x70 [amdgpu] Jul 30 10:18:10 youpi kernel: Modules linked in: sd_mod usbhid uas hid usb_storage amdgpu(+) amdxcp drm_exec gpu_sched drm_buddy i2c_algo_bit drm_suballoc_helper drm> Jul 30 10:18:10 youpi kernel: CPU: 0 UID: 0 PID: 186 Comm: (udev-worker) Not tainted 6.11.0-rc1-jcg+ #1 Jul 30 10:18:10 youpi kernel: Hardware name: LENOVO 10VGS02P00/3130, BIOS M1XKT57A 02/10/2022 Jul 30 10:18:10 youpi kernel: RIP: 0010:amdgpu_irq_put+0x45/0x70 [amdgpu] Jul 30 10:18:10 youpi kernel: Code: 48 8b 4e 10 48 83 39 00 74 2c 89 d1 48 8d 04 88 8b 08 85 c9 74 14 f0 ff 08 b8 00 00 00 00 74 05 e9 50 c5 f7 d8 e9 6b fd ff ff <0f> Jul 30 10:18:10 youpi kernel: RSP: 0018:af1480677940 EFLAGS: 00010246 Jul 30 10:18:10 youpi kernel: RAX: 94f286417540 RBX: 94f285818880 RCX: Jul 30 10:18:10 youpi kernel: RDX: RSI: 94f2858254c0 RDI: 94f28580 Jul 30 10:18:10 youpi kernel: RBP: 94f285810208 R08: 0002 R09: 0003 Jul 30 10:18:10 youpi kernel: R10: af1480677768 R11: 9a4c96c8 R12: 94f2858105e8 Jul 30 10:18:10 youpi kernel: R13: 94f285800010 R14: 94f28580 R15: 94f2858254c0 Jul 30 10:18:10 youpi kernel: FS: 7f03450bb8c0() GS:94f31760() knlGS: Jul 30 10:18:10 youpi kernel: CS: 0010 DS: ES: CR0: 80050033 Jul 30 10:18:10 youpi kernel: CR2: 7f03450b2028 CR3: 0001458d8000 CR4: 001506f0 Jul 30 10:18:10 youpi kernel: Call Trace: Jul 30 10:18:10 youpi kernel: Jul 30 10:18:10 youpi kernel: ? __warn+0x7c/0x120 Jul 30 10:18:10 youpi kernel: ? amdgpu_irq_put+0x45/0x70 [amdgpu] Jul 30 10:18:10 youpi kernel: ? report_bug+0x155/0x170 Jul 30 10:18:10 youpi kernel: ? handle_bug+0x3f/0x80 Jul 30 10:18:10 youpi kernel: ? exc_invalid_op+0x13/0x60 Jul 30 10:18:10 youpi kernel: ? asm_exc_invalid_op+0x16/0x20 Jul 30 10:18:10 youpi kernel: ? amdgpu_irq_put+0x45/0x70 [amdgpu] Jul 30 10:18:10 youpi kernel: amdgpu_fence_driver_hw_fini+0xfa/0x130 [amdgpu] Jul 30 10:18:10 youpi kernel: amdgpu_device_fini_hw+0xa2/0x3f0 [amdgpu] Jul 30 10:18:10 youpi kernel: amdgpu_driver_load_kms+0x79/0xb0 [amdgpu] Jul 30 10:18:10 youpi kernel: amdgpu_pci_probe+0x195/0x520 [amdgpu] Jul 30 10:18:10 youpi kernel: local_pci_probe+0x41/0x90 Jul 30 10:18:10 youpi kernel: pci_device_probe+0xbb/0x1e0 Jul 30 10:18:10 youpi kernel: really_probe+0xd6/0x390 Jul 30 10:18:10 youpi kernel: ? __pfx___driver_attach+0x10/0x10 Jul 30 10:18:10 youpi kernel: __driver_probe_device+0x78/0x150 Jul 30 10:18:10 youpi kernel: driver_probe_device+0x1f/0x90 Jul 30 10:18:10 youpi kernel: __driver_attach+0xce/0x1c0 Jul 30 10:18:10 youpi kernel: bus_for_each_dev+0x84/0xd0 Jul 30 10:18:10 youpi kernel: bus_add_driver+0x10e/0x240 Jul 30 10:18:10 youpi kernel: driver_register+0x55/0x100 Jul 30 10:18:10 youpi kernel: ? __pfx_amdgpu_init+0x10/0x10 [amdgpu] Jul 30 10:18:10 youpi kernel: do_one_initcall+0x57/0x320 Jul 30 10:18:10 youpi kernel: do_init_module+0x60/0x230 Jul 30 10:18:10 youpi kernel: init_module_from_file+0x86/0xc0 Jul 30 10:18:10 youpi kernel: idempotent_init_module+0x11b/0x2b0 Jul 30 10:18:10 youpi kernel: __x64_sys_finit_module+0x5a/0xb0 Jul 30 10:18:10 youpi kernel: do_syscall_64+0x7e/0x190 Jul 30 10:18:10 youpi kernel: ? syscall_exit_to_user_mode+0xc/0x1d0 Jul 30 10:18:10 youpi kernel: ? do_syscall_64+0x8a/0x190 Jul 30 10:18:10 youpi kernel: ? do_syscall_64+0x8a/0x190 Jul 30 10:18:10 youpi kernel: ? syscall_exit_to_user_mode+0xc/0x1d0 Jul 30 10:18:10 youpi kernel: ? do_syscall_64+0x8a/0x190 Jul 30 10:18:10 youpi kernel: ?
[Bug 219091] amdgpu: after updating to linux 6.10, screen flickering occurs
https://bugzilla.kernel.org/show_bug.cgi?id=219091 --- Comment #4 from Christian Heusel (christ...@heusel.eu) --- Yes the mentioned patch fixes the issue for the reporter I have been in contact with! -- 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 219091] amdgpu: after updating to linux 6.10, screen flickering occurs
https://bugzilla.kernel.org/show_bug.cgi?id=219091 Alex Deucher (alexdeuc...@gmail.com) changed: What|Removed |Added CC||alexdeuc...@gmail.com --- Comment #3 from Alex Deucher (alexdeuc...@gmail.com) --- Likely already fixed by: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e3615bd198289f319172c428f20857accb46b830 -- 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 219091] amdgpu: after updating to linux 6.10, screen flickering occurs
https://bugzilla.kernel.org/show_bug.cgi?id=219091 Christian Heusel (christ...@heusel.eu) changed: What|Removed |Added CC||christ...@heusel.eu --- Comment #2 from Christian Heusel (christ...@heusel.eu) --- We're currently in the progress of bisecting the issue :) -- 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 219092] Problem with fill_dc_mst_payload_table_from_drm [amdgpu]
https://bugzilla.kernel.org/show_bug.cgi?id=219092 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 Before doing that make sure your bug is reproducible in 6.10.1 because vendor kernels are not normally supported. -- 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 219092] New: Problem with fill_dc_mst_payload_table_from_drm [amdgpu]
https://bugzilla.kernel.org/show_bug.cgi?id=219092 Bug ID: 219092 Summary: Problem with fill_dc_mst_payload_table_from_drm [amdgpu] Product: Drivers Version: 2.5 Kernel Version: Ubuntu 6.8.0-40.40-generic 6.8.12 Hardware: i386 OS: Linux Status: NEW Severity: normal Priority: P3 Component: Video(DRI - non Intel) Assignee: drivers_video-...@kernel-bugs.osdl.org Reporter: a9...@hotmail.com Regression: No Dear maintainers, I am using a Intel NUC nuc8i7hvk hades-canyon, there I want to use the thunderbolt3 (usb-c) for my two displays via Lenovo Docking Station, but the only interfaces via HDMI and Mini-DP at the Intel-NUC are working. The displays are recognised, but enabling is not possible , I have disabled them in KDE for now. The problem is via tb3-usb-c-directly connnected and also via Lenovo Docking Station. First at bootup there is a warning message with a problem at fill_dc_mst_payload_table_from_drm and then you see "amdgpu :01:00.0: [drm] enabling link 1 failed: 15"-messages. On MS Windows 10 (or in the BIOS_UEFI setup) there is no problem tb3/usb-c with the two displays and the docking station. My workaround for now is to connect the two displays (each two cables) to the Intel-NUC via HDMI/Mini-DP AND to the Docking-Station to have a working setup. Is there the possibility to fix this problem? Thank you in advance. Best regards, Bernhard Messages: # Outputs uname -a Linux stargazer 6.8.0-40-generic #40-Ubuntu SMP PREEMPT_DYNAMIC Fri Jul 5 10:34:03 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux Ubuntu 6.8.0-40.40-generic 6.8.12 # Specs of the Intel NUC nuc8i7hvk hades-canyon https://geizhals.at/intel-nuc-kit-nuc8i7hvk-hades-canyon-boxnuc8i7hvk-a1752708.html => Discrete Graphics is AMD VEGA M and IGP is Intel . Mobo: Intel model: NUC8i7HVB UEFI: Intel v: HNKBLi70.86A.0070.2022.1103.1527 date: 11/03/2022 product: NUC8i7HVK Graphics: Device-1: AMD Polaris 22 XT [Radeon RX Vega M GH] vendor: Intel driver: amdgpu v: kernel arch: GCN-4 pcie: speed: 8 GT/s lanes: 8 ports: active: HDMI-A-1,HDMI-A-2 off: DP-7,DP-8 empty: DP-1, DP-2, DP-3, DP-4, DP-5, DP-6, DP-9 bus-ID: 01:00.0 chip-ID: 1002:694c Kubuntu 24.04 Display: server: X.Org v: 21.1.11 with: Xwayland v: 23.2.6 compositor: kwin_x11 driver: X: loaded: amdgpu unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1 Screen-1: 0 s-res: 7680x2160 s-dpi: 96 Monitor-1: DP-7 mapped: DisplayPort-6 note: disabled model: Dell S2722QC res: N/A dpi: 163 diag: 685mm (27") Monitor-2: DP-8 mapped: DisplayPort-7 note: disabled model: Dell S2722QC res: N/A dpi: 163 diag: 685mm (27") Monitor-3: HDMI-A-1 mapped: HDMI-A-0 pos: left model: Dell S2722QC res: 3840x2160 dpi: 163 diag: 685mm (27") Monitor-4: HDMI-A-2 mapped: HDMI-A-1 pos: primary,right model: Dell S2722QC res: 3840x2160 dpi: 163 diag: 685mm (27") API: EGL v: 1.5 platforms: device: 0 drv: radeonsi device: 1 drv: swrast surfaceless: drv: radeonsi x11: drv: radeonsi inactive: gbm,wayland API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.0.9-0ubuntu0.1 glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX Vega M GH Graphics (radeonsi vegam LLVM 17.0.6 DRM 3.57 6.8.0-40-generic) device-ID: 1002:694c API: Vulkan v: 1.3.275 surfaces: xcb,xlib device: 0 type: discrete-gpu driver: N/A device-ID: 1002:694c device: 1 type: cpu driver: N/A device-ID: 10005: lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 05) 00:01.0 PCI bridge: Intel Corporation 6th-10th Gen Core Processor PCIe Controller (x16) (rev 05) 00:01.1 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x8) (rev 05) 00:01.2 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x4) (rev 05) 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model 00:14.0 USB controller: Intel Corporation 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller (rev 31) 00:14.2 Signal processing controller: Intel Corporation 100 Series/C230 Series Chipset Family Thermal Subsystem (rev 31) 00:15.0 Signal processing controller: Intel Corporation 100 Series/C230 Series Chipset Family Serial IO I2C Controller #0 (rev 31) 00:15.1 Signal processing controller: Intel Corporation 100 Series/C230 Series Chipset Family Serial IO I2C Controller #1 (rev 31) 00:15.2 Signal processing controller: Intel Corporation 100 Series/C230 Series Chipset Family Serial IO I2C Controller #2 (rev 31) 00:16.0 Communication controller: Intel Corporation 100 Series/C230 Series Chipset Family MEI Controller #1 (rev 31) 00:1c.0 PCI bridge: Intel Corporation 100 Series/C23
[Bug 219091] amdgpu: after updating to linux 6.10, screen flickering occurs
https://bugzilla.kernel.org/show_bug.cgi?id=219091 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 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 211807] [drm:drm_dp_mst_dpcd_read] *ERROR* mstb 000000004e6288dd port 3: DPCD read on addr 0x60 for 1 bytes NAKed
https://bugzilla.kernel.org/show_bug.cgi?id=211807 joggarden (wellsedith...@gmail.com) changed: What|Removed |Added CC||wellsedith...@gmail.com --- Comment #28 from joggarden (wellsedith...@gmail.com) --- This error indicates a problem with DisplayPort Multi-Stream Transport (MST) on your system. While it hasn't caused visible issues, it's worth investigating. You might try updating your kernel to the latest version if you haven't already, as MST support has seen continuous improvements. https://drift-hunters.io -- 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 219091] New: amdgpu: after updating to linux 6.10, screen flickering occurs
https://bugzilla.kernel.org/show_bug.cgi?id=219091 Bug ID: 219091 Summary: amdgpu: after updating to linux 6.10, screen flickering occurs Product: Drivers Version: 2.5 Hardware: AMD OS: Linux Status: NEW Severity: high Priority: P3 Component: Video(DRI - non Intel) Assignee: drivers_video-...@kernel-bugs.osdl.org Reporter: hurricanepoo...@protonmail.com Regression: No Arch Linux updated their linux package to 6.10 recently, and since then, my system has had a screen flickering on the upper portion of the monitor. I tried out linux-lts, and the flickering went away. Furthermore, I downgraded the linux package back to 6.9.10, and the flickering also went away. My setup is: KDE Plasma 6.1.3, Xorg-Server 21.1.13, Mesa 24.1.4, and libdrm 2.4.122. I have a Radeon RX 6800 and a Ryzen 5 5600. The flickering occurs both on X11 and Wayland. My display is an Acer KG240, and is connected over displayport at 144hz. I have found one other report, which has a youtube video uploaded of the problem: https://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg1981054.html -- 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 219007] opening and closing /dev/dri/card0 in a QEMU KVM instance will shutdown system, 6.10.0-rc6+
https://bugzilla.kernel.org/show_bug.cgi?id=219007 Colin Ian King (colin.i.k...@gmail.com) changed: What|Removed |Added CC||colin.i.k...@gmail.com --- Comment #5 from Colin Ian King (colin.i.k...@gmail.com) --- Created attachment 306610 --> https://bugzilla.kernel.org/attachment.cgi?id=306610&action=edit dmesg 6.10 log Attached, dmesg log. Apologies for the delayed reply. -- 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 211807] [drm:drm_dp_mst_dpcd_read] *ERROR* mstb 000000004e6288dd port 3: DPCD read on addr 0x60 for 1 bytes NAKed
https://bugzilla.kernel.org/show_bug.cgi?id=211807 getcrarea (farareja...@gmail.com) changed: What|Removed |Added CC||farareja...@gmail.com --- Comment #27 from getcrarea (farareja...@gmail.com) --- Games often involve setting goals https://snakeio.org working towards them, which can help players develop perseverance and determination. -- 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 201497] [amdgpu]: '*ERROR* No EDID read' is back in 4.19
https://bugzilla.kernel.org/show_bug.cgi?id=201497 --- Comment #36 from Rev (r...@pop.ms) --- I still get around 700 error logs per day on my 24/7 PC. amdgpu :06:00.0: [drm] *ERROR* No EDID read. I am using the standard-kernel of ubuntu 24.04 LTS now (6.8.0-36-generic), with the standard mesa (24.0.9) drivers that come with the OS. Display standby's and wake-up's work as intended tho in ubuntu 24.04. Putting the whole system on standby and waking it up works since the change from ubuntu 22.04 to 24.04. So for me it is not an issue about a function. It is an issue that is most prominent in the logs of ubuntu. If I did not review the logs I would never had known about wake-up issues in 24.04, that was different in 22.04. Putting the PC in standby in 22.04 meant never waking up the display again and the need of a cold boot. But an average of 700 error messages per day means there is something not working right, imo. And since that is a very, very old issue since a far older kernel version, and a lot of AMD gpu users out there, I would like to help. But I am not a tech expert, just a user who can read stuff and do stuff a bit better that an average user. So please, if you want some more help from users with that issue, please explain how we can help for a solution and I would guess people would contribute their information to help solving this issue. Sorry for the long winded comment. -- 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 201497] [amdgpu]: '*ERROR* No EDID read' is back in 4.19
https://bugzilla.kernel.org/show_bug.cgi?id=201497 --- Comment #35 from Emre (ereno...@gmail.com) --- Hi Artem, I did not see my issue (stated above) since the last few kernel releases. I'm now at 6.9.9-arch1-1. These days it seemed reliable to me. Sometimes I'm losing "4k resolution" but that may be due to the Monitor not the driver (power cycling monitor fixes it). -- 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 201497] [amdgpu]: '*ERROR* No EDID read' is back in 4.19
https://bugzilla.kernel.org/show_bug.cgi?id=201497 Artem S. Tashkinov (a...@gmx.com) changed: What|Removed |Added CC||a...@gmx.com --- Comment #34 from Artem S. Tashkinov (a...@gmx.com) --- If no one wants this bug to be fixed, I will close the freedesktop issue. The AMD team can't do much if the affected people are not willing to collaborate. -- 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 201497] [amdgpu]: '*ERROR* No EDID read' is back in 4.19
https://bugzilla.kernel.org/show_bug.cgi?id=201497 Artem S. Tashkinov (a...@gmx.com) changed: What|Removed |Added URL||https://gitlab.freedesktop. ||org/drm/amd/-/issues/3494 --- Comment #33 from Artem S. Tashkinov (a...@gmx.com) --- Please take it to here: https://gitlab.freedesktop.org/drm/amd/-/issues/3494 -- 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 201497] [amdgpu]: '*ERROR* No EDID read' is back in 4.19
https://bugzilla.kernel.org/show_bug.cgi?id=201497 Artem S. Tashkinov (a...@gmx.com) changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |ANSWERED --- Comment #32 from Artem S. Tashkinov (a...@gmx.com) --- All the amdgpu hackers are here, please refile and attach dmesg for 6.10 if you're still affected: 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 201497] [amdgpu]: '*ERROR* No EDID read' is back in 4.19
https://bugzilla.kernel.org/show_bug.cgi?id=201497 --- Comment #31 from gabriel barros (gabrielbarro...@gmail.com) --- Created attachment 306574 --> https://bugzilla.kernel.org/attachment.cgi?id=306574&action=edit 6.9.9 kernel logs, rebooting with monitor connected. -- 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 201497] [amdgpu]: '*ERROR* No EDID read' is back in 4.19
https://bugzilla.kernel.org/show_bug.cgi?id=201497 --- Comment #30 from gabriel barros (gabrielbarro...@gmail.com) --- Created attachment 306573 --> https://bugzilla.kernel.org/attachment.cgi?id=306573&action=edit kernel logs, failure when attaching HDMI cable to long running system Adding to Comment 29. I still get the EDID errors even when it "works" after a reboot-with-monitor-already-plugged. Here are the logs. First the log for the failure, which happens when i plug in the monitor in a long running 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 201497] [amdgpu]: '*ERROR* No EDID read' is back in 4.19
https://bugzilla.kernel.org/show_bug.cgi?id=201497 gabriel barros (gabrielbarro...@gmail.com) changed: What|Removed |Added CC||gabrielbarro...@gmail.com --- Comment #29 from gabriel barros (gabrielbarro...@gmail.com) --- This bug doesn't have much trigger information. But i arrived here with a completely different system than what is on the reports (6650U iGPU, with both a DP monitor and a hdmi1.2 and 1.4 TVs). Reboot as mentioned in Comment 25 "solved" it. The link on Comment 18 is dead, in case anyone want to share the kernel options 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 219007] opening and closing /dev/dri/card0 in a QEMU KVM instance will shutdown system, 6.10.0-rc6+
https://bugzilla.kernel.org/show_bug.cgi?id=219007 --- Comment #4 from The Linux kernel's regression tracker (Thorsten Leemhuis) (regressi...@leemhuis.info) --- And one more comment: could you please share a dmesg from the VM so we know what drm driver is used. -- 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 219007] opening and closing /dev/dri/card0 in a QEMU KVM instance will shutdown system, 6.10.0-rc6+
https://bugzilla.kernel.org/show_bug.cgi?id=219007 --- Comment #3 from The Linux kernel's regression tracker (Thorsten Leemhuis) (regressi...@leemhuis.info) --- Forgot: I'll forward this report by mail, as it's a regression, so no need to do anything for you. But it's not the first bug I see from you here, so I thought a reminder might be wise. -- 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 219007] opening and closing /dev/dri/card0 in a QEMU KVM instance will shutdown system, 6.10.0-rc6+
https://bugzilla.kernel.org/show_bug.cgi?id=219007 The Linux kernel's regression tracker (Thorsten Leemhuis) (regressi...@leemhuis.info) changed: What|Removed |Added CC||regressi...@leemhuis.info --- Comment #2 from The Linux kernel's regression tracker (Thorsten Leemhuis) (regressi...@leemhuis.info) --- Colin, quick reminder: many bugs reported here are never forwarded to any developer. For some of the details see https://lwn.net/Articles/910740/ and the links in there. So the people you are trying to reach most likely won't even see this. Mail is usually the best for reporting, as mentioned in https://docs.kernel.org/admin-guide/reporting-issues.html (which also tells people to avoid bugzilla in most cases) -- 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 219007] opening and closing /dev/dri/card0 in a QEMU KVM instance will shutdown system, 6.10.0-rc6+
https://bugzilla.kernel.org/show_bug.cgi?id=219007 --- Comment #1 from Colin Ian King (colin.i.k...@gmail.com) --- Note this also can reproduce when running *without* root privileged too, so this is a user space DoS attack vector. -- 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 219007] opening and closing /dev/dri/card0 in a QEMU KVM instance will shutdown system, 6.10.0-rc6+
https://bugzilla.kernel.org/show_bug.cgi?id=219007 Colin Ian King (colin.i.k...@gmail.com) changed: What|Removed |Added Hardware|All |Intel Severity|normal |high -- 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 219007] New: opening and closing /dev/dri/card0 in a QEMU KVM instance will shutdown system, 6.10.0-rc6+
https://bugzilla.kernel.org/show_bug.cgi?id=219007
Bug ID: 219007
Summary: opening and closing /dev/dri/card0 in a QEMU KVM
instance will shutdown system, 6.10.0-rc6+
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: colin.i.k...@gmail.com
Regression: No
The following code when run as root on a Debian sid amd64 server running in
virt-manager (KVM QEMU) will shut the system down with 6.10.0-rc6. The fork()
is required to cause racing on the open/close on /dev/dri/card0
#include
#include
int main(void)
{
pid_t pid = fork();
while (1) {
int fd;
fd = openat(AT_FDCWD, "/dev/dri/card0",
O_WRONLY|O_NONBLOCK|O_SYNC);
close(fd);
}
}
This was originally found using: while true; do sudo ./stress-ng --dev 4
--dev-file /dev/dri/card0 -t 5; done and narrowed down to the above reproducer.
(cf: https://github.com/ColinIanKing/stress-ng/issues/407 )
This does not occur on pre 6.10 kernels, so it looks like a 6.10 regression.
--
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 218900] amdgpu: Fatal error during GPU init
https://bugzilla.kernel.org/show_bug.cgi?id=218900 --- Comment #22 from Vasant Hegde (vasant.he...@amd.com) --- (In reply to dreamlike_clinking040 from comment #21) > (In reply to Vasant Hegde from comment #19) > > Can confirm this patch also fixes my suspend/resume issue, thanks! Thanks a lot. -Vasant -- 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 218900] amdgpu: Fatal error during GPU init
https://bugzilla.kernel.org/show_bug.cgi?id=218900 dreamlike_clinking...@simplelogin.com changed: What|Removed |Added CC||dreamlike_clinking040@simpl ||elogin.com --- Comment #21 from dreamlike_clinking...@simplelogin.com --- (In reply to Vasant Hegde from comment #19) > Unfortunately there was another big in suspend/resume path. Can you please > test with below patch? > > https://lore.kernel.org/linux-iommu/znqzxycu8bn32...@8bytes.org/T/ > #m1cd1520facb8b758efdf7a8c0261f9ee2ec217d7 > > > > -Vasant Can confirm this patch also fixes my suspend/resume issue, thanks! -- 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 218993] SIGBUS with amdgpu on multi-GPU system on X server with DRI3/GBM
https://bugzilla.kernel.org/show_bug.cgi?id=218993 Artem S. Tashkinov (a...@gmx.com) changed: What|Removed |Added URL||https://gitlab.freedesktop. ||org/drm/amd/-/issues/3457 -- 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 218993] SIGBUS with amdgpu on multi-GPU system on X server with DRI3/GBM
https://bugzilla.kernel.org/show_bug.cgi?id=218993 Artem S. Tashkinov (a...@gmx.com) changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |MOVED -- 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 218993] SIGBUS with amdgpu on multi-GPU system on X server with DRI3/GBM
https://bugzilla.kernel.org/show_bug.cgi?id=218993 --- Comment #2 from Artem S. Tashkinov (a...@gmx.com) --- This doesn't look like a kernel bug to me. You could try asking here though: 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 218993] SIGBUS with amdgpu on multi-GPU system on X server with DRI3/GBM
https://bugzilla.kernel.org/show_bug.cgi?id=218993 ad...@cendio.se changed: What|Removed |Added Kernel Version||6.9.5-200.fc40.x86_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 218993] SIGBUS with amdgpu on multi-GPU system on X server with DRI3/GBM
https://bugzilla.kernel.org/show_bug.cgi?id=218993 --- Comment #1 from ad...@cendio.se --- To clarify, the crash does not come from gbm_bo_map() directly, but by the incorrectly mapped memory which causes a crash later in the program. -- 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 218993] New: SIGBUS with amdgpu on multi-GPU system on X server with DRI3/GBM
https://bugzilla.kernel.org/show_bug.cgi?id=218993 Bug ID: 218993 Summary: SIGBUS with amdgpu on multi-GPU system on X server with DRI3/GBM 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: ad...@cendio.se Regression: No Created attachment 306503 --> https://bugzilla.kernel.org/attachment.cgi?id=306503&action=edit trace before crash, Xvnc on Ryzen 5 7600, vkcube on Arc A380 I ran into a SIGBUS when using multiple GPUs and DRI with an X server that has GPU acceleration (TigerVNC's Xvnc). This happened on a machine with: OS: Fedora 40 running 6.9.5-200.fc40.x86_64 iGPU: Ryzen 5 7600 dGPU: RTX 4060 | Arc A380 | RX 7600 The issue occurs when the X server is configured to use an AMD rendernode, and an application wants to use a non-AMD rendernode. When opening the AMD rendernode using gbm_create_device(), a SIGBUS will occur when gbm_bo_map() is called, if the application wants to use another rendernode that is not an AMD GPU. In my setup, /dev/dri/renderD128 is the AMD iGPU, and /dev/dri/renderD129 is an RTX 4060. If I run the X server with $ Xvnc :50 -rendernode /dev/dri/renderD128 and vkcube with renderD129 on the X server $ DISPLAY=:50 vkcube --gpu_number 1 I get the sigbus: (EE) (EE) Backtrace: (EE) 0: Xvnc (xorg_backtrace+0x82) [0x560c52b47d42] (EE) 1: Xvnc (0x560c52991000+0x1b7f4c) [0x560c52b48f4c] (EE) 2: /lib64/libc.so.6 (0x7f0c99613000+0x40710) [0x7f0c99653710] (EE) 3: /lib64/libpixman-1.so.0 (0x7f0c99ed+0x8a2d0) [0x7f0c99f5a2d0] (EE) 4: /lib64/libpixman-1.so.0 (pixman_blt+0x81) [0x7f0c99ede8d1] (EE) 5: Xvnc (vncDRI3SyncPixmapFromGPU+0x10e) [0x560c529f303e] (EE) 6: Xvnc (0x560c52991000+0x622c3) [0x560c529f32c3] (EE) 7: Xvnc (dri3_pixmap_from_fds+0xcf) [0x560c52a7fdaf] (EE) 8: Xvnc (0x560c52991000+0xf1309) [0x560c52a82309] (EE) 9: Xvnc (Dispatch+0x426) [0x560c52ae3f56] (EE) 10: Xvnc (dix_main+0x46a) [0x560c52af2d4a] (EE) 11: /lib64/libc.so.6 (0x7f0c99613000+0x2a088) [0x7f0c9963d088] (EE) 12: /lib64/libc.so.6 (__libc_start_main+0x8b) [0x7f0c9963d14b] (EE) 13: Xvnc (_start+0x25) [0x560c529eed75] (EE) (EE) Bus error at address 0x7f0c8e211000 (EE) Fatal server error: (EE) Caught signal 7 (Bus error). Server aborting (EE) Aborted (core dumped) The same crash occurs when running vkcube on an Arc GPU (A380). However, running the X server on an Arc or Nvidia GPU, and vkcube on the AMD GPU, does not cause a crash. Neither does running the X server on AMD, and vkcube on a different AMD GPU (iGPU & RX 7600 for example). I've attached a stacktrace with the last call to mmap() before the crash. -- 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 218900] amdgpu: Fatal error during GPU init
https://bugzilla.kernel.org/show_bug.cgi?id=218900 --- Comment #20 from Jean-Denis Girard (jd.gir...@sysnux.pf) --- Yes, I confirm the patch "iommu/amd: Fix GT feature enablement again" applied to 6.10-rc5 fixes resume on my machine. Thanks for prompt reply! -- 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 218900] amdgpu: Fatal error during GPU init
https://bugzilla.kernel.org/show_bug.cgi?id=218900 --- Comment #19 from Vasant Hegde (vasant.he...@amd.com) --- Unfortunately there was another big in suspend/resume path. Can you please test with below patch? https://lore.kernel.org/linux-iommu/znqzxycu8bn32...@8bytes.org/T/#m1cd1520facb8b758efdf7a8c0261f9ee2ec217d7 -Vasant -- 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 218900] amdgpu: Fatal error during GPU init
https://bugzilla.kernel.org/show_bug.cgi?id=218900 --- Comment #18 from Jean-Denis Girard (jd.gir...@sysnux.pf) --- Created attachment 306495 --> https://bugzilla.kernel.org/attachment.cgi?id=306495&action=edit Complete dmesg -- 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 218900] amdgpu: Fatal error during GPU init
https://bugzilla.kernel.org/show_bug.cgi?id=218900 Jean-Denis Girard (jd.gir...@sysnux.pf) changed: What|Removed |Added CC||jd.gir...@sysnux.pf --- Comment #17 from Jean-Denis Girard (jd.gir...@sysnux.pf) --- I seem to have a similar problem on 6.10-rc5 after suspend. I get a black screen on resume. [ 269.157149] amdgpu :02:00.0: amdgpu: reserve 0x40 from 0xf41f80 for PSP TMR [ 269.159956] iommu ivhd0: AMD-Vi: Event logged [ILLEGAL_DEV_TABLE_ENTRY device=:02:00.0 pasid=0x0 address=0x13140 flags=0x0180] [ 269.159960] AMD-Vi: DTE[0]: 6193 [ 269.159962] AMD-Vi: DTE[1]: 1001049e000b [ 269.159963] AMD-Vi: DTE[2]: 20013c610013 [ 269.159963] AMD-Vi: DTE[3]: [ 269.160104] amdgpu :02:00.0: amdgpu: failed to load ucode SDMA0(0x1) [ 269.160108] amdgpu :02:00.0: amdgpu: psp gfx command LOAD_IP_FW(0x6) failed and response status is (0xF) -- 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 211807] [drm:drm_dp_mst_dpcd_read] *ERROR* mstb 000000004e6288dd port 3: DPCD read on addr 0x60 for 1 bytes NAKed
https://bugzilla.kernel.org/show_bug.cgi?id=211807 TiaPadavano (jiloxe4...@elahan.com) changed: What|Removed |Added CC||jiloxe4...@elahan.com --- Comment #26 from TiaPadavano (jiloxe4...@elahan.com) --- This game is an epic adventure with breathtaking graphics. https://lafontanacitta.com/blog/what-time-does-mcdonalds-stop-selling-breakfast/ -- 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 211807] [drm:drm_dp_mst_dpcd_read] *ERROR* mstb 000000004e6288dd port 3: DPCD read on addr 0x60 for 1 bytes NAKed
https://bugzilla.kernel.org/show_bug.cgi?id=211807 Artem S. Tashkinov (a...@gmx.com) changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |ANSWERED --- Comment #25 from Artem S. Tashkinov (a...@gmx.com) --- Most Linux developers are not aware of this issue. If you're still affected using either 6.9.5 or 6.6.34, please file a new bug report here: For Intel: https://gitlab.freedesktop.org/drm/intel/-/issues For AMD: https://gitlab.freedesktop.org/drm/amd/-/issues To me it looks like a HW issue of some sort but I'm not an expert. Would be nice if affected people tried a different HDMI/DP cable. -- 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 206309] Experimental amdgpu w/ Dell E6540 with HD 8790M (MARS XTX), massive performance improvement after ACPI suspend
https://bugzilla.kernel.org/show_bug.cgi?id=206309 --- Comment #4 from jerbear3.14...@gmail.com --- Thanks for the quick reply. Guess I'll have to dust off ye ol' Windows installer and confirm once and for all who's to blame here. I'll post my findings here probably in a few weeks when I can. 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 206309] Experimental amdgpu w/ Dell E6540 with HD 8790M (MARS XTX), massive performance improvement after ACPI suspend
https://bugzilla.kernel.org/show_bug.cgi?id=206309 Travis Juntara (changhaitra...@gmail.com) changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WILL_NOT_FIX --- Comment #3 from Travis Juntara (changhaitra...@gmail.com) --- Pretty sure this is due to chipset or bios. After upgrading to i7 4810MQ, from i5 4310M standby mode no longer resets the power throttling, but rebooting does. Also I believe I've seen similar behavior reported by windows users. -- 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 206309] Experimental amdgpu w/ Dell E6540 with HD 8790M (MARS XTX), massive performance improvement after ACPI suspend
https://bugzilla.kernel.org/show_bug.cgi?id=206309 jerbear3.14...@gmail.com changed: What|Removed |Added CC||jerbear3.14...@gmail.com --- Comment #2 from jerbear3.14...@gmail.com --- Hi, did you ever figure anything else out with this bug? I have the same problem on a Dell Precision M2800 which has pretty much identical specs: ~$ DRI_PRIME=1 glxinfo -B name of display: :0.0 display: :0 screen: 0 direct rendering: Yes Extended renderer info (GLX_MESA_query_renderer): Vendor: AMD (0x1002) Device: AMD Radeon HD 8790M (oland, LLVM 15.0.7, DRM 3.54, 6.5.0-41-generic) (0x6606) Version: 23.2.1 Accelerated: yes Video memory: 2048MB Unified memory: no Preferred profile: core (0x1) Max core profile version: 4.6 Max compat profile version: 4.6 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.2 Memory info (GL_ATI_meminfo): VBO free memory - total: 1667 MB, largest block: 1667 MB VBO free aux. memory - total: 3882 MB, largest block: 3882 MB Texture free memory - total: 1667 MB, largest block: 1667 MB Texture free aux. memory - total: 3882 MB, largest block: 3882 MB Renderbuffer free memory - total: 1667 MB, largest block: 1667 MB Renderbuffer free aux. memory - total: 3882 MB, largest block: 3882 MB Memory info (GL_NVX_gpu_memory_info): Dedicated video memory: 2048 MB Total available memory: 5966 MB Currently available dedicated video memory: 1667 MB OpenGL vendor string: AMD OpenGL renderer string: AMD Radeon HD 8790M (oland, LLVM 15.0.7, DRM 3.54, 6.5.0-41-generic) OpenGL core profile version string: 4.6 (Core Profile) Mesa 23.2.1-1ubuntu3.1 OpenGL core profile shading language version string: 4.60 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL version string: 4.6 (Compatibility Profile) Mesa 23.2.1-1ubuntu3.1 OpenGL shading language version string: 4.60 OpenGL context flags: (none) OpenGL profile mask: compatibility profile OpenGL ES profile version string: OpenGL ES 3.2 Mesa 23.2.1-1ubuntu3.1 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 I also set `radeon.si_support=0 amdgpu.si_support=1` in order to force the amdgpu driver. The interesting thing is that the bug happens specifically when I boot up with the charger plugged in (AC power brick; not a docking station), and when I unplug it, the GPU clock speeds tank to 300MHz memory/300MHz shader. I've tried forcing the performance level back up to "high" which gives me this error: echo -n high > /sys/class/drm/card1/device/power_dpm_force_performance_level bash: echo: write error: Invalid argument up until I reboot again, and the cycle restarts. It's pretty annoying how careful I have to be about staying plugged in. Any help is appreciated! -- 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 211807] [drm:drm_dp_mst_dpcd_read] *ERROR* mstb 000000004e6288dd port 3: DPCD read on addr 0x60 for 1 bytes NAKed
https://bugzilla.kernel.org/show_bug.cgi?id=211807 Felix Andrea (felixandre...@gmail.com) changed: What|Removed |Added CC||felixandre...@gmail.com --- Comment #24 from Felix Andrea (felixandre...@gmail.com) --- I have tried updating the driver and related firmware but it still doesn't seem to solve the problem. Does disabling fwupd checking DP aux ports help? I found this thread: https://lists.freedesktop.org/archives/dri-devel/2022-February/342776.html https://ricepurity-test.io/ but not really know how to fix it. -- 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 218900] amdgpu: Fatal error during GPU init
https://bugzilla.kernel.org/show_bug.cgi?id=218900 --- Comment #16 from Vasant Hegde (vasant.he...@amd.com) --- (In reply to Hanabishi from comment #15) > (In reply to Vasant Hegde from comment #5) > > Created attachment 306364 [details] > > Check Enhanced PPR support before enabling PPR > > I applied your patch on top of rc2 and also confirm that it works. > Thank you. Thanks Hanabishi for testing. FYI. Patches merged into -rc3. -Vasant -- 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 218900] amdgpu: Fatal error during GPU init
https://bugzilla.kernel.org/show_bug.cgi?id=218900 --- Comment #15 from Hanabishi (i.r.e.c.c.a.k.u.n+bugzilla.kernel@gmail.com) --- (In reply to Vasant Hegde from comment #5) > Created attachment 306364 [details] > Check Enhanced PPR support before enabling PPR I applied your patch on top of rc2 and also confirm that it works. Thank you. -- 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 218900] amdgpu: Fatal error during GPU init
https://bugzilla.kernel.org/show_bug.cgi?id=218900 Hanabishi (i.r.e.c.c.a.k.u.n+bugzilla.kernel@gmail.com) changed: What|Removed |Added CC||i.r.e.c.c.a.k.u.n+bugzilla. ||kernel@gmail.com --- Comment #14 from Hanabishi (i.r.e.c.c.a.k.u.n+bugzilla.kernel@gmail.com) --- *** Bug 218921 has been marked as a duplicate of this bug. *** -- 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 #103 from MasterCATZ (masterc...@hotmail.com) --- and 6.9.3 also crashed -- 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 #102 from MasterCATZ (masterc...@hotmail.com) --- issue seems to only be with xorg , used wayland today and could not trigger it -- 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 #101 from Mario Limonciello (AMD) (mario.limoncie...@amd.com) --- #100: You have a GFX10 product, this is not affected by amdgpu.mcbp=0/1. That's only for GFX9. Please open your own issue for it. Also in the kernel bug tracker please only report issues with mainline kernels. 6.8 is already EoL. -- 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 MasterCATZ (masterc...@hotmail.com) changed: What|Removed |Added CC||masterc...@hotmail.com --- Comment #100 from MasterCATZ (masterc...@hotmail.com) --- I am pretty sure I have amdgpu.mcbp=0 set and after doing Ubuntu 24.04 LTS , just doing just about anything crashes the GPU open web browser = crash , then I have to ssh in and restart desktop session GL_VENDOR: AMD GL_RENDERER: AMD Radeon RX 6800 XT (radeonsi, navi21, LLVM 15.0.7, DRM 3.57, 6.8.0-31-generic) GL_VERSION:4.6 (Compatibility Profile) Mesa 24.2~git2406010600.71d455~oibaf~j (git-71d455b 2024-06-01 jammy-oi 6.8.0-31-generic [ 26.417827] [drm] amdgpu kernel modesetting enabled. [ 26.431708] amdgpu: Virtual CRAT table created for CPU [ 26.431727] amdgpu: Topology: Add CPU node [ 26.431934] [drm] initializing kernel modesetting (SIENNA_CICHLID 0x1002:0x73BF 0x1043:0x04F0 0xC1). [ 26.431949] [drm] register mmio base: 0xFC90 [ 26.431951] [drm] register mmio size: 1048576 [ 26.435975] [drm] add ip block number 0 [ 26.435978] [drm] add ip block number 1 [ 26.435980] [drm] add ip block number 2 [ 26.435982] [drm] add ip block number 3 [ 26.435983] [drm] add ip block number 4 [ 26.435985] [drm] add ip block number 5 [ 26.435986] [drm] add ip block number 6 [ 26.435988] [drm] add ip block number 7 [ 26.435990] [drm] add ip block number 8 [ 26.435996] [drm] add ip block number 9 [ 26.436013] amdgpu :0e:00.0: No more image in the PCI ROM [ 26.436028] amdgpu :0e:00.0: amdgpu: Fetched VBIOS from ROM BAR [ 26.436031] amdgpu: ATOM BIOS: 115-D412BS0-101 [ 26.473962] [drm] VCN(0) decode is enabled in VM mode [ 26.473965] [drm] VCN(1) decode is enabled in VM mode [ 26.473967] [drm] VCN(0) encode is enabled in VM mode [ 26.473968] [drm] VCN(1) encode is enabled in VM mode [ 26.477565] [drm] JPEG decode is enabled in VM mode [ 26.477596] amdgpu :0e:00.0: vgaarb: deactivate vga console [ 26.478479] Console: switching to colour dummy device 80x25 [ 26.478490] amdgpu :0e:00.0: amdgpu: Trusted Memory Zone (TMZ) feature disabled as experimental (default) [ 26.478548] amdgpu :0e:00.0: amdgpu: MEM ECC is not presented. [ 26.478550] amdgpu :0e:00.0: amdgpu: SRAM ECC is not presented. [ 26.478570] [drm] vm size is 262144 GB, 4 levels, block size is 9-bit, fragment size is 9-bit [ 26.478577] amdgpu :0e:00.0: amdgpu: VRAM: 16368M 0x0080 - 0x0083FEFF (16368M used) [ 26.478580] amdgpu :0e:00.0: amdgpu: GART: 512M 0x - 0x1FFF [ 26.478588] [drm] Detected VRAM RAM=16368M, BAR=256M [ 26.478589] [drm] RAM width 256bits GDDR6 [ 26.478734] [drm] amdgpu: 16368M of VRAM memory ready [ 26.478739] [drm] amdgpu: 64363M of GTT memory ready. [ 26.478768] [drm] GART: num cpu pages 131072, num gpu pages 131072 [ 26.478919] [drm] PCIE GART of 512M enabled (table at 0x00800090). [ 27.968739] amdgpu :0e:00.0: amdgpu: STB initialized to 2048 entries [ 27.969354] [drm] Loading DMUB firmware via PSP: version=0x02020020 [ 27.969777] [drm] use_doorbell being set to: [true] [ 27.969791] [drm] use_doorbell being set to: [true] [ 27.969803] [drm] use_doorbell being set to: [true] [ 27.969815] [drm] use_doorbell being set to: [true] [ 27.969830] [drm] Found VCN firmware Version ENC: 1.30 DEC: 3 VEP: 0 Revision: 4 [ 27.969842] amdgpu :0e:00.0: amdgpu: Will use PSP to load VCN firmware [ 28.036225] [drm] reserve 0xa0 from 0x83fd00 for PSP TMR [ 28.184762] amdgpu :0e:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available [ 28.184784] amdgpu :0e:00.0: amdgpu: smu driver if version = 0x0040, smu fw if version = 0x0041, smu fw program = 0, version = 0x003a5900 (58.89.0) [ 28.184788] amdgpu :0e:00.0: amdgpu: SMU driver if version not matched [ 28.184816] amdgpu :0e:00.0: amdgpu: use vbios provided pptable [ 28.257551] amdgpu :0e:00.0: amdgpu: SMU is initialized successfully! [ 28.257835] [drm] Display Core v3.2.266 initialized on DCN 3.0 [ 28.257837] [drm] DP-HDMI FRL PCON supported [ 28.259090] [drm] DMUB hardware initialized: version=0x02020020 [ 28.261811] snd_hda_intel :0e:00.1: bound :0e:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) [ 28.390798] [drm] kiq ring mec 2 pipe 1 q 0 [ 28.398526] [drm] VCN decode and encode initialized successfully(under DPG Mode). [ 28.398700] [drm] JPEG decode initialized successfully. [ 28.471332] amdgpu: HMM registered 16368MB device memory [ 28.473409] kfd kfd: amdgpu: Allocated 3969056 bytes on gart [ 28.473425] kfd kfd: amdgpu: Total number of KFD nodes to be created: 1 [ 28.473606] amdgpu: Virtual CRAT table created for GPU [ 28.474183]
[Bug 218900] amdgpu: Fatal error during GPU init
https://bugzilla.kernel.org/show_bug.cgi?id=218900 --- Comment #13 from Vasant Hegde (vasant.he...@amd.com) --- Thanks Jean for testing. I will send patch with your Tested-by today. -Vasant -- 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 218900] amdgpu: Fatal error during GPU init
https://bugzilla.kernel.org/show_bug.cgi?id=218900 Artem S. Tashkinov (a...@gmx.com) changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |CODE_FIX -- 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 218900] amdgpu: Fatal error during GPU init
https://bugzilla.kernel.org/show_bug.cgi?id=218900 --- Comment #12 from Jean-Christophe Guillain (jean-christo...@guillain.net) --- (I still finished my bisection, and as you said, c4cb2303a841c2df30058597398443bcad5f is the first bad 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 218900] amdgpu: Fatal error during GPU init
https://bugzilla.kernel.org/show_bug.cgi?id=218900 Jean-Christophe Guillain (jean-christo...@guillain.net) changed: What|Removed |Added Bisected commit-id||c4cb2303a841c2df3005859 ||7398443bcad5f -- 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 218900] amdgpu: Fatal error during GPU init
https://bugzilla.kernel.org/show_bug.cgi?id=218900 --- Comment #11 from Jean-Christophe Guillain (jean-christo...@guillain.net) --- Created attachment 306367 --> https://bugzilla.kernel.org/attachment.cgi?id=306367&action=edit Full dmesg after applying Vasant's 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 218900] amdgpu: Fatal error during GPU init
https://bugzilla.kernel.org/show_bug.cgi?id=218900 --- Comment #10 from Jean-Christophe Guillain (jean-christo...@guillain.net) --- I applied your patch to the 6.10.0-rc1 kernel, and I confirm that it fixes this bug. Thank you very much ! jC (full dmesg attached) -- 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 218900] amdgpu: Fatal error during GPU init
https://bugzilla.kernel.org/show_bug.cgi?id=218900 Mario Limonciello (AMD) (mario.limoncie...@amd.com) changed: What|Removed |Added Attachment #306364|0 |1 is 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 218900] amdgpu: Fatal error during GPU init
https://bugzilla.kernel.org/show_bug.cgi?id=218900 --- Comment #9 from Vasant Hegde (vasant.he...@amd.com) --- (In reply to Jean-Christophe Guillain from comment #8) > Hi, > > I plan to finish the bisection today, and I'll test your patch. > You mean bisecting for this issue? If so we know the culprit commit. Issue is happening because IOMMU driver tried to enable PPR bit in DTE without checking Enhanced PPR support in EFR register. -Vasant -- 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 218900] amdgpu: Fatal error during GPU init
https://bugzilla.kernel.org/show_bug.cgi?id=218900 --- Comment #8 from Jean-Christophe Guillain (jean-christo...@guillain.net) --- Hi, I plan to finish the bisection today, and I'll test your patch. jC -- 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 218900] amdgpu: Fatal error during GPU init
https://bugzilla.kernel.org/show_bug.cgi?id=218900 --- Comment #7 from Vasant Hegde (vasant.he...@amd.com) --- Also can you please attach full dmesg? I want to see IOMMU feature list and confirm what I am doing is right. -Vasant -- 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 218900] amdgpu: Fatal error during GPU init
https://bugzilla.kernel.org/show_bug.cgi?id=218900 --- Comment #6 from Vasant Hegde (vasant.he...@amd.com) --- Hi, Attached patch should fix this issue. Can you please test it? I will send proper patch to mailing list soon. -Vasant -- 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 218900] amdgpu: Fatal error during GPU init
https://bugzilla.kernel.org/show_bug.cgi?id=218900 Vasant Hegde (vasant.he...@amd.com) changed: What|Removed |Added CC||vasant.he...@amd.com --- Comment #5 from Vasant Hegde (vasant.he...@amd.com) --- Created attachment 306364 --> https://bugzilla.kernel.org/attachment.cgi?id=306364&action=edit Check Enhanced PPR support before enabling PPR -- 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 218900] amdgpu: Fatal error during GPU init
https://bugzilla.kernel.org/show_bug.cgi?id=218900 Mario Limonciello (AMD) (mario.limoncie...@amd.com) changed: What|Removed |Added CC||mario.limoncie...@amd.com --- Comment #4 from Mario Limonciello (AMD) (mario.limoncie...@amd.com) --- Possibly the same as this report: https://lore.kernel.org/all/20240527192159.GEZlTdV7OoOuJrHmI0@fat_crate.local/ -- 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 218900] amdgpu: Fatal error during GPU init
https://bugzilla.kernel.org/show_bug.cgi?id=218900 Jean-Christophe Guillain (jean-christo...@guillain.net) changed: What|Removed |Added Bisected commit-id|db5d28c0bfe566908719bec8e25 | |443aabecbb802 | -- 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 218900] amdgpu: Fatal error during GPU init
https://bugzilla.kernel.org/show_bug.cgi?id=218900 --- Comment #3 from Jean-Christophe Guillain (jean-christo...@guillain.net) --- Bisecting: 5720 revisions left to test after this (roughly 13 steps) I'll try, but it will take some time. My machine is not very powerful... -- 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 218900] amdgpu: Fatal error during GPU init
https://bugzilla.kernel.org/show_bug.cgi?id=218900 Alex Deucher (alexdeuc...@gmail.com) changed: What|Removed |Added CC||alexdeuc...@gmail.com --- Comment #2 from Alex Deucher (alexdeuc...@gmail.com) --- Can you bisect? https://docs.kernel.org/admin-guide/bug-bisect.html -- 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 218900] amdgpu: Fatal error during GPU init
https://bugzilla.kernel.org/show_bug.cgi?id=218900 Jean-Christophe Guillain (jean-christo...@guillain.net) changed: What|Removed |Added Bisected commit-id||db5d28c0bfe566908719bec8e25 ||443aabecbb802 Kernel Version||6.10.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 218900] amdgpu: Fatal error during GPU init
https://bugzilla.kernel.org/show_bug.cgi?id=218900 --- Comment #1 from Jean-Christophe Guillain (jean-christo...@guillain.net) --- Created attachment 306354 --> https://bugzilla.kernel.org/attachment.cgi?id=306354&action=edit Full logs of the boot. I added the full log of the boot process showing all the 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 218900] New: amdgpu: Fatal error during GPU init
https://bugzilla.kernel.org/show_bug.cgi?id=218900 Bug ID: 218900 Summary: amdgpu: Fatal error during GPU init Product: Drivers Version: 2.5 Hardware: AMD OS: Linux Status: NEW Severity: blocking Priority: P3 Component: Video(DRI - non Intel) Assignee: drivers_video-...@kernel-bugs.osdl.org Reporter: jean-christo...@guillain.net Regression: No Hello ! Trying the new kernel RC today (6.10.0-rc1), I no longer have video. With 6.9.1 works. Lenovo ThinkCentre M715q 00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] (rev e4) In the journal, I have multiple entries like this one : May 27 14:24:22 youpi kernel: iommu ivhd0: AMD-Vi: Event logged [ILLEGAL_DEV_TABLE_ENTRY device=:00:01.0 pasid=0x0 address=0x102e89980 flags=0x0080] May 27 14:24:22 youpi kernel: AMD-Vi: DTE[0]: 7193 May 27 14:24:22 youpi kernel: AMD-Vi: DTE[1]: 1001034f0002 May 27 14:24:22 youpi kernel: AMD-Vi: DTE[2]: 20010022a013 May 27 14:24:22 youpi kernel: AMD-Vi: DTE[3]: Then, multiple entries like that one : May 27 14:24:22 youpi kernel: amdgpu :00:01.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring gfx test failed (-110) May 27 14:24:22 youpi kernel: [drm:amdgpu_device_init [amdgpu]] *ERROR* hw_init of IP block failed -110 May 27 14:24:22 youpi kernel: amdgpu :00:01.0: amdgpu: amdgpu_device_ip_init failed May 27 14:24:22 youpi kernel: amdgpu :00:01.0: amdgpu: Fatal error during GPU init May 27 14:24:22 youpi kernel: amdgpu :00:01.0: amdgpu: amdgpu: finishing device. May 27 14:24:22 youpi kernel: [ cut here ] May 27 14:24:22 youpi kernel: WARNING: CPU: 0 PID: 179 at drivers/gpu/drm/amd/amdgpu/amdgpu_irq.c:630 amdgpu_irq_put+0x45/0x70 [amdgpu] May 27 14:24:22 youpi kernel: Modules linked in: sd_mod usbhid uas hid usb_storage amdgpu(+) amdxcp drm_exec gpu_sched drm_buddy i2c_algo_bit drm_suballoc_helper drm> May 27 14:24:22 youpi kernel: CPU: 0 PID: 179 Comm: (udev-worker) Not tainted 6.10.0-rc1-jcg #1 May 27 14:24:22 youpi kernel: Hardware name: LENOVO 10VGS02P00/3130, BIOS M1XKT57A 02/10/2022 May 27 14:24:22 youpi kernel: RIP: 0010:amdgpu_irq_put+0x45/0x70 [amdgpu] May 27 14:24:22 youpi kernel: Code: 48 8b 4e 10 48 83 39 00 74 2c 89 d1 48 8d 04 88 8b 08 85 c9 74 14 f0 ff 08 b8 00 00 00 00 74 05 e9 80 d8 a3 fc e9 6b fd ff ff <0f> May 27 14:24:22 youpi kernel: RSP: 0018:bc9c80813a48 EFLAGS: 00010246 May 27 14:24:22 youpi kernel: RAX: 985ad74e3780 RBX: 985a82f18878 RCX: May 27 14:24:22 youpi kernel: RDX: RSI: 985a82f254b8 RDI: 985a82f0 May 27 14:24:22 youpi kernel: RBP: 985a82f10208 R08: R09: 0003 May 27 14:24:22 youpi kernel: R10: bc9c80813880 R11: bdec7828 R12: 985a82f105e8 May 27 14:24:22 youpi kernel: R13: 985a82f00010 R14: 985a82f0 R15: 985a82f254b8 May 27 14:24:22 youpi kernel: FS: 7f18ca0058c0() GS:985b5760() knlGS: May 27 14:24:22 youpi kernel: CS: 0010 DS: ES: CR0: 80050033 May 27 14:24:22 youpi kernel: CR2: 5563a55b3a68 CR3: 00010f8bc000 CR4: 001506f0 May 27 14:24:22 youpi kernel: Call Trace: May 27 14:24:22 youpi kernel: May 27 14:24:22 youpi kernel: ? __warn+0x7c/0x120 May 27 14:24:22 youpi kernel: ? amdgpu_irq_put+0x45/0x70 [amdgpu] May 27 14:24:22 youpi kernel: ? report_bug+0x155/0x170 May 27 14:24:22 youpi kernel: ? handle_bug+0x3f/0x80 May 27 14:24:22 youpi kernel: ? exc_invalid_op+0x13/0x60 May 27 14:24:22 youpi kernel: ? asm_exc_invalid_op+0x16/0x20 May 27 14:24:22 youpi kernel: ? amdgpu_irq_put+0x45/0x70 [amdgpu] May 27 14:24:22 youpi kernel: amdgpu_fence_driver_hw_fini+0xfa/0x130 [amdgpu] May 27 14:24:22 youpi kernel: amdgpu_device_fini_hw+0xa2/0x3f0 [amdgpu] May 27 14:24:22 youpi kernel: amdgpu_driver_load_kms+0x79/0xb0 [amdgpu] May 27 14:24:22 youpi kernel: amdgpu_pci_probe+0x182/0x4f0 [amdgpu] May 27 14:24:22 youpi kernel: local_pci_probe+0x41/0x90 May 27 14:24:22 youpi kernel: pci_device_probe+0xbb/0x1e0 May 27 14:24:22 youpi kernel: really_probe+0xd6/0x390 May 27 14:24:22 youpi kernel: ? __pfx___driver_attach+0x10/0x10 May 27 14:24:22 youpi kernel: __driver_probe_device+0x78/0x150 May 27 14:24:22 youpi kernel: driver_probe_device+0x1f/0x90 May 27 14:24:22 youpi kernel: __driver_attach+0xce/0x1c0 May 27 14:24:22 youpi kernel: bus_for_each_dev+0x84/0xd0 May 27 14:24:22 youpi kernel: bus_add_driver+0x10e/0x240 May 27 14:24:22 youpi kernel: driver_register+0x55/0x100 May 27 14:24:22 youpi kernel: ? __pfx_amdgpu_init+0x10/0x10 [amdgpu] May 27 14:24:22 youpi kernel: do_one_initcall+0x57/0x320 May 27 14:24:22 youpi kernel: do_init_module+0x60/0x230 May 27 14:24:22 youpi kernel: init_module_from_file+0x86/0xc0 May 27 14:2
[Bug 218891] In function ‘dcn321_update_bw_bounding_box’ - warning: the frame size of 1336 bytes is larger than 1280 bytes
https://bugzilla.kernel.org/show_bug.cgi?id=218891 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 refile here: https://gitlab.freedesktop.org/drm/amd/-/issues Thank you. -- 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 218891] In function ‘dcn321_update_bw_bounding_box’ - warning: the frame size of 1336 bytes is larger than 1280 bytes
https://bugzilla.kernel.org/show_bug.cgi?id=218891 sander44 (ionut_n2...@yahoo.com) changed: What|Removed |Added Kernel Version||6.9.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 218891] New: In function ‘dcn321_update_bw_bounding_box’ - warning: the frame size of 1336 bytes is larger than 1280 bytes
https://bugzilla.kernel.org/show_bug.cgi?id=218891 Bug ID: 218891 Summary: In function ‘dcn321_update_bw_bounding_box’ - warning: the frame size of 1336 bytes is larger than 1280 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: ionut_n2...@yahoo.com Regression: No Kernel 6.9.0 ... CC [M] drivers/gpu/drm/amd/amdgpu/../display/dc/dml2/dml2_wrapper.o CC [M] drivers/gpu/drm/amd/amdgpu/../display/dc/dml2/dml2_utils.o drivers/gpu/drm/amd/amdgpu/../display/dc/resource/dcn321/dcn321_resource.c: In function ‘dcn321_update_bw_bounding_box’: drivers/gpu/drm/amd/amdgpu/../display/dc/resource/dcn321/dcn321_resource.c:1599:1: warning: the frame size of 1336 bytes is larger than 1280 bytes [-Wframe-larger-than=] 1599 | } | ^ CC [M] drivers/gpu/drm/amd/amdgpu/../display/dc/dml2/dml2_policy.o CC [M] drivers/gpu/drm/amd/amdgpu/../display/dc/dml2/dml2_translation_helper.o CC [M] drivers/gpu/drm/amd/amdgpu/../display/dc/dml2/dml2_dc_resource_mgmt.o CC [M] drivers/gpu/drm/amd/amdgpu/../display/dc/dml2/dml2_mall_phantom.o CC [M] drivers/gpu/drm/amd/amdgpu/../display/dc/dml2/dml_display_rq_dlg_calc.o CC [M] drivers/gpu/drm/amd/amdgpu/../display/dc/dce120/dce120_timing_generator.o CC [M] drivers/gpu/drm/amd/amdgpu/../display/dc/dce112/dce112_compressor.o CC [M] drivers/gpu/drm/amd/amdgpu/../display/dc/dce110/dce110_timing_generator.o CC [M] drivers/gpu/drm/amd/amdgpu/../display/dc/dce110/dce110_compressor.o CC [M] drivers/gpu/drm/amd/amdgpu/../display/dc/dce110/dce110_opp_regamma_v.o CC [M] drivers/gpu/drm/amd/amdgpu/../display/dc/dce110/dce110_opp_csc_v.o CC [M] drivers/gpu/drm/amd/amdgpu/../display/dc/dce110/dce110_timing_generator_v.o CC [M] drivers/gpu/drm/amd/amdgpu/../display/dc/dce110/dce110_mem_input_v.o drivers/gpu/drm/amd/amdgpu/../display/dc/resource/dcn32/dcn32_resource.c: In function ‘dcn32_update_bw_bounding_box’: drivers/gpu/drm/amd/amdgpu/../display/dc/resource/dcn32/dcn32_resource.c:2024:1: warning: the frame size of 1336 bytes is larger than 1280 bytes [-Wframe-larger-than=] 2024 | } | ^ CC [M] drivers/gpu/drm/amd/amdgpu/../display/dc/dce110/dce110_opp_v.o CC [M] drivers/gpu/drm/amd/amdgpu/../display/dc/dce110/dce110_transform_v.o CC [M] drivers/gpu/drm/amd/amdgpu/../display/dc/dce80/dce80_timing_generator.o CC [M] drivers/gpu/drm/amd/amdgpu/../display/dc/dce60/dce60_timing_generator.o CC [M] drivers/gpu/drm/amd/amdgpu/../display/dc/dce60/dce60_hw_sequencer.o CC [M] drivers/gpu/drm/amd/amdgpu/../display/dc/dce60/dce60_resource.o CC [M] drivers/gpu/drm/amd/amdgpu/../display/dc/hdcp/hdcp_msg.o CC [M] drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc.o CC [M] drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_stat.o CC [M] drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_resource.o CC [M] drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_hw_sequencer.o CC [M] drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_sink.o CC [M] drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_surface.o CC [M] drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_debug.o CC [M] drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_stream.o CC [M] drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_link_enc_cfg.o CC [M] drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_link_exports.o CC [M] drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_state.o CC [M] drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_vm_helper.o CC [M] drivers/gpu/drm/amd/amdgpu/../display/dc/dc_helper.o CC [M] drivers/gpu/drm/amd/amdgpu/../display/dc/dc_dmub_srv.o CC [M] drivers/gpu/drm/amd/amdgpu/../display/dc/dc_edid_parser.o CC [M] drivers/gpu/drm/amd/amdgpu/../display/modules/freesync/freesync.o CC [M] drivers/gpu/drm/amd/amdgpu/../display/modules/color/color_gamma.o CC [M] drivers/gpu/drm/amd/amdgpu/../display/modules/color/color_table.o CC [M] drivers/gpu/drm/amd/amdgpu/../display/modules/info_packet/info_packet.o CC [M] drivers/gpu/drm/amd/amdgpu/../display/modules/power/power_helpers.o CC [M] drivers/gpu/drm/amd/amdgpu/../display/dmub/src/dmub_srv.o CC [M] drivers/gpu/drm/amd/amdgpu/../display/dmub/src/dmub_srv_stat.o CC [M] drivers/gpu/drm/amd/amdgpu/../display/dmub/src/dmub_reg.o CC [M] drivers/gpu/drm/amd/amdgpu/../display/dmub/src/dmub_dcn20.o CC [M] drivers/gpu/drm/amd/amdgpu/../display/dmub/src/dmub_dcn21.o CC [M] drivers/gpu/drm/amd/amdgpu/../display/dmub/src/dmub_dcn30.o CC [M] drivers/gpu/drm/amd/amdgpu/../display/dmub/src/dmub_dcn301.o CC [M] drivers/gpu/drm/amd/amdgpu/../display/dmub/src/dmub_dcn302.o CC [M] drivers/gpu/drm/amd/amdgpu/../display/dmub/src/dmub_dcn303.o CC [M] drivers/gpu/drm/amd/amdg
[Bug 217607] null pointer dereference with NVIDIA installer on 5.15.118 and 5.15.119
https://bugzilla.kernel.org/show_bug.cgi?id=217607 Jani Nikula (jani.nik...@intel.com) changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |INVALID -- 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 218864] HP Envy x360: Graphical corruption over time without amdgpu.sg_display=0 kernel option
https://bugzilla.kernel.org/show_bug.cgi?id=218864 Mario Limonciello (AMD) (mario.limoncie...@amd.com) changed: What|Removed |Added Hardware|All |AMD -- 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 218864] HP Envy x360: Graphical corruption over time without amdgpu.sg_display=0 kernel option
https://bugzilla.kernel.org/show_bug.cgi?id=218864 Mario Limonciello (AMD) (mario.limoncie...@amd.com) changed: What|Removed |Added Component|BIOS|Video(DRI - non Intel) Assignee|acpi_b...@kernel-bugs.osdl. |drivers_video-dri@kernel-bu |org |gs.osdl.org Product|ACPI|Drivers -- 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 218841] Security issue (VERY old video memory displaying in Window preview)
https://bugzilla.kernel.org/show_bug.cgi?id=218841 Artem S. Tashkinov (a...@gmx.com) changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |ANSWERED --- Comment #3 from Artem S. Tashkinov (a...@gmx.com) --- If that's reproducible, please file it 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.
