[Bug 94877] Radeon 7500: GPU lockup after starting Xorg

2019-11-18 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=94877

Martin Peres  changed:

   What|Removed |Added

 Resolution|--- |MOVED
 Status|NEW |RESOLVED

--- Comment #14 from Martin Peres  ---
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been
closed from further activity.

You can subscribe and participate further through the new bug through this link
to our GitLab instance:
https://gitlab.freedesktop.org/xorg/driver/xf86-video-ati/issues/157.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
https://lists.x.org/mailman/listinfo/xorg-driver-ati

[Bug 94877] Radeon 7500: GPU lockup after starting Xorg

2016-10-10 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=94877

erhar...@mailbox.org changed:

   What|Removed |Added

Version|unspecified |7.7 (2012.06)

--- Comment #13 from erhar...@mailbox.org ---
Now as my problem in Bug 97987 is solved I am facing this bug with the radeon
driver. I use a r300 card, but the error messages are very similar so I decided
not to open a new bug. Unlike the original bug report I am running a current
4.8.1-kernel, xorg-server-1.18.4, xf86-video-ati-7.7.1 and mesa-12.0.3.

Having said that Bug 95017, Bug 91893, Bug 96519 look seem very similar.

Sometimes the GPU can reset itself, most of the time I get a hard lock. If I
use "radeon-agpmode=-1" as kernel parameter, X on my G5 holds out longer, but
sooner or later I get a hard lock too.

dmesg-output:
[  774.360780] radeon :f0:10.0: ring 0 stalled for more than 10443msec
[  774.360790] radeon :f0:10.0: GPU lockup (current fence id
0x0407 last fence id 0x040e on ring 0)
[  774.511407] Failed to wait GUI idle while programming pipes. Bad things
might happen.
[  774.512511] radeon :f0:10.0: Saved 251 dwords of commands on ring 0.
[  774.512530] radeon :f0:10.0: (r300_asic_reset:425)
RBBM_STATUS=0x80010140
[  775.012522] radeon :f0:10.0: (r300_asic_reset:444)
RBBM_STATUS=0x80010140
[  775.508519] radeon :f0:10.0: (r300_asic_reset:456)
RBBM_STATUS=0x0140
[  775.508551] radeon :f0:10.0: GPU reset succeed
[  775.508556] radeon :f0:10.0: GPU reset succeeded, trying to resume
[  775.508593] [drm] radeon: 1 quad pipes, 1 Z pipes initialized.
[  775.508601] radeon :f0:10.0: WB disabled
[  775.508607] radeon :f0:10.0: fence driver on ring 0 use gpu addr
0x and cpu addr 0xd139d000
[  775.508699] [drm] radeon: ring at 0x1000
[  775.508769] [drm] ring test succeeded in 0 usecs
[  775.559042] [drm] ib test succeeded in 0 usecs

What I also got is some interesting output in Xorg.0.log via sshd from another
machine. Maybe this is of some help:

