https://bugs.freedesktop.org/show_bug.cgi?id=91278
--- Comment #50 from Michel Dänzer ---
(In reply to Andy Furniss from comment #49)
> If it's still an issue for anyone you can reopen.
This is your report, so anyone else please file their own instead.
--
You are receiving this mail because:
https://bugs.freedesktop.org/show_bug.cgi?id=91278
Andy Furniss changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=91278
EoD changed:
What|Removed |Added
CC||EoD at xmw.de
--- Comment #48 from EoD ---
I
https://bugs.freedesktop.org/show_bug.cgi?id=91278
--- Comment #47 from Andy Furniss ---
Seems like you are using an old kernel - though what I call old may be current
for what's released.
The hanging for me stopped with 4.4, but 4.3 is release.
If you are using 4.3 maybe booting with the
https://bugs.freedesktop.org/show_bug.cgi?id=91278
--- Comment #46 from Daniele Ruffini ---
Just forgot to mention that the bug for me happens totally randomly.
No Unigine Heave. No intensive graphic usage.
It seems to happen when something new is displayed tough but i wasn't able to
recreate it
https://bugs.freedesktop.org/show_bug.cgi?id=91278
--- Comment #45 from Daniele Ruffini ---
Created attachment 119679
--> https://bugs.freedesktop.org/attachment.cgi?id=119679=edit
journalctl | grep amdgpu
Went on for a while, cut short because the error was just repeating
--
You are
https://bugs.freedesktop.org/show_bug.cgi?id=91278
--- Comment #44 from Mathias Tillman ---
Just done some tests:
enable_scheduler=0, enable_semaphores=1, vm_fault_stop=0, vm_debug=1
Hang after a few minutes, normal desktop use or running the valley test. Many
VM faults in dmesg.
https://bugs.freedesktop.org/show_bug.cgi?id=91278
--- Comment #43 from Christian König ---
(In reply to Alex Deucher from comment #42)
> (In reply to Mathias Tillman from comment #41)
> > Just tried it again with the latest drm-next-4.4 and the kernel parameters
> > amdgpu.enable_scheduler=0
https://bugs.freedesktop.org/show_bug.cgi?id=91278
--- Comment #42 from Alex Deucher ---
(In reply to Mathias Tillman from comment #41)
> Just tried it again with the latest drm-next-4.4 and the kernel parameters
> amdgpu.enable_scheduler=0 amdgpu.vm_debug=1 amdgpu.enable_semaphores=1.
I don't
https://bugs.freedesktop.org/show_bug.cgi?id=91278
--- Comment #41 from Mathias Tillman ---
Just tried it again with the latest drm-next-4.4 and the kernel parameters
amdgpu.enable_scheduler=0 amdgpu.vm_debug=1 amdgpu.enable_semaphores=1. Can't
even make it to the beginning of the test (it hangs
https://bugs.freedesktop.org/show_bug.cgi?id=91278
--- Comment #40 from Andy Furniss ---
(In reply to Mathias Tillman from comment #39)
> (In reply to Andy Furniss from comment #38)
> > (In reply to Andy Furniss from comment #32)
> >
> > > I'll try over the weekend - no locks so far.
> >
> >
https://bugs.freedesktop.org/show_bug.cgi?id=91278
--- Comment #39 from Mathias Tillman ---
(In reply to Andy Furniss from comment #38)
> (In reply to Andy Furniss from comment #32)
>
> > I'll try over the weekend - no locks so far.
>
> Still good, I've also tried to hang with Unreal demos and
https://bugs.freedesktop.org/show_bug.cgi?id=91278
--- Comment #38 from Andy Furniss ---
(In reply to Andy Furniss from comment #32)
> I'll try over the weekend - no locks so far.
Still good, I've also tried to hang with Unreal demos and mplayer+uvd, no hangs
and no vm faults so far.
--
You
https://bugs.freedesktop.org/show_bug.cgi?id=91278
--- Comment #37 from Grazvydas Ignotas ---
ok then my guess is wrong.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
https://bugs.freedesktop.org/show_bug.cgi?id=91278
--- Comment #36 from Mathias Tillman ---
I have run the valley test the entire day (10 hours or so) without a single VM
fault or hang with the GPU scheduler enabled on 4.4.
Re-ran the test with your (Grazvydas) patch and it's showing the same
https://bugs.freedesktop.org/show_bug.cgi?id=91278
--- Comment #35 from Christian König ---
The ring and IB are just normal system memory made accessible to the GPU. So
it's perfectly fine that it's mapped WC by the CPU.
The processing of the commands written into the ring and IB are triggered
https://bugs.freedesktop.org/show_bug.cgi?id=91278
Grazvydas Ignotas changed:
What|Removed |Added
CC||notasas at gmail.com
--- Comment
https://bugs.freedesktop.org/show_bug.cgi?id=91278
--- Comment #33 from Mathias Tillman ---
(In reply to Andy Furniss from comment #32)
> (In reply to Mathias Tillman from comment #31)
> > Small update: I have been able to run it for a total of 7 hours (2 + 2 + 3)
> > without a hang on the
https://bugs.freedesktop.org/show_bug.cgi?id=91278
--- Comment #32 from Andy Furniss ---
(In reply to Mathias Tillman from comment #31)
> Small update: I have been able to run it for a total of 7 hours (2 + 2 + 3)
> without a hang on the latest drm-next-4.4-wip. Tried the latest
> drm-fixes-4.3
https://bugs.freedesktop.org/show_bug.cgi?id=91278
--- Comment #31 from Mathias Tillman ---
Small update: I have been able to run it for a total of 7 hours (2 + 2 + 3)
without a hang on the latest drm-next-4.4-wip. Tried the latest drm-fixes-4.3
and it hung after about 30 minutes, so I
https://bugs.freedesktop.org/show_bug.cgi?id=91278
--- Comment #30 from Mathias Tillman ---
Just updated to latest drm-next-4.4-wip and mesa and reran the valley test.
Been running for two hours now without a hang (although there have been vm
faults). Will test more over the weekend, but it's
https://bugs.freedesktop.org/show_bug.cgi?id=91278
--- Comment #29 from Michel Dänzer ---
That is interesting, though; the radeonsi driver seems to think there should be
something mapped at the faulting address. This indicates that either the kernel
driver fails to handle the mapping properly,
https://bugs.freedesktop.org/show_bug.cgi?id=91278
--- Comment #28 from Mathias Tillman ---
(In reply to Andy Furniss from comment #27)
> Created attachment 118665 [details]
> valley vm fault dump
>
> Aha, here it is.
I am getting similar results using check_vm. However, since the hang usually
https://bugs.freedesktop.org/show_bug.cgi?id=91278
--- Comment #27 from Andy Furniss ---
Created attachment 118665
--> https://bugs.freedesktop.org/attachment.cgi?id=118665=edit
valley vm fault dump
Aha, here it is.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=91278
--- Comment #26 from Michel Dänzer ---
(In reply to Andy Furniss from comment #25)
> I also see a new R600_DEBUG=check_vm in mesa. I don't know what, if any,
> extra info is expected from that, but testing valley with it caused it to
> quit
https://bugs.freedesktop.org/show_bug.cgi?id=91278
--- Comment #25 from Andy Furniss ---
(In reply to Andy Furniss from comment #24)
> (In reply to Andy Furniss from comment #23)
>
> > I haven't seen thousands until Today so that aspect could be to do with the
> > patches.
>
> Ignore that,
https://bugs.freedesktop.org/show_bug.cgi?id=91278
--- Comment #24 from Andy Furniss ---
(In reply to Andy Furniss from comment #23)
> I haven't seen thousands until Today so that aspect could be to do with the
> patches.
Ignore that, more grepping of kernel log does show I have got thousands
https://bugs.freedesktop.org/show_bug.cgi?id=91278
--- Comment #23 from Andy Furniss ---
(In reply to Mathias Tillman from comment #22)
> (In reply to Andy Furniss from comment #21)
> > (In reply to Mathias Tillman from comment #20)
> >
> > > Do you get those GPU faults in the log even when
https://bugs.freedesktop.org/show_bug.cgi?id=91278
--- Comment #22 from Mathias Tillman ---
(In reply to Andy Furniss from comment #21)
> (In reply to Mathias Tillman from comment #20)
>
> > Do you get those GPU faults in the log even when there's no hang?
>
> Yes and I can also hang without
https://bugs.freedesktop.org/show_bug.cgi?id=91278
--- Comment #21 from Andy Furniss ---
(In reply to Mathias Tillman from comment #20)
> Do you get those GPU faults in the log even when there's no hang?
Yes and I can also hang without getting any.
--
You are receiving this mail because:
You
https://bugs.freedesktop.org/show_bug.cgi?id=91278
--- Comment #20 from Mathias Tillman ---
(In reply to Andy Furniss from comment #19)
> (In reply to Andy Furniss from comment #18)
> > So after last update I ran valley again briefly and saw a few vmfaults, then
> > a longer run and got
https://bugs.freedesktop.org/show_bug.cgi?id=91278
--- Comment #19 from Andy Furniss ---
(In reply to Andy Furniss from comment #18)
> So after last update I ran valley again briefly and saw a few vmfaults, then
> a longer run and got thousands again.
>
> without touching anything else did echo
https://bugs.freedesktop.org/show_bug.cgi?id=91278
--- Comment #18 from Andy Furniss ---
So after last update I ran valley again briefly and saw a few vmfaults, then a
longer run and got thousands again.
without touching anything else did echo mem >/sys/power/state and then woke up.
10 minute
https://bugs.freedesktop.org/show_bug.cgi?id=91278
--- Comment #17 from Andy Furniss ---
Haven't had time yet to hang with the patches.
Yesterday without I them I hung, rebooted, did the memsleep, then tested the
rest of the day trying to lock valley and unreal but couldn't. For the whole
day,
https://bugs.freedesktop.org/show_bug.cgi?id=91278
--- Comment #16 from Mathias Tillman ---
(In reply to Alex Deucher from comment #15)
> These patches may help:
> http://lists.llvm.org/pipermail/llvm-commits/Week-of-Mon-20150928/302380.html
>
https://bugs.freedesktop.org/show_bug.cgi?id=91278
--- Comment #15 from Alex Deucher ---
These patches may help:
http://lists.llvm.org/pipermail/llvm-commits/Week-of-Mon-20150928/302380.html
http://lists.freedesktop.org/archives/mesa-dev/2015-September/095718.html
--
You are receiving this
https://bugs.freedesktop.org/show_bug.cgi?id=91278
--- Comment #14 from Andy Furniss ---
FWIW I don't think the Valley code/shaders/whatever its self triggers this.
I can run valley for > an hour depending on luck/state of my box.
One way to get a long run for me is to go into mem sleep, come
https://bugs.freedesktop.org/show_bug.cgi?id=91278
--- Comment #13 from Mathias Tillman ---
Sorry for triple posting, but I have some more info that may or may not be
useful.
When enabling verbose output from glretrace, I can see that the next to last
operation before a hang is always
https://bugs.freedesktop.org/show_bug.cgi?id=91278
--- Comment #12 from Mathias Tillman ---
(In reply to Michel Dänzer from comment #10)
> Mathias, so you can reliably reproduce the hang by replaying that apitrace?
Okay, I have been able to replay the trace by compiling apitrace from source,
https://bugs.freedesktop.org/show_bug.cgi?id=91278
--- Comment #11 from Mathias Tillman ---
(In reply to Michel Dänzer from comment #10)
> Mathias, so you can reliably reproduce the hang by replaying that apitrace?
Unfortunately I haven't been able to replay the apitrace properly - I just get
https://bugs.freedesktop.org/show_bug.cgi?id=91278
--- Comment #10 from Michel Dänzer ---
Mathias, so you can reliably reproduce the hang by replaying that apitrace?
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML
https://bugs.freedesktop.org/show_bug.cgi?id=91278
--- Comment #9 from Mathias Tillman ---
Created attachment 118448
--> https://bugs.freedesktop.org/attachment.cgi?id=118448=edit
apitrace of hang
Not exactly sure how useful it is, but I have attached an excerpt of an
apitrace of the unigine
https://bugs.freedesktop.org/show_bug.cgi?id=91278
Alex Deucher changed:
What|Removed |Added
CC||edward.ocallaghan at koparo.co
https://bugs.freedesktop.org/show_bug.cgi?id=91278
--- Comment #7 from Andy Furniss ---
Created attachment 117964
--> https://bugs.freedesktop.org/attachment.cgi?id=117964=edit
hung tast with current agd5f drm-next-4.3
Valley does sometimes get further with newer gits - I have recently got
https://bugs.freedesktop.org/show_bug.cgi?id=91278
--- Comment #6 from Michel Dänzer ---
(In reply to Mathias Tillman from comment #5)
> Have been getting the same hangs, though I get it while just using the
> computer normally, or even while it was idle.
The symptoms may be similar, but since
https://bugs.freedesktop.org/show_bug.cgi?id=91278
Mathias Tillman changed:
What|Removed |Added
CC||master.homer at gmail.com
--- Comment
https://bugs.freedesktop.org/show_bug.cgi?id=91278
--- Comment #4 from Andy Furniss ---
I tested Xonotic with load over the weekend and it did lock after about 10
minutes - but I then tested without any memory pressure and still managed to
lock, it did take longer.
I got another lock ehile
https://bugs.freedesktop.org/show_bug.cgi?id=91278
--- Comment #3 from Andy Furniss ---
I've of course tried various things sine reporting - Valley doesn't always
instantly lock. Unreal 4.5 Elemental got half way before locking.
Perhaps more interesting I managed to reset/fail resume just
https://bugs.freedesktop.org/show_bug.cgi?id=91278
--- Comment #2 from Andy Furniss ---
Created attachment 117013
--> https://bugs.freedesktop.org/attachment.cgi?id=117013=edit
xorg-log for ref (not from lock)
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=91278
--- Comment #1 from Andy Furniss ---
Created attachment 117012
--> https://bugs.freedesktop.org/attachment.cgi?id=117012=edit
dmesg with lock
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part
https://bugs.freedesktop.org/show_bug.cgi?id=91278
Bug ID: 91278
Summary: Tonga GPU lock/reset fail with Unigine Valley
Product: DRI
Version: XOrg git
Hardware: Other
OS: All
Status: NEW
Severity: normal
51 matches
Mail list logo
