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
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 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 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 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 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 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 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
12 matches
Mail list logo
