https://bugs.freedesktop.org/show_bug.cgi?id=100465
Martin Peres changed:
What|Removed |Added
Resolution|--- |MOVED
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=100465
--- Comment #26 from Zachary Michaels ---
Also note that forcing VGT_STREAMOUT_SYNC, VGT_STREAMOUT_RESET, or VGT_FLUSH to
be emitted on each call to si_draw_vbo (via si_emit_cache_flush) also appears
to work around the issue, though this has not
https://bugs.freedesktop.org/show_bug.cgi?id=100465
--- Comment #25 from Zachary Michaels ---
These settings reproduce consistently on my W600 test machine:
./thrash -w 1920 -h 1080 -c 3 -t 1000 -m 10
--
You are receiving this mail because:
You are the assignee for the bug._
https://bugs.freedesktop.org/show_bug.cgi?id=100465
--- Comment #24 from Zachary Michaels ---
Hi! There is a stress test here that we have been using to reproduce this
issue: https://github.com/Oblong/thrasher
Enabling debug tracing works around the issue. Specifically, when si_draw_vbo
calls si
https://bugs.freedesktop.org/show_bug.cgi?id=100465
--- Comment #23 from Julien Isorce ---
I confirm that comment #9 and #12 are about a different issue (or at least
different symptoms). I reported it here:
https://bugs.freedesktop.org/show_bug.cgi?id=100712
--
You are receiving this mail becau
https://bugs.freedesktop.org/show_bug.cgi?id=100465
Julien Isorce changed:
What|Removed |Added
Attachment #130789|0 |1
is obsolete|
https://bugs.freedesktop.org/show_bug.cgi?id=100465
Julien Isorce changed:
What|Removed |Added
Attachment #130790|0 |1
is obsolete|
https://bugs.freedesktop.org/show_bug.cgi?id=100465
Julien Isorce changed:
What|Removed |Added
Attachment #130787|0 |1
is obsolete|
https://bugs.freedesktop.org/show_bug.cgi?id=100465
Julien Isorce changed:
What|Removed |Added
Attachment #130788|0 |1
is obsolete|
https://bugs.freedesktop.org/show_bug.cgi?id=100465
--- Comment #18 from Julien Isorce ---
-simplify +simply
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://li
https://bugs.freedesktop.org/show_bug.cgi?id=100465
--- Comment #17 from Julien Isorce ---
These last 4 attachements logs are for comment #12. And generated with
GALLIUM_DDEBUG="pipelined 1" R600_DEBUG=check_vm . Again it is potentially
a different freeze than the one reported initially, simp
https://bugs.freedesktop.org/show_bug.cgi?id=100465
--- Comment #16 from Julien Isorce ---
Created attachment 130790
--> https://bugs.freedesktop.org/attachment.cgi?id=130790&action=edit
ddebug_dumps_HD7770_kernel_agd5f-drm-next-4.12_ring_stalled
--
You are receiving this mail because:
You ar
https://bugs.freedesktop.org/show_bug.cgi?id=100465
--- Comment #15 from Julien Isorce ---
Created attachment 130789
--> https://bugs.freedesktop.org/attachment.cgi?id=130789&action=edit
dmesg_HD7770_kernel_agd5f-drm-next-4.12_ring_stalled
--
You are receiving this mail because:
You are the a
https://bugs.freedesktop.org/show_bug.cgi?id=100465
--- Comment #14 from Julien Isorce ---
Created attachment 130788
--> https://bugs.freedesktop.org/attachment.cgi?id=130788&action=edit
ddebug_dumps_HD7770_kernel_amd-staging-4.9_ring_stalled
--
You are receiving this mail because:
You are th
https://bugs.freedesktop.org/show_bug.cgi?id=100465
--- Comment #13 from Julien Isorce ---
Created attachment 130787
--> https://bugs.freedesktop.org/attachment.cgi?id=130787&action=edit
dmesg_HD7770_kernel_amd-staging-4.9_ring_stalled
--
You are receiving this mail because:
You are the assig
https://bugs.freedesktop.org/show_bug.cgi?id=100465
--- Comment #12 from Julien Isorce ---
Thx for the answers and suggestions. In order to make sure I am still tracking
the same hard lockup, will any failure to load the gpu microcode will lead to a
total freeze of the machine ?
Currently in the
https://bugs.freedesktop.org/show_bug.cgi?id=100465
--- Comment #11 from Michel Dänzer ---
When R600_DEBUG=check_vm catches a VM fault, it generates a report in
~/ddebug_dumps/ , please attach that here.
A similar report from something like GALLIUM_DDEBUG="pipelined 1" might
give more inform
https://bugs.freedesktop.org/show_bug.cgi?id=100465
--- Comment #10 from Alex Deucher ---
(In reply to Julien Isorce from comment #9)
>
> So I have 4 questions:
> 1: Can an application causes a "ring 0 stalled" ? or is it a driver bug
> (kernel side or mesa/drm or xserver) ?
driver bug. Proba
https://bugs.freedesktop.org/show_bug.cgi?id=100465
--- Comment #9 from Julien Isorce ---
When using R600_DEBUG=check_vm on both Xorg and the gl app I can get some
output in kern.log. It looks like a "ring 0 stalled" is detected and then
follow a gpu softreset which succeeds ("GPU reset succeeded
https://bugs.freedesktop.org/show_bug.cgi?id=100465
--- Comment #8 from Julien Isorce ---
(In reply to Michel Dänzer from comment #3)
> Doesn't seem to happen with my Tonga after 30 minutes.
>
> One thing to keep in mind is that FurMark is designed to stress the GPU. Do
> the systems you're test
https://bugs.freedesktop.org/show_bug.cgi?id=100465
--- Comment #7 from Julien Isorce ---
(In reply to joro-2013 from comment #4)
> I've noticed the same difference on my ancient mac mini G4 with a humble
> RV280 GPU. I try to boot it in AGP mode from time to time after applying
> some patches, j
https://bugs.freedesktop.org/show_bug.cgi?id=100465
--- Comment #6 from joro-2013 ---
Yeah, i know. But the behaviour of not writing to kern.log but just completely
locking up appeared after said patch.
--
You are receiving this mail because:
You are the assignee for the bug.___
https://bugs.freedesktop.org/show_bug.cgi?id=100465
--- Comment #5 from Alex Deucher ---
(In reply to joro-2013 from comment #4)
> I've noticed the same difference on my ancient mac mini G4 with a humble
> RV280 GPU. I try to boot it in AGP mode from time to time after applying
> some patches, ju
https://bugs.freedesktop.org/show_bug.cgi?id=100465
--- Comment #4 from joro-2013 ---
I've noticed the same difference on my ancient mac mini G4 with a humble RV280
GPU. I try to boot it in AGP mode from time to time after applying some
patches, just for fun. Before i would see some GPU lockup-re
https://bugs.freedesktop.org/show_bug.cgi?id=100465
--- Comment #3 from Michel Dänzer ---
Doesn't seem to happen with my Tonga after 30 minutes.
One thing to keep in mind is that FurMark is designed to stress the GPU. Do the
systems you're testing on have appropriate power supply and cooling?
G
https://bugs.freedesktop.org/show_bug.cgi?id=100465
Michel Dänzer changed:
What|Removed |Added
Attachment #130563|text/x-log |text/plain
mime type|
https://bugs.freedesktop.org/show_bug.cgi?id=100465
--- Comment #2 from Julien Isorce ---
Created attachment 130569
--> https://bugs.freedesktop.org/attachment.cgi?id=130569&action=edit
Same result with amdgpu using a 4.10 kernel
--
You are receiving this mail because:
You are the assignee fo
https://bugs.freedesktop.org/show_bug.cgi?id=100465
--- Comment #1 from Julien Isorce ---
Created attachment 130564
--> https://bugs.freedesktop.org/attachment.cgi?id=130564&action=edit
xorg.log
--
You are receiving this mail because:
You are the assignee for the bug._
https://bugs.freedesktop.org/show_bug.cgi?id=100465
Bug ID: 100465
Summary: Hard lockup with radeonsi driver on FirePro W600,
W9000 and W9100
Product: DRI
Version: DRI git
Hardware: x86-64 (AMD64)
OS: All
29 matches
Mail list logo
