https://bugs.freedesktop.org/show_bug.cgi?id=85207
Christian König changed:
What|Removed |Added
Status|RESOLVED|CLOSED
--- Comment #16 from
https://bugs.freedesktop.org/show_bug.cgi?id=85207
Christian König changed:
What|Removed |Added
CC||commiethebeastie at gmail.com
---
https://bugs.freedesktop.org/show_bug.cgi?id=85207
Andy Furniss changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=85207
--- Comment #13 from Christian König ---
(In reply to Michel Dänzer from comment #11)
> (In reply to Lorenzo Bona from comment #10)
> >
> > [ 1384.901951] [drm:radeon_gem_va_ioctl [radeon]] *ERROR* Couldn't update
> > BO_VA (-512)
>
>
https://bugs.freedesktop.org/show_bug.cgi?id=85207
--- Comment #12 from Christian König ---
Created attachment 111961
--> https://bugs.freedesktop.org/attachment.cgi?id=111961=edit
Fix for printing the error message
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=85207
--- Comment #11 from Michel Dänzer ---
(In reply to Lorenzo Bona from comment #10)
>
> [ 1384.901951] [drm:radeon_gem_va_ioctl [radeon]] *ERROR* Couldn't update
> BO_VA (-512)
Christian, any ideas for these? Various people including myself
https://bugs.freedesktop.org/show_bug.cgi?id=85207
--- Comment #10 from Lorenzo Bona ---
I found same issues here.
[ 1384.901951] [drm:radeon_gem_va_ioctl [radeon]] *ERROR* Couldn't update BO_VA
(-512)
[ 1453.198866] [drm:radeon_gem_va_ioctl [radeon]] *ERROR* Couldn't update BO_VA
(-512)
[
https://bugs.freedesktop.org/show_bug.cgi?id=85207
--- Comment #9 from Andy Furniss ---
(In reply to Christian König from comment #6)
> But first things first, is the original issue with the list corruption
> fixed? If yes we can start to look into this one as well.
Enough time has passed
https://bugs.freedesktop.org/show_bug.cgi?id=85207
--- Comment #8 from Andy Furniss ---
(In reply to Andy Furniss from comment #7)
> (In reply to Christian K?nig from comment #6)
> > (In reply to Andy Furniss from comment #5)
> > > I don't know about Elemental as it's far harder to trigger, but
https://bugs.freedesktop.org/show_bug.cgi?id=85207
--- Comment #7 from Andy Furniss ---
(In reply to Christian K?nig from comment #6)
> (In reply to Andy Furniss from comment #5)
> > I don't know about Elemental as it's far harder to trigger, but first try
> > with valley produced -
> >
> > [
https://bugs.freedesktop.org/show_bug.cgi?id=85207
--- Comment #6 from Christian K?nig ---
(In reply to Andy Furniss from comment #5)
> I don't know about Elemental as it's far harder to trigger, but first try
> with valley produced -
>
> [ 156.617954] radeon :01:00.0: GPU fault detected:
https://bugs.freedesktop.org/show_bug.cgi?id=85207
--- Comment #5 from Andy Furniss ---
(In reply to Christian K?nig from comment #4)
> Created attachment 108165 [details] [review]
> Possible fix
>
> Ups! Forgotten to take the VM lock in radeon_gem_va_update_vm. Fix is
> attached.
>
> Thanks
https://bugs.freedesktop.org/show_bug.cgi?id=85207
Christian K?nig changed:
What|Removed |Added
CC||deathsimple at vodafone.de
---
https://bugs.freedesktop.org/show_bug.cgi?id=85207
--- Comment #3 from Andy Furniss ---
(In reply to Michel D?nzer from comment #2)
> (In reply to Andy Furniss from comment #0)
> > Haven't seen on drm-next-3.18-wip
>
> Can you bisect the kernel?
May be a bit early, but I will sit on the one
https://bugs.freedesktop.org/show_bug.cgi?id=85207
--- Comment #2 from Michel D?nzer ---
(In reply to Andy Furniss from comment #0)
> Haven't seen on drm-next-3.18-wip
Can you bisect the kernel?
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part
https://bugs.freedesktop.org/show_bug.cgi?id=85207
--- Comment #1 from Andy Furniss ---
Also noticed in that dmesg and searching kern log that I sometimes get
apparently without effect -
kernel: [drm:radeon_gem_va_update_vm] *ERROR* Couldn't update BO_VA (-512)
With this kernel.
--
You are
16 matches
Mail list logo
