Bug 88211 - [drm:radeon_gem_va_update_vm [radeon]] *ERROR* Couldn't update BO_VA (-512) with linux-git
Summary: [drm:radeon_gem_va_update_vm [radeon]] *ERROR* Couldn't update BO_VA (-512) w...
Status: CLOSED DUPLICATE of bug 85207
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/Gallium/radeonsi (show other bugs)
Version: git
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-08 19:35 UTC by commiethebeastie
Modified: 2015-08-02 11:40 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
dmesg (71.12 KB, text/plain)
2015-01-08 19:35 UTC, commiethebeastie 		Details
glxinfo (59.88 KB, text/plain)
2015-01-08 19:35 UTC, commiethebeastie 		Details
lspci vvv (44.99 KB, text/plain)
2015-01-08 19:36 UTC, commiethebeastie 		Details
Xorg.0.log (83.14 KB, text/plain)
2015-01-08 19:36 UTC, commiethebeastie 		Details
View All

Description commiethebeastie 2015-01-08 19:35:22 UTC 
Created attachment 111968 [details]
dmesg

Radeon R9 280X
Comment 1 commiethebeastie 2015-01-08 19:35:49 UTC 
Created attachment 111969 [details]
glxinfo
Comment 2 commiethebeastie 2015-01-08 19:36:16 UTC 
Created attachment 111970 [details]
lspci vvv
Comment 3 commiethebeastie 2015-01-08 19:36:41 UTC 
Created attachment 111971 [details]
Xorg.0.log
Comment 4 Michel Dänzer 2015-01-09 00:49:45 UTC 
Christian just attached a fix for this to bug 85207. Can you test it?
Comment 5 commiethebeastie 2015-01-09 13:48:24 UTC 
Error missing with patch.
Comment 6 Michel Dänzer 2015-01-13 10:06:14 UTC 
Alex is queueing up the fix.
Comment 7 Marek Olšák 2015-08-02 11:34:28 UTC 
(In reply to Michel Dänzer from comment #6)
> Alex is queueing up the fix.

So this can be closed, right?
Comment 8 Christian König 2015-08-02 11:40:04 UTC 
Yeah indeed, this bug was always just a duplicate.

*** This bug has been marked as a duplicate of bug 85207 ***

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.