https://bugs.freedesktop.org/show_bug.cgi?id=53122
Bug #: 53122
Summary: X lockups /
Classification: Unclassified
Product: DRI
Version: XOrg CVS
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: 201208bugzillaz(a)moo.uklinux.net
Created attachment 65122
--> https://bugs.freedesktop.org/attachment.cgi?id=65122
X log file
Upon swapping video cards, I have started getting intermittent freezes of X
on my Slackware65 13.37 AMD Opteron box (kernel 3.4.4)
The display freezes up totally, including mouse pointer; occasionally there are
short (eg ~10s) freezes which might be related, and usually it happens when
web browsing (mostly when there is embedded flash on the bbc.co.uk olympics
pages)
I hope the below is sufficient info; I need to swap video cards back because I
can't afford such lockups ATM.
Here's the lspci lines:
0a:00.0 VGA compatible controller: ATI Technologies Inc RV710 [Radeon HD 4550]
(prog-if 00 [VGA controller])
Subsystem: Giga-byte Technology Device 21ae
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 74
Region 0: Memory at d0000000 (64-bit, prefetchable) [size=256M]
Region 2: Memory at f0500000 (64-bit, non-prefetchable) [size=64K]
Region 4: I/O ports at 4000 [size=256]
[virtual] Expansion ROM at f0520000 [disabled] [size=128K]
Capabilities: <access denied>
Kernel driver in use: radeon
Kernel modules: radeon
This appears in /var/log/messages (if I wait 20+mins, it seems to unfreeze
fairly reliably)
Aug 3 17:28:11 fishpond acpid: client 2126[0:0] has disconnected
Aug 3 17:28:11 fishpond acpid: client connected from 2126[0:0]
Aug 3 17:28:11 fishpond acpid: 1 client rule loaded
Aug 3 17:48:19 fishpond kernel: [68040.346054] X D
ffffffff816065c0 0 2111 2098 0x00400004
Aug 3 17:50:19 fishpond kernel: [68160.346048] X D
ffffffff816065c0 0 2111 2098 0x00400004
Aug 3 17:52:19 fishpond kernel: [68280.346054] X D
ffffffff816065c0 0 2111 2098 0x00400004
Aug 3 17:54:19 fishpond kernel: [68400.346054] X D
ffffffff816065c0 0 2111 2098 0x00400004
Aug 3 17:56:19 fishpond kernel: [68520.346048] X D
ffffffff816065c0 0 2111 2098 0x00400004
Aug 3 17:58:19 fishpond kernel: [68640.346053] X D
ffffffff816065c0 0 2111 2098 0x00400004
Aug 3 18:00:19 fishpond kernel: [68760.346054] X D
ffffffff816065c0 0 2111 2098 0x00400004
Aug 3 18:02:19 fishpond kernel: [68880.346047] X D
ffffffff816065c0 0 2111 2098 0x00400004
Aug 3 18:04:19 fishpond kernel: [69000.346052] X D
ffffffff816065c0 0 2111 2098 0x00400004
Aug 3 18:06:19 fishpond kernel: [69120.346052] X D
ffffffff816065c0 0 2111 2098 0x00400004
And instances of this in /var/log/syslog
[69120.346044] INFO: task X:2111 blocked for more than 120 seconds.
[69120.346049] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.
[69120.346052] X D ffffffff816065c0 0 2111 2098 0x00400004
[69120.346058] ffff8801743d9b58 0000000000000082 ffff8801743d9ae8
0000000000011dc0
[69120.346062] 0000000000011dc0 ffff880179dd06d0 0000000000011dc0
ffff8801743d9fd8
[69120.346066] ffff8801743d8000 0000000000011dc0 ffff8801743d9fd8
0000000000011dc0
[69120.346071] Call Trace:
[69120.346083] [<ffffffff81562859>] schedule+0x29/0x70
[69120.346087] [<ffffffff81562ade>] schedule_preempt_disabled+0xe/0x10
[69120.346091] [<ffffffff815613b9>] __mutex_lock_slowpath+0xd9/0x150
[69120.346095] [<ffffffff815610fb>] mutex_lock+0x2b/0x50
[69120.346125] [<ffffffffa0222820>] radeon_bo_create+0x150/0x2a0 [radeon]
[69120.346141] [<ffffffffa0233e6a>] radeon_gem_object_create+0x5a/0x100
[radeon]
[69120.346155] [<ffffffffa0234254>] radeon_gem_create_ioctl+0x54/0xe0 [radeon]
[69120.346160] [<ffffffff815610ee>] ? mutex_lock+0x1e/0x50
[69120.346174] [<ffffffffa023470c>] ? radeon_gem_get_tiling_ioctl+0xbc/0xf0
[radeon]
[69120.346189] [<ffffffffa013405f>] drm_ioctl+0x2cf/0x520 [drm]
[69120.346204] [<ffffffffa0234200>] ? radeon_gem_pwrite_ioctl+0x30/0x30
[radeon]
[69120.346210] [<ffffffff81142ad7>] do_vfs_ioctl+0x97/0x540
[69120.346213] [<ffffffff81143011>] sys_ioctl+0x91/0xa0
[69120.346217] [<ffffffff815640d2>] system_call_fastpath+0x16/0x1b
There is no error logged by X, but here its (but note that I run 6
simultaneaous X's on vt7-vt12). I've attached a log file
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=52467
Bug #: 52467
Summary: Radeon HD6450 KMS garbled screen on boot.
Classification: Unclassified
Product: DRI
Version: XOrg CVS
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: sowadski(a)miner.mst.edu
Just recently upgraded to a Radeon HD6450. Upon boot, as soon as fbcon takes
over, the screen gets corrupted. (note X is not started on boot). SSHing into
the box and starting and restarting X a couple time sometimes fixes the issue,
sometimes locks of the machine.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=52345
Bug #: 52345
Summary: KMS Power Management have no effect
Classification: Unclassified
Product: DRI
Version: XOrg CVS
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: d2xdt2(a)gmail.com
Using
OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD SUMO2
OpenGL version string: 2.1 Mesa 8.0.3
OpenGL shading language version string: 1.20
AMD A4-3400 APU with Radeon(tm) HD Graphics
Fedora 17 64bit
Linux amd 3.4.5-2.fc17.x86_64 #1 SMP Mon Jul 16 20:52:08 UTC 2012 x86_64 x86_64
x86_64 GNU/Linux
According to
http://wiki.x.org/wiki/RadeonFeature
should
echo profile > /sys/class/drm/card0/device/power_method
echo high > /sys/class/drm/card0/device/power_profile
put the GPU in high performance mode and
echo profile > /sys/class/drm/card0/device/power_method
echo low > /sys/class/drm/card0/device/power_profile
in low performance mode.
glxgears gives 60 FPS in both cases, which leads me to beleive that power
management does work.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=51190
Bug #: 51190
Summary: [RADEON:KMS:RV370:RESUME] garbage on screen (console
or X) after suspend-resume with radeon (KMS only)
Classification: Unclassified
Product: DRI
Version: unspecified
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: cyberbat(a)lavabit.com
Created attachment 63153
--> https://bugs.freedesktop.org/attachment.cgi?id=63153
full kernel 3.5rc2 log
Screen on my Samsung R50 notebook with AMD Mobility Radeon X300 (RV370 chipset)
become completely unusable after resume (watch screenshots). I've tested
different kernels from 2.6.32 till 3.5rc2. Just the same thing. The thing
happens only with KMS turned on. I have tried suspend from X (Xfce) and from
console (using pm-suspend).
I repeatedly get following errors in kernel log after resume:
Jun 15 18:56:39 localhost kernel: radeon 0000:01:00.0: GPU lockup CP stall for
more than 10000msec
Jun 15 18:56:39 localhost kernel: radeon 0000:01:00.0: GPU lockup (waiting for
0x000000000000023d last fence id 0x000000000000023c)
Jun 15 18:56:39 localhost kernel: Failed to wait GUI idle while programming
pipes. Bad things might happen.
Jun 15 18:56:39 localhost kernel: radeon 0000:01:00.0: (r300_asic_reset:392)
RBBM_STATUS=0x80010140
Jun 15 18:56:39 localhost kernel: radeon 0000:01:00.0: (r300_asic_reset:411)
RBBM_STATUS=0x80010140
Jun 15 18:56:39 localhost kernel: radeon 0000:01:00.0: (r300_asic_reset:423)
RBBM_STATUS=0x00000140
Jun 15 18:56:39 localhost kernel: radeon 0000:01:00.0: GPU reset succeed
Jun 15 18:56:39 localhost kernel: radeon 0000:01:00.0: GPU reset succeed
Jun 15 18:56:39 localhost kernel: radeon 0000:01:00.0: f5eaf400 unpin not
necessary
Jun 15 18:56:39 localhost kernel: [drm] radeon: 1 quad pipes, 1 Z pipes
initialized.
Jun 15 18:56:39 localhost kernel: [drm] PCIE GART of 512M enabled (table at
0x00000000D0040000).
Jun 15 18:56:39 localhost kernel: radeon 0000:01:00.0: WB enabled
Jun 15 18:56:39 localhost kernel: radeon 0000:01:00.0: fence driver on ring 0
use gpu addr 0x00000000b0000000 and cpu addr 0xff8de000
Jun 15 18:56:39 localhost kernel: [drm] radeon: ring at 0x00000000B0001000
Jun 15 18:56:39 localhost kernel: [drm] ring test succeeded in 1 usecs
Jun 15 18:56:39 localhost kernel: [drm] ib test succeeded in 0 usecs
...
Jun 15 18:58:32 localhost kernel: radeon 0000:01:00.0: GPU lockup CP stall for
more than 10000msec
Jun 15 18:58:32 localhost kernel: radeon 0000:01:00.0: GPU lockup (waiting for
0x0000000000000490 last fence id 0x000000000000033b)
Jun 15 18:58:32 localhost kernel: Failed to wait GUI idle while programming
pipes. Bad things might happen.
Jun 15 18:58:32 localhost kernel: radeon 0000:01:00.0: (r300_asic_reset:392)
RBBM_STATUS=0x80010140
Jun 15 18:58:32 localhost kernel: radeon 0000:01:00.0: (r300_asic_reset:411)
RBBM_STATUS=0x80010140
Jun 15 18:58:32 localhost kernel: radeon 0000:01:00.0: (r300_asic_reset:423)
RBBM_STATUS=0x00000140
Jun 15 18:58:32 localhost kernel: radeon 0000:01:00.0: GPU reset succeed
Jun 15 18:58:32 localhost kernel: radeon 0000:01:00.0: GPU reset succeed
Jun 15 18:58:32 localhost kernel: radeon 0000:01:00.0: f5eaf400 unpin not
necessary
Jun 15 18:58:32 localhost kernel: [drm] radeon: 1 quad pipes, 1 Z pipes
initialized.
Jun 15 18:58:32 localhost kernel: [drm] PCIE GART of 512M enabled (table at
0x00000000D0040000).
Jun 15 18:58:32 localhost kernel: radeon 0000:01:00.0: WB enabled
Jun 15 18:58:32 localhost kernel: radeon 0000:01:00.0: fence driver on ring 0
use gpu addr 0x00000000b0000000 and cpu addr 0xff8de000
Jun 15 18:58:32 localhost kernel: [drm] radeon: ring at 0x00000000B0001000
Jun 15 18:58:32 localhost kernel: [drm] ring test succeeded in 1 usecs
Jun 15 18:58:32 localhost kernel: [drm] ib test succeeded in 0 usecs
Jun 15 19:00:46 localhost /usr/sbin/gpm[1110]: *** info
[daemon/processrequest.c(42)]:
Jun 15 19:00:46 localhost /usr/sbin/gpm[1110]: Request on 6 (console 1)
Jun 15 19:01:42 localhost kernel: radeon 0000:01:00.0: GPU lockup CP stall for
more than 200579msec
Jun 15 19:01:42 localhost kernel: radeon 0000:01:00.0: GPU lockup (waiting for
0x000000000000058f)
Jun 15 19:01:42 localhost kernel: radeon 0000:01:00.0: failed to get a new IB
(-35)
Jun 15 19:01:42 localhost kernel: [drm:radeon_cs_ib_chunk] *ERROR* Failed to
get ib !
Jun 15 19:01:42 localhost kernel: Failed to wait GUI idle while programming
pipes. Bad things might happen.
Jun 15 19:01:42 localhost kernel: radeon 0000:01:00.0: (r300_asic_reset:392)
RBBM_STATUS=0x80010140
Jun 15 19:01:42 localhost kernel: radeon 0000:01:00.0: (r300_asic_reset:411)
RBBM_STATUS=0x80010140
Jun 15 19:01:42 localhost kernel: radeon 0000:01:00.0: (r300_asic_reset:423)
RBBM_STATUS=0x00000140
Jun 15 19:01:42 localhost kernel: radeon 0000:01:00.0: GPU reset succeed
Jun 15 19:01:42 localhost kernel: radeon 0000:01:00.0: GPU reset succeed
I recognize that I have really old notebook, but It has enough power for my
tasks so it will be good to use KMS on it cause I loose a lot of features of X
without it.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=50805
Bug #: 50805
Summary: radeon gpu driver bug on suspend/resume in 3.5-rc1
Classification: Unclassified
Product: DRI
Version: unspecified
Platform: Other
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: austin.lund(a)gmail.com
Created attachment 62685
--> https://bugs.freedesktop.org/attachment.cgi?id=62685
two samples of the kernel log
I get the attached traces with 3.5-rc1 after suspend/resume,
sometimes. It doesn't always happen. Usually happens at least once
in 10 suspend/resume cycles. The first trace seems non fatal, but the
system locks up in the second one and needs to be rebooted.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=49943
Bug #: 49943
Summary: radeon/drm: Hotplug udev events stop working
Classification: Unclassified
Product: DRI
Version: XOrg CVS
Platform: All
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: h.judt(a)gmx.at
Making use of udev events, I'd like to launch a script when a monitor gets
connected or disconnected. However, an event is only fired once and then never
again.
Kernel: linux-3.4.0-rc7
lspci:
01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Cayman
PRO [Radeon HD 6950] (prog-if 00 [VGA controller])
Subsystem: Advanced Micro Devices [AMD] nee ATI Device 0b00
Flags: bus master, fast devsel, latency 0, IRQ 54
Memory at c0000000 (64-bit, prefetchable) [size=256M]
Memory at fe620000 (64-bit, non-prefetchable) [size=128K]
I/O ports at e000 [size=256]
Expansion ROM at fe600000 [disabled] [size=128K]
Capabilities: [50] Power Management version 3
Capabilities: [58] Express Legacy Endpoint, MSI 00
Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010
<?>
Capabilities: [150] Advanced Error Reporting
Kernel driver in use: radeon
xrandr --verbose:
HDMI-0 connected (normal left inverted right x axis y axis)
Identifier: 0x58
Timestamp: 21810
Subpixel: horizontal rgb
Clones:
CRTCs: 0 1 2 3 4 5
Transform: 1.000000 0.000000 0.000000
0.000000 1.000000 0.000000
0.000000 0.000000 1.000000
filter:
EDID:
00ffffffffffff002203010be9030000
00110103804627780b1990a755469824
10494b3fcf00818081cf81c061c04bc0
4bcf453c61cf011d007251d01e206e28
5500c48e2100001e011d8018711c1620
582c2500c48e2100009e000000fc004d
737461722044656d6f0a2020000000fd
0016500e5b10000a202020202020014b
02031df24a0102038405101293141f23
0907078301000065030c0010008c0ad0
8a20e02d10103e9600138e2100001801
1d00bc52d01e20b8285540c48e210000
1e011d80d0721c1620102c2580c48e21
00009e8c0ad08a20e02d10103e9600c4
8e210000188c0ad090204031200c4055
00c48e2100001800000000000000002b
underscan vborder: 0 (0x00000000) range: (0,128)
underscan hborder: 0 (0x00000000) range: (0,128)
underscan: off
supported: off on auto
coherent: 1 (0x00000001) range: (0,1)
----- [modes cut off here] -----
ls -la /sys/class/drm/card0-HDMI-A-1/
insgesamt 0
drwxr-xr-x 3 root root 0 15. Mai 2012 .
drwxr-xr-x 8 root root 0 15. Mai 2012 ..
lrwxrwxrwx 1 root root 0 15. Mai 10:12 device -> ../../card0
-r--r--r-- 1 root root 4096 15. Mai 10:12 dpms
-r--r--r-- 1 root root 0 15. Mai 10:12 edid
-r--r--r-- 1 root root 4096 15. Mai 10:12 enabled
-r--r--r-- 1 root root 4096 15. Mai 10:12 modes
drwxr-xr-x 2 root root 0 15. Mai 10:12 power
-r--r--r-- 1 root root 4096 15. Mai 09:14 status
lrwxrwxrwx 1 root root 0 15. Mai 2012 subsystem ->
../../../../../../../class/drm
-rw-r--r-- 1 root root 4096 15. Mai 2012 uevent
Note the modification date of status and the other files. That of status did
not change at all since boot, and the mdates of the others did change once
apparently.
I can poll "status" and see the changes when executing xrandr, but there will
be no more events, and the modification dates do not change anymore.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=49322
Bug #: 49322
Summary: No picture on display connected via Displayport
adaptor to HD 7870
Classification: Unclassified
Product: DRI
Version: XOrg CVS
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: briancschott(a)gmail.com
Created attachment 60820
--> https://bugs.freedesktop.org/attachment.cgi?id=60820
dmesg output
Radeon HD 7870
mesa 8.0.2
Kernel 3.4-rc5
X.Org X Server 1.12.0
xf86-video-modesetting 0.2.0
* Monitor is a DVI monitor connected to an active mini-displayport to DVI
adaptor.
* Output to all three screens functions in Windows.
* dmesg output and xrandr output are able to see the display and print out the
correct supported resolutions
* HDMI and DVI output are functioning correctly on the card.
* Using xrandr I'm able to get the X server to think that the display is
present and functioning. (I can place windows and the cursor on the screen)
* The display is in power-saving mode from the moment that the framebuffer
console initializes. I'm not able to get any image on it.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.