amd issueshttps://gitlab.freedesktop.org/drm/amd/-/issues2024-02-01T14:19:43Zhttps://gitlab.freedesktop.org/drm/amd/-/issues/3146PowerPC64 Mesa 23.3.2 RADEONSI KMSCUBE error2024-02-01T14:19:43ZGhost UserPowerPC64 Mesa 23.3.2 RADEONSI KMSCUBE errorI am running the KMSCUBE example on the 64-bit PowerPC e5500 architecture with OpenGL ES 2.0 Mesa 23.3.2, LLVM 15.0.3, DRM 2.50, and Linux Kernel version 6.1.44. While the background color is rendering, I cannot see the cube. I am encoun...I am running the KMSCUBE example on the 64-bit PowerPC e5500 architecture with OpenGL ES 2.0 Mesa 23.3.2, LLVM 15.0.3, DRM 2.50, and Linux Kernel version 6.1.44. While the background color is rendering, I cannot see the cube. I am encountering the error below:
radeon 0000:00:02.0: ring 0 stalled for more than 10240msec
radeon 0000:00:02.0: GPU lockup (current fence id 0x0000000000000009 last fence id 0x000000000000000a on ring 0)
radeon 0000:00:02.0: Saved 20 dwords of commands on ring 0. radeon 0000:00:02.0: GPU softreset: 0x00000049 radeon 0000:00:01.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000000 radeon 0000:00:01.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000![log![log](/uploads/5ecd3550c6c8c436d891e0946354c35f/log.png)https://gitlab.freedesktop.org/drm/amd/-/issues/2678Regression: Since Mesa 23.1.x, onboard AMD Radeon graphics APUs hang / freeze...2023-07-13T09:45:24ZJeff Fortin TamRegression: Since Mesa 23.1.x, onboard AMD Radeon graphics APUs hang / freeze with "ring stalled" errors after a few seconds using GNOME Shell## Brief summary of the problem:
Since applying package upgrades to version 23.1.3 of Mesa, this computer with onboard AMD graphics reliably/reproduceably experiences hangs/freezes of all kinds (i.e: input non-responsive, animations not...## Brief summary of the problem:
Since applying package upgrades to version 23.1.3 of Mesa, this computer with onboard AMD graphics reliably/reproduceably experiences hangs/freezes of all kinds (i.e: input non-responsive, animations not working, graphical corruption if you resart gdm, etc.) after a few seconds of using GNOME Shell (ex: launching applications, trying to open the "Activities" overview, etc.), under Wayland (did not test Xorg). Surprisingly, those hangs eventually recover after waiting maybe a minute or so, rather than crashing down the whole machine/kernel; maybe because I'm running on Wayland there?
Downgrading package versions to 23.0.1 "fixes" the problem.
The dmesg logs point to the infamous "ring stalled" errors that we've seen [elsewhere here](https://gitlab.freedesktop.org/drm/amd/-/issues/?search=ring%20stalled) and [elsewhere there](https://discussion.fedoraproject.org/t/where-to-report-amd-gpu-lockups-crasher-hangs-bugs-related-to-seemingly-triggered-by-firefox-va-api-after-resuming-from-suspend/69378/).
...except that this time it has nothing to do with suspend/resume (it happens on a fresh boot, unlike issue #2252) and nothing to do with video or hardware-accelerated decoding like issue #2440 (unless the fact that GNOME Remote Desktop is present/activated is related to this, but it's not actually used with a remote connection while this bug is occuring). It just really happens rapidly after basic usage on a fresh boot, and it didn't before this update, so maybe this is an independent regression.
## Hardware description:
- CPU: AMD Phenom 9600B Quad-Core, on a HP Compaq dc5850 Microtower (AP470US#ABC)
- GPU: `01:05.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] RS780C [Radeon 3100] [1002:9611]`
physical id: 5
bus info: pci@0000:01:05.0
logical name: /dev/fb0
version: 00
width: 32 bits
clock: 33MHz
capabilities: pm msi vga_controller bus_master cap_list rom fb
configuration: depth=32 driver=radeon latency=0 resolution=1600,900
resources: irq:18 memory:e0000000-efffffff ioport:1100(size=256) memory:f0100000-f010ffff memory:f0000000-f00fffff memory:c0000-dffff
- System Memory: 4GiB DDR2
- Display(s): HP 2011x LCD TN display, 1600x900 resolution
- Type of Display Connection: VGA (D-Sub) (it's the only output on the motherboard, AFAICS)
## System information:
- Distro name and Version: Fedora 38, 64-bits, Wayland GNOME
- Kernel version: 6.3.8-200.fc38.x86_64
- Custom kernel: N/A
- AMD official driver version: N/A (default open source AMD/radeon Mesa Gallium driver provided by Fedora)
## How to reproduce the issue:
On that kind of computer with onboard AMD graphics, a fully up-to-date Fedora 38 with GNOME is sufficient to trigger the issue on my end, simply by logging into a GNOME Wayland session, launching a few applications (such as Nautilus, Evolution, Firefox, etc.) and pressing the `Super` key (or using the `Activities` button) to try to open the overview. At that time, I will experience a hang that may easily last for a minute.
## Attached files:
### Log files
- Full dmesg log: attached as
[2023-07-04_full_dmesg_on_radeon_APU_lockup_on_home_computer.txt](/uploads/8e832929066c667df9b819c1b96df919/2023-07-04_full_dmesg_on_radeon_APU_lockup_on_home_computer.txt)
- Xorg log: not available, since the computer is running Wayland? At least I could not find any xorg log on the system partition nor in ~/.local/share/xorg/
- Any other log: see below
Watching the computer "live" over SSH with `journalctl -f`, this is what happens as soon as the GPU locks up a few seconds after logging into a GNOME Shell Wayland session, when you mouse over some app launcher icons:
```
jui 04 13:01:18 desktop-house kernel: radeon 0000:01:05.0: ring 0 stalled for more than 10080msec
jui 04 13:01:18 desktop-house kernel: radeon 0000:01:05.0: GPU lockup (current fence id 0x00000000000002ae last fence id 0x00000000000002af on ring 0)
jui 04 13:01:19 desktop-house kernel: radeon 0000:01:05.0: ring 0 stalled for more than 10584msec
jui 04 13:01:19 desktop-house kernel: radeon 0000:01:05.0: GPU lockup (current fence id 0x00000000000002ae last fence id 0x00000000000002af on ring 0)
jui 04 13:01:19 desktop-house realmd[1331]: quitting realmd service after timeout
jui 04 13:01:19 desktop-house realmd[1331]: stopping service
jui 04 13:01:19 desktop-house systemd[1]: realmd.service: Deactivated successfully.
jui 04 13:01:19 desktop-house audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=realmd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
jui 04 13:01:19 desktop-house kernel: radeon 0000:01:05.0: ring 0 stalled for more than 11088msec
jui 04 13:01:19 desktop-house kernel: radeon 0000:01:05.0: GPU lockup (current fence id 0x00000000000002ae last fence id 0x00000000000002af on ring 0)
jui 04 13:01:20 desktop-house kernel: radeon 0000:01:05.0: ring 0 stalled for more than 11592msec
jui 04 13:01:20 desktop-house kernel: radeon 0000:01:05.0: GPU lockup (current fence id 0x00000000000002ae last fence id 0x00000000000002af on ring 0)
jui 04 13:01:20 desktop-house kernel: radeon 0000:01:05.0: ring 0 stalled for more than 12096msec
jui 04 13:01:20 desktop-house kernel: radeon 0000:01:05.0: GPU lockup (current fence id 0x00000000000002ae last fence id 0x00000000000002af on ring 0)
jui 04 13:01:21 desktop-house kernel: radeon 0000:01:05.0: ring 0 stalled for more than 12600msec
jui 04 13:01:21 desktop-house kernel: radeon 0000:01:05.0: GPU lockup (current fence id 0x00000000000002ae last fence id 0x00000000000002af on ring 0)
jui 04 13:01:21 desktop-house kernel: radeon 0000:01:05.0: ring 0 stalled for more than 13104msec
jui 04 13:01:21 desktop-house kernel: radeon 0000:01:05.0: GPU lockup (current fence id 0x00000000000002ae last fence id 0x00000000000002af on ring 0)
jui 04 13:01:22 desktop-house kernel: radeon 0000:01:05.0: ring 0 stalled for more than 13608msec
jui 04 13:01:22 desktop-house kernel: radeon 0000:01:05.0: GPU lockup (current fence id 0x00000000000002ae last fence id 0x00000000000002af on ring 0)
jui 04 13:01:22 desktop-house kernel: radeon 0000:01:05.0: ring 0 stalled for more than 14112msec
jui 04 13:01:22 desktop-house kernel: radeon 0000:01:05.0: GPU lockup (current fence id 0x00000000000002ae last fence id 0x00000000000002af on ring 0)
jui 04 13:01:23 desktop-house kernel: radeon 0000:01:05.0: ring 0 stalled for more than 14616msec
jui 04 13:01:23 desktop-house kernel: radeon 0000:01:05.0: GPU lockup (current fence id 0x00000000000002ae last fence id 0x00000000000002af on ring 0)
jui 04 13:01:23 desktop-house kernel: radeon 0000:01:05.0: ring 0 stalled for more than 15120msec
jui 04 13:01:23 desktop-house kernel: radeon 0000:01:05.0: GPU lockup (current fence id 0x00000000000002ae last fence id 0x00000000000002af on ring 0)
jui 04 13:01:24 desktop-house kernel: radeon 0000:01:05.0: ring 0 stalled for more than 15624msec
jui 04 13:01:24 desktop-house kernel: radeon 0000:01:05.0: GPU lockup (current fence id 0x00000000000002ae last fence id 0x00000000000002af on ring 0)
jui 04 13:01:24 desktop-house systemd[1]: systemd-hostnamed.service: Deactivated successfully.
jui 04 13:01:24 desktop-house audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
jui 04 13:01:24 desktop-house audit: BPF prog-id=75 op=UNLOAD
jui 04 13:01:24 desktop-house audit: BPF prog-id=74 op=UNLOAD
jui 04 13:01:24 desktop-house audit: BPF prog-id=73 op=UNLOAD
jui 04 13:01:24 desktop-house systemd[1]: systemd-localed.service: Deactivated successfully.
jui 04 13:01:24 desktop-house audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=systemd-localed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
jui 04 13:01:24 desktop-house audit: BPF prog-id=82 op=UNLOAD
jui 04 13:01:24 desktop-house audit: BPF prog-id=81 op=UNLOAD
jui 04 13:01:24 desktop-house audit: BPF prog-id=80 op=UNLOAD
jui 04 13:01:24 desktop-house kernel: radeon 0000:01:05.0: ring 0 stalled for more than 16128msec
jui 04 13:01:24 desktop-house kernel: radeon 0000:01:05.0: GPU lockup (current fence id 0x00000000000002ae last fence id 0x00000000000002af on ring 0)
jui 04 13:01:25 desktop-house kernel: radeon 0000:01:05.0: ring 0 stalled for more than 16632msec
jui 04 13:01:25 desktop-house kernel: radeon 0000:01:05.0: GPU lockup (current fence id 0x00000000000002ae last fence id 0x00000000000002af on ring 0)
jui 04 13:01:25 desktop-house kernel: radeon 0000:01:05.0: ring 0 stalled for more than 17136msec
jui 04 13:01:25 desktop-house kernel: radeon 0000:01:05.0: GPU lockup (current fence id 0x00000000000002ae last fence id 0x00000000000002af on ring 0)
jui 04 13:01:26 desktop-house kernel: radeon 0000:01:05.0: ring 0 stalled for more than 17640msec
jui 04 13:01:26 desktop-house kernel: radeon 0000:01:05.0: GPU lockup (current fence id 0x00000000000002ae last fence id 0x00000000000002af on ring 0)
jui 04 13:01:26 desktop-house kernel: radeon 0000:01:05.0: ring 0 stalled for more than 18144msec
jui 04 13:01:26 desktop-house kernel: radeon 0000:01:05.0: GPU lockup (current fence id 0x00000000000002ae last fence id 0x00000000000002af on ring 0)
jui 04 13:01:27 desktop-house kernel: radeon 0000:01:05.0: ring 0 stalled for more than 18648msec
jui 04 13:01:27 desktop-house kernel: radeon 0000:01:05.0: GPU lockup (current fence id 0x00000000000002ae last fence id 0x00000000000002af on ring 0)
jui 04 13:01:27 desktop-house kernel: radeon 0000:01:05.0: ring 0 stalled for more than 19152msec
jui 04 13:01:27 desktop-house kernel: radeon 0000:01:05.0: GPU lockup (current fence id 0x00000000000002ae last fence id 0x00000000000002af on ring 0)
jui 04 13:01:28 desktop-house chronyd[722]: Selected source 216.197.156.83 (2.fedora.pool.ntp.org)
jui 04 13:01:28 desktop-house kernel: radeon 0000:01:05.0: ring 0 stalled for more than 19656msec
jui 04 13:01:28 desktop-house kernel: radeon 0000:01:05.0: GPU lockup (current fence id 0x00000000000002ae last fence id 0x00000000000002af on ring 0)
jui 04 13:01:28 desktop-house kernel: radeon 0000:01:05.0: ring 0 stalled for more than 20160msec
jui 04 13:01:28 desktop-house kernel: radeon 0000:01:05.0: GPU lockup (current fence id 0x00000000000002ae last fence id 0x00000000000002af on ring 0)
jui 04 13:01:29 desktop-house kernel: radeon 0000:01:05.0: ring 0 stalled for more than 20664msec
jui 04 13:01:29 desktop-house kernel: radeon 0000:01:05.0: GPU lockup (current fence id 0x00000000000002ae last fence id 0x00000000000002af on ring 0)
jui 04 13:01:29 desktop-house kernel: radeon 0000:01:05.0: ring 0 stalled for more than 21168msec
jui 04 13:01:29 desktop-house kernel: radeon 0000:01:05.0: GPU lockup (current fence id 0x00000000000002ae last fence id 0x00000000000002af on ring 0)
jui 04 13:01:30 desktop-house kernel: radeon 0000:01:05.0: ring 0 stalled for more than 21672msec
jui 04 13:01:30 desktop-house kernel: radeon 0000:01:05.0: GPU lockup (current fence id 0x00000000000002ae last fence id 0x00000000000002af on ring 0)
jui 04 13:01:30 desktop-house kernel: radeon 0000:01:05.0: ring 0 stalled for more than 22176msec
jui 04 13:01:30 desktop-house kernel: radeon 0000:01:05.0: GPU lockup (current fence id 0x00000000000002ae last fence id 0x00000000000002af on ring 0)
jui 04 13:01:31 desktop-house kernel: radeon 0000:01:05.0: ring 0 stalled for more than 22680msec
jui 04 13:01:31 desktop-house kernel: radeon 0000:01:05.0: GPU lockup (current fence id 0x00000000000002ae last fence id 0x00000000000002af on ring 0)
jui 04 13:01:31 desktop-house kernel: radeon 0000:01:05.0: ring 0 stalled for more than 23184msec
jui 04 13:01:31 desktop-house kernel: radeon 0000:01:05.0: GPU lockup (current fence id 0x00000000000002ae last fence id 0x00000000000002af on ring 0)
jui 04 13:01:32 desktop-house kernel: radeon 0000:01:05.0: ring 0 stalled for more than 23688msec
jui 04 13:01:32 desktop-house kernel: radeon 0000:01:05.0: GPU lockup (current fence id 0x00000000000002ae last fence id 0x00000000000002af on ring 0)
jui 04 13:01:32 desktop-house kernel: radeon 0000:01:05.0: ring 0 stalled for more than 24193msec
jui 04 13:01:32 desktop-house kernel: radeon 0000:01:05.0: GPU lockup (current fence id 0x00000000000002ae last fence id 0x00000000000002af on ring 0)
jui 04 13:01:33 desktop-house kernel: radeon 0000:01:05.0: ring 0 stalled for more than 24696msec
jui 04 13:01:33 desktop-house kernel: radeon 0000:01:05.0: GPU lockup (current fence id 0x00000000000002ae last fence id 0x00000000000002af on ring 0)
jui 04 13:01:33 desktop-house kernel: radeon 0000:01:05.0: ring 0 stalled for more than 25200msec
jui 04 13:01:33 desktop-house kernel: radeon 0000:01:05.0: GPU lockup (current fence id 0x00000000000002ae last fence id 0x00000000000002af on ring 0)
jui 04 13:01:34 desktop-house kernel: radeon 0000:01:05.0: ring 0 stalled for more than 25704msec
jui 04 13:01:34 desktop-house kernel: radeon 0000:01:05.0: GPU lockup (current fence id 0x00000000000002ae last fence id 0x00000000000002af on ring 0)
jui 04 13:01:34 desktop-house kernel: radeon 0000:01:05.0: ring 0 stalled for more than 26208msec
jui 04 13:01:34 desktop-house kernel: radeon 0000:01:05.0: GPU lockup (current fence id 0x00000000000002ae last fence id 0x00000000000002af on ring 0)
jui 04 13:01:35 desktop-house kernel: radeon 0000:01:05.0: ring 0 stalled for more than 26712msec
jui 04 13:01:35 desktop-house kernel: radeon 0000:01:05.0: GPU lockup (current fence id 0x00000000000002ae last fence id 0x00000000000002af on ring 0)
jui 04 13:01:35 desktop-house kernel: radeon 0000:01:05.0: ring 0 stalled for more than 27216msec
jui 04 13:01:35 desktop-house kernel: radeon 0000:01:05.0: GPU lockup (current fence id 0x00000000000002ae last fence id 0x00000000000002af on ring 0)
jui 04 13:01:36 desktop-house kernel: radeon 0000:01:05.0: ring 0 stalled for more than 27720msec
jui 04 13:01:36 desktop-house kernel: radeon 0000:01:05.0: GPU lockup (current fence id 0x00000000000002ae last fence id 0x00000000000002af on ring 0)
jui 04 13:01:36 desktop-house kernel: radeon 0000:01:05.0: ring 0 stalled for more than 28224msec
jui 04 13:01:36 desktop-house kernel: radeon 0000:01:05.0: GPU lockup (current fence id 0x00000000000002ae last fence id 0x00000000000002af on ring 0)
jui 04 13:01:37 desktop-house kernel: radeon 0000:01:05.0: ring 0 stalled for more than 28728msec
jui 04 13:01:37 desktop-house kernel: radeon 0000:01:05.0: GPU lockup (current fence id 0x00000000000002ae last fence id 0x00000000000002af on ring 0)
jui 04 13:01:37 desktop-house kernel: radeon 0000:01:05.0: ring 0 stalled for more than 29232msec
jui 04 13:01:37 desktop-house kernel: radeon 0000:01:05.0: GPU lockup (current fence id 0x00000000000002ae last fence id 0x00000000000002af on ring 0)
jui 04 13:01:38 desktop-house kernel: radeon 0000:01:05.0: ring 0 stalled for more than 29736msec
jui 04 13:01:38 desktop-house kernel: radeon 0000:01:05.0: GPU lockup (current fence id 0x00000000000002ae last fence id 0x00000000000002af on ring 0)
jui 04 13:01:38 desktop-house kernel: radeon 0000:01:05.0: Saved 25 dwords of commands on ring 0.
jui 04 13:01:38 desktop-house kernel: radeon 0000:01:05.0: GPU softreset: 0x00000008
jui 04 13:01:38 desktop-house kernel: radeon 0000:01:05.0: R_008010_GRBM_STATUS = 0xA0002030
jui 04 13:01:38 desktop-house kernel: radeon 0000:01:05.0: R_008014_GRBM_STATUS2 = 0x00000003
jui 04 13:01:38 desktop-house kernel: radeon 0000:01:05.0: R_000E50_SRBM_STATUS = 0x20000040
jui 04 13:01:38 desktop-house kernel: radeon 0000:01:05.0: R_008674_CP_STALLED_STAT1 = 0x00000000
jui 04 13:01:38 desktop-house kernel: radeon 0000:01:05.0: R_008678_CP_STALLED_STAT2 = 0x00040000
jui 04 13:01:38 desktop-house kernel: radeon 0000:01:05.0: R_00867C_CP_BUSY_STAT = 0x00000000
jui 04 13:01:38 desktop-house kernel: radeon 0000:01:05.0: R_008680_CP_STAT = 0x80040000
jui 04 13:01:38 desktop-house kernel: radeon 0000:01:05.0: R_00D034_DMA_STATUS_REG = 0x44C83D57
jui 04 13:01:38 desktop-house kernel: radeon 0000:01:05.0: R_008020_GRBM_SOFT_RESET=0x00004001
jui 04 13:01:38 desktop-house kernel: radeon 0000:01:05.0: SRBM_SOFT_RESET=0x00000100
jui 04 13:01:38 desktop-house kernel: radeon 0000:01:05.0: R_008010_GRBM_STATUS = 0xA0003030
jui 04 13:01:38 desktop-house kernel: radeon 0000:01:05.0: R_008014_GRBM_STATUS2 = 0x00000003
jui 04 13:01:38 desktop-house kernel: radeon 0000:01:05.0: R_000E50_SRBM_STATUS = 0x20008040
jui 04 13:01:38 desktop-house kernel: radeon 0000:01:05.0: R_008674_CP_STALLED_STAT1 = 0x00000000
jui 04 13:01:38 desktop-house kernel: radeon 0000:01:05.0: R_008678_CP_STALLED_STAT2 = 0x00000000
jui 04 13:01:38 desktop-house kernel: radeon 0000:01:05.0: R_00867C_CP_BUSY_STAT = 0x00000000
jui 04 13:01:38 desktop-house kernel: radeon 0000:01:05.0: R_008680_CP_STAT = 0x80100000
jui 04 13:01:38 desktop-house kernel: radeon 0000:01:05.0: R_00D034_DMA_STATUS_REG = 0x44C83D57
jui 04 13:01:38 desktop-house kernel: radeon 0000:01:05.0: GPU reset succeeded, trying to resume
jui 04 13:01:38 desktop-house kernel: [drm] PCIE GART of 512M enabled (table at 0x00000000C0040000).
jui 04 13:01:38 desktop-house kernel: radeon 0000:01:05.0: WB enabled
jui 04 13:01:38 desktop-house kernel: radeon 0000:01:05.0: fence driver on ring 0 use gpu addr 0x00000000a0000c00
jui 04 13:01:38 desktop-house kernel: debugfs: File 'radeon_ring_gfx' in directory '0' already present!
jui 04 13:01:38 desktop-house kernel: [drm] ring test on 0 succeeded in 1 usecs
jui 04 13:01:39 desktop-house gnome-shell[1802]: radeon: The kernel rejected CS, see dmesg for more information (-16).
jui 04 13:01:39 desktop-house kernel: [drm:r600_ib_test [radeon]] *ERROR* radeon: fence wait timed out.
jui 04 13:01:39 desktop-house kernel: [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed testing IB on GFX ring (-110).
jui 04 13:01:39 desktop-house gnome-shell[1802]: radeon: The kernel rejected CS, see dmesg for more information (-16).
```
### Additional troubleshooting and package versions info
Kernel downgrades between 6.3.8 and 6.3.5 did nothing, so it's not a kernel regression; neither did gnome-shell or mutter downgrades, nor downgrades of the `amd-gpu-firmware` Fedora package.
Doing a `dnf downgrade *mesa*` to 23.0.1 instead of 23.1.3 is what fixed it (no need to downgrade packages matching `*radeon*` and `*amd*`, according to my testing). These are the packages that get downgraded by the command, leading to a stable system again:
mesa-dri-drivers-23.0.1-2.fc38.x86_64
mesa-filesystem-23.0.1-2.fc38.x86_64
mesa-libEGL-23.0.1-2.fc38.x86_64
mesa-libGL-23.0.1-2.fc38.x86_64
mesa-libgbm-23.0.1-2.fc38.x86_64
mesa-libglapi-23.0.1-2.fc38.x86_64
mesa-libxatracker-23.0.1-2.fc38.x86_64
mesa-va-drivers-23.0.1-2.fc38.x86_64
mesa-vulkan-drivers-23.0.1-2.fc38.x86_64
With these, the system no longer experiences hangs/freezes, and the journalctl logs do not log anything in particular regarding the radeon graphics.
The faulty packages, according to a `dnf upgrade` without versionlock, would be:
mesa-dri-drivers 23.1.3-1.fc38
mesa-filesystem 23.1.3-1.fc38
mesa-libEGL 23.1.3-1.fc38
mesa-libGL 23.1.3-1.fc38
mesa-libgbm 23.1.3-1.fc38
mesa-libglapi 23.1.3-1.fc38
mesa-libxatracker 23.1.3-1.fc38
mesa-va-drivers 23.1.3-1.fc38
mesa-vulkan-drivers 23.1.3-1.fc38
I have now done a `dnf versionlock *mesa*`, which freezes the installed package versions to 23.0.1, to avoid accidental upgrades.https://gitlab.freedesktop.org/drm/amd/-/issues/2269r300 powerpc crashes when using 3D2023-05-25T03:33:31ZEd Robbinsr300 powerpc crashes when using 3D## Brief summary of the problem:
These r300 powerpc systems crash when running anything 3D related. I have tried many different xorg.conf configurations and radeon module parameters to no avail.
I am happy to build and test patches.
I ...## Brief summary of the problem:
These r300 powerpc systems crash when running anything 3D related. I have tried many different xorg.conf configurations and radeon module parameters to no avail.
I am happy to build and test patches.
I have so far tested on two systems (radeon 9600 and radeon mobility 9550). Behaviour on both systems is identical. Also two different sets of package versions (debian unstable, the first packages are a couple of years old, but the second set are very recent). Behaviour is slightly different with different sets of packages:
# First package versions tested
`xserver-xorg-video-radeon=19.1.0-2 firmware-amd-graphics=20200918-1 libdrm-radeon1=2.4.103-1 mesa=20.0.2-1`
X starts fine. glxgears runs fine. glxinfo reports hardware acceleration enabled. Running something more intense results in a crash: kodi crashes after a minute or two, openarena crashes generally after the initial animation or just after the menu is shown. The system is unresponsive after the crash and ssh connections are dropped, the machine has to be rebooted. On /var/log/messages via ssh we can sometimes see:
```
radeon 0000:00:10.0: GPU lockup (current fence id 0x0000000000001298 last fence id 0x000000000000129c on ring 0)
radeon: wait for empty RBBM fifo failed! Bad things might happen.
Failed to wait GUI idle while programming pipes. Bad things might happen.
```
# Second package versions tested
`xserver-xorg-video-radeon=19.1.0-3 firmware-amd-graphics=20221109-2 libdrm-radeon1=2.4.114-1 mesa=22.2.4-1`
X starts fine. glxinfo reports hardware acceleration enabled. Running anything that uses 3D results in the same crash as with older packages above, with the same kernel output, but much more quickly: glxgears crashes instantly, as does openarena, in both cases without drawing anything except a window. kodi sometimes works for a short time.
However on one occasion I also experienced the system staying alive, with ssh still active but the X session freezing and the display mode continually being reset every 5 to 10 seconds. In that case it is impossible to recover the graphics session, but we see this in /var/log/messages, looping continually:
```
[ 253.927650] radeon 0000:00:10.0: ring 0 stalled for more than 10196msec
[ 253.927684] radeon 0000:00:10.0: GPU lockup (current fence id 0x000000000000087e last fence id 0x0000000000000880 on ring 0)
[ 254.065322] Failed to wait GUI idle while programming pipes. Bad things might happen.
[ 254.069528] radeon 0000:00:10.0: Saved 59 dwords of commands on ring 0.
[ 254.069559] radeon 0000:00:10.0: (r300_asic_reset:426) RBBM_STATUS=0x84110140
[ 254.567341] radeon 0000:00:10.0: (r300_asic_reset:445) RBBM_STATUS=0x80010140
[ 255.061136] radeon 0000:00:10.0: (r300_asic_reset:457) RBBM_STATUS=0x00000140
[ 255.061168] radeon 0000:00:10.0: GPU reset succeed
[ 255.061174] radeon 0000:00:10.0: GPU reset succeeded, trying to resume
[ 255.072909] debugfs: File 'r100_mc_info' in directory '0' already present!
[ 255.072957] [drm] radeon: 1 quad pipes, 1 Z pipes initialized
[ 255.072965] [drm] PCI GART of 512M enabled (table at 0x0000000002C00000).
[ 255.072982] radeon 0000:00:10.0: WB enabled
[ 255.072992] radeon 0000:00:10.0: fence driver on ring 0 use gpu addr 0x0000000078000000
[ 255.073004] debugfs: File 'r100_cp_ring_info' in directory '0' already present!
[ 255.073009] debugfs: File 'r100_cp_csq_fifo' in directory '0' already present!
[ 255.073093] debugfs: File 'radeon_ring_gfx' in directory '0' already present!
[ 255.073099] [drm] radeon: ring at 0x0000000078001000
[ 255.209686] [drm:r100_ring_test [radeon]] *ERROR* radeon: ring test failed (scratch(0x15E8)=0xCAFEDEAD)
[ 255.209942] [drm:r100_cp_init [radeon]] *ERROR* radeon: cp isn't working (-22).
[ 255.210024] radeon 0000:00:10.0: failed initializing CP (-22).
[ 265.267508] radeon 0000:00:10.0: ring 0 stalled for more than 10248msec
[ 265.267542] radeon 0000:00:10.0: GPU lockup (current fence id 0x000000000000087e last fence id 0x0000000000000880 on ring 0)
[ 265.274188] radeon 0000:00:10.0: Saved 192635 dwords of commands on ring 0.
[ 265.278385] radeon 0000:00:10.0: GPU reset succeeded, trying to resume
[ 265.278429] debugfs: File 'r100_mc_info' in directory '0' already present!
[ 265.278457] [drm] radeon: 1 quad pipes, 1 Z pipes initialized
[ 265.278465] [drm] PCI GART of 512M enabled (table at 0x0000000002C00000).
[ 265.278477] radeon 0000:00:10.0: WB enabled
[ 265.278486] radeon 0000:00:10.0: fence driver on ring 0 use gpu addr 0x0000000078000000
[ 265.278495] debugfs: File 'r100_cp_ring_info' in directory '0' already present!
[ 265.278501] debugfs: File 'r100_cp_csq_fifo' in directory '0' already present!
[ 265.278584] debugfs: File 'radeon_ring_gfx' in directory '0' already present!
[ 265.278590] [drm] radeon: ring at 0x0000000078001000
[ 265.415280] [drm:r100_ring_test [radeon]] *ERROR* radeon: ring test failed (scratch(0x15E8)=0xCAFEDEAD)
[ 265.415525] [drm:r100_cp_init [radeon]] *ERROR* radeon: cp isn't working (-22).
[ 265.415608] radeon 0000:00:10.0: failed initializing CP (-22).
[ 275.488778] radeon 0000:00:10.0: ring 0 stalled for more than 10232msec
[ 275.488813] radeon 0000:00:10.0: GPU lockup (current fence id 0x000000000000087e last fence id 0x0000000000000880 on ring 0)
[ 275.493557] radeon 0000:00:10.0: Saved 123067 dwords of commands on ring 0.
[ 275.498395] radeon 0000:00:10.0: GPU reset succeeded, trying to resume
```
## Hardware description:
Tested on two systems, behaviour is identical.
System 1: Apple iBook G4 12" 1.33 GHz
- CPU: PowerPC 7447A
- GPU: 0000:00:10.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] RV360/M12 [Mobility Radeon 9550] [1002:4e56] (rev 80)
- System Memory: 1.5GB
- Display(s): Laptop LCD
- Type of Display Connection: LVDS
System 2: Apple eMac 1.42GHz
- CPU: PowerPC 7447A
- GPU: 0000:00:10.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550/9600/X1050 Series] [1002:4150]
- System Memory: 2GB
- Display(s): CRT
- Type of Display Connection: VGA
## System information:
- Distro name and Version: Debian unstable
- Kernel version: 6.0.0-4-powerpc. Behaviour similar on 5.5.0-2-powerpc
## How to reproduce the issue:
Install debian with packages: `xserver-xorg-video-radeon=19.1.0-3 firmware-amd-graphics=20221109-2 libdrm-radeon1=2.4.114-1 mesa=22.2.4-1`. Run glxgears. Useful to have an ssh session running to catch kernel output.
### Log files (for system lockups / game freezes / crashes)
- Dmesg log: From after boot, before the problem. [dmesg](/uploads/6dbaca58326165fb26d421c6f7a21550/dmesg)
- Syslog: syslog where I have stripped out the previous and next boots. This is from the case where the video mode is continually reset, without a complete system lockup. [syslog](/uploads/b6a32d529d19c4ac3540627b7268b084/syslog)
- Xorg log: From after the problem, recovered after reboot. [Xorg.0.log](/uploads/a337a10e0418e7f223b576c2a468fd9e/Xorg.0.log)https://gitlab.freedesktop.org/drm/amd/-/issues/846AMD HAINAN (Radeon R5 M330) Clock frequency is 750MHz while it is supposed to...2023-05-25T05:24:06ZBugzilla Migration UserAMD HAINAN (Radeon R5 M330) Clock frequency is 750MHz while it is supposed to be 1030MHz## Submitted by Yassine Oudjana
Assigned to **Default DRI bug account**
**[Link to original bug (#105664)](https://bugs.freedesktop.org/show_bug.cgi?id=105664)**
## Description
Kernel source: /drivers/gpu/drm/radeon/si_dpm.c line ...## Submitted by Yassine Oudjana
Assigned to **Default DRI bug account**
**[Link to original bug (#105664)](https://bugs.freedesktop.org/show_bug.cgi?id=105664)**
## Description
Kernel source: /drivers/gpu/drm/radeon/si_dpm.c line 2985:<br>
<br>
max_sclk = 75000;<br>
<br>
instead of<br>
<br>
max_sclk = 103000;<br>
<br>
Why is that? I changed it and rebuilt the kernel, and I can say that<br>
there are absolutely no issues when using the 1030MHz clock, **which is the default frequency this GPU is designed for**.https://gitlab.freedesktop.org/drm/amd/-/issues/634[radeon] [drm:si_dpm_set_power_state [radeon]] *ERROR* si_restrict_performanc...2023-08-04T10:59:38ZBugzilla Migration User[radeon] [drm:si_dpm_set_power_state [radeon]] *ERROR* si_restrict_performance_levels_before_switch failed## Submitted by Alexandre Demers `@Oxalin`
Assigned to **Default DRI bug account**
**[Link to original bug (#91375)](https://bugs.freedesktop.org/show_bug.cgi?id=91375)**
## Description
[drm:si_dpm_set_power_state [radeon]] *ERROR...## Submitted by Alexandre Demers `@Oxalin`
Assigned to **Default DRI bug account**
**[Link to original bug (#91375)](https://bugs.freedesktop.org/show_bug.cgi?id=91375)**
## Description
[drm:si_dpm_set_power_state [radeon]] *ERROR* si_restrict_performance_levels_before_switch failed<br>
<br>
I just found out there is this message at boot. Using latest ddx, mesa and drm from git combined with a 4.1 kernel. I don't see any impact or side effect.<br>
<br>
As always, using a R9 280X.https://gitlab.freedesktop.org/drm/amd/-/issues/251Monitor not turning on after DisplayPort re-plug in Xorg2019-11-19T16:33:47ZBugzilla Migration UserMonitor not turning on after DisplayPort re-plug in Xorg## Submitted by Tvrtko Ursulin
Assigned to **Default DRI bug account**
**[Link to original bug (#46711)](https://bugs.freedesktop.org/show_bug.cgi?id=46711)**
## Description
Created attachment 57747<br>
Kernel DRM debug log showin...## Submitted by Tvrtko Ursulin
Assigned to **Default DRI bug account**
**[Link to original bug (#46711)](https://bugs.freedesktop.org/show_bug.cgi?id=46711)**
## Description
Created attachment 57747<br>
Kernel DRM debug log showing successful replug without, and failing with Xorg running.<br>
<br>
On a AMD G-T56N (Radeon HD 6310) box connected to the monitor via DisplayPort <br>
monitor does not come on after re-plugging the display cable but claims to be <br>
in power save.<br>
<br>
At the same time, according to xrandr it is connected and displaying.<br>
<br>
Stopping Xorg and monitor comes back up displaying the console.<br>
<br>
Re-pluging the display cable with no Xorg running is fine.<br>
<br>
Attached kernel DRM debug log. Log itself which ends after cable re-plug when Xorg is running. Which is when the display goes into power save. Before that in the same log you can find Xorg starting up and before that a successful cable re-<br>
plug when X was not running.<br>
<br>
All this is with kernel.org 3.3.0-rc4 kernel. Xorg packages are:<br>
<br>
xorg-x11-server-Xorg-1.11.3-1.fc16.x86_64<br>
xorg-x11-drv-ati-6.14.3-8.20120209gite20284409.fc16.x86_64<br>
<br>
**Attachment 57747**, "Kernel DRM debug log showing successful replug without, and failing with Xorg running.": <br>
[replug.Xorg.bz2](/uploads/2b23649991be4bd4e72b1aa4099e9201/replug.Xorg.bz2)<br>https://gitlab.freedesktop.org/drm/amd/-/issues/28946.5.5: UBSAN: radeon_atombios.c: index 1 is out of range for type 'UCHAR [1]'2024-03-06T13:55:36ZJustin Piszcz6.5.5: UBSAN: radeon_atombios.c: index 1 is out of range for type 'UCHAR [1]'### Before submitting your bug report:
- Check if your bug has already been reported [here](lspci -nn | grep VGA).
- I did not find anything here or on Google for this driver/out of range error.
$ lspci -nn | grep VGA
03:00.0 VGA compa...### Before submitting your bug report:
- Check if your bug has already been reported [here](lspci -nn | grep VGA).
- I did not find anything here or on Google for this driver/out of range error.
$ lspci -nn | grep VGA
03:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Park [Mobility Radeon HD 5430] [1002:68e1]
- For any logs, backtraces, etc - use [code blocks](https://docs.gitlab.com/ee/user/markdown.html#code-spans-and-blocks)
```
[Sun Oct 1 15:59:04 2023] ACPI: bus type drm_connector registered
[Sun Oct 1 15:59:04 2023] [drm] radeon kernel modesetting enabled.
[Sun Oct 1 15:59:04 2023] [drm] initializing kernel modesetting (CEDAR 0x1002:0x68E1 0x1787:0x3000 0x00).
[Sun Oct 1 15:59:04 2023] ATOM BIOS: PARK
[Sun Oct 1 15:59:04 2023] radeon 0000:03:00.0: VRAM: 1024M 0x0000000000000000 - 0x000000003FFFFFFF (1024M used)
[Sun Oct 1 15:59:04 2023] radeon 0000:03:00.0: GTT: 1024M 0x0000000040000000 - 0x000000007FFFFFFF
[Sun Oct 1 15:59:04 2023] [drm] Detected VRAM RAM=1024M, BAR=256M
[Sun Oct 1 15:59:04 2023] [drm] RAM width 64bits DDR
[Sun Oct 1 15:59:04 2023] [drm] radeon: 1024M of VRAM memory ready
[Sun Oct 1 15:59:04 2023] [drm] radeon: 1024M of GTT memory ready.
[Sun Oct 1 15:59:04 2023] [drm] Loading CEDAR Microcode
[Sun Oct 1 15:59:04 2023] [drm] Internal thermal controller with fan control
[Sun Oct 1 15:59:04 2023] ================================================================================
[Sun Oct 1 15:59:04 2023] UBSAN: array-index-out-of-bounds in drivers/gpu/drm/radeon/radeon_atombios.c:2620:43
[Sun Oct 1 15:59:04 2023] index 1 is out of range for type 'UCHAR [1]'
[Sun Oct 1 15:59:04 2023] CPU: 5 PID: 1 Comm: swapper/0 Tainted: G T 6.5.5 #13 55df8de52754ef95effc50a55e9206abdea304ac
[Sun Oct 1 15:59:04 2023] Hardware name: Supermicro X9SRL-F/X9SRL-F, BIOS 3.3 11/13/2018
[Sun Oct 1 15:59:04 2023] Call Trace:
[Sun Oct 1 15:59:04 2023] <TASK>
[Sun Oct 1 15:59:04 2023] dump_stack_lvl+0x36/0x50
[Sun Oct 1 15:59:04 2023] __ubsan_handle_out_of_bounds+0xc7/0x110
[Sun Oct 1 15:59:04 2023] radeon_atombios_get_power_modes+0x87a/0x8f0
[Sun Oct 1 15:59:04 2023] radeon_pm_init+0x13a/0x7e0
[Sun Oct 1 15:59:04 2023] evergreen_init+0x13d/0x3d0
[Sun Oct 1 15:59:04 2023] radeon_device_init+0x60a/0xbf0
[Sun Oct 1 15:59:04 2023] radeon_driver_load_kms+0xb1/0x250
[Sun Oct 1 15:59:04 2023] drm_dev_register+0xfc/0x250
[Sun Oct 1 15:59:04 2023] radeon_pci_probe+0xd0/0x150
[Sun Oct 1 15:59:04 2023] pci_device_probe+0x97/0x130
[Sun Oct 1 15:59:04 2023] really_probe+0xbe/0x2f0
[Sun Oct 1 15:59:04 2023] ? __pfx___driver_attach+0x10/0x10
[Sun Oct 1 15:59:04 2023] __driver_probe_device+0x6e/0x120
[Sun Oct 1 15:59:04 2023] driver_probe_device+0x1a/0x90
[Sun Oct 1 15:59:04 2023] __driver_attach+0xd4/0x170
[Sun Oct 1 15:59:04 2023] bus_for_each_dev+0x87/0xe0
[Sun Oct 1 15:59:04 2023] bus_add_driver+0xf3/0x1f0
[Sun Oct 1 15:59:04 2023] driver_register+0x58/0x120
[Sun Oct 1 15:59:04 2023] ? __pfx_radeon_module_init+0x10/0x10
[Sun Oct 1 15:59:04 2023] do_one_initcall+0x93/0x4a0
[Sun Oct 1 15:59:04 2023] kernel_init_freeable+0x301/0x580
[Sun Oct 1 15:59:04 2023] ? __pfx_kernel_init+0x10/0x10
[Sun Oct 1 15:59:04 2023] kernel_init+0x15/0x1b0
[Sun Oct 1 15:59:04 2023] ret_from_fork+0x2f/0x50
[Sun Oct 1 15:59:04 2023] ? __pfx_kernel_init+0x10/0x10
[Sun Oct 1 15:59:04 2023] ret_from_fork_asm+0x1b/0x30
[Sun Oct 1 15:59:04 2023] </TASK>
[Sun Oct 1 15:59:04 2023] ================================================================================
[Sun Oct 1 15:59:04 2023] [drm] radeon: dpm initialized
[Sun Oct 1 15:59:04 2023] [drm] GART: num cpu pages 262144, num gpu pages 262144
[Sun Oct 1 15:59:04 2023] [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0
[Sun Oct 1 15:59:04 2023] [drm] PCIE GART of 1024M enabled (table at 0x000000000014C000).
[Sun Oct 1 15:59:04 2023] radeon 0000:03:00.0: WB enabled
[Sun Oct 1 15:59:04 2023] radeon 0000:03:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00
[Sun Oct 1 15:59:04 2023] radeon 0000:03:00.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c
[Sun Oct 1 15:59:04 2023] radeon 0000:03:00.0: fence driver on ring 5 use gpu addr 0x000000000005c418
[Sun Oct 1 15:59:04 2023] radeon 0000:03:00.0: radeon: MSI limited to 32-bit
[Sun Oct 1 15:59:04 2023] radeon 0000:03:00.0: radeon: using MSI.
[Sun Oct 1 15:59:04 2023] [drm] radeon: irq initialized.
```
- As examples of good bug reports you may review one of these - #1698, #1536, #1734
Otherwise, fill the requested information below.
And please remove anything that doesn't apply to keep things readable :)
## Brief summary of the problem:
1. Never had a problem.
2. Enabled UBSAN with 6.5.5 and it caught an out of range error.
## Hardware description:
- CPU: Xeon E5-1660
- GPU: < TODO: `lspci -nn | grep VGA` or `lshw -C display -numeric` >
```
*-display
description: VGA compatible controller
product: Park [Mobility Radeon HD 5430] [1002:68E1]
vendor: Advanced Micro Devices, Inc. [AMD/ATI] [1002]
physical id: 0
bus info: pci@0000:03:00.0
logical name: /dev/fb0
version: 00
width: 64 bits
clock: 33MHz
capabilities: pm pciexpress msi vga_controller bus_master cap_list rom fb
configuration: depth=32 driver=radeon latency=0 resolution=2560,1600
resources: irq:44 memory:e0000000-efffffff memory:fbb20000-fbb3ffff ioport:d000(size=256) memory:c0000-dffff
```
- System Memory: 64GB
- Display(s): 1 x DVI-D to Dell Monitor
- Type of Display Connection: <TODO: DP, HDMI, DVI, etc>
- DVI-D
## System information:
- Distro name and Version: Debian Testing
- Kernel version: Linux box1 6.5.5 #13 SMP Sun Oct 1 15:57:11 EDT 2023 x86_64 GNU/Linux
- Custom kernel: Custom kernel
- AMD official driver version: Not using AMD version, just Linux kernel driver + the non-free firmware.
## How to reproduce the issue:
Enable UBSAN on the Linux kernel (6.5.5) and also use AMD/DRM driver with firmware-linux-nonfree package and I get this error at boot as shown in the dmesg output above.
## Attached files:
### Screenshots/video files
N/A; kernel error is logged in dmesg.
### Log files (for system lockups / game freezes / crashes)
N/Alinux-6.7https://gitlab.freedesktop.org/drm/amd/-/issues/2851WARNING: CPU: 1 PID: 915 at drivers/gpu/drm/ttm/ttm_bo.c:353 ttm_bo_release+0...2024-02-29T07:20:20ZWojtas JDWARNING: CPU: 1 PID: 915 at drivers/gpu/drm/ttm/ttm_bo.c:353 ttm_bo_release+0x309/0x330 [ttm] after lowering resolution (GUI settings)## Brief summary of the problem:
After lowering resolution (for example from 1920x1080 -> 1680x1050) from GUI (Displays section in GNOME Control Center or KDE systemsettings) I'm getting this **ttm** WARNING in `dmesg` ( /usr/lib/xorg/X...## Brief summary of the problem:
After lowering resolution (for example from 1920x1080 -> 1680x1050) from GUI (Displays section in GNOME Control Center or KDE systemsettings) I'm getting this **ttm** WARNING in `dmesg` ( /usr/lib/xorg/Xorg has PID 915 here )
```
[ 93.996019] ------------[ cut here ]------------
[ 93.996026] WARNING: CPU: 1 PID: 915 at drivers/gpu/drm/ttm/ttm_bo.c:353 ttm_bo_release+0x309/0x330 [ttm]
[ 93.996046] Modules linked in: amdgpu iommu_v2 drm_buddy gpu_sched snd_hda_codec_via snd_hda_codec_generic snd_hda_codec_hdmi ledtrig_audio snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec coretemp kvm_intel snd_hda_core snd_hwdep kvm snd_pcm radeon irqbypass snd_seq_midi sha512_ssse3 drm_ttm_helper ttm drm_display_helper snd_seq_midi_event cec input_leds snd_rawmidi rc_core joydev drm_kms_helper serio_raw snd_seq at24 i2c_algo_bit snd_seq_device syscopyarea sysfillrect snd_timer sysimgblt video snd asus_atk0110 wmi mac_hid soundcore sch_fq_codel msr binfmt_misc parport_pc ppdev lp parport ramoops reed_solomon drm pstore_blk pstore_zone efi_pstore ip_tables x_tables autofs4 hid_generic uas r8169 usbhid ahci usb_storage lpc_ich libahci hid i2c_i801 psmouse realtek i2c_smbus
[ 93.996122] CPU: 1 PID: 915 Comm: Xorg Not tainted 6.2.0-32-generic #32~22.04.1-Ubuntu
[ 93.996126] Hardware name: System manufacturer System Product Name/P5QL-CM, BIOS 0901 05/11/2010
[ 93.996128] RIP: 0010:ttm_bo_release+0x309/0x330 [ttm]
[ 93.996140] Code: 4c 89 e7 e8 79 2a 00 00 48 8b 7b 90 e9 76 fd ff ff be 03 00 00 00 e8 d6 f2 04 ed e9 06 fe ff ff e8 7c ed 3d ed e9 fc fd ff ff <0f> 0b 48 83 7b 20 00 0f 84 33 fd ff ff 0f 0b e9 2c fd ff ff 0f 0b
[ 93.996143] RSP: 0018:ffffa00a01047c70 EFLAGS: 00010202
[ 93.996146] RAX: 0000000000000000 RBX: ffff91a75a5ad5e0 RCX: 0000000000000000
[ 93.996148] RDX: 0000000000000001 RSI: 0000000000000000 RDI: ffff91a75a5ad5e0
[ 93.996150] RBP: ffffa00a01047cd0 R08: ffff91a75a5ad5e0 R09: 0000000000000000
[ 93.996151] R10: 0000000000000000 R11: 0000000000000000 R12: ffff91a8138c06f0
[ 93.996153] R13: ffff91a757b1cad8 R14: ffff91a75a5ad478 R15: ffff91a757b1ca80
[ 93.996155] FS: 00007fb70c7aca80(0000) GS:ffff91a81bc80000(0000) knlGS:0000000000000000
[ 93.996158] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 93.996160] CR2: 00007fb6fa1d4010 CR3: 0000000001ef6000 CR4: 00000000000406e0
[ 93.996162] Call Trace:
[ 93.996165] <TASK>
[ 93.996169] ? show_regs+0x72/0x90
[ 93.996175] ? ttm_bo_release+0x309/0x330 [ttm]
[ 93.996186] ? __warn+0x8d/0x160
[ 93.996191] ? ttm_bo_release+0x309/0x330 [ttm]
[ 93.996203] ? report_bug+0x1bb/0x1d0
[ 93.996208] ? handle_bug+0x46/0x90
[ 93.996213] ? exc_invalid_op+0x19/0x80
[ 93.996217] ? asm_exc_invalid_op+0x1b/0x20
[ 93.996221] ? ttm_bo_release+0x309/0x330 [ttm]
[ 93.996232] ? __call_rcu_common.constprop.0+0xa6/0x2c0
[ 93.996237] ttm_bo_put+0x3d/0x70 [ttm]
[ 93.996249] radeon_bo_unref+0x1e/0x40 [radeon]
[ 93.996339] radeon_gem_object_free+0x34/0x60 [radeon]
[ 93.996407] drm_gem_object_free+0x1d/0x40 [drm]
[ 93.996479] drm_gem_dmabuf_release+0x47/0x70 [drm]
[ 93.996530] dma_buf_release+0x4a/0xb0
[ 93.996534] __dentry_kill+0x110/0x1b0
[ 93.996538] dput+0x1d1/0x330
[ 93.996541] __fput+0xf4/0x290
[ 93.996546] ____fput+0xe/0x20
[ 93.996549] task_work_run+0x61/0xa0
[ 93.996552] exit_to_user_mode_loop+0x111/0x140
[ 93.996555] exit_to_user_mode_prepare+0xb9/0xd0
[ 93.996558] syscall_exit_to_user_mode+0x2a/0x50
[ 93.996561] do_syscall_64+0x69/0x90
[ 93.996565] ? radeon_drm_ioctl+0x6f/0x90 [radeon]
[ 93.996618] ? exit_to_user_mode_prepare+0x3b/0xd0
[ 93.996621] ? syscall_exit_to_user_mode+0x2a/0x50
[ 93.996624] ? do_syscall_64+0x69/0x90
[ 93.996627] ? exit_to_user_mode_prepare+0x3b/0xd0
[ 93.996630] ? syscall_exit_to_user_mode+0x2a/0x50
[ 93.996633] ? do_syscall_64+0x69/0x90
[ 93.996636] entry_SYSCALL_64_after_hwframe+0x72/0xdc
[ 93.996639] RIP: 0033:0x7fb70cb1aaff
[ 93.996641] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <41> 89 c0 3d 00 f0 ff ff 77 1f 48 8b 44 24 18 64 48 2b 04 25 28 00
[ 93.996644] RSP: 002b:00007fffdff69e50 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
[ 93.996647] RAX: 0000000000000000 RBX: 00007fffdff69ef8 RCX: 00007fb70cb1aaff
[ 93.996649] RDX: 00007fffdff69ef8 RSI: 0000000040086409 RDI: 0000000000000010
[ 93.996651] RBP: 0000000040086409 R08: 0000000000b8a58c R09: 0000000000000000
[ 93.996653] R10: 00007fb70c3e7220 R11: 0000000000000246 R12: 0000558642c667a8
[ 93.996655] R13: 0000000000000010 R14: 0000000000000384 R15: 0000558642be77b0
[ 93.996658] </TASK>
[ 93.996659] ---[ end trace 0000000000000000 ]---
```
It occurs in several distributions like:
- Ubuntu 22.04.3 (GNOME 42.9 @ X11), kernel 6.2.0-32-generic (64-bit)
- Manjaro (KDE Plasma 5.27.7 @ X11), kernel 6.5.0-1-MANJARO (64-bit) and 6.1.49-1-MANJARO (64-bit)
- openSUSE Leap 15.5 (KDE Plasma 5.27.4 @ X11), kernel 5.14.21-150500-55.19-default (64-bit)
Easy to reproduce but not all resolutions cause this warning.
Kernel warning occurs one time (probably because WARN_ON_ONCE() function), so to repeat the problem machine must be rebooted.
It seems that changing resolution with `xrandr` (after reboot) does not cause this problem.
## Hardware description:
- CPU: quad core Intel Xeon L5430 [MCP] speed (MHz): 2,66 GHz
- GPU: 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550 / R5 230] [1002:6759]
- System Memory: 4096 MiB
- Display(s): LCD Samsung 27" 1920x1080
- Type of Display Connection: HDMI
## System information:
- Distro name and Version: Ubuntu 22.04.3 (also: Manjaro 23 KDE Plasma; openSUSE Leap 15.5 KDE Plasma)
- Kernel version: 6.2.0-32-generic
- Custom kernel: N/A
- AMD official driver version: N/A
## How to reproduce the issue:
Try lowering display resolution from the GUI settings.
## Attached files:[dmesg.txt](/uploads/0c6426eec9002295c615cbbcc36a90fd/dmesg.txt)[Xorg.0.log](/uploads/2026a1884f4196d960de994e8fa1f42e/Xorg.0.log)https://gitlab.freedesktop.org/drm/amd/-/issues/2826Kernel version 6.1.50 regression: AMD ES1000 - radeonfb deactivate vga console2023-10-10T16:17:47ZAlexei GradinariKernel version 6.1.50 regression: AMD ES1000 - radeonfb deactivate vga consoleSince kernel version 6.1.50 the VGA console stopped working on all HP ProLiant (G6 and G7) servers with [AMD/ATI] ES1000 VGA controller.
No issue with all kernel version 6.1.X before 6.1.50.
No issue with the kernel 6.1.50 with the reve...Since kernel version 6.1.50 the VGA console stopped working on all HP ProLiant (G6 and G7) servers with [AMD/ATI] ES1000 VGA controller.
No issue with all kernel version 6.1.X before 6.1.50.
No issue with the kernel 6.1.50 with the reversed next commit:
```
commit 6db53af15444e7022640d7b8d5e7531d94e27a43
Author: Daniel Vetter <daniel.vetter@ffwll.ch>
Date: Wed Jan 11 16:41:08 2023 +0100
fbdev/radeon: use pci aperture helpers
```
With the commit 6db53af15444e7022640d7b8d5e7531d94e27a43 there is kernel log "radeonfb 0000:01:03.0: vgaarb: deactivate vga console" and VGA console not working. Without this commit no such log and VGA console working.
Equipment:
```
HP ProLiant DL360 G7
01:03.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] ES1000 (rev 02) (prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company ProLiant DL360 G5
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Interrupt: pin A routed to IRQ 23
Region 0: Memory at e8000000 (32-bit, prefetchable) [size=128M]
Region 1: I/O ports at 2000 [size=256]
Region 2: Memory at f1cf0000 (32-bit, non-prefetchable) [size=64K]
Expansion ROM at 000c0000 [virtual] [disabled] [size=128K]
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Kernel driver in use: radeonfb
HP ProLiant ML330 G6
01:03.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] ES1000 (rev 02) (prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company ProLiant DL360 G5
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Interrupt: pin A routed to IRQ 23
Region 0: Memory at f0000000 (32-bit, prefetchable) [size=128M]
Region 1: I/O ports at 3000 [size=256]
Region 2: Memory at fbef0000 (32-bit, non-prefetchable) [size=64K]
Expansion ROM at 000c0000 [virtual] [disabled] [size=128K]
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Kernel driver in use: radeonfb
```Daniel VetterDaniel Vetterhttps://gitlab.freedesktop.org/drm/amd/-/issues/2753imac12,2 (27” 2011) with Radeon HD 6770M can’t change backlight/brightness2024-03-02T02:04:24ZRedBearAKimac12,2 (27” 2011) with Radeon HD 6770M can’t change backlight/brightnessI have a sibling of the iMac12 model described in issue #1838, which was closed (I think successfully) about a year ago.
The title was "imac12,1 (21.5” 2011) with Radeon HD 6750M can’t change backlight/brightness"
What I have here is ...I have a sibling of the iMac12 model described in issue #1838, which was closed (I think successfully) about a year ago.
The title was "imac12,1 (21.5” 2011) with Radeon HD 6750M can’t change backlight/brightness"
What I have here is the iMac12,2 (27" 2011) model, which seems to have a Radeon HD 6770M. Same problem as in the older issue report, there should be a "radeon_bl0" folder in /sys/class/backlight, but when installing openSUSE Tumbleweed with kernel 6.4.6 there is only "acpi_video0", and manipulating the value in the "brightness" file in that folder has no effect on the backlight at all. Max value for that is 15 in the "max_brightness" file, other values cause an error. But no value from 0 to 15 makes any difference in brightness.
Booting from a Linux Mint 21.2 live ISO which is still using kernel 5.15, I see the "radeon_bl0" folder. Max value is 255, and manipulating the value in the "brightness" file with values between 0 and 255 will change the backlight brightness from completely off to full brightness.
Oddly, the brightness keys while booted into Linux Mint 21.2 show the OSD overlay changing, but apparently the backlight device being manipulated by the brightness keys is the "acpi_video0" device, since there is no change in brightness unless I manually change the value in the "radeon_bl0" folder.
Any chance a similar patch can be made to the one that fixed #1838? I barely know what I'm looking at but the patch diff seemed like it was only changing a few lines of something.
Edit: I didn't notice there was a way to link a new issue to an existing issue (from the vertical "..." menu). There doesn't seem to be a way to add this linking after the fact by just editing the issue.https://gitlab.freedesktop.org/drm/amd/-/issues/2615radeon/i586: BUG: kernel NULL pointer dereference, address: 000000042023-10-02T15:31:10ZTaketo Kaberadeon/i586: BUG: kernel NULL pointer dereference, address: 00000004## Brief summary of the problem:
radeon and drm driver emits BUG and kernel panics on i586 CPU and AGP bus card.
## Hardware description:
- CPU: Pentium 120 (P54C)
- GPU: 01:00.0 0300: 1002:5960 (rev 01)
01:00.0 VGA compatible...## Brief summary of the problem:
radeon and drm driver emits BUG and kernel panics on i586 CPU and AGP bus card.
## Hardware description:
- CPU: Pentium 120 (P54C)
- GPU: 01:00.0 0300: 1002:5960 (rev 01)
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV280
[Radeon 9200 PRO / 9250] (rev 01) (prog-if 00 [VGA controller])
Bus connection: AGP
- System Memory: 1GiB
- Display(s): 1
- Type of Display Connection: VGA
## System information:
- Distro name and Version: Rocky Linux 9.2
- Kernel version: kernel-6.1.11 https://gitlab.freedesktop.org/agd5f/linux.git HEAD->amd-staging-drm-next 9487fb8eb1f
- Custom kernel: Kernel from amd-staging-drm-next, compiled under rpmbuild
## How to reproduce the issue:
- Compile an i586 kernel with CONFIG_DRM_RADEON=m .
- Install onto machine with Radeon 9200 AGP card.
- Boot. On transition to graphical console, the kernel panics.
- To grab the kernel panic message, boot by adding "console=ttyS0" and use serial console.
### Console Log
```
[ 463.512597] [drm] radeon kernel modesetting enabled.
[ 463.571435] radeon 0000:01:00.0: vgaarb: deactivate vga console
[ 463.676628] Console: switching to colour dummy device 80x25
[ 463.834998] [drm] initializing kernel modesetting (RV280 0x1002:0x5960 0x148C:0x2094 0x01).
[ 463.845435] [drm] Forcing AGP to PCI mode
[ 464.060722] [drm] Generation 2 PCI interface, using max accessible memory
[ 464.061689] radeon 0000:01:00.0: VRAM: 128M 0x00000000C0000000 - 0x00000000C7FFFFFF (128M used)
[ 464.074217] radeon 0000:01:00.0: GTT: 512M 0x00000000A0000000 - 0x00000000BFFFFFFF
[ 464.242304] [drm] Detected VRAM RAM=128M, BAR=128M
[ 464.251369] [drm] RAM width 64bits DDR
[ 464.392636] [drm] radeon: 128M of VRAM memory ready
[ 464.462477] [drm] radeon: 512M of GTT memory ready.
[ 464.522200] [drm] GART: num cpu pages 131072, num gpu pages 131072
[ 464.701594] [drm] PCI GART of 512M enabled (table at 0x0000000008200000).
[ 464.777076] radeon 0000:01:00.0: WB disabled
[ 464.783044] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x00000000a0000000
[ 464.857834] radeon 0000:01:00.0: Disabling GPU acceleration
[ 464.874988] [drm] radeon: cp finalized
[ 465.110546] [drm] Radeon Display Connectors
[ 465.115998] [drm] Connector 0:
[ 465.125799] [drm] VGA-1
[ 465.140634] [drm] DDC: 0x60 0x60 0x60 0x60 0x60 0x60 0x60 0x60
[ 465.146921] [drm] Encoders:
[ 465.155015] [drm] CRT1: INTERNAL_DAC1
[ 465.169283] [drm] Connector 1:
[ 465.177982] [drm] DVI-I-1
[ 465.184978] [drm] HPD1
[ 465.200419] [drm] DDC: 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64
[ 465.206674] [drm] Encoders:
[ 465.214656] [drm] CRT2: INTERNAL_DAC2
[ 465.228887] [drm] DFP1: INTERNAL_TMDS1
[ 465.233613] [drm] Connector 2:
[ 465.242142] [drm] SVIDEO-1
[ 465.259632] [drm] Encoders:
[ 465.267660] [drm] TV1: INTERNAL_DAC2
[ 466.211483] BUG: kernel NULL pointer dereference, address: 00000004
[ 466.221070] #PF: supervisor read access in kernel mode
[ 466.221070] #PF: error_code(0x0000) - not-present page
[ 466.221070] *pde = 00000000
[ 466.221070] Oops: 0000 [#1] PREEMPT SMP
[ 466.221070] CPU: 0 PID: 370 Comm: systemd-udevd Not tainted 6.1.11-1.el9_2.v1.i586 #1
[ 466.221070] Hardware name: System Manufacturer System Name/ALADDIN5, BIOS 0626 07/15/95
[ 466.221070] EIP: _raw_spin_lock_irqsave+0x1f/0x40
[ 466.221070] Code: cc cc cc cc cc cc cc cc cc cc cc 3e 8d 74 26 00 55 89 c1 89 e5 56 53 9c 5b fa 64 ff 05 dc d6 79 c2 31 d2 be 01 00 00 00 89 d0 <3e> 0f b1 31 75 0b 89 d8 5b 5e 5d c3 8d 74 26 00 90 89 c2 89 c8 e8
[ 466.221070] EAX: 00000000 EBX: 00000246 ECX: 00000004 EDX: 00000000
[ 466.221070] ESI: 00000001 EDI: c3e5dc28 EBP: c3e5dc1c ESP: c3e5dc14
[ 466.221070] DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 EFLAGS: 00010046
[ 466.221070] CR0: 80050033 CR2: 00000004 CR3: 05818000 CR4: 00000010
[ 466.221070] Call Trace:
[ 466.221070] kthread_flush_worker+0x52/0xa0
[ 466.221070] ? kthread_data+0x30/0x30
[ 466.221070] drm_crtc_vblank_off+0x173/0x260 [drm]
[ 466.221070] ? ww_mutex_lock+0x14/0x80
[ 466.221070] radeon_crtc_dpms+0x197/0x1b0 [radeon]
[ 466.221070] radeon_crtc_disable+0x16/0xa0 [radeon]
[ 466.221070] __drm_helper_disable_unused_functions+0x74/0xc0 [drm_kms_helper]
[ 466.221070] drm_helper_disable_unused_functions+0x3c/0x50 [drm_kms_helper]
[ 466.221070] radeon_fbdev_init+0xb0/0x130 [radeon]
[ 466.221070] radeon_modeset_init+0x24d/0x310 [radeon]
[ 466.221070] radeon_driver_load_kms+0xc4/0x240 [radeon]
[ 466.221070] drm_dev_register+0xd6/0x1c0 [drm]
[ 466.221070] radeon_pci_probe+0xc0/0x100 [radeon]
[ 466.221070] pci_device_probe+0xaa/0x160
[ 466.221070] really_probe+0xb7/0x340
[ 466.221070] __driver_probe_device+0x79/0x1e0
[ 466.221070] ? sysfs_create_dir_ns+0x54/0xc0
[ 466.221070] driver_probe_device+0x1f/0x90
[ 466.221070] __driver_attach+0xc7/0x1a0
[ 466.221070] ? __device_attach_driver+0x100/0x100
[ 466.221070] bus_for_each_dev+0x58/0x90
[ 466.221070] driver_attach+0x19/0x20
[ 466.221070] ? __device_attach_driver+0x100/0x100
[ 466.221070] bus_add_driver+0x177/0x1c0
[ 466.221070] driver_register+0x79/0xd0
[ 466.221070] ? 0xf7e2a000
[ 466.221070] __pci_register_driver+0x4c/0x50
[ 466.221070] radeon_module_init+0x5c/0x1000 [radeon]
[ 466.221070] do_one_initcall+0x3e/0x1c0
[ 466.221070] ? __vunmap+0x20b/0x2a0
[ 466.221070] ? __kmem_cache_alloc_node+0x2f/0x3e0
[ 466.221070] ? do_init_module+0x21/0x1d0
[ 466.221070] ? kmalloc_trace+0x20/0x90
[ 466.221070] ? do_init_module+0x21/0x1d0
[ 466.221070] do_init_module+0x43/0x1d0
[ 466.221070] load_module+0x862/0x8f0
[ 466.221070] ? check_heap_object+0xdf/0x130
[ 466.221070] ? security_kernel_post_load_data+0x52/0x60
[ 466.221070] __ia32_sys_init_module+0x16d/0x1a0
[ 466.221070] do_int80_syscall_32+0x2e/0x80
[ 466.221070] entry_INT80_32+0xf0/0xf0
[ 466.221070] EIP: 0xb79f0e4e
[ 466.221070] Code: 0f 83 d6 06 00 00 c3 66 90 66 90 90 57 56 53 8b 7c 24 20 8b 74 24 1c 8b 54 24 18 8b 4c 24 14 8b 5c 24 10 b8 80 00 00 00 cd 80 <5b> 5e 5f 3d 01 f0 ff ff 0f 83 a4 06 00 00 c3 66 90 90 53 8b 54 24
[ 466.221070] EAX: ffffffda EBX: b5516010 ECX: 0023bca2 EDX: b7c2f274
[ 466.221070] ESI: b7c29295 EDI: b7c36dd8 EBP: 009d6500 ESP: bfc86d60
[ 466.221070] DS: 007b ES: 007b FS: 0000 GS: 0033 SS: 007b EFLAGS: 00000292
[ 466.221070] Modules linked in: nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib radeon(+) nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 amdxcp gpu_sched drm_buddy video wmi i2c_algo_bit drm_display_helper cec drm_ttm_helper ppdev rfkill ip_set ttm nf_tables libcrc32c nfnetlink drm_kms_helper pcspkr e100 syscopyarea parport_pc sysfillrect mii sysimgblt parport qrtr drm fuse ext4 mbcache jbd2 sd_mod t10_pi sr_mod crc64_rocksoft_generic cdrom crc64_rocksoft crc64 sg ata_generic pata_ali libata serio_raw
[ 466.221070] CR2: 0000000000000004
[ 466.221070] ---[ end trace 0000000000000000 ]---
[ 466.221070] EIP: _raw_spin_lock_irqsave+0x1f/0x40
[ 466.221070] Code: cc cc cc cc cc cc cc cc cc cc cc 3e 8d 74 26 00 55 89 c1 89 e5 56 53 9c 5b fa 64 ff 05 dc d6 79 c2 31 d2 be 01 00 00 00 89 d0 <3e> 0f b1 31 75 0b 89 d8 5b 5e 5d c3 8d 74 26 00 90 89 c2 89 c8 e8
[ 466.221070] EAX: 00000000 EBX: 00000246 ECX: 00000004 EDX: 00000000
[ 466.221070] ESI: 00000001 EDI: c3e5dc28 EBP: c3e5dc1c ESP: c3e5dc14
[ 466.221070] DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 EFLAGS: 00010046
[ 466.221070] CR0: 80050033 CR2: 00000004 CR3: 05818000 CR4: 00000010
[ 466.221070] Kernel panic - not syncing: Fatal exception
[ 466.221070] Kernel Offset: disabled
[ 466.221070] ---[ end Kernel panic - not syncing: Fatal exception ]--
```
## Discussion
Previous Rocky Linux 9.1 kernel (kernel-5.14.0-162.23.1) was working flawlessly.
RHEL 9.2 seems to have retrofitted kernel-6.0 DRM code according to %changelog,
so this seems to be a regression.
Interesting phenomena:
By booting kernel option "init=/bin/sh", and typing "exec /usr/lib/systemd/systemd" on the shell prompt,
makes the radeon.ko driver to propely work.
It looks like some raw input to the console fixes something.https://gitlab.freedesktop.org/drm/amd/-/issues/2608`[drm] amdgpu kernel modesetting enabled.` shown on system using *radeon* module2023-07-26T17:53:01ZPaul Menzel`[drm] amdgpu kernel modesetting enabled.` shown on system using *radeon* moduleOn an Asus F2A85-M PRO with an AMD/ATI Aruba device, 0x1002:0x9996, the modules *radeon* and *amdgpu* both show initialized messages:
[ 2.445105] [drm] radeon kernel modesetting enabled.
[ 2.448389] [drm] initializing kern...On an Asus F2A85-M PRO with an AMD/ATI Aruba device, 0x1002:0x9996, the modules *radeon* and *amdgpu* both show initialized messages:
[ 2.445105] [drm] radeon kernel modesetting enabled.
[ 2.448389] [drm] initializing kernel modesetting (ARUBA 0x1002:0x9996 0x1002:0x9996 0x00).
[ 6.323650] [drm] amdgpu kernel modesetting enabled.
[kodi-linux-6.4.0-rc4-00369-gf8a8b449098c.txt](/uploads/daf6e4addbd601932a284f6b987a518e/kodi-linux-6.4.0-rc4-00369-gf8a8b449098c.txt)https://gitlab.freedesktop.org/drm/amd/-/issues/2584KFENCE: use-after-free read in dma_resv_iter_next_unlocked2024-01-24T11:49:01ZMariusz BiałończykKFENCE: use-after-free read in dma_resv_iter_next_unlockedHi,
My kernel discovered the following use-after-free bug:
```
[Fri May 26 17:22:47 2023] ==================================================================
[Fri May 26 17:22:47 2023] BUG: KFENCE: use-after-free read in dma_resv_iter_n...Hi,
My kernel discovered the following use-after-free bug:
```
[Fri May 26 17:22:47 2023] ==================================================================
[Fri May 26 17:22:47 2023] BUG: KFENCE: use-after-free read in dma_resv_iter_next_unlocked+0x1d/0xa0
[Fri May 26 17:22:47 2023] Use-after-free read at 0x000000009a757fb4 (in kfence-#199):
[Fri May 26 17:22:47 2023] dma_resv_iter_next_unlocked+0x1d/0xa0
[Fri May 26 17:22:47 2023] dma_resv_wait_timeout+0x6c/0xe0
[Fri May 26 17:22:47 2023] ttm_bo_delayed_delete+0x2a/0x80 [ttm]
[Fri May 26 17:22:47 2023] process_one_work+0x1c7/0x3d0
[Fri May 26 17:22:47 2023] worker_thread+0x51/0x390
[Fri May 26 17:22:47 2023] kthread+0xde/0x110
[Fri May 26 17:22:47 2023] ret_from_fork+0x2c/0x50
[Fri May 26 17:22:47 2023] kfence-#199: 0x00000000bfaaf5bb-0x00000000ba9596a0, size=752, cache=kmalloc-1k
[Fri May 26 17:22:47 2023] allocated by task 554 on cpu 2 at 37.441744s:
[Fri May 26 17:22:47 2023] __kmem_cache_alloc_node+0x2c3/0x310
[Fri May 26 17:22:47 2023] kmalloc_trace+0x2a/0xa0
[Fri May 26 17:22:47 2023] radeon_bo_create+0x83/0x1e0 [radeon]
[Fri May 26 17:22:47 2023] radeon_gem_object_create+0xb7/0x1c0 [radeon]
[Fri May 26 17:22:47 2023] radeon_gem_create_ioctl+0x77/0x130 [radeon]
[Fri May 26 17:22:47 2023] drm_ioctl_kernel+0xcd/0x170
[Fri May 26 17:22:47 2023] drm_ioctl+0x26d/0x4b0
[Fri May 26 17:22:47 2023] radeon_drm_ioctl+0x4d/0x80 [radeon]
[Fri May 26 17:22:47 2023] __x64_sys_ioctl+0x94/0xd0
[Fri May 26 17:22:47 2023] do_syscall_64+0x60/0x90
[Fri May 26 17:22:47 2023] entry_SYSCALL_64_after_hwframe+0x72/0xdc
[Fri May 26 17:22:47 2023] freed by task 6154 on cpu 3 at 45587.323250s:
[Fri May 26 17:22:47 2023] process_one_work+0x1c7/0x3d0
[Fri May 26 17:22:47 2023] worker_thread+0x51/0x390
[Fri May 26 17:22:47 2023] kthread+0xde/0x110
[Fri May 26 17:22:47 2023] ret_from_fork+0x2c/0x50
[Fri May 26 17:22:47 2023] CPU: 3 PID: 112 Comm: kworker/3:1H Not tainted 6.3.3-arch1-1 #1 fa7b7e0107004b3021a57a74b951e0a25e7e8584
[Fri May 26 17:22:47 2023] Hardware name: System manufacturer System Product Name/M4A785TD-V EVO, BIOS 2105 07/23/2010
[Fri May 26 17:22:47 2023] Workqueue: ttm ttm_bo_delayed_delete [ttm]
[Fri May 26 17:22:47 2023] ==================================================================
```
After this bug occur, more it is working in this state, more problems I have; so finally I need to restart the machine.https://gitlab.freedesktop.org/drm/amd/-/issues/2567[Bisected][Radeon] Monitor connected with DisplayPort shows a black screen on...2023-06-02T16:13:44ZAdrian Chan[Bisected][Radeon] Monitor connected with DisplayPort shows a black screen on bootI have a desktop `HP EliteDesk 705 G1` that has the graphics card
`Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8470D] [1002:9996]`
as reported by `lspci`. I have a monitor `HP E27u G4` connected to this desktop via Displ...I have a desktop `HP EliteDesk 705 G1` that has the graphics card
`Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8470D] [1002:9996]`
as reported by `lspci`. I have a monitor `HP E27u G4` connected to this desktop via DisplayPort. When I boot up Ubuntu 23.04, the monitor initially shows the splash screen (indicating that the monitor does work) but then fails to detect a signal when it boots Ubuntu. Unplugging the DisplayPort cable and then plugging it back in fixes the issue (i.e. I can see the Ubuntu screen and everything works fine).
It might be worth noting that I have been working on ChromeOS Flex to try to figure out the cause of the issue because that is where I saw the issue initially. I believe that all my findings below apply to Ubuntu 23.04 as well; the issue certainly is able to be reproduced on Ubuntu 23.04.
On ChromeOS Flex, running kernel 5.15 with some backported changes from 6.1, this upstream commit https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/gpu/drm/radeon?id=01ad1d9c2888d51f2fb5b5ac88af8bd47d76937e seems to be where the issue started happening. Reintroducing the deleted lines to `drivers/gpu/drm/radeon/radeon_irq_kms.c`'s function `static void radeon_dp_work_func(struct work_struct *work)` fixes the issue (i.e. the monitor displays the GUI correctly without needing to reconnect the DisplayPort cable). (The deleted lines I reintroduced can be more clearly seen in this link https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/gpu/drm/radeon/radeon_irq_kms.c?id=01ad1d9c2888d51f2fb5b5ac88af8bd47d76937e.)https://gitlab.freedesktop.org/drm/amd/-/issues/2107Enable SI/CIK in amdgpu by default/remove from radeon?2023-05-19T20:34:49ZLegacy DevicesEnable SI/CIK in amdgpu by default/remove from radeon?Vulkan performance and OpenGL performance using radv and amdgpu mesa drivers is great with SI and CIK cards when paired with amdgpu rather than radeon.
There is no reason the average user should have to make modprobe.d/radeon.conf with...Vulkan performance and OpenGL performance using radv and amdgpu mesa drivers is great with SI and CIK cards when paired with amdgpu rather than radeon.
There is no reason the average user should have to make modprobe.d/radeon.conf with `option radeon si_support=0 cik_support=0` or modprobe.d/amdgpu.conf with `option amdgpu si_support=1 cik_support=1`, blocklist radeon and also ensure that the amdgpu module loads before radeon.
Why does this remain incomplete, what is needed to move it forward, and are there any volunteers to make it happen?https://gitlab.freedesktop.org/drm/amd/-/issues/2072The image trembles strongly when moving the mouse (fedora 36, gnome 42.2)2023-05-25T03:40:07ZDmitriy BeketovThe image trembles strongly when moving the mouse (fedora 36, gnome 42.2)The image trembles strongly when moving the mouse (see attached video).
It repeats always, at each session of work.
## Hardware description:
- CPU: Intel Core i7-10700KF
- GPU: VGA compatible controller [0300]: Advanced Micro Devices,...The image trembles strongly when moving the mouse (see attached video).
It repeats always, at each session of work.
## Hardware description:
- CPU: Intel Core i7-10700KF
- GPU: VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Hawaii XT / Grenada XT [Radeon R9 290X/390X] [1002:67b0] (rev 80)
- System Memory: Kingston DDR4 (4x8GB=32GB)
- Display(s): LG Ultra HD GSM5b08 (3840x2160) - 2 pieces and AOC 4k - the problem manifests itself when connecting any of them
- Type of Display Connection: dp (the problem occurs when connected via HDMI)
## System information:
- Distro name and Version: Fedora 36
- Kernel version: Linux fedora 5.18.6-200.fc36.x86_64 #1 SMP PREEMPT_DYNAMIC Wed Jun 22 13:46:18 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
- Custom kernel: N/A
- AMD official driver version: N/A
## How to reproduce the issue:
Often. For example, when moving the mouse and scrolling in Google Chrome - always. When working with the console - rarely. On Skype - also often. Often in other programs, and in general if the programs are not running - too.
I try wayland and xorg - the problem is here and there.
3 monitors connected. But if you connect 2 or 1 - the problem is the same.
I tried connecting via hdmi and via display port and different wires - the problem does not disappear.
There is no problem when working in the Windows operating system.
Steps to Reproduce:
1.Load operating system.
2.Open google chrome.
3.Move the mouse cursor over it.
Actual results:
Image shakes a lot.
Expected results:
Trembling should be absent
Additional info:
I did not install video drivers, I installed the system and that's it.
## Attached files:
### Screenshots/video files
![bug](/uploads/dce7449cbac65db0e5922fb92edaa78e/bug.mp4)https://gitlab.freedesktop.org/drm/amd/-/issues/2053BS GPL2 headers?2023-01-09T20:09:20ZYusuf KhanBS GPL2 headers?linux/drivers/gpu/drm/radeon/Makefile and linux/drivers/gpu/drm/radeon/Kconfig both have GPL-2.0 liscence headers after the liscence cleanup(b24413180f5600bcb3bb70fbed5cf186b60864bd). Is this needed?linux/drivers/gpu/drm/radeon/Makefile and linux/drivers/gpu/drm/radeon/Kconfig both have GPL-2.0 liscence headers after the liscence cleanup(b24413180f5600bcb3bb70fbed5cf186b60864bd). Is this needed?https://gitlab.freedesktop.org/drm/amd/-/issues/2012Radeon HD 7420G: audio is slow and low-pitched when played over DisplayPort2023-10-13T21:10:56ZNicholas BishopRadeon HD 7420G: audio is slow and low-pitched when played over DisplayPort## Brief summary of the problem:
Test device is an HP ProBook mt41 with a Radeon HD 7420G. Audio played over DisplayPort is slow and low-pitched. When using a DP->HDMI converter cable the audio sounds fine, but with a DP cable the bug h...## Brief summary of the problem:
Test device is an HP ProBook mt41 with a Radeon HD 7420G. Audio played over DisplayPort is slow and low-pitched. When using a DP->HDMI converter cable the audio sounds fine, but with a DP cable the bug happens in 100% of my testing.
(I'm unsure whether this is the right bug tracker to report the issue in; please let me know if there's a more appropriate place.)
## Hardware description:
- CPU: `AMD A4-4300M`
- GPU: `00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Trinity 2 [Radeon HD 7420G] [1002:9992]`
- System Memory: 8G
- Display(s): Internal laptop display, external [Samsung S34E790C](https://www.samsung.com/africa_en/monitors/ultra-wide/curved-monitor-34-inch-ls34e790cns-ng/) monitor
- Type of Display Connection: DP
## System information:
- Distro name and Version: ChromeOS Flex, also confirmed bug on Fedora 32 and 36
- Kernel version: `Linux localhost 5.18.0-rc6.mybuild-00111-g364a453ab912 #110 SMP PREEMPT_DYNAMIC Fri May 13 13:37:28 EDT 2022 x86_64 AMD A4-4300M APU with Radeon(tm) HD Graphics AuthenticAMD GNU/Linux`
- Custom kernel: Latest master (commit 364a453ab9123f493edfa246798ce9eeda452bdb)
- AMD official driver version: N/A
## How to reproduce the issue:
Laptop has one DisplayPort output. Connect that via a DisplayPort cable to a monitor that also supports DisplayPort. (Connecting via a DP->HDMI cable does not reproduce the issue.)
Play a wav file:
```
aplay -D plughw:0,3 test.wav
```
Audio plays from the external monitor. The audio is slower and lower-pitched than it should be.
## Attached files:
### Log files (for system lockups / game freezes / crashes)
- Dmesg log: [dp-audio-bug-dmesg.txt](/uploads/197e6bc5ab1978d176213783007f722c/dp-audio-bug-dmesg.txt)https://gitlab.freedesktop.org/drm/amd/-/issues/1988Radeon HD5770 incorrect refresh rate via display port2023-05-25T03:43:11ZRoman ElshinRadeon HD5770 incorrect refresh rate via display portOriginal bug report was filed here https://bugzilla.kernel.org/show_bug.cgi?id=214369 but no response and it seems here is a more right place.
I just test it with win7 and old catalyst version (10-12) - the card sets video mode correctly...Original bug report was filed here https://bugzilla.kernel.org/show_bug.cgi?id=214369 but no response and it seems here is a more right place.
I just test it with win7 and old catalyst version (10-12) - the card sets video mode correctly. But my previous test with win7 and some other driver version (can't remember it was a while ago) was showing the same issue.https://gitlab.freedesktop.org/drm/amd/-/issues/1970Diagonal tearing in OpenGL output on Aruba r600 GPU (Radeon HD 7660D) since L...2022-04-28T02:04:43ZPetr PisarDiagonal tearing in OpenGL output on Aruba r600 GPU (Radeon HD 7660D) since Linux 5.16I have a Radeon HD 7660D GPU and for some time I observe diagonal tearing when playing a video using OpenGL (e.g. with "mpv --video=gpu"). Other displaying methods (Xv, VDPAU, plain X11) are not affected. It happens in current Linux 5.17...I have a Radeon HD 7660D GPU and for some time I observe diagonal tearing when playing a video using OpenGL (e.g. with "mpv --video=gpu"). Other displaying methods (Xv, VDPAU, plain X11) are not affected. It happens in current Linux 5.17.2, 5.17.1, 5.17.0 and I have been experiencing it for a few months.
Today I bisected it to v5.15-rc1-369-g0597ca7b43e4:
~~~~
commit 0597ca7b43e41c509bd0feb143bdfb7278496397 (refs/bisect/bad)
Author: Christian König <christian.koenig@amd.com>
Date: Wed Jun 16 09:23:50 2021 +0200
drm/radeon: use new iterator in radeon_sync_resv
Simplifying the code a bit.
Signed-off-by: Christian König <christian.koenig@amd.com>
Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Link: https://patchwork.freedesktop.org/patch/msgid/20211005113742.1101-16-christian.koenig@amd.com
~~~~
Reverting the commit from 5.17.2 tree helps for me.
I'm using xorg-server-21.1.3, xf86-video-ati-19.1.0, mesa-22.0.1, mpv-0.33.1. My xorg.conf:
~~~~
Section "Device"
Identifier "Radeon"
Driver "radeon"
Option "AccelMethod" "glamor"
Option "AccelDFS" "True"
EndSection
~~~~
An excerpt from Xorg.0.log:
~~~~
[ 47.619] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 47.619] (II) Platform probe for /sys/devices/pci0000:00/0000:00:01.0/drm/card0
[ 47.620] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 10 paused 0
[ 47.625] (--) PCI:*(0@0:1:0) 1002:9901:1043:8526 rev 0, Mem @ 0xc0000000/268435456, 0xfef00000/262144, I/O @ 0x0000f000/256, BIOS @ 0x????????/131072
[ 47.625] (II) "glx" will be loaded. This was enabled by default and also specified in the config file.
[ 47.625] (II) LoadModule: "dbe"
[ 47.625] (II) Module "dbe" already built-in
[ 47.625] (II) LoadModule: "extmod"
[ 47.625] (II) Module "extmod" already built-in
[ 47.625] (II) LoadModule: "dri3"
[ 47.625] (II) Module "dri3" already built-in
[ 47.625] (II) LoadModule: "glamoregl"
[ 47.641] (II) Loading /usr/lib64/xorg/modules/libglamoregl.so
[ 47.789] (II) Module glamoregl: vendor="X.Org Foundation"
[ 47.789] compiled for 1.21.1.3, module version = 1.0.1
[ 47.789] ABI class: X.Org ANSI C Emulation, version 0.4
[ 47.789] (II) LoadModule: "glx"
[ 47.789] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so
[ 47.881] (II) Module glx: vendor="X.Org Foundation"
[ 47.881] compiled for 1.21.1.3, module version = 1.0.0
[ 47.881] ABI class: X.Org Server Extension, version 10.0
[ 47.881] (II) LoadModule: "radeon"
[ 47.881] (II) Loading /usr/lib64/xorg/modules/drivers/radeon_drv.so
[ 47.929] (II) Module radeon: vendor="X.Org Foundation"
[ 47.929] compiled for 1.21.1.3, module version = 19.1.0
[ 47.929] Module class: X.Org Video Driver
[ 47.929] ABI class: X.Org Video Driver, version 25.2
[...]
[ 48.047] (II) RADEON: Driver for ATI/AMD Radeon chipsets:
[...]
[ 48.050] (II) [KMS] Kernel modesetting enabled.
[ 48.050] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[ 48.050] (II) RADEON(0): Creating default Display subsection in Screen section
"Screen 1" for depth/fbbpp 24/32
[ 48.050] (**) RADEON(0): Depth 24, (--) framebuffer bpp 32
[ 48.050] (II) RADEON(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps)
[ 48.050] (==) RADEON(0): Default visual is TrueColor
[ 48.050] (**) RADEON(0): Option "AccelMethod" "glamor"
[ 48.050] (==) RADEON(0): RGB weight 888
[ 48.050] (II) RADEON(0): Using 8 bits per RGB (8 bit DAC)
[ 48.050] (--) RADEON(0): Chipset: "ARUBA" (ChipID = 0x9901)
[ 48.050] (II) Loading sub module "fb"
[ 48.050] (II) LoadModule: "fb"
[ 48.050] (II) Module "fb" already built-in
[ 48.051] (II) Loading sub module "dri2"
[ 48.051] (II) LoadModule: "dri2"
[ 48.051] (II) Module "dri2" already built-in
[ 49.889] (II) Loading sub module "glamoregl"
[ 49.889] (II) LoadModule: "glamoregl"
[ 49.889] (II) Loading /usr/lib64/xorg/modules/libglamoregl.so
[ 49.889] (II) Module glamoregl: vendor="X.Org Foundation"
[ 49.889] compiled for 1.21.1.3, module version = 1.0.1
[ 49.889] ABI class: X.Org ANSI C Emulation, version 0.4
[ 50.124] (II) RADEON(0): glamor X acceleration enabled on AMD ARUBA (DRM 2.50.0 / 5.17.2, LLVM 13.0.1)
[ 50.124] (II) RADEON(0): glamor detected, initialising EGL layer.
[ 50.124] (II) RADEON(0): KMS Color Tiling: enabled
[ 50.124] (II) RADEON(0): KMS Color Tiling 2D: enabled
[ 50.124] (==) RADEON(0): TearFree property default: auto
[ 50.124] (II) RADEON(0): KMS Pageflipping: enabled
[ 50.126] (II) RADEON(0): Output HDMI-0 using monitor section DVI-0
[ 50.167] (II) RADEON(0): Output VGA-0 using monitor section VGA-0
[ 50.167] (**) RADEON(0): Option "DefaultModes" "false"
[ 50.198] (II) RADEON(0): Output DVI-0 using monitor section DVI-0
[ 50.200] (II) RADEON(0): EDID for output HDMI-0
[ 50.241] (II) RADEON(0): EDID for output VGA-0
[ 50.273] (II) RADEON(0): EDID for output DVI-0
[ 50.273] (II) RADEON(0): Manufacturer: DEL Model: 407e Serial#: 1096111955
[ 50.273] (II) RADEON(0): Year: 2014 Week: 21
[ 50.273] (II) RADEON(0): EDID Version: 1.3
[ 50.273] (II) RADEON(0): Digital Display Input
[ 50.273] (II) RADEON(0): Max Image Size [cm]: horiz.: 60 vert.: 34
[ 50.273] (II) RADEON(0): Gamma: 2.20
[ 50.273] (II) RADEON(0): DPMS capabilities: StandBy Suspend Off
[ 50.273] (II) RADEON(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
[ 50.273] (II) RADEON(0): First detailed timing is preferred mode
[...]
[ 50.274] (II) RADEON(0): [DRI2] Setup complete
[ 50.274] (II) RADEON(0): [DRI2] DRI driver: r600
[ 50.274] (II) RADEON(0): [DRI2] VDPAU driver: r600
[ 50.274] (II) RADEON(0): Front buffer size: 14400K
[ 50.274] (II) RADEON(0): VRAM usage limit set to 206402K
[ 50.311] (II) RADEON(0): SYNC extension fences enabled
[ 50.311] (II) RADEON(0): Present extension enabled
[ 50.311] (==) RADEON(0): DRI3 enabled
[ 50.311] (==) RADEON(0): Backing store disabled
[ 50.311] (II) RADEON(0): Direct rendering enabled
[ 50.570] (II) RADEON(0): Use GLAMOR acceleration.
[ 50.570] (II) RADEON(0): Acceleration enabled
[ 50.570] (**) RADEON(0): DPMS enabled
[ 50.570] (==) RADEON(0): Silken mouse enabled
[ 50.570] (II) RADEON(0): Set up textured video (glamor)
[ 50.570] (II) RADEON(0): [XvMC] Associated with GLAMOR Textured Video.
[ 50.570] (II) RADEON(0): [XvMC] Extension initialized.
[ 50.583] (WW) RADEON(0): Option "AccelDFS" is not used
[ 50.583] (II) Initializing extension Generic Event Extension
[ 50.583] (II) Initializing extension SHAPE
[ 50.583] (II) Initializing extension MIT-SHM
[ 50.583] (II) Initializing extension XInputExtension
[ 50.608] (II) Initializing extension XTEST
[ 50.608] (II) Initializing extension BIG-REQUESTS
[ 50.608] (II) Initializing extension SYNC
[ 50.608] (II) Initializing extension XKEYBOARD
[ 50.608] (II) Initializing extension XC-MISC
[ 50.608] (II) Initializing extension XFIXES
[ 50.608] (II) Initializing extension RENDER
[ 50.608] (II) Initializing extension RANDR
[ 50.608] (II) Initializing extension DAMAGE
[ 50.608] (II) Initializing extension MIT-SCREEN-SAVER
[ 50.608] (II) Initializing extension DOUBLE-BUFFER
[ 50.608] (II) Initializing extension RECORD
[ 50.608] (II) Initializing extension DPMS
[ 50.608] (II) Initializing extension Present
[ 50.608] (II) Initializing extension DRI3
[ 50.608] (II) Initializing extension X-Resource
[ 50.608] (II) Initializing extension XVideo
[ 50.608] (II) Initializing extension XVideo-MotionCompensation
[ 50.608] (II) Initializing extension GLX
[ 50.618] (II) AIGLX: Loaded and initialized r600
[ 50.618] (II) GLX: Initialized DRI2 GL provider for screen 0
[ 50.618] (II) Initializing extension XFree86-VidModeExtension
[ 50.618] (II) Initializing extension XFree86-DGA
[ 50.618] (II) Initializing extension XFree86-DRI
[ 50.618] (II) Initializing extension DRI2
[ 50.618] (II) RADEON(0): Setting screen physical size to 596 x 334
~~~~