| Priority | medium |
|---|---|
| Bug ID | 63599 |
| Assignee | dri-devel@lists.freedesktop.org |
| Summary | [r600][r600] GPU lockup CP stall (kernel 3.8, 3.9) |
| Severity | normal |
| Classification | Unclassified |
| OS | Linux (All) |
| Reporter | wojtask9@wp.pl |
| Hardware | x86-64 (AMD64) |
| Status | NEW |
| Version | XOrg CVS |
| Component | DRM/Radeon |
| Product | DRI |
Created attachment 78069 [details]
lspci
This happens always with KDM, LightDM/XDM (xdm-archlinux package). Login screen
freezes (but I can move mouse pointer).
First I thought that was my configuration error but the same issue with knoppix
livecd (7.0.5, kernel 3.6.10, mesa-9.0.1)
Without Display Manager (startx from console) result is the same. Screen
appears but is frozen (test using xfce4 and kde). Without DM I don't see any
GPU lockup but Xorg.0.log shows errors.
Setting R600_HYPERZ=0 or R600_DEBUG=nohyperz doesn't help
system
kernel 3.8.5 or 3.9.0-rc7
mesa 9.1.1
other packages are up to date form arch repository
Created attachment 78071 [details]
Xorg.0.log without crash (but GPU lockup CP stall appears)
I've just installed Gentoo. Issue still exists. radeon-ucode-20130513 mesa-9.2-20130515 (without llvm) kernel-3.9.2 (UVD disabled because kms with UVD don't work) libdrm-2.4.44 xf86-video-ati-7.1.0 (without glamour) any ideas or patches to test?
| What | Removed | Added |
|---|---|---|
| Attachment #78070 mime type | application/octet-stream | text/plain |
Is this a regression with kernels 3.8, 3.9? I.e., did 3.7 work ok?
This is the first linux installation on that machine. I cannot confirm if this is regression. First time when I installed Arch linux kernel version was 3.7 and GPU lockup occurred
short summary (Alex suggestions on IRC): remove r600g_dri.so -> NOT OK "ColorTiling2D" "false" -> NOT OK kernel-3.10-rc1 -> NOT OK "NoAccel" "true" -> OK
What is the motherboard and cpu reference ? AMD A4-3400 ?
Motherboard: Gigabyte Technology Co., Ltd. GA-A75M-UD2H/GA-A75M-UD2H, BIOS F5 11/03/2011 CPU: AMD A4-3400 APU with Radeon(tm) HD Graphics (fam: 12, model: 01, stepping: 00)
| What | Removed | Added |
|---|---|---|
| Summary | [r600][r600] GPU lockup CP stall (kernel 3.8, 3.9) | [r600][r600] GPU lockup CP stall (kernel 3.2.47,3.4,3.8, 3.9) |
probably duplicate https://bugs.freedesktop.org/show_bug.cgi?id=56081 and almost the same issue http://www.mail-archive.com/dri-devel@lists.freedesktop.org/msg40024.html On my system with tree from http://cgit.freedesktop.org/~agd5f/linux/log/?h=drm-next-3.11-wip-4 GPU lockup still present (tested on X11 and Wayland)
Try comparing the following registers between fglrx and radeon: 0x98FC 0x98F8 0x8950 0x98F4 0x3F88 0x9B7C 0x3F90 0x9148 0x3F94 0x914C 0x8954 0x2004 0x2008 0x2768 0x8B24 0xA008 0xA020 0xA02C 0x9100 0x913C 0x960c 0x9610 0x88C4 You can use radeonreg (as root): ./radeonreg regmatch 0x98FC See if changing any of them to what fglrx programs before starting X with tiling disabled.
| What | Removed | Added |
|---|---|---|
| Summary | [r600][r600] GPU lockup CP stall (kernel 3.2.47,3.4,3.8, 3.9) | [r600] SUMO2 GPU lockup CP stall (kernel 3.2.47,3.4,3.8, 3.9, 3.10) |
It doesn't help :/ xorg.conf ColorTilling "false" ColorTilling2D "false" Maybe I'm doing something wrong? modprobe fglrx radeonreg reg radeon > fglrx_reg_dump_console.log start x radeonreg reg radeon > fglrx_reg_dump_x11.log restart computer modprobe radeon radeonreg reg radeon > radeon_reg_dump_console.log ./diff_and_select select_registers.txt > selected_registers.txt #script that generate diff and select only registers from comment#13 ./set_registers selected_registers.txt #script read selected_registers.txt and execute radeonreg regset "register" "register_value"
diff between registers from comment#13 before startx diff fglrx_registers_c.log radeon_registers_c.log 2c2 < 0x98F8 0x00000000 (0) --- > 0x98F8 0x02010002 (33619970) 7,8c7,8 < 0x3F90 0xffff0000 (-65536) < 0x9148 0xffff0000 (-65536) --- > 0x3F90 0x00000000 (0) > 0x9148 0x00000000 (0) 15,17c15,17 < 0x8B24 0x00000000 (0) < 0xA008 0x00030000 (196608) < 0xA020 0x00158011 (1409041) --- > 0x8B24 0x00ff0fff (16715775) > 0xA008 0x00010000 (65536) > 0xA020 0x00020009 (131081) 20,21c20,21 < 0x913C 0x01000000 (16777216) < 0x960c 0x76543210 (1985229328) --- > 0x913C 0x00000004 (4) > 0x960c 0x54763210 (1417032208) 23c23 < 0x88C4 0x00000000 (0) --- > 0x88C4 0x000000c1 (193)
Hi, there. I don't absolutely sure I've got the same issue, but at least, my problem is very close to one reported here. System: 00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Sumo [Radeon HD 6480G] xorg-server-1.14.2-alt1 xorg-drv-radeon-7.1.0-alt2 Linux 3.9.10-std-def-alt1 I'm asking you to test the following thing, please: try to modprobe radeon vramlimit=32 On my system it helps, but only a little: the X screen doesn't freeze, just highly corrupted. And VTs could be switched. The vramlimit=16 option works the same way, but any other value I've tried -- 64, 128 --- doesn't! Does it mean something we can use to trace down this bug?
Created attachment 82523 [details]
dmesg output, vramlimit=16, Xorg started
Attached the dmesg | grep 'radeon' after modprobe radeon vramlimit=16 and Xorg
start (kdm).
Created attachment 82524 [details]
dmesg output, vramlimit=32, Xorg started
Attached the dmesg | grep 'radeon' after modprobe radeon vramlimit=32 and Xorg
start (kdm).
Created attachment 82525 [details]
dmesg output, vramlimit=128, Xorg started
Attached the dmesg | grep 'radeon' after modprobe radeon vramlimit=128 and Xorg
start (kdm).
It freezes as with no vramlimit option. Used ...; sleep 10; dmesg | grep
'radeon' >file to catch the output.
yeah :) with vramlimit=16 xeyes works perfect :). KDM (4.10.5) is working (without artifacts). kernel-3.11-rc1 from(http://cgit.freedesktop.org/~agd5f/linux/log/?h=drm-fixes-3.11) I'll do more tests later
That just disables the use of vram for exa pixmaps. You can accomplish the same thing by adding: Option "EXAPixmaps" "false" to the device section of your xorg.conf
(In reply to comment #21) > That just disables the use of vram for exa pixmaps. You can accomplish the > same thing by adding: > Option "EXAPixmaps" "false" > to the device section of your xorg.conf Yes, the option helps a little: I can see the KDM screen without any artifacts. However, it is dead, i.e. frozen. Feels like a GPU lockup, but no error messages in Xorg log or dmesg. How can I get more info?