https://bugs.freedesktop.org/show_bug.cgi?id=63599
--- Comment #37 from Paul Wolneykien ---
(In reply to comment #36)
> (In reply to comment #35)
> >
> > Your chip was misclassified. The attached patch should fix it.
>
> Great! Now, it works! :)))
>
> Thank you so much.
However, the fun
https://bugs.freedesktop.org/show_bug.cgi?id=63599
--- Comment #36 from Paul Wolneykien ---
(In reply to comment #35)
> Created attachment 91154 [details] [review]
> possible fix
>
> (In reply to comment #34)
> >
> > $ lspci -nn | grep 'VGA'
> > 00:01.0 VGA compatible controller [0300]: Advance
https://bugs.freedesktop.org/show_bug.cgi?id=63599
--- Comment #35 from Alex Deucher ---
Created attachment 91154
--> https://bugs.freedesktop.org/attachment.cgi?id=91154&action=edit
possible fix
(In reply to comment #34)
>
> $ lspci -nn | grep 'VGA'
> 00:01.0 VGA compatible controller [0300]
https://bugs.freedesktop.org/show_bug.cgi?id=63599
--- Comment #34 from Paul Wolneykien ---
(In reply to comment #33)
> (In reply to comment #32)
> > (In reply to comment #31)
> > > (In reply to comment #30)
> > > >
> > > > I've set each register values from fglrx-console.data and call xinit.
https://bugs.freedesktop.org/show_bug.cgi?id=63599
--- Comment #33 from Alex Deucher ---
(In reply to comment #32)
> (In reply to comment #31)
> > (In reply to comment #30)
> > >
> > > I've set each register values from fglrx-console.data and call xinit.
> > > Lockup again, nothing changes.
>
https://bugs.freedesktop.org/show_bug.cgi?id=63599
--- Comment #32 from Paul Wolneykien ---
(In reply to comment #31)
> (In reply to comment #30)
> >
> > I've set each register values from fglrx-console.data and call xinit.
> > Lockup again, nothing changes.
>
> Does the patch in comment 29 f
https://bugs.freedesktop.org/show_bug.cgi?id=63599
Alex Deucher changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=63599
--- Comment #31 from Alex Deucher ---
(In reply to comment #30)
>
> I've set each register values from fglrx-console.data and call xinit.
> Lockup again, nothing changes.
Does the patch in comment 29 fix the issue for you? That patch is upst
https://bugs.freedesktop.org/show_bug.cgi?id=63599
--- Comment #30 from Paul Wolneykien ---
(In reply to comment #13)
> Try comparing the following registers between fglrx and radeon:
>
> ...
>
> You can use radeonreg (as root):
> ./radeonreg regmatch 0x98FC
>
Here is the console mode compari
https://bugs.freedesktop.org/show_bug.cgi?id=63599
--- Comment #29 from wojtek ---
Created attachment 86938
--> https://bugs.freedesktop.org/attachment.cgi?id=86938&action=edit
sumo2.patch
simple patch that's fix problem on my system :)
--
You are receiving this mail because:
You are the ass
https://bugs.freedesktop.org/show_bug.cgi?id=63599
--- Comment #28 from Alex Deucher ---
(In reply to comment #25)
> Hi. I'm having a similar GPU lockup CP stall on a REDWOOD card. But it
> doesn't happen at login. With kernels 3.9, 3.10 I can run Xorg, use KDE
> Kwin effects without any issue;
https://bugs.freedesktop.org/show_bug.cgi?id=63599
--- Comment #27 from pablow.1422 at gmail.com ---
Created attachment 83489
--> https://bugs.freedesktop.org/attachment.cgi?id=83489&action=edit
dmesg output from ssh (hyperz disabled)
--
You are receiving this mail because:
You are the assigne
https://bugs.freedesktop.org/show_bug.cgi?id=63599
--- Comment #26 from pablow.1422 at gmail.com ---
Created attachment 83488
--> https://bugs.freedesktop.org/attachment.cgi?id=83488&action=edit
dmesg output from ssh (hyperz enabled)
--
You are receiving this mail because:
You are the assignee
https://bugs.freedesktop.org/show_bug.cgi?id=63599
--- Comment #25 from pablow.1422 at gmail.com ---
Hi. I'm having a similar GPU lockup CP stall on a REDWOOD card. But it doesn't
happen at login. With kernels 3.9, 3.10 I can run Xorg, use KDE Kwin effects
without any issue; but when I start a ga
https://bugs.freedesktop.org/show_bug.cgi?id=63599
--- Comment #28 from Alex Deucher ---
(In reply to comment #25)
> Hi. I'm having a similar GPU lockup CP stall on a REDWOOD card. But it
> doesn't happen at login. With kernels 3.9, 3.10 I can run Xorg, use KDE
> Kwin effects without any issue;
https://bugs.freedesktop.org/show_bug.cgi?id=63599
--- Comment #27 from pablow.1...@gmail.com ---
Created attachment 83489
--> https://bugs.freedesktop.org/attachment.cgi?id=83489&action=edit
dmesg output from ssh (hyperz disabled)
--
You are receiving this mail because:
You are the assignee f
https://bugs.freedesktop.org/show_bug.cgi?id=63599
--- Comment #26 from pablow.1...@gmail.com ---
Created attachment 83488
--> https://bugs.freedesktop.org/attachment.cgi?id=83488&action=edit
dmesg output from ssh (hyperz enabled)
--
You are receiving this mail because:
You are the assignee fo
https://bugs.freedesktop.org/show_bug.cgi?id=63599
--- Comment #25 from pablow.1...@gmail.com ---
Hi. I'm having a similar GPU lockup CP stall on a REDWOOD card. But it doesn't
happen at login. With kernels 3.9, 3.10 I can run Xorg, use KDE Kwin effects
without any issue; but when I start a game
https://bugs.freedesktop.org/show_bug.cgi?id=63599
--- Comment #24 from wojtek ---
> left (fglrx) right(rad)
> GB_ADDR_CONFIG
> -0x98F8 0x02010002 (33619970)
> +0x98F8 0x02010001 (33619969)
my mistake
- (left - radeon)
+ (right -fglrx)
--
You are receiving this mail because:
You are the assi
https://bugs.freedesktop.org/show_bug.cgi?id=63599
--- Comment #23 from wojtek ---
(In reply to comment #13)
> Try comparing the following registers between fglrx and radeon:
>
difference:
left (fglrx) right(rad)
GB_ADDR_CONFIG
-0x98F8 0x02010002 (33619970)
+0x98F8 0x02010001 (33619969)
CGTS_
https://bugs.freedesktop.org/show_bug.cgi?id=63599
--- Comment #24 from wojtek ---
> left (fglrx) right(rad)
> GB_ADDR_CONFIG
> -0x98F8 0x02010002 (33619970)
> +0x98F8 0x02010001 (33619969)
my mistake
- (left - radeon)
+ (right -fglrx)
--
You are receiving this mail because:
You are the assi
https://bugs.freedesktop.org/show_bug.cgi?id=63599
--- Comment #23 from wojtek ---
(In reply to comment #13)
> Try comparing the following registers between fglrx and radeon:
>
difference:
left (fglrx) right(rad)
GB_ADDR_CONFIG
-0x98F8 0x02010002 (33619970)
+0x98F8 0x02010001 (33619969)
CGTS_
https://bugs.freedesktop.org/show_bug.cgi?id=63599
--- Comment #22 from Paul Wolneykien ---
(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
Ye
https://bugs.freedesktop.org/show_bug.cgi?id=63599
--- Comment #22 from Paul Wolneykien ---
(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
Ye
https://bugs.freedesktop.org/show_bug.cgi?id=63599
--- Comment #21 from Alex Deucher ---
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
--
You are receiving this mail because:
https://bugs.freedesktop.org/show_bug.cgi?id=63599
--- Comment #20 from wojtek ---
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
--
Y
https://bugs.freedesktop.org/show_bug.cgi?id=63599
--- Comment #19 from Paul Wolneykien ---
Created attachment 82525
--> https://bugs.freedesktop.org/attachment.cgi?id=82525&action=edit
dmesg output, vramlimit=128, Xorg started
Attached the dmesg | grep 'radeon' after modprobe radeon vramlimit
https://bugs.freedesktop.org/show_bug.cgi?id=63599
--- Comment #18 from Paul Wolneykien ---
Created attachment 82524
--> https://bugs.freedesktop.org/attachment.cgi?id=82524&action=edit
dmesg output, vramlimit=32, Xorg started
Attached the dmesg | grep 'radeon' after modprobe radeon vramlimit=
https://bugs.freedesktop.org/show_bug.cgi?id=63599
--- Comment #17 from Paul Wolneykien ---
Created attachment 82523
--> https://bugs.freedesktop.org/attachment.cgi?id=82523&action=edit
dmesg output, vramlimit=16, Xorg started
Attached the dmesg | grep 'radeon' after modprobe radeon vramlimit=
https://bugs.freedesktop.org/show_bug.cgi?id=63599
--- Comment #16 from Paul Wolneykien ---
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
https://bugs.freedesktop.org/show_bug.cgi?id=63599
--- Comment #21 from Alex Deucher ---
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
--
You are receiving this mail because:
https://bugs.freedesktop.org/show_bug.cgi?id=63599
--- Comment #20 from wojtek ---
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
--
Y
https://bugs.freedesktop.org/show_bug.cgi?id=63599
--- Comment #19 from Paul Wolneykien ---
Created attachment 82525
--> https://bugs.freedesktop.org/attachment.cgi?id=82525&action=edit
dmesg output, vramlimit=128, Xorg started
Attached the dmesg | grep 'radeon' after modprobe radeon vramlimit
https://bugs.freedesktop.org/show_bug.cgi?id=63599
--- Comment #18 from Paul Wolneykien ---
Created attachment 82524
--> https://bugs.freedesktop.org/attachment.cgi?id=82524&action=edit
dmesg output, vramlimit=32, Xorg started
Attached the dmesg | grep 'radeon' after modprobe radeon vramlimit=
https://bugs.freedesktop.org/show_bug.cgi?id=63599
--- Comment #17 from Paul Wolneykien ---
Created attachment 82523
--> https://bugs.freedesktop.org/attachment.cgi?id=82523&action=edit
dmesg output, vramlimit=16, Xorg started
Attached the dmesg | grep 'radeon' after modprobe radeon vramlimit=
https://bugs.freedesktop.org/show_bug.cgi?id=63599
--- Comment #16 from Paul Wolneykien ---
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
https://bugs.freedesktop.org/show_bug.cgi?id=63599
--- Comment #15 from wojtek ---
diff between registers from comment#13 before startx
diff fglrx_registers_c.log radeon_registers_c.log
2c2
< 0x98F80x (0)
---
> 0x98F80x02010002 (33619970)
7,8c7,8
< 0x3F900x000
https://bugs.freedesktop.org/show_bug.cgi?id=63599
wojtek changed:
What|Removed |Added
Summary|[r600][r600] GPU lockup CP |[r600] SUMO2 GPU lockup CP
|s
https://bugs.freedesktop.org/show_bug.cgi?id=63599
--- Comment #15 from wojtek ---
diff between registers from comment#13 before startx
diff fglrx_registers_c.log radeon_registers_c.log
2c2
< 0x98F80x (0)
---
> 0x98F80x02010002 (33619970)
7,8c7,8
< 0x3F900x000
https://bugs.freedesktop.org/show_bug.cgi?id=63599
wojtek changed:
What|Removed |Added
Summary|[r600][r600] GPU lockup CP |[r600] SUMO2 GPU lockup CP
|s
40 matches
Mail list logo