(EE) [mi] EQ overflowing.  Additional events will be discarded until existing
events are processed.
(EE) 
(EE) Backtrace:
(EE) 0: /usr/bin/X (xorg_backtrace+0x6c) [0x101db7fc]
(EE) 1: /usr/bin/X (mieqEnqueue+0x2d0) [0x101b8eb0]
(EE) 2: /usr/bin/X (QueuePointerEvents+0x94) [0x10053254]
(EE) 3: /usr/bin/X (xf86PostMotionEventM+0x2dc) [0x10097adc]
(EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xcf6c000+0x4dd0) [0xcf70dd0]
(EE) 5: /usr/lib/xorg/modules/input/evdev_drv.so (0xcf6c000+0x56ac) [0xcf716ac]
(EE) 6: /usr/lib/xorg/modules/input/evdev_drv.so (0xcf6c000+0x5960) [0xcf71960]
(EE) 7: /usr/bin/X (0x1000+0x848cc) [0x100848cc]
(EE) 8: /usr/bin/X (0x1000+0xb3328) [0x100b3328]
(EE) 9: linux-vdso32.so.1 (__kernel_sigtramp32+0x0) [0x1003f4]
(EE) 10: /lib/libc.so.6 (ioctl+0xe8) [0xf9478d8]
(EE) 11: ?? [0x5b]
(EE) 12: /usr/lib/libdrm.so.2 (drmIoctl+0x54) [0xfd15484]
(EE) 13: /usr/lib/libdrm.so.2 (drmCommandWrite+0x38) [0xfd19618]
(EE) 14: /usr/lib/libdrm_radeon.so.1 (0xee9d000+0x17d8) [0xee9e7d8]
(EE) 15: /usr/lib/libdrm_radeon.so.1 (0xee9d000+0x1a98) [0xee9ea98]
(EE) 16: /usr/lib/libdrm_radeon.so.1 (radeon_bo_map+0x20) [0xeea06f0]
(EE) 17: /usr/lib/xorg/modules/drivers/radeon_drv.so (0xeece000+0x2e1e4)
[0xeefc1e4]
(EE) 18: /usr/lib/xorg/modules/libexa.so (0xed68000+0x6130) [0xed6e130]
(EE) 19: /usr/lib/xorg/modules/libexa.so (0xed68000+0x8fd8) [0xed70fd8]
(EE) 20: /usr/lib/xorg/modules/libexa.so (0xed68000+0x137d0) [0xed7b7d0]
(EE) 21: /usr/lib/xorg/modules/libexa.so (0xed68000+0x10024) [0xed78024]
(EE) 22: /usr/bin/X (0x1000+0x14fac8) [0x1014fac8]
(EE) 23: /usr/bin/X (CompositePicture+0x294) [0x1013c3f4]
(EE) 24: /usr/lib/xorg/modules/libexa.so (0xed68000+0x10ef0) [0xed78ef0]
(EE) 25: /usr/bin/X (CompositeTrapezoids+0xb8) [0x1013c6b8]
(EE) 26: /usr/bin/X (0x1000+0x143330) [0x10143330]
(EE) 27: /usr/bin/X (0x1000+0x13cb34) [0x1013cb34]
(EE) 28: /usr/bin/X (0x1000+0x340cc) [0x100340cc]
(EE) 29: /usr/bin/X (0x1000+0x38cac) [0x10038cac]
(EE) 30: /usr/bin/X (0x1000+0x1e304) [0x1001e304]
(EE) 31: /lib/libc.so.6 (0xf855000+0x21414) [0xf876414]
(EE) 32: /lib/libc.so.6 (__libc_start_main+0xc0) [0xf8765d0]
(EE) 
(EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up
the stack.
(EE) [mi] mieq is *NOT* the cause.  It is a victim.
[   775.542] [mi] Increasing EQ size to 1024 to prevent dropped events.
[   775.544] [mi] EQ processing has resumed after 85 dropped events.
[   775.544] [mi] This may be caused by a misbehaving driver monopolizing the
server's resources.

If requested I can add full kernel config, Xorg.0.log and dmesg output. Or open
a new bug if more appropriate.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
xorg-driver-ati mailing list

[Bug 94877] Radeon 7500: GPU lockup after starting Xorg

2016-04-16 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=94877

--- Comment #12 from ma...@hotmail.com ---
I have discovered that running

  Option "NoAccel" "True"

in xorg.conf "fixes" the problem, however I don't consider unaccelerated
graphics an acceptable solution.

Does this in any way help narrow down where the real problem is?

-- 
You are receiving this mail because:
You are the assignee for the bug.___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
https://lists.x.org/mailman/listinfo/xorg-driver-ati


[Bug 94877] Radeon 7500: GPU lockup after starting Xorg

2016-04-10 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=94877

--- Comment #11 from ma...@hotmail.com ---
In this example, I discovered that moving the mouse triggers the "Saved ...
dwords of commands" sequence, which otherwise occurrs every 30 seconds or so:


(start xorg)
(open a window e.g. terminal and maximise it)
(open another window e.g. file manager and drag it around in front of the
maximised window for a few seconds)
(screen freezes with "tracers" of the last few frames of the moving window
visible)
(exception information appears in Xorg.0.log similar to "Full Xorg.0.log
(radeon.agpmode=-1)" attachment)
(the following kernel messages start appearing)
Apr 10 15:35:11 [kernel] radeon :00:10.0: ring 0 stalled for more than
1msec
Apr 10 15:35:11 [kernel] radeon :00:10.0: GPU lockup (current fence id
0x2633 last fence id 0x2635 on ring 0)
Apr 10 15:35:12 [kernel] radeon :00:10.0: ring 0 stalled for more than
10500msec
Apr 10 15:35:12 [kernel] radeon :00:10.0: GPU lockup (current fence id
0x2633 last fence id 0x2635 on ring 0)
Apr 10 15:35:12 [kernel] radeon :00:10.0: ring 0 stalled for more than
11000msec
Apr 10 15:35:12 [kernel] radeon :00:10.0: GPU lockup (current fence id
0x2633 last fence id 0x2635 on ring 0)
Apr 10 15:35:13 [kernel] radeon :00:10.0: ring 0 stalled for more than
11500msec
Apr 10 15:35:13 [kernel] radeon :00:10.0: GPU lockup (current fence id
0x2633 last fence id 0x2635 on ring 0)
Apr 10 15:35:13 [kernel] radeon :00:10.0: ring 0 stalled for more than
12000msec
Apr 10 15:35:13 [kernel] radeon :00:10.0: GPU lockup (current fence id
0x2633 last fence id 0x2635 on ring 0)
Apr 10 15:35:14 [kernel] radeon :00:10.0: ring 0 stalled for more than
12500msec
Apr 10 15:35:14 [kernel] radeon :00:10.0: GPU lockup (current fence id
0x2633 last fence id 0x2635 on ring 0)
Apr 10 15:35:14 [kernel] radeon :00:10.0: ring 0 stalled for more than
13000msec
Apr 10 15:35:14 [kernel] radeon :00:10.0: GPU lockup (current fence id
0x2633 last fence id 0x2635 on ring 0)
Apr 10 15:35:15 [kernel] radeon :00:10.0: ring 0 stalled for more than
13500msec
Apr 10 15:35:15 [kernel] radeon :00:10.0: GPU lockup (current fence id
0x2633 last fence id 0x2635 on ring 0)
Apr 10 15:35:15 [kernel] radeon :00:10.0: ring 0 stalled for more than
14000msec
Apr 10 15:35:15 [kernel] radeon :00:10.0: GPU lockup (current fence id
0x2633 last fence id 0x2635 on ring 0)
Apr 10 15:35:16 [kernel] radeon :00:10.0: ring 0 stalled for more than
14500msec
Apr 10 15:35:16 [kernel] radeon :00:10.0: GPU lockup (current fence id
0x2633 last fence id 0x2635 on ring 0)
Apr 10 15:35:16 [kernel] radeon :00:10.0: ring 0 stalled for more than
15000msec
Apr 10 15:35:16 [kernel] radeon :00:10.0: GPU lockup (current fence id
0x2633 last fence id 0x2635 on ring 0)
Apr 10 15:35:17 [kernel] radeon :00:10.0: ring 0 stalled for more than
15500msec
Apr 10 15:35:17 [kernel] radeon :00:10.0: GPU lockup (current fence id
0x2633 last fence id 0x2635 on ring 0)
Apr 10 15:35:17 [kernel] radeon :00:10.0: ring 0 stalled for more than
16000msec
Apr 10 15:35:17 [kernel] radeon :00:10.0: GPU lockup (current fence id
0x2633 last fence id 0x2635 on ring 0)
Apr 10 15:35:18 [kernel] radeon :00:10.0: ring 0 stalled for more than
16500msec
Apr 10 15:35:18 [kernel] radeon :00:10.0: GPU lockup (current fence id
0x2633 last fence id 0x2635 on ring 0)
Apr 10 15:35:18 [kernel] radeon :00:10.0: ring 0 stalled for more than
17000msec
Apr 10 15:35:18 [kernel] radeon :00:10.0: GPU lockup (current fence id
0x2633 last fence id 0x2635 on ring 0)
Apr 10 15:35:19 [kernel] radeon :00:10.0: ring 0 stalled for more than
17500msec
Apr 10 15:35:19 [kernel] radeon :00:10.0: GPU lockup (current fence id
0x2633 last fence id 0x2635 on ring 0)
Apr 10 15:35:19 [kernel] radeon :00:10.0: ring 0 stalled for more than
18000msec
Apr 10 15:35:19 [kernel] radeon :00:10.0: GPU lockup (current fence id
0x2633 last fence id 0x2635 on ring 0)
Apr 10 15:35:20 [kernel] radeon :00:10.0: ring 0 stalled for more than
18500msec
Apr 10 15:35:20 [kernel] radeon :00:10.0: GPU lockup (current fence id
0x2633 last fence id 0x2635 on ring 0)
Apr 10 15:35:20 [kernel] radeon :00:10.0: ring 0 stalled for more than
19000msec
Apr 10 15:35:20 [kernel] radeon :00:10.0: GPU lockup (current fence id
0x2633 last fence id 0x2635 on ring 0)
Apr 10 15:35:21 [kernel] radeon :00:10.0: ring 0 stalled for more than
19500msec
Apr 10 15:35:21 

[Bug 94877] Radeon 7500: GPU lockup after starting Xorg

2016-04-10 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=94877

--- Comment #3 from ma...@hotmail.com ---
Example 1: Drag a window

(start xorg)
(open a window and drag it, contents displayed while dragging)
(window drags a few centimeters, but very slowly)
(screen freezes, contents still shown)
Apr 09 18:23:04 [kernel] radeon :00:10.0: ring 0 stalled for more than
1msec
Apr 09 18:23:04 [kernel] radeon :00:10.0: GPU lockup (current fence id
0x00ff last fence id 0x0100 on ring 0)
Apr 09 18:23:05 [kernel] radeon: wait for empty RBBM fifo failed ! Bad things
might happen.
Apr 09 18:23:05 [kernel] Failed to wait GUI idle while programming pipes. Bad
things might happen.
Apr 09 18:23:07 [kernel] radeon :00:10.0: Saved 27 dwords of commands on
ring 0.
Apr 09 18:23:07 [kernel] radeon :00:10.0: (r100_asic_reset:2570)
RBBM_STATUS=0x8006C139
Apr 09 18:23:07 [kernel] radeon :00:10.0: (r100_asic_reset:2591)
RBBM_STATUS=0x8002C139
Apr 09 18:23:07 [kernel] radeon :00:10.0: (r100_asic_reset:2599)
RBBM_STATUS=0x8002C139
Apr 09 18:23:07 [kernel] radeon :00:10.0: GPU reset succeed
Apr 09 18:23:07 [kernel] radeon :00:10.0: GPU reset succeeded, trying to
resume
Apr 09 18:23:07 [kernel] radeon :00:10.0: (r100_asic_reset:2570)
RBBM_STATUS=0x8002C139
Apr 09 18:23:07 [kernel] radeon :00:10.0: (r100_asic_reset:2591)
RBBM_STATUS=0x8002C139
Apr 09 18:23:07 [kernel] radeon :00:10.0: (r100_asic_reset:2599)
RBBM_STATUS=0x8002C139
Apr 09 18:23:07 [kernel] radeon :00:10.0: GPU reset succeed
Apr 09 18:23:07 [kernel] radeon :00:10.0: WB disabled
Apr 09 18:23:07 [kernel] radeon :00:10.0: fence driver on ring 0 use gpu
addr 0x and cpu addr 0xf106b000
Apr 09 18:23:07 [kernel] radeon: wait for empty RBBM fifo failed ! Bad things
might happen.
Apr 09 18:23:07 [kernel] Failed to wait GUI idle while programming pipes. Bad
things might happen.
Apr 09 18:23:07 [kernel] [drm] radeon: ring at 0x1000
Apr 09 18:23:07 [kernel] [drm] ring test succeeded in 0 usecs
(screen flashes black for 1-2 seconds, then redisplays contents from the time
it froze)
Apr 09 18:23:18 [kernel] radeon :00:10.0: ring 0 stalled for more than
10492msec
Apr 09 18:23:18 [kernel] radeon :00:10.0: GPU lockup (current fence id
0x00ff last fence id 0x0101 on ring 0)
Apr 09 18:23:18 [kernel] [drm:r100_ib_test] *ERROR* radeon: fence wait failed
(-35).
Apr 09 18:23:18 [kernel] [drm:radeon_ib_ring_tests] *ERROR* radeon: failed
testing IB on GFX ring (-35).
Apr 09 18:23:18 [kernel] radeon: wait for empty RBBM fifo failed ! Bad things
might happen.
Apr 09 18:23:18 [kernel] Failed to wait GUI idle while programming pipes. Bad
things might happen.
Apr 09 18:23:20 [kernel] radeon :00:10.0: Saved 254043 dwords of commands
on ring 0.
Apr 09 18:23:20 [kernel] radeon :00:10.0: (r100_asic_reset:2570)
RBBM_STATUS=0x8002C135
Apr 09 18:23:20 [kernel] radeon :00:10.0: (r100_asic_reset:2591)
RBBM_STATUS=0x8002C135
Apr 09 18:23:20 [kernel] radeon :00:10.0: (r100_asic_reset:2599)
RBBM_STATUS=0x8002C135
Apr 09 18:23:20 [kernel] radeon :00:10.0: GPU reset succeed
Apr 09 18:23:20 [kernel] radeon :00:10.0: GPU reset succeeded, trying to
resume
Apr 09 18:23:20 [kernel] radeon :00:10.0: (r100_asic_reset:2570)
RBBM_STATUS=0x8002C135
Apr 09 18:23:20 [kernel] radeon :00:10.0: (r100_asic_reset:2591)
RBBM_STATUS=0x8002C135
Apr 09 18:23:20 [kernel] radeon :00:10.0: (r100_asic_reset:2599)
RBBM_STATUS=0x8002C135
Apr 09 18:23:20 [kernel] radeon :00:10.0: GPU reset succeed
Apr 09 18:23:20 [kernel] radeon :00:10.0: WB disabled
Apr 09 18:23:20 [kernel] radeon :00:10.0: fence driver on ring 0 use gpu
addr 0x and cpu addr 0xf106b000
Apr 09 18:23:20 [kernel] radeon: wait for empty RBBM fifo failed ! Bad things
might happen.
Apr 09 18:23:20 [kernel] Failed to wait GUI idle while programming pipes. Bad
things might happen.
Apr 09 18:23:20 [kernel] [drm] radeon: ring at 0x1000
Apr 09 18:23:20 [kernel] [drm] ring test succeeded in 0 usecs
(screen flashes black for 1-2 seconds, then redisplays contents from the time
it froze)
Apr 09 18:23:31 [kernel] radeon :00:10.0: ring 0 stalled for more than
10484msec
Apr 09 18:23:31 [kernel] radeon :00:10.0: GPU lockup (current fence id
0x00ff last fence id 0x0102 on ring 0)
Apr 09 18:23:31 [kernel] [drm:r100_ib_test] *ERROR* radeon: fence wait failed
(-35).
Apr 09 18:23:31 [kernel] [drm:radeon_ib_ring_tests] *ERROR* radeon: failed
testing IB on GFX ring (-35).
Apr 09 18:23:31 [kernel] radeon: wait for empty RBBM fifo failed ! Bad things
might happen.
Apr 09 18:23:31 [kernel] Failed to wait GUI idle while programming pipes. Bad
things might happen.
Apr 09 18:23:31 [kernel] radeon :00:10.0: Saved 245915 dwords of commands
on ring 0.
Apr 09 18:23:33 [kernel] radeon :00:10.0: (r100_asic_reset:2570)
RBBM_STATUS=0x8002C131
Apr 09 18:23:33 [kernel] 

[Bug 94877] Radeon 7500: GPU lockup after starting Xorg

2016-04-09 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=94877

--- Comment #10 from ma...@hotmail.com ---
(start xorg)
(open window with a scrollbar-scrollable region e.g. web browser)
(start scrolling using scrollbar)
(viewport scrolls a centimeter or two)
(screen freezes)
(exception information appears in Xorg.0.log, see "Full Xorg.0.log
(radeon.agpmode=-1)" attachment)
(the folowing kernel messages appear)
Apr 10 09:53:57 [kernel] radeon :00:10.0: ring 0 stalled for more than
1msec
Apr 10 09:53:57 [kernel] radeon :00:10.0: GPU lockup (current fence id
0x2424 last fence id 0x2425 on ring 0)
Apr 10 09:53:57 [kernel] radeon :00:10.0: Saved 27 dwords of commands on
ring 0.
Apr 10 09:53:57 [kernel] radeon :00:10.0: GPU reset succeeded, trying to
resume
Apr 10 09:53:57 [kernel] [drm] PCI GART of 512M enabled (table at
0x2EF0).
Apr 10 09:53:57 [kernel] radeon :00:10.0: WB disabled
Apr 10 09:53:57 [kernel] radeon :00:10.0: fence driver on ring 0 use gpu
addr 0x7800 and cpu addr 0xeeea8000
Apr 10 09:53:57 [kernel] [drm] radeon: ring at 0x78001000
Apr 10 09:53:57 [kernel] [drm:r100_ring_test] *ERROR* radeon: ring test failed
(scratch(0x15E8)=0xCAFEDEAD)
Apr 10 09:53:57 [kernel] [drm:r100_cp_init] *ERROR* radeon: cp isn't working
(-22).
Apr 10 09:53:57 [kernel] radeon :00:10.0: failed initializing CP (-22).
(previous block of error messages repeats every 1-2 seconds forever, each time
screen flashes black then redisplays frozen screen contents, machine stays
responsive over SSH)

-- 
You are receiving this mail because:
You are the assignee for the bug.___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
https://lists.x.org/mailman/listinfo/xorg-driver-ati


[Bug 94877] Radeon 7500: GPU lockup after starting Xorg

2016-04-09 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=94877

--- Comment #9 from ma...@hotmail.com ---
Hi Alex,

Disabling AGP (see attached dmesg and Xorg.0.log) improves the situation
somewhat.

The system seems to survive more gui interaction now, but still fails
consistently before long.  Examples below.

Prior to failing, screen updates seem accurate (in that there are no painting
glitches) but are disappointingly slow.  To be expected in PCI mode?

Thank you for your assistance, Alex.  I realise this obsolete hardware is
probably of little interest to you (or AMD), but it's a collectors' item to me
and means a lot so I really appreciate it.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
https://lists.x.org/mailman/listinfo/xorg-driver-ati


[Bug 94877] Radeon 7500: GPU lockup after starting Xorg

2016-04-09 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=94877

--- Comment #8 from ma...@hotmail.com ---
Created attachment 122842
  --> https://bugs.freedesktop.org/attachment.cgi?id=122842=edit
Full Xorg.0.log (radeon.agpmode=-1)

-- 
You are receiving this mail because:
You are the assignee for the bug.___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
https://lists.x.org/mailman/listinfo/xorg-driver-ati


[Bug 94877] Radeon 7500: GPU lockup after starting Xorg

2016-04-09 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=94877

--- Comment #7 from ma...@hotmail.com ---
Created attachment 122841
  --> https://bugs.freedesktop.org/attachment.cgi?id=122841=edit
Full dmesg (radeon.agpmode=-1)

-- 
You are receiving this mail because:
You are the assignee for the bug.___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
https://lists.x.org/mailman/listinfo/xorg-driver-ati


[Bug 94877] Radeon 7500: GPU lockup after starting Xorg

2016-04-09 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=94877

--- Comment #6 from Alex Deucher  ---
AGP is pretty problematic on Macs.  Does disabling AGP (append
radeon.agpmode=-1 to your kernel command line) help?

-- 
You are receiving this mail because:
You are the assignee for the bug.___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
https://lists.x.org/mailman/listinfo/xorg-driver-ati


[Bug 94877] Radeon 7500: GPU lockup after starting Xorg

2016-04-09 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=94877

--- Comment #5 from ma...@hotmail.com ---
Example 3: Popup menus

(start xorg)
(repeatedly open and close root right-click menu for 20-30 seconds)
(screen goes black)
Apr 09 18:19:10 [kernel] radeon :00:10.0: ring 0 stalled for more than
10212msec
Apr 09 18:19:10 [kernel] radeon :00:10.0: GPU lockup (current fence id
0x03e2 last fence id 0x03e4 on ring 0)
(previous two lines repeat forever, screen stays black, machine stays
accessible over SSH)

-- 
You are receiving this mail because:
You are the assignee for the bug.___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
https://lists.x.org/mailman/listinfo/xorg-driver-ati


[Bug 94877] Radeon 7500: GPU lockup after starting Xorg

2016-04-09 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=94877

--- Comment #4 from ma...@hotmail.com ---
Example 2: Desktop selection box

(start xorg)
(Click-drag on desktop, creating a shaded selection box)
(screen goes black)
Apr 09 18:06:15 [kernel] radeon :00:10.0: ring 0 stalled for more than
1msec
Apr 09 18:06:15 [kernel] radeon :00:10.0: GPU lockup (current fence id
0x0016 last fence id 0x0017 on ring 0)
(previous two lines repeat forever, screen stays black, machine stays
accessible over SSH)

-- 
You are receiving this mail because:
You are the assignee for the bug.___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
https://lists.x.org/mailman/listinfo/xorg-driver-ati


[Bug 94877] Radeon 7500: GPU lockup after starting Xorg

2016-04-09 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=94877

--- Comment #2 from ma...@hotmail.com ---
Created attachment 122835
  --> https://bugs.freedesktop.org/attachment.cgi?id=122835=edit
Full Xorg.0.log

-- 
You are receiving this mail because:
You are the assignee for the bug.___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
https://lists.x.org/mailman/listinfo/xorg-driver-ati


[Bug 94877] Radeon 7500: GPU lockup after starting Xorg

2016-04-09 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=94877

--- Comment #1 from ma...@hotmail.com ---
Created attachment 122834
  --> https://bugs.freedesktop.org/attachment.cgi?id=122834=edit
Full dmesg

-- 
You are receiving this mail because:
You are the assignee for the bug.___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
https://lists.x.org/mailman/listinfo/xorg-driver-ati