[PATCH] drm/radeon: disable any GPU activity after unrecovered lockup v5

On Mit, 2012-06-27 at 14:14 -0400, j.glisse at gmail.com wrote: > From: Jerome Glisse > > After unrecovered GPU lockup avoid any GPU activities to avoid > things like kernel segfault and alike to happen in any of the > path that assume hw is working. > > The segfault is due to PCIE vram gart

Re: [PATCH] drm/radeon: disable any GPU activity after unrecovered lockup v5

On Mit, 2012-06-27 at 14:14 -0400, j.gli...@gmail.com wrote: From: Jerome Glisse jgli...@redhat.com After unrecovered GPU lockup avoid any GPU activities to avoid things like kernel segfault and alike to happen in any of the path that assume hw is working. The segfault is due to PCIE

[PATCH] drm/radeon: disable any GPU activity after unrecovered lockup

On Mit, 2012-06-27 at 10:49 -0400, Jerome Glisse wrote: > On Wed, Jun 27, 2012 at 5:19 AM, Michel D?nzer wrote: > > On Die, 2012-06-26 at 17:04 -0400, j.glisse at gmail.com wrote: > >> From: Jerome Glisse > >> > >> After unrecovered GPU lockup avoid any GPU activities to avoid > >> things like

[PATCH] drm/radeon: disable any GPU activity after unrecovered lockup v5

From: Jerome Glisse After unrecovered GPU lockup avoid any GPU activities to avoid things like kernel segfault and alike to happen in any of the path that assume hw is working. The segfault is due to PCIE vram gart table being unmapped after suspend in the GPU reset path. To

[PATCH] drm/radeon: disable any GPU activity after unrecovered lockup v4

From: Jerome Glisse After unrecovered GPU lockup avoid any GPU activities to avoid things like kernel segfault and alike to happen in any of the path that assume hw is working. The segfault is due to PCIE vram gart table being unmapped after suspend in the GPU reset path. To

[PATCH] drm/radeon: disable any GPU activity after unrecovered lockup v3

From: Jerome Glisse After unrecovered GPU lockup avoid any GPU activities to avoid things like kernel segfault and alike to happen in any of the path that assume hw is working. The segfault is due to PCIE vram gart table being unmapped after suspend in the GPU reset path. To

[PATCH] drm/radeon: disable any GPU activity after unrecovered lockup v2

From: Jerome Glisse After unrecovered GPU lockup avoid any GPU activities to avoid things like kernel segfault and alike to happen in any of the path that assume hw is working. The segfault is due to PCIE vram gart table being unmapped after suspend in the GPU reset path. To

[PATCH] drm/radeon: disable any GPU activity after unrecovered lockup

On Die, 2012-06-26 at 17:04 -0400, j.glisse at gmail.com wrote: > From: Jerome Glisse > > After unrecovered GPU lockup avoid any GPU activities to avoid > things like kernel segfault and alike to happen in any of the > path that assume hw is working. Has the patch been tested and confirmed to

[PATCH] drm/radeon: disable any GPU activity after unrecovered lockup

On Wed, Jun 27, 2012 at 5:19 AM, Michel D?nzer wrote: > On Die, 2012-06-26 at 17:04 -0400, j.glisse at gmail.com wrote: >> From: Jerome Glisse >> >> After unrecovered GPU lockup avoid any GPU activities to avoid >> things like kernel segfault and alike to happen in any of the >> path that assume

Re: [PATCH] drm/radeon: disable any GPU activity after unrecovered lockup

On Die, 2012-06-26 at 17:04 -0400, j.gli...@gmail.com wrote: From: Jerome Glisse jgli...@redhat.com After unrecovered GPU lockup avoid any GPU activities to avoid things like kernel segfault and alike to happen in any of the path that assume hw is working. Has the patch been tested and

Re: [PATCH] drm/radeon: disable any GPU activity after unrecovered lockup

On Wed, Jun 27, 2012 at 5:19 AM, Michel Dänzer mic...@daenzer.net wrote: On Die, 2012-06-26 at 17:04 -0400, j.gli...@gmail.com wrote: From: Jerome Glisse jgli...@redhat.com After unrecovered GPU lockup avoid any GPU activities to avoid things like kernel segfault and alike to happen in any of

[PATCH] drm/radeon: disable any GPU activity after unrecovered lockup v2

From: Jerome Glisse jgli...@redhat.com After unrecovered GPU lockup avoid any GPU activities to avoid things like kernel segfault and alike to happen in any of the path that assume hw is working. The segfault is due to PCIE vram gart table being unmapped after suspend in the GPU reset path. To

Re: [PATCH] drm/radeon: disable any GPU activity after unrecovered lockup

On Mit, 2012-06-27 at 10:49 -0400, Jerome Glisse wrote: On Wed, Jun 27, 2012 at 5:19 AM, Michel Dänzer mic...@daenzer.net wrote: On Die, 2012-06-26 at 17:04 -0400, j.gli...@gmail.com wrote: From: Jerome Glisse jgli...@redhat.com After unrecovered GPU lockup avoid any GPU activities to

[PATCH] drm/radeon: disable any GPU activity after unrecovered lockup v3

From: Jerome Glisse jgli...@redhat.com After unrecovered GPU lockup avoid any GPU activities to avoid things like kernel segfault and alike to happen in any of the path that assume hw is working. The segfault is due to PCIE vram gart table being unmapped after suspend in the GPU reset path. To

[PATCH] drm/radeon: disable any GPU activity after unrecovered lockup v4

From: Jerome Glisse jgli...@redhat.com After unrecovered GPU lockup avoid any GPU activities to avoid things like kernel segfault and alike to happen in any of the path that assume hw is working. The segfault is due to PCIE vram gart table being unmapped after suspend in the GPU reset path. To

[PATCH] drm/radeon: disable any GPU activity after unrecovered lockup v5

From: Jerome Glisse jgli...@redhat.com After unrecovered GPU lockup avoid any GPU activities to avoid things like kernel segfault and alike to happen in any of the path that assume hw is working. The segfault is due to PCIE vram gart table being unmapped after suspend in the GPU reset path. To

[PATCH] drm/radeon: disable any GPU activity after unrecovered lockup

From: Jerome Glisse After unrecovered GPU lockup avoid any GPU activities to avoid things like kernel segfault and alike to happen in any of the path that assume hw is working. cc: stable at vger.kernel.org Signed-off-by: Jerome Glisse ---