search for: radeon_ib_ring_test

...han 10722msec Dec 22 09:43:37 elitebox kernel: radeon 0000:01:00.0: GPU lockup (current fence id 0x00000000000002f3 last fence id 0x0000000000000302 on ring 0) Dec 22 09:43:38 elitebox kernel: [drm:r600_ib_test [radeon]] *ERROR* radeon: fence wait failed (-35). Dec 22 09:43:38 elitebox kernel: [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed testing IB on GFX ring (-35). That's indicative of either a GPU (i.e. graphics card) problem or a driver issue. You can search on the 2nd from last line and there are lots of hits on it but no real solution - I've seen "limit memory use to 3G",...

...are any alternative method to troubleshoot the issue on CentOS. I suspect it may be related to the Radeon GPU as I notice that every now and then after fresh boot, the GUI desktop will freeze for a while and dmesg will contain errors: [drm:cik_ib_test] *ERROR* radeon: fence wait failed (-35) [drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on ring 2 (-35) As a side note, this laptop had no problems with suspend/resume when it was running Ubuntu 14.04

...{ /* no need to trigger GPU reset as we are unloading */ diff --git a/drivers/gpu/drm/radeon/radeon_ring.c b/drivers/gpu/drm/radeon/radeon_ring.c index f8050f5429e2..594d871a6fce 100644 --- a/drivers/gpu/drm/radeon/radeon_ring.c +++ b/drivers/gpu/drm/radeon/radeon_ring.c @@ -261,6 +261,7 @@ int radeon_ib_ring_tests(struct radeon_device *rdev) r = radeon_ib_test(rdev, i, ring); if (r) { + radeon_fence_cancel_delayed_check(rdev, i); ring->ready = false; rdev->needs_reset = false;

...er GPU reset as we are unloading */ > diff --git a/drivers/gpu/drm/radeon/radeon_ring.c b/drivers/gpu/drm/radeon/radeon_ring.c > index f8050f5429e2..594d871a6fce 100644 > --- a/drivers/gpu/drm/radeon/radeon_ring.c > +++ b/drivers/gpu/drm/radeon/radeon_ring.c > @@ -261,6 +261,7 @@ int radeon_ib_ring_tests(struct radeon_device *rdev) > > r = radeon_ib_test(rdev, i, ring); > if (r) { > + radeon_fence_cancel_delayed_check(rdev, i); > ring->ready = false; > rdev->needs_reset = false; > >

On Fri, Dec 21, 2018 at 01:06:14PM -0800, Alice Wonder wrote: > On 12/21/18 12:44 PM, Fred Smith wrote: > >On Fri, Dec 21, 2018 at 06:27:45PM +0000, Liam O'Toole wrote: > >>On 2018-12-19, Fred Smith > >><fredex at fcshome.stoneham.ma.us> wrote: > >> > >>[...] > >> > >>>Result: Boots to GDM just fine, but Mate is a black

Am 04.08.2014 um 17:09 schrieb Maarten Lankhorst: > op 04-08-14 17:04, Christian K?nig schreef: >> Am 04.08.2014 um 16:58 schrieb Maarten Lankhorst: >>> op 04-08-14 16:45, Christian K?nig schreef: >>>> Am 04.08.2014 um 16:40 schrieb Maarten Lankhorst: >>>>> op 04-08-14 16:37, Christian K?nig schreef: >>>>>>> It'a pain to deal

...> rdev->asic->asic_reset(rdev, true); > @@ -1687,8 +1668,6 @@ int radeon_resume_kms(struct drm_device *dev, bool resume, bool fbcon) > return -1; > } > } > - /* resume AGP if in use */ > - radeon_agp_resume(rdev); > radeon_resume(rdev); > > r = radeon_ib_ring_tests(rdev); > diff --git a/drivers/gpu/drm/radeon/radeon_drv.c b/drivers/gpu/drm/radeon/radeon_drv.c > index bbb0883e8ce6..62a5dfaf990b 100644 > --- a/drivers/gpu/drm/radeon/radeon_drv.c > +++ b/drivers/gpu/drm/radeon/radeon_drv.c > @@ -171,12 +171,6 @@ int radeon_no_wb; > int radeon...

...amp;& !(rdev->flags & RADEON_IS_IGP)) { rdev->asic->asic_reset(rdev, true); @@ -1687,8 +1668,6 @@ int radeon_resume_kms(struct drm_device *dev, bool resume, bool fbcon) return -1; } } - /* resume AGP if in use */ - radeon_agp_resume(rdev); radeon_resume(rdev); r = radeon_ib_ring_tests(rdev); diff --git a/drivers/gpu/drm/radeon/radeon_drv.c b/drivers/gpu/drm/radeon/radeon_drv.c index bbb0883e8ce6..62a5dfaf990b 100644 --- a/drivers/gpu/drm/radeon/radeon_drv.c +++ b/drivers/gpu/drm/radeon/radeon_drv.c @@ -171,12 +171,6 @@ int radeon_no_wb; int radeon_modeset = -1; int radeon_dyn...

...687,8 +1668,6 @@ int radeon_resume_kms(struct drm_device *dev, bool resume, bool fbcon) > return -1; > } > } > - /* resume AGP if in use */ > - radeon_agp_resume(rdev); > radeon_resume(rdev); > > r = radeon_ib_ring_tests(rdev); > diff --git a/drivers/gpu/drm/radeon/radeon_drv.c b/drivers/gpu/drm/radeon/radeon_drv.c > index bbb0883e8ce6..62a5dfaf990b 100644 > --- a/drivers/gpu/drm/radeon/radeon_drv.c > +++ b/drivers/gpu/drm/radeon/radeon_drv.c > @@ -171,12 +171,6 @@ int radeon_no_wb; > int radeon...

Hi guys, Well let's face it AGP is a total headache to maintain and dead for at least 10+ years. We have a lot of x86 specific stuff in the architecture independent graphics memory management to get the caching right, abusing the DMA API on multiple occasions, need to distinct between AGP and driver specific page tables etc etc... So the idea here is to just go ahead and remove the support

fence_is_signaled callback should support being run in atomic context, but not in irq context. Signed-off-by: Maarten Lankhorst <maarten.lankhorst at canonical.com> --- include/linux/fence.h | 23 +++++++++++++++++++---- 1 file changed, 19 insertions(+), 4 deletions(-) diff --git a/include/linux/fence.h b/include/linux/fence.h index d174585b874b..c1a4519ba2f5 100644 ---