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 ta
On Mit, 2012-06-27 at 14:14 -0400, j.gli...@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 table
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 k
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 avoid segault to hap
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 avoid segault to hap
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 avoid segault to hap
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 avoid segault to hap
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 ac
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 avoid segault to hap
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 avoid segault to hap
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
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 avoid segault to hap
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.gli...@gmail.com wrote:
> >> From: Jerome Glisse
> >>
> >> After unrecovered GPU lockup avoid any GPU activities to avoid
> >> things like kern
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 avoid segault to hap
On Wed, Jun 27, 2012 at 5:19 AM, Michel Dänzer wrote:
> On Die, 2012-06-26 at 17:04 -0400, j.gli...@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
On Die, 2012-06-26 at 17:04 -0400, j.gli...@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 actua
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
---
drivers/gpu/drm/radeon/radeon_device.c |9 ---
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: sta...@vger.kernel.org
Signed-off-by: Jerome Glisse
---
drivers/gpu/drm/radeon/radeon_device.c |9 ---
dr
18 matches
Mail list logo
