All of lore.kernel.org
 help / color / mirror / Atom feed
* RE: Tonga PRO [Radeon R9 285/380] [1002:6939] blank screen
       [not found] ` <mailman.10603.1507217137.1832.amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>
@ 2017-10-05 18:26   ` Martin Babutzka
       [not found]     ` <1507228004.5007.1.camel-BGeptl67XyCzQB+pC5nmwQ@public.gmane.org>
  2017-10-06 16:43   ` Regression: Crash/freeze when resuming from suspend or locked screen Martin Babutzka
  1 sibling, 1 reply; 10+ messages in thread
From: Martin Babutzka @ 2017-10-05 18:26 UTC (permalink / raw)
  To: amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW

@Steven Falco: This behavior was EXACTLY the same with my R9 380 caused
by commit e37a7b4088da ("drm/amd/powerplay: tidy up ret checks in
amd_powerplay.c"). This is reverted now since a few days - are you sure
your kernel build already includes commit adc6af2349f0
("drm/amd/powerplay: fix ret checks in amd_powerplay.c")?

@AMD Devs/Alex: It would be nice if you push "Revert drm/amd/powerplay:
Add support for CI asics to hwmgr (Deucher, Alexander)" to agd5f. Then
I can try to build a non-crashing, flicker-free and hopefully overall
decent 4.13.5 kernel based on amd-staging-drm-next tomorrow.

Thanks & best regards,
Martin


Am Donnerstag, den 05.10.2017, 15:25 +0000 schrieb amd-gfx-
request@lists.freedesktop.org:
> Send amd-gfx mailing list submissions to
> 	amd-gfx@lists.freedesktop.org
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> 	https://lists.freedesktop.org/mailman/listinfo/amd-gfx
> or, via email, send a message with subject or body 'help' to
> 	amd-gfx-request@lists.freedesktop.org
> 
> You can reach the person managing the list at
> 	amd-gfx-owner@lists.freedesktop.org
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of amd-gfx digest..."
> 
> 
> Today's Topics:
> 
>    1. Tonga PRO [Radeon R9 285/380] [1002:6939] blank screen
>       (Steven Falco)
>    2. Re: Tonga PRO [Radeon R9 285/380] [1002:6939] blank screen
>       (Tom St Denis)
>    3. RE: Tonga PRO [Radeon R9 285/380] [1002:6939] blank screen
>       (Deucher, Alexander)
>    4. [PATCH libdrm v2 1/2] tests/amdgpu: add new uvd enc support
>       check (James Zhu)
> 
> 
> -------------------------------------------------------------------
> ---
> 
> Message: 1
> Date: Thu, 5 Oct 2017 10:45:59 -0400
> From: Steven Falco <stevenfalco@gmail.com>
> To: amd-gfx@lists.freedesktop.org
> Subject: Tonga PRO [Radeon R9 285/380] [1002:6939] blank screen
> Message-ID: <93ad0081-4ceb-f389-e900-6eb114ea0ee9@gmail.com>
> Content-Type: text/plain; charset=utf-8
> 
> I have a Radeon R9 285/380 video card in a machine that is running
> Fedora 26.  When I run with Fedora kernel version 4.11.11 the video
> card works properly, using the amdgpu kernel driver.
> 
> However, once I upgrade to a newer kernel in the 4.12 or 4.13 series,
> my display goes blank during boot and stays that way.  The monitor
> appears to be getting sync, because it doesn't go to sleep, however
> there is nothing visible on the screen.
> 
> What information should I post to this list to help diagnose the
> problem?
> 
> 	Thanks,
> 	Steve
> 
> 
> ------------------------------
> 
> Message: 2
> Date: Thu, 5 Oct 2017 11:15:27 -0400
> From: Tom St Denis <tom.stdenis@amd.com>
> To: amd-gfx@lists.freedesktop.org
> Subject: Re: Tonga PRO [Radeon R9 285/380] [1002:6939] blank screen
> Message-ID: <662dc623-7b77-e3d3-faaa-fc7b2b8ccc43@amd.com>
> Content-Type: text/plain; charset=utf-8; format=flowed
> 
> Hi Steve,
> 
> A dmesg log for starters would help.  Could be as simple as a
> firmware 
> file missing or being the wrong version.
> 
> Cheers,
> Tom
> 
> On 05/10/17 10:45 AM, Steven Falco wrote:
> > I have a Radeon R9 285/380 video card in a machine that is running
> > Fedora 26.  When I run with Fedora kernel version 4.11.11 the video
> > card works properly, using the amdgpu kernel driver.
> > 
> > However, once I upgrade to a newer kernel in the 4.12 or 4.13
> > series, my display goes blank during boot and stays that way.  The
> > monitor appears to be getting sync, because it doesn't go to sleep,
> > however there is nothing visible on the screen.
> > 
> > What information should I post to this list to help diagnose the
> > problem?
> > 
> > 	Thanks,
> > 	Steve
> > _______________________________________________
> > amd-gfx mailing list
> > amd-gfx@lists.freedesktop.org
> > https://lists.freedesktop.org/mailman/listinfo/amd-gfx
> > 
> 
> 
> 
> ------------------------------
> 
> Message: 3
> Date: Thu, 5 Oct 2017 15:16:27 +0000
> From: "Deucher, Alexander" <Alexander.Deucher@amd.com>
> To: 'Steven Falco' <stevenfalco@gmail.com>,
> 	"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>
> Subject: RE: Tonga PRO [Radeon R9 285/380] [1002:6939] blank screen
> Message-ID:
> 	<BN6PR12MB1652C0A1337626E55C459EA8F7700@BN6PR12MB1652.namprd12.
> prod.outlook.com>
> 	
> Content-Type: text/plain; charset="utf-8"
> 
> > -----Original Message-----
> > From: amd-gfx [mailto:amd-gfx-bounces@lists.freedesktop.org] On
> > Behalf
> > Of Steven Falco
> > Sent: Thursday, October 05, 2017 10:46 AM
> > To: amd-gfx@lists.freedesktop.org
> > Subject: Tonga PRO [Radeon R9 285/380] [1002:6939] blank screen
> > 
> > I have a Radeon R9 285/380 video card in a machine that is running
> > Fedora 26.
> > When I run with Fedora kernel version 4.11.11 the video card works
> > properly,
> > using the amdgpu kernel driver.
> > 
> > However, once I upgrade to a newer kernel in the 4.12 or 4.13
> > series, my
> > display goes blank during boot and stays that way.  The monitor
> > appears to
> > be getting sync, because it doesn't go to sleep, however there is
> > nothing
> > visible on the screen.
> > 
> > What information should I post to this list to help diagnose the
> > problem?
> 
> Please file a bug report (https://bugs.freedesktop.org) and attach
> your xorg log and dmesg output.
> 
> Thanks!
> 
> Alex
> 
> > 
> > 	Thanks,
> > 	Steve
> > _______________________________________________
> > amd-gfx mailing list
> > amd-gfx@lists.freedesktop.org
> > https://lists.freedesktop.org/mailman/listinfo/amd-gfx
> 
> ------------------------------
> 
> Message: 4
> Date: Thu,  5 Oct 2017 11:24:49 -0400
> From: James Zhu <James.Zhu@amd.com>
> To: amd-gfx@lists.freedesktop.org,	dri-devel@lists.freedesktop
> .org
> Subject: [PATCH libdrm v2 1/2] tests/amdgpu: add new uvd enc support
> 	check
> Message-ID: <1507217090-10669-1-git-send-email-James.Zhu@amd.com>
> Content-Type: text/plain
> 
> Query hardware IP information to find out if there are uvd encode
> rings
> ready for use in kernel driver.
> 
> Signed-off-by: James Zhu <James.Zhu@amd.com>
> ---
>  tests/amdgpu/uvd_enc_tests.c | 27 +++++++++++++++++++++------
>  1 file changed, 21 insertions(+), 6 deletions(-)
> 
> diff --git a/tests/amdgpu/uvd_enc_tests.c
> b/tests/amdgpu/uvd_enc_tests.c
> index 6c19f7b..7518103 100644
> --- a/tests/amdgpu/uvd_enc_tests.c
> +++ b/tests/amdgpu/uvd_enc_tests.c
> @@ -79,6 +79,8 @@ static void amdgpu_cs_uvd_enc_session_init(void);
>  static void amdgpu_cs_uvd_enc_encode(void);
>  static void amdgpu_cs_uvd_enc_destroy(void);
>  
> +static bool uvd_enc_support(void);
> +
>  CU_TestInfo uvd_enc_tests[] = {
>  	{ "UVD ENC create",  amdgpu_cs_uvd_enc_create },
>  	{ "UVD ENC session init",  amdgpu_cs_uvd_enc_session_init },
> @@ -98,7 +100,7 @@ int suite_uvd_enc_tests_init(void)
>  
>  	family_id = device_handle->info.family_id;
>  
> -	if (family_id < AMDGPU_FAMILY_AI || family_id >=
> AMDGPU_FAMILY_RV) {
> +	if (!uvd_enc_support()) {
>  		printf("\n\nThe ASIC NOT support UVD ENC, all sub-
> tests will pass\n");
>  		return CUE_SUCCESS;
>  	}
> @@ -121,7 +123,7 @@ int suite_uvd_enc_tests_clean(void)
>  {
>  	int r;
>  
> -	if (family_id < AMDGPU_FAMILY_AI || family_id >=
> AMDGPU_FAMILY_RV) {
> +	if (!uvd_enc_support()) {
>  
>  		r = amdgpu_device_deinitialize(device_handle);
>  		if (r)
> @@ -238,11 +240,24 @@ static void free_resource(struct
> amdgpu_uvd_enc_bo *uvd_enc_bo)
>  	memset(uvd_enc_bo, 0, sizeof(*uvd_enc_bo));
>  }
>  
> +static bool uvd_enc_support(void)
> +{
> +	int r;
> +	struct drm_amdgpu_info_hw_ip info;
> +
> +	r = amdgpu_query_hw_ip_info(device_handle,
> AMDGPU_HW_IP_UVD_ENC, 0, &info);
> +
> +	if (r)
> +		return false;
> +	else
> +		return (info.available_rings?true:false);
> +}
> +
>  static void amdgpu_cs_uvd_enc_create(void)
>  {
>  	int len, r;
>  
> -	if (family_id < AMDGPU_FAMILY_AI || family_id >=
> AMDGPU_FAMILY_RV)
> +	if (!uvd_enc_support())
>  		return;
>  
>  	enc.width = 160;
> @@ -281,7 +296,7 @@ static void amdgpu_cs_uvd_enc_session_init(void)
>  {
>  	int len, r;
>  
> -	if (family_id < AMDGPU_FAMILY_AI || family_id >=
> AMDGPU_FAMILY_RV)
> +	if (!uvd_enc_support())
>  		return;
>  
>  	len = 0;
> @@ -339,7 +354,7 @@ static void amdgpu_cs_uvd_enc_encode(void)
>  	vbuf_size = ALIGN(enc.width, align) * ALIGN(enc.height, 16)
> * 1.5;
>  	cpb_size = vbuf_size * 10;
>  
> -	if (family_id < AMDGPU_FAMILY_AI || family_id >=
> AMDGPU_FAMILY_RV)
> +	if (!uvd_enc_support())
>  		return;
>  
>  	num_resources  = 0;
> @@ -472,7 +487,7 @@ static void amdgpu_cs_uvd_enc_destroy(void)
>  	struct amdgpu_uvd_enc_bo sw_ctx;
>  	int len, r;
>  
> -	if (family_id < AMDGPU_FAMILY_AI || family_id >=
> AMDGPU_FAMILY_RV)
> +	if (!uvd_enc_support())
>  		return;
>  
>  	num_resources  = 0;
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: Tonga PRO [Radeon R9 285/380] [1002:6939] blank screen
       [not found]     ` <1507228004.5007.1.camel-BGeptl67XyCzQB+pC5nmwQ@public.gmane.org>
@ 2017-10-05 18:28       ` Tom St Denis
  2017-10-06 12:37       ` Steven Falco
  2017-10-06 20:24       ` Steven Falco
  2 siblings, 0 replies; 10+ messages in thread
From: Tom St Denis @ 2017-10-05 18:28 UTC (permalink / raw)
  To: amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW

On 05/10/17 02:26 PM, Martin Babutzka wrote:
> @Steven Falco: This behavior was EXACTLY the same with my R9 380 caused
> by commit e37a7b4088da ("drm/amd/powerplay: tidy up ret checks in
> amd_powerplay.c"). This is reverted now since a few days - are you sure
> your kernel build already includes commit adc6af2349f0
> ("drm/amd/powerplay: fix ret checks in amd_powerplay.c")?
> 
> @AMD Devs/Alex: It would be nice if you push "Revert drm/amd/powerplay:
> Add support for CI asics to hwmgr (Deucher, Alexander)" to agd5f. Then
> I can try to build a non-crashing, flicker-free and hopefully overall
> decent 4.13.5 kernel based on amd-staging-drm-next tomorrow.

Hi Martin,

We actually came up with a partial revert that fixes glitches for me at 
least.  It's already been pushed to drm-next.

Cheers,
Tom

> 
> Thanks & best regards,
> Martin
> 
> 
> Am Donnerstag, den 05.10.2017, 15:25 +0000 schrieb amd-gfx-
> request@lists.freedesktop.org:
>> Send amd-gfx mailing list submissions to
>> 	amd-gfx@lists.freedesktop.org
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>> 	https://lists.freedesktop.org/mailman/listinfo/amd-gfx
>> or, via email, send a message with subject or body 'help' to
>> 	amd-gfx-request@lists.freedesktop.org
>>
>> You can reach the person managing the list at
>> 	amd-gfx-owner@lists.freedesktop.org
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of amd-gfx digest..."
>>
>>
>> Today's Topics:
>>
>>     1. Tonga PRO [Radeon R9 285/380] [1002:6939] blank screen
>>        (Steven Falco)
>>     2. Re: Tonga PRO [Radeon R9 285/380] [1002:6939] blank screen
>>        (Tom St Denis)
>>     3. RE: Tonga PRO [Radeon R9 285/380] [1002:6939] blank screen
>>        (Deucher, Alexander)
>>     4. [PATCH libdrm v2 1/2] tests/amdgpu: add new uvd enc support
>>        check (James Zhu)
>>
>>
>> -------------------------------------------------------------------
>> ---
>>
>> Message: 1
>> Date: Thu, 5 Oct 2017 10:45:59 -0400
>> From: Steven Falco <stevenfalco@gmail.com>
>> To: amd-gfx@lists.freedesktop.org
>> Subject: Tonga PRO [Radeon R9 285/380] [1002:6939] blank screen
>> Message-ID: <93ad0081-4ceb-f389-e900-6eb114ea0ee9@gmail.com>
>> Content-Type: text/plain; charset=utf-8
>>
>> I have a Radeon R9 285/380 video card in a machine that is running
>> Fedora 26.  When I run with Fedora kernel version 4.11.11 the video
>> card works properly, using the amdgpu kernel driver.
>>
>> However, once I upgrade to a newer kernel in the 4.12 or 4.13 series,
>> my display goes blank during boot and stays that way.  The monitor
>> appears to be getting sync, because it doesn't go to sleep, however
>> there is nothing visible on the screen.
>>
>> What information should I post to this list to help diagnose the
>> problem?
>>
>> 	Thanks,
>> 	Steve
>>
>>
>> ------------------------------
>>
>> Message: 2
>> Date: Thu, 5 Oct 2017 11:15:27 -0400
>> From: Tom St Denis <tom.stdenis@amd.com>
>> To: amd-gfx@lists.freedesktop.org
>> Subject: Re: Tonga PRO [Radeon R9 285/380] [1002:6939] blank screen
>> Message-ID: <662dc623-7b77-e3d3-faaa-fc7b2b8ccc43@amd.com>
>> Content-Type: text/plain; charset=utf-8; format=flowed
>>
>> Hi Steve,
>>
>> A dmesg log for starters would help.  Could be as simple as a
>> firmware
>> file missing or being the wrong version.
>>
>> Cheers,
>> Tom
>>
>> On 05/10/17 10:45 AM, Steven Falco wrote:
>>> I have a Radeon R9 285/380 video card in a machine that is running
>>> Fedora 26.  When I run with Fedora kernel version 4.11.11 the video
>>> card works properly, using the amdgpu kernel driver.
>>>
>>> However, once I upgrade to a newer kernel in the 4.12 or 4.13
>>> series, my display goes blank during boot and stays that way.  The
>>> monitor appears to be getting sync, because it doesn't go to sleep,
>>> however there is nothing visible on the screen.
>>>
>>> What information should I post to this list to help diagnose the
>>> problem?
>>>
>>> 	Thanks,
>>> 	Steve
>>> _______________________________________________
>>> amd-gfx mailing list
>>> amd-gfx@lists.freedesktop.org
>>> https://lists.freedesktop.org/mailman/listinfo/amd-gfx
>>>
>>
>>
>>
>> ------------------------------
>>
>> Message: 3
>> Date: Thu, 5 Oct 2017 15:16:27 +0000
>> From: "Deucher, Alexander" <Alexander.Deucher@amd.com>
>> To: 'Steven Falco' <stevenfalco@gmail.com>,
>> 	"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>
>> Subject: RE: Tonga PRO [Radeon R9 285/380] [1002:6939] blank screen
>> Message-ID:
>> 	<BN6PR12MB1652C0A1337626E55C459EA8F7700@BN6PR12MB1652.namprd12.
>> prod.outlook.com>
>> 	
>> Content-Type: text/plain; charset="utf-8"
>>
>>> -----Original Message-----
>>> From: amd-gfx [mailto:amd-gfx-bounces@lists.freedesktop.org] On
>>> Behalf
>>> Of Steven Falco
>>> Sent: Thursday, October 05, 2017 10:46 AM
>>> To: amd-gfx@lists.freedesktop.org
>>> Subject: Tonga PRO [Radeon R9 285/380] [1002:6939] blank screen
>>>
>>> I have a Radeon R9 285/380 video card in a machine that is running
>>> Fedora 26.
>>> When I run with Fedora kernel version 4.11.11 the video card works
>>> properly,
>>> using the amdgpu kernel driver.
>>>
>>> However, once I upgrade to a newer kernel in the 4.12 or 4.13
>>> series, my
>>> display goes blank during boot and stays that way.  The monitor
>>> appears to
>>> be getting sync, because it doesn't go to sleep, however there is
>>> nothing
>>> visible on the screen.
>>>
>>> What information should I post to this list to help diagnose the
>>> problem?
>>
>> Please file a bug report (https://bugs.freedesktop.org) and attach
>> your xorg log and dmesg output.
>>
>> Thanks!
>>
>> Alex
>>
>>>
>>> 	Thanks,
>>> 	Steve
>>> _______________________________________________
>>> amd-gfx mailing list
>>> amd-gfx@lists.freedesktop.org
>>> https://lists.freedesktop.org/mailman/listinfo/amd-gfx
>>
>> ------------------------------
>>
>> Message: 4
>> Date: Thu,  5 Oct 2017 11:24:49 -0400
>> From: James Zhu <James.Zhu@amd.com>
>> To: amd-gfx@lists.freedesktop.org,	dri-devel@lists.freedesktop
>> .org
>> Subject: [PATCH libdrm v2 1/2] tests/amdgpu: add new uvd enc support
>> 	check
>> Message-ID: <1507217090-10669-1-git-send-email-James.Zhu@amd.com>
>> Content-Type: text/plain
>>
>> Query hardware IP information to find out if there are uvd encode
>> rings
>> ready for use in kernel driver.
>>
>> Signed-off-by: James Zhu <James.Zhu@amd.com>
>> ---
>>   tests/amdgpu/uvd_enc_tests.c | 27 +++++++++++++++++++++------
>>   1 file changed, 21 insertions(+), 6 deletions(-)
>>
>> diff --git a/tests/amdgpu/uvd_enc_tests.c
>> b/tests/amdgpu/uvd_enc_tests.c
>> index 6c19f7b..7518103 100644
>> --- a/tests/amdgpu/uvd_enc_tests.c
>> +++ b/tests/amdgpu/uvd_enc_tests.c
>> @@ -79,6 +79,8 @@ static void amdgpu_cs_uvd_enc_session_init(void);
>>   static void amdgpu_cs_uvd_enc_encode(void);
>>   static void amdgpu_cs_uvd_enc_destroy(void);
>>   
>> +static bool uvd_enc_support(void);
>> +
>>   CU_TestInfo uvd_enc_tests[] = {
>>   	{ "UVD ENC create",  amdgpu_cs_uvd_enc_create },
>>   	{ "UVD ENC session init",  amdgpu_cs_uvd_enc_session_init },
>> @@ -98,7 +100,7 @@ int suite_uvd_enc_tests_init(void)
>>   
>>   	family_id = device_handle->info.family_id;
>>   
>> -	if (family_id < AMDGPU_FAMILY_AI || family_id >=
>> AMDGPU_FAMILY_RV) {
>> +	if (!uvd_enc_support()) {
>>   		printf("\n\nThe ASIC NOT support UVD ENC, all sub-
>> tests will pass\n");
>>   		return CUE_SUCCESS;
>>   	}
>> @@ -121,7 +123,7 @@ int suite_uvd_enc_tests_clean(void)
>>   {
>>   	int r;
>>   
>> -	if (family_id < AMDGPU_FAMILY_AI || family_id >=
>> AMDGPU_FAMILY_RV) {
>> +	if (!uvd_enc_support()) {
>>   
>>   		r = amdgpu_device_deinitialize(device_handle);
>>   		if (r)
>> @@ -238,11 +240,24 @@ static void free_resource(struct
>> amdgpu_uvd_enc_bo *uvd_enc_bo)
>>   	memset(uvd_enc_bo, 0, sizeof(*uvd_enc_bo));
>>   }
>>   
>> +static bool uvd_enc_support(void)
>> +{
>> +	int r;
>> +	struct drm_amdgpu_info_hw_ip info;
>> +
>> +	r = amdgpu_query_hw_ip_info(device_handle,
>> AMDGPU_HW_IP_UVD_ENC, 0, &info);
>> +
>> +	if (r)
>> +		return false;
>> +	else
>> +		return (info.available_rings?true:false);
>> +}
>> +
>>   static void amdgpu_cs_uvd_enc_create(void)
>>   {
>>   	int len, r;
>>   
>> -	if (family_id < AMDGPU_FAMILY_AI || family_id >=
>> AMDGPU_FAMILY_RV)
>> +	if (!uvd_enc_support())
>>   		return;
>>   
>>   	enc.width = 160;
>> @@ -281,7 +296,7 @@ static void amdgpu_cs_uvd_enc_session_init(void)
>>   {
>>   	int len, r;
>>   
>> -	if (family_id < AMDGPU_FAMILY_AI || family_id >=
>> AMDGPU_FAMILY_RV)
>> +	if (!uvd_enc_support())
>>   		return;
>>   
>>   	len = 0;
>> @@ -339,7 +354,7 @@ static void amdgpu_cs_uvd_enc_encode(void)
>>   	vbuf_size = ALIGN(enc.width, align) * ALIGN(enc.height, 16)
>> * 1.5;
>>   	cpb_size = vbuf_size * 10;
>>   
>> -	if (family_id < AMDGPU_FAMILY_AI || family_id >=
>> AMDGPU_FAMILY_RV)
>> +	if (!uvd_enc_support())
>>   		return;
>>   
>>   	num_resources  = 0;
>> @@ -472,7 +487,7 @@ static void amdgpu_cs_uvd_enc_destroy(void)
>>   	struct amdgpu_uvd_enc_bo sw_ctx;
>>   	int len, r;
>>   
>> -	if (family_id < AMDGPU_FAMILY_AI || family_id >=
>> AMDGPU_FAMILY_RV)
>> +	if (!uvd_enc_support())
>>   		return;
>>   
>>   	num_resources  = 0;
> _______________________________________________
> amd-gfx mailing list
> amd-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/amd-gfx
> 

_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: Tonga PRO [Radeon R9 285/380] [1002:6939] blank screen
       [not found]     ` <1507228004.5007.1.camel-BGeptl67XyCzQB+pC5nmwQ@public.gmane.org>
  2017-10-05 18:28       ` Tom St Denis
@ 2017-10-06 12:37       ` Steven Falco
       [not found]         ` <f52fce30-bdc9-ce80-b50b-4d2d4ffb0b9a-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
  2017-10-06 20:24       ` Steven Falco
  2 siblings, 1 reply; 10+ messages in thread
From: Steven Falco @ 2017-10-06 12:37 UTC (permalink / raw)
  To: Martin Babutzka, amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW

On 10/05/2017 02:26 PM, Martin Babutzka wrote:
> @Steven Falco: This behavior was EXACTLY the same with my R9 380 caused
> by commit e37a7b4088da ("drm/amd/powerplay: tidy up ret checks in
> amd_powerplay.c"). This is reverted now since a few days - are you sure
> your kernel build already includes commit adc6af2349f0
> ("drm/amd/powerplay: fix ret checks in amd_powerplay.c")?
> 
> @AMD Devs/Alex: It would be nice if you push "Revert drm/amd/powerplay:
> Add support for CI asics to hwmgr (Deucher, Alexander)" to agd5f. Then
> I can try to build a non-crashing, flicker-free and hopefully overall
> decent 4.13.5 kernel based on amd-staging-drm-next tomorrow.

That sounds very promising.  I am currently running the Fedora kernel.  Where would I download the one with the revisions you mentioned?

	Steve

_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: Tonga PRO [Radeon R9 285/380] [1002:6939] blank screen
       [not found]         ` <f52fce30-bdc9-ce80-b50b-4d2d4ffb0b9a-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
@ 2017-10-06 12:57           ` Tom St Denis
       [not found]             ` <c3045ba5-ca9d-fabf-7ef9-ac7d29cdfb93-5C7GfCeVMHo@public.gmane.org>
  0 siblings, 1 reply; 10+ messages in thread
From: Tom St Denis @ 2017-10-06 12:57 UTC (permalink / raw)
  To: amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW

On 06/10/17 08:37 AM, Steven Falco wrote:
> On 10/05/2017 02:26 PM, Martin Babutzka wrote:
>> @Steven Falco: This behavior was EXACTLY the same with my R9 380 caused
>> by commit e37a7b4088da ("drm/amd/powerplay: tidy up ret checks in
>> amd_powerplay.c"). This is reverted now since a few days - are you sure
>> your kernel build already includes commit adc6af2349f0
>> ("drm/amd/powerplay: fix ret checks in amd_powerplay.c")?
>>
>> @AMD Devs/Alex: It would be nice if you push "Revert drm/amd/powerplay:
>> Add support for CI asics to hwmgr (Deucher, Alexander)" to agd5f. Then
>> I can try to build a non-crashing, flicker-free and hopefully overall
>> decent 4.13.5 kernel based on amd-staging-drm-next tomorrow.
> 
> That sounds very promising.  I am currently running the Fedora kernel.  Where would I download the one with the revisions you mentioned?

The commits will show up in

https://cgit.freedesktop.org/~agd5f/linux/log/?h=amd-staging-drm-next

Probably today or tomorrow.  You'll have to build your own kernel for 
now.  The typical path would be these patches make it into 4.15 (if that 
window is still open) and then eventually be released as part of 4.15 
and then the older tree maintainers can cherry-pick things into their trees.

Getting into a distro kernel depends on the distro I imagine.  Might be 
able to file a bug with the Fedora bug tracker for the kernel and then 
we can co-ordinate getting the patches into their tree.

Tom
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: Tonga PRO [Radeon R9 285/380] [1002:6939] blank screen
       [not found]             ` <c3045ba5-ca9d-fabf-7ef9-ac7d29cdfb93-5C7GfCeVMHo@public.gmane.org>
@ 2017-10-06 13:11               ` Steven Falco
  0 siblings, 0 replies; 10+ messages in thread
From: Steven Falco @ 2017-10-06 13:11 UTC (permalink / raw)
  To: Tom St Denis, amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW

On 10/06/2017 08:57 AM, Tom St Denis wrote:
> On 06/10/17 08:37 AM, Steven Falco wrote:
>> On 10/05/2017 02:26 PM, Martin Babutzka wrote:
>>> @Steven Falco: This behavior was EXACTLY the same with my R9 380 caused
>>> by commit e37a7b4088da ("drm/amd/powerplay: tidy up ret checks in
>>> amd_powerplay.c"). This is reverted now since a few days - are you sure
>>> your kernel build already includes commit adc6af2349f0
>>> ("drm/amd/powerplay: fix ret checks in amd_powerplay.c")?
>>>
>>> @AMD Devs/Alex: It would be nice if you push "Revert drm/amd/powerplay:
>>> Add support for CI asics to hwmgr (Deucher, Alexander)" to agd5f. Then
>>> I can try to build a non-crashing, flicker-free and hopefully overall
>>> decent 4.13.5 kernel based on amd-staging-drm-next tomorrow.
>>
>> That sounds very promising.  I am currently running the Fedora kernel.  Where would I download the one with the revisions you mentioned?
> 
> The commits will show up in
> 
> https://cgit.freedesktop.org/~agd5f/linux/log/?h=amd-staging-drm-next
> 
> Probably today or tomorrow.  You'll have to build your own kernel for now.  The typical path would be these patches make it into 4.15 (if that window is still open) and then eventually be released as part of 4.15 and then the older tree maintainers can cherry-pick things into their trees.
> 
> Getting into a distro kernel depends on the distro I imagine.  Might be able to file a bug with the Fedora bug tracker for the kernel and then we can co-ordinate getting the patches into their tree.

Ok - I'll grab that repo and build a new kernel.

I also found https://cgit.freedesktop.org/drm/drm-amd/log/?h=for-linux-next but I guess that is the wrong repo.  Would that repo also get the patches at some point?

I'll file a bug with Fedora once I build a good kernel.

Thanks!
Steve

_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Regression: Crash/freeze when resuming from suspend or locked screen
       [not found] ` <mailman.10603.1507217137.1832.amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>
  2017-10-05 18:26   ` Tonga PRO [Radeon R9 285/380] [1002:6939] blank screen Martin Babutzka
@ 2017-10-06 16:43   ` Martin Babutzka
       [not found]     ` <1507308193.2877.4.camel-BGeptl67XyCzQB+pC5nmwQ@public.gmane.org>
  1 sibling, 1 reply; 10+ messages in thread
From: Martin Babutzka @ 2017-10-06 16:43 UTC (permalink / raw)
  To: amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW

[-- Attachment #1: Type: text/plain, Size: 746 bytes --]

Hello there,

Sorry it is me again with another regression. I just built the latest
amd-staging-drm-next and the issue which was already reported here:
https://github.com/M-Bab/linux-kernel-amdgpu-binaries/issues/29
and which I can confirm is still existing.

The issue is caused occasionally when re-enabling the display from
either suspend or from a locked screen. The frozen image can be black,
a weird colorful pattern or the login screen. Attached you can find the
kernel crash+trace error I just caught.

So far I have no idea when it was exactly introduced. I asked the other
users if they are able to give me a time range I will try to bisect it.

My setup: Xubuntu 17.04, patched amd-staging-drm-next kernel, R9 380

Many regards,
Martin

[-- Attachment #2: crash_trace_resume.log --]
[-- Type: text/x-log, Size: 7562 bytes --]

Oct  6 17:52:45 Main-PC kernel: [   88.605940] BUG: unable to handle kernel NULL pointer dereference at           (null)
Oct  6 17:52:45 Main-PC kernel: [   88.606042] IP: dce110_vblank_set+0x59/0xb0 [amdgpu]
Oct  6 17:52:45 Main-PC kernel: [   88.606047] PGD 0 
Oct  6 17:52:45 Main-PC kernel: [   88.606049] P4D 0 
Oct  6 17:52:45 Main-PC kernel: [   88.606052] 
Oct  6 17:52:45 Main-PC kernel: [   88.606059] Oops: 0000 [#1] SMP
Oct  6 17:52:45 Main-PC kernel: [   88.606064] Modules linked in: rfcomm bnep binfmt_misc intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel dm_crypt kvm irqbypass crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel pcbc snd_seq_midi snd_seq_midi_event aesni_intel aes_x86_64 crypto_simd glue_helper cryptd snd_hda_codec_realtek intel_cstate intel_rapl_perf snd_hda_codec_generic snd_rawmidi snd_hda_codec_h
dmi snd_seq input_leds snd_hda_intel joydev serio_raw snd_hda_codec snd_hda_core snd_hwdep snd_seq_device snd_pcm snd_timer btusb snd btrtl soundcore mei_me shpchp mei hci_uart btbcm serdev btqca btintel bluetoo
th ecdh_generic intel_lpss_acpi intel_lpss mac_hid acpi_als tpm_infineon kfifo_buf acpi_pad industrialio parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic uas usb_storage usbhid amdkfd amd_iommu
_v2
Oct  6 17:52:45 Main-PC kernel: [   88.606147]  amdgpu chash i2c_algo_bit ttm drm_kms_helper e1000e syscopyarea sysfillrect sysimgblt fb_sys_fops ptp r8169 pps_core drm mii ahci libahci wmi pinctrl_sunrisepoint 
video i2c_hid pinctrl_intel hid
Oct  6 17:52:45 Main-PC kernel: [   88.606175] CPU: 6 PID: 1489 Comm: xfwm4 Tainted: G        W       4.13.5+ #1
Oct  6 17:52:45 Main-PC kernel: [   88.606178] Hardware name: Gigabyte Technology Co., Ltd. B250-HD3P/B250-HD3P-CF, BIOS F3 12/07/2016
Oct  6 17:52:45 Main-PC kernel: [   88.606182] task: ffff8a625429b900 task.stack: ffffae59c2fdc000
Oct  6 17:52:45 Main-PC kernel: [   88.606244] RIP: 0010:dce110_vblank_set+0x59/0xb0 [amdgpu]
Oct  6 17:52:45 Main-PC kernel: [   88.606247] RSP: 0018:ffffae59c2fdfb28 EFLAGS: 00010086
Oct  6 17:52:45 Main-PC kernel: [   88.606251] RAX: ffff8a623fe00000 RBX: 0000000000000001 RCX: 0000000000000000
Oct  6 17:52:45 Main-PC kernel: [   88.606254] RDX: 0000000000000000 RSI: 0000000000000002 RDI: 0000000000000000
Oct  6 17:52:45 Main-PC kernel: [   88.606256] RBP: ffffae59c2fdfb50 R08: 0000000000000000 R09: 0000000000000000
Oct  6 17:52:45 Main-PC kernel: [   88.606259] R10: fffffffffffffff2 R11: 00000000fffffff2 R12: ffff8a6250d79c80
Oct  6 17:52:45 Main-PC kernel: [   88.606261] R13: ffff8a626bc18600 R14: ffffffffc04551e0 R15: ffff8a62508a4000
Oct  6 17:52:45 Main-PC kernel: [   88.606265] FS:  00007f5018552a80(0000) GS:ffff8a626ed80000(0000) knlGS:0000000000000000
Oct  6 17:52:45 Main-PC kernel: [   88.606268] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Oct  6 17:52:45 Main-PC kernel: [   88.606271] CR2: 0000000000000000 CR3: 00000004180c9000 CR4: 00000000003406e0
Oct  6 17:52:45 Main-PC kernel: [   88.606274] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Oct  6 17:52:45 Main-PC kernel: [   88.606277] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Oct  6 17:52:45 Main-PC kernel: [   88.606279] Call Trace:
Oct  6 17:52:45 Main-PC kernel: [   88.606341]  dal_irq_service_set+0x6f/0x90 [amdgpu]
Oct  6 17:52:45 Main-PC kernel: [   88.606399]  dc_interrupt_set+0x24/0x30 [amdgpu]
Oct  6 17:52:45 Main-PC kernel: [   88.606473]  amdgpu_dm_set_crtc_irq_state+0x35/0x60 [amdgpu]
Oct  6 17:52:45 Main-PC kernel: [   88.606532]  amdgpu_irq_update+0x55/0xa0 [amdgpu]
Oct  6 17:52:45 Main-PC kernel: [   88.606588]  amdgpu_irq_get+0x49/0x60 [amdgpu]
Oct  6 17:52:45 Main-PC kernel: [   88.606629]  amdgpu_enable_vblank_kms+0x27/0x30 [amdgpu]
Oct  6 17:52:45 Main-PC kernel: [   88.606645]  drm_vblank_enable+0x84/0x100 [drm]
Oct  6 17:52:45 Main-PC kernel: [   88.606658]  drm_vblank_get+0x92/0xb0 [drm]
Oct  6 17:52:45 Main-PC kernel: [   88.606670]  drm_wait_vblank_ioctl+0xba/0x5b0 [drm]
Oct  6 17:52:45 Main-PC kernel: [   88.606677]  ? import_iovec+0x3a/0xe0
Oct  6 17:52:45 Main-PC kernel: [   88.606684]  ? unix_stream_recvmsg+0x54/0x70
Oct  6 17:52:45 Main-PC kernel: [   88.606690]  ? unix_state_double_lock+0x70/0x70
Oct  6 17:52:45 Main-PC kernel: [   88.606702]  ? drm_legacy_modeset_ctl_ioctl+0x100/0x100 [drm]
Oct  6 17:52:45 Main-PC kernel: [   88.606715]  drm_ioctl_kernel+0x69/0xb0 [drm]
Oct  6 17:52:45 Main-PC kernel: [   88.606727]  drm_ioctl+0x33c/0x3f0 [drm]
Oct  6 17:52:45 Main-PC kernel: [   88.606738]  ? drm_legacy_modeset_ctl_ioctl+0x100/0x100 [drm]
Oct  6 17:52:45 Main-PC kernel: [   88.606780]  amdgpu_drm_ioctl+0x4f/0x90 [amdgpu]
Oct  6 17:52:45 Main-PC kernel: [   88.606787]  do_vfs_ioctl+0xa3/0x610
Oct  6 17:52:45 Main-PC kernel: [   88.606792]  ? __sys_recvmsg+0x51/0x90
Oct  6 17:52:45 Main-PC kernel: [   88.606795]  ? __sys_recvmsg+0x51/0x90
Oct  6 17:52:45 Main-PC kernel: [   88.606802]  SyS_ioctl+0x79/0x90
Oct  6 17:52:45 Main-PC kernel: [   88.606806]  entry_SYSCALL_64_fastpath+0x1e/0xa9
Oct  6 17:52:45 Main-PC kernel: [   88.606810] RIP: 0033:0x7f5014c6d587
Oct  6 17:52:45 Main-PC kernel: [   88.606813] RSP: 002b:00007ffe34170958 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
Oct  6 17:52:45 Main-PC kernel: [   88.606817] RAX: ffffffffffffffda RBX: 0000562aec72b650 RCX: 00007f5014c6d587
Oct  6 17:52:45 Main-PC kernel: [   88.606820] RDX: 00007ffe341709d0 RSI: 00000000c018643a RDI: 0000000000000006
Oct  6 17:52:45 Main-PC kernel: [   88.606822] RBP: 00007ffe34170864 R08: 00000000006001e5 R09: 0000000000000000
Oct  6 17:52:45 Main-PC kernel: [   88.606825] R10: 00007ffe34170910 R11: 0000000000000246 R12: 0000562aec72b668
Oct  6 17:52:45 Main-PC kernel: [   88.606827] R13: 00007ffe34170868 R14: 0000000000000001 R15: 00007ffe34170770
Oct  6 17:52:45 Main-PC kernel: [   88.606831] Code: 84 db 74 34 83 e8 4e be 02 00 00 00 0f b6 d0 48 89 d0 48 c1 e0 04 48 29 d0 48 c1 e0 06 49 03 87 38 01 00 00 48 8b b8 68 02 00 00 <48> 8b 07 ff 90 d8 00 00 00 84 c0 74 1e 0f b6 d3 4c 89 f6 4c 89 
Oct  6 17:52:45 Main-PC kernel: [   88.606954] RIP: dce110_vblank_set+0x59/0xb0 [amdgpu] RSP: ffffae59c2fdfb28
Oct  6 17:52:45 Main-PC kernel: [   88.606957] CR2: 0000000000000000
Oct  6 17:52:45 Main-PC kernel: [   88.606961] ---[ end trace afd0d6685dd56a18 ]---
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@

[-- Attachment #3: Type: text/plain, Size: 154 bytes --]

_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: Tonga PRO [Radeon R9 285/380] [1002:6939] blank screen
       [not found]     ` <1507228004.5007.1.camel-BGeptl67XyCzQB+pC5nmwQ@public.gmane.org>
  2017-10-05 18:28       ` Tom St Denis
  2017-10-06 12:37       ` Steven Falco
@ 2017-10-06 20:24       ` Steven Falco
  2 siblings, 0 replies; 10+ messages in thread
From: Steven Falco @ 2017-10-06 20:24 UTC (permalink / raw)
  To: Martin Babutzka, amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW

On 10/05/2017 02:26 PM, Martin Babutzka wrote:
> @Steven Falco: This behavior was EXACTLY the same with my R9 380 caused
> by commit e37a7b4088da ("drm/amd/powerplay: tidy up ret checks in
> amd_powerplay.c"). This is reverted now since a few days - are you sure
> your kernel build already includes commit adc6af2349f0
> ("drm/amd/powerplay: fix ret checks in amd_powerplay.c")?

I've built a kernel from the amd-staging-drm-next branch of the agd5f tree.  It gives me a usable gui, but I get a lot of error messages on any terminals that I open.

I've added a new dmesg and xorg log file to the bug at https://bugs.freedesktop.org/show_bug.cgi?id=103111

The dmesg attachment is here: https://bugs.freedesktop.org/attachment.cgi?id=134713

The basic error message is "page dumped because: corrupted mapping in tail page" and the call trace has references to amdgpu, apparently beginning at amdgpu_drm_ioctl.

Please let me know if I can provide any additional information.

	Thanks,
	Steve
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Fwd: Regression: Crash/freeze when resuming from suspend or locked screen
       [not found]     ` <1507308193.2877.4.camel-BGeptl67XyCzQB+pC5nmwQ@public.gmane.org>
@ 2017-10-10  6:55       ` Martin Babutzka
       [not found]         ` <624136700.113676.1507618522363-NM1PAhYDU/Oo9dU1Uvar1Q@public.gmane.org>
  0 siblings, 1 reply; 10+ messages in thread
From: Martin Babutzka @ 2017-10-10  6:55 UTC (permalink / raw)
  To: amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW

[-- Attachment #1: Type: text/html, Size: 1511 bytes --]

[-- Attachment #2: crash_trace_resume.log --]
[-- Type: text/x-log, Size: 7562 bytes --]

Oct  6 17:52:45 Main-PC kernel: [   88.605940] BUG: unable to handle kernel NULL pointer dereference at           (null)
Oct  6 17:52:45 Main-PC kernel: [   88.606042] IP: dce110_vblank_set+0x59/0xb0 [amdgpu]
Oct  6 17:52:45 Main-PC kernel: [   88.606047] PGD 0 
Oct  6 17:52:45 Main-PC kernel: [   88.606049] P4D 0 
Oct  6 17:52:45 Main-PC kernel: [   88.606052] 
Oct  6 17:52:45 Main-PC kernel: [   88.606059] Oops: 0000 [#1] SMP
Oct  6 17:52:45 Main-PC kernel: [   88.606064] Modules linked in: rfcomm bnep binfmt_misc intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel dm_crypt kvm irqbypass crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel pcbc snd_seq_midi snd_seq_midi_event aesni_intel aes_x86_64 crypto_simd glue_helper cryptd snd_hda_codec_realtek intel_cstate intel_rapl_perf snd_hda_codec_generic snd_rawmidi snd_hda_codec_h
dmi snd_seq input_leds snd_hda_intel joydev serio_raw snd_hda_codec snd_hda_core snd_hwdep snd_seq_device snd_pcm snd_timer btusb snd btrtl soundcore mei_me shpchp mei hci_uart btbcm serdev btqca btintel bluetoo
th ecdh_generic intel_lpss_acpi intel_lpss mac_hid acpi_als tpm_infineon kfifo_buf acpi_pad industrialio parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic uas usb_storage usbhid amdkfd amd_iommu
_v2
Oct  6 17:52:45 Main-PC kernel: [   88.606147]  amdgpu chash i2c_algo_bit ttm drm_kms_helper e1000e syscopyarea sysfillrect sysimgblt fb_sys_fops ptp r8169 pps_core drm mii ahci libahci wmi pinctrl_sunrisepoint 
video i2c_hid pinctrl_intel hid
Oct  6 17:52:45 Main-PC kernel: [   88.606175] CPU: 6 PID: 1489 Comm: xfwm4 Tainted: G        W       4.13.5+ #1
Oct  6 17:52:45 Main-PC kernel: [   88.606178] Hardware name: Gigabyte Technology Co., Ltd. B250-HD3P/B250-HD3P-CF, BIOS F3 12/07/2016
Oct  6 17:52:45 Main-PC kernel: [   88.606182] task: ffff8a625429b900 task.stack: ffffae59c2fdc000
Oct  6 17:52:45 Main-PC kernel: [   88.606244] RIP: 0010:dce110_vblank_set+0x59/0xb0 [amdgpu]
Oct  6 17:52:45 Main-PC kernel: [   88.606247] RSP: 0018:ffffae59c2fdfb28 EFLAGS: 00010086
Oct  6 17:52:45 Main-PC kernel: [   88.606251] RAX: ffff8a623fe00000 RBX: 0000000000000001 RCX: 0000000000000000
Oct  6 17:52:45 Main-PC kernel: [   88.606254] RDX: 0000000000000000 RSI: 0000000000000002 RDI: 0000000000000000
Oct  6 17:52:45 Main-PC kernel: [   88.606256] RBP: ffffae59c2fdfb50 R08: 0000000000000000 R09: 0000000000000000
Oct  6 17:52:45 Main-PC kernel: [   88.606259] R10: fffffffffffffff2 R11: 00000000fffffff2 R12: ffff8a6250d79c80
Oct  6 17:52:45 Main-PC kernel: [   88.606261] R13: ffff8a626bc18600 R14: ffffffffc04551e0 R15: ffff8a62508a4000
Oct  6 17:52:45 Main-PC kernel: [   88.606265] FS:  00007f5018552a80(0000) GS:ffff8a626ed80000(0000) knlGS:0000000000000000
Oct  6 17:52:45 Main-PC kernel: [   88.606268] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Oct  6 17:52:45 Main-PC kernel: [   88.606271] CR2: 0000000000000000 CR3: 00000004180c9000 CR4: 00000000003406e0
Oct  6 17:52:45 Main-PC kernel: [   88.606274] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Oct  6 17:52:45 Main-PC kernel: [   88.606277] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Oct  6 17:52:45 Main-PC kernel: [   88.606279] Call Trace:
Oct  6 17:52:45 Main-PC kernel: [   88.606341]  dal_irq_service_set+0x6f/0x90 [amdgpu]
Oct  6 17:52:45 Main-PC kernel: [   88.606399]  dc_interrupt_set+0x24/0x30 [amdgpu]
Oct  6 17:52:45 Main-PC kernel: [   88.606473]  amdgpu_dm_set_crtc_irq_state+0x35/0x60 [amdgpu]
Oct  6 17:52:45 Main-PC kernel: [   88.606532]  amdgpu_irq_update+0x55/0xa0 [amdgpu]
Oct  6 17:52:45 Main-PC kernel: [   88.606588]  amdgpu_irq_get+0x49/0x60 [amdgpu]
Oct  6 17:52:45 Main-PC kernel: [   88.606629]  amdgpu_enable_vblank_kms+0x27/0x30 [amdgpu]
Oct  6 17:52:45 Main-PC kernel: [   88.606645]  drm_vblank_enable+0x84/0x100 [drm]
Oct  6 17:52:45 Main-PC kernel: [   88.606658]  drm_vblank_get+0x92/0xb0 [drm]
Oct  6 17:52:45 Main-PC kernel: [   88.606670]  drm_wait_vblank_ioctl+0xba/0x5b0 [drm]
Oct  6 17:52:45 Main-PC kernel: [   88.606677]  ? import_iovec+0x3a/0xe0
Oct  6 17:52:45 Main-PC kernel: [   88.606684]  ? unix_stream_recvmsg+0x54/0x70
Oct  6 17:52:45 Main-PC kernel: [   88.606690]  ? unix_state_double_lock+0x70/0x70
Oct  6 17:52:45 Main-PC kernel: [   88.606702]  ? drm_legacy_modeset_ctl_ioctl+0x100/0x100 [drm]
Oct  6 17:52:45 Main-PC kernel: [   88.606715]  drm_ioctl_kernel+0x69/0xb0 [drm]
Oct  6 17:52:45 Main-PC kernel: [   88.606727]  drm_ioctl+0x33c/0x3f0 [drm]
Oct  6 17:52:45 Main-PC kernel: [   88.606738]  ? drm_legacy_modeset_ctl_ioctl+0x100/0x100 [drm]
Oct  6 17:52:45 Main-PC kernel: [   88.606780]  amdgpu_drm_ioctl+0x4f/0x90 [amdgpu]
Oct  6 17:52:45 Main-PC kernel: [   88.606787]  do_vfs_ioctl+0xa3/0x610
Oct  6 17:52:45 Main-PC kernel: [   88.606792]  ? __sys_recvmsg+0x51/0x90
Oct  6 17:52:45 Main-PC kernel: [   88.606795]  ? __sys_recvmsg+0x51/0x90
Oct  6 17:52:45 Main-PC kernel: [   88.606802]  SyS_ioctl+0x79/0x90
Oct  6 17:52:45 Main-PC kernel: [   88.606806]  entry_SYSCALL_64_fastpath+0x1e/0xa9
Oct  6 17:52:45 Main-PC kernel: [   88.606810] RIP: 0033:0x7f5014c6d587
Oct  6 17:52:45 Main-PC kernel: [   88.606813] RSP: 002b:00007ffe34170958 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
Oct  6 17:52:45 Main-PC kernel: [   88.606817] RAX: ffffffffffffffda RBX: 0000562aec72b650 RCX: 00007f5014c6d587
Oct  6 17:52:45 Main-PC kernel: [   88.606820] RDX: 00007ffe341709d0 RSI: 00000000c018643a RDI: 0000000000000006
Oct  6 17:52:45 Main-PC kernel: [   88.606822] RBP: 00007ffe34170864 R08: 00000000006001e5 R09: 0000000000000000
Oct  6 17:52:45 Main-PC kernel: [   88.606825] R10: 00007ffe34170910 R11: 0000000000000246 R12: 0000562aec72b668
Oct  6 17:52:45 Main-PC kernel: [   88.606827] R13: 00007ffe34170868 R14: 0000000000000001 R15: 00007ffe34170770
Oct  6 17:52:45 Main-PC kernel: [   88.606831] Code: 84 db 74 34 83 e8 4e be 02 00 00 00 0f b6 d0 48 89 d0 48 c1 e0 04 48 29 d0 48 c1 e0 06 49 03 87 38 01 00 00 48 8b b8 68 02 00 00 <48> 8b 07 ff 90 d8 00 00 00 84 c0 74 1e 0f b6 d3 4c 89 f6 4c 89 
Oct  6 17:52:45 Main-PC kernel: [   88.606954] RIP: dce110_vblank_set+0x59/0xb0 [amdgpu] RSP: ffffae59c2fdfb28
Oct  6 17:52:45 Main-PC kernel: [   88.606957] CR2: 0000000000000000
Oct  6 17:52:45 Main-PC kernel: [   88.606961] ---[ end trace afd0d6685dd56a18 ]---
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@

[-- Attachment #3: Type: text/plain, Size: 154 bytes --]

_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

^ permalink raw reply	[flat|nested] 10+ messages in thread

* RE: Regression: Crash/freeze when resuming from suspend or locked screen
       [not found]         ` <624136700.113676.1507618522363-NM1PAhYDU/Oo9dU1Uvar1Q@public.gmane.org>
@ 2017-10-10 14:41           ` Deucher, Alexander
       [not found]             ` <CY4PR12MB16533EE2F12BC8E8BF9BD4EFF7750-rpdhrqHFk06apTa93KjAaQdYzm3356FpvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
  0 siblings, 1 reply; 10+ messages in thread
From: Deucher, Alexander @ 2017-10-10 14:41 UTC (permalink / raw)
  To: 'Martin Babutzka', amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW


[-- Attachment #1.1: Type: text/plain, Size: 1561 bytes --]

We haven't had a chance to look into it yet.

Alex

From: amd-gfx [mailto:amd-gfx-bounces@lists.freedesktop.org] On Behalf Of Martin Babutzka
Sent: Tuesday, October 10, 2017 2:55 AM
To: amd-gfx@lists.freedesktop.org
Subject: Fwd: Regression: Crash/freeze when resuming from suspend or locked screen


Dear AMD developers,

Are there no comments/questions on this issue or did the mail just got lost in between the flood of patches?

Many regards,
Martin



---------- Ursprüngliche Nachricht ----------
Von: Martin Babutzka <martin.babutzka@online.de<mailto:martin.babutzka@online.de>>
An: amd-gfx@lists.freedesktop.org<mailto:amd-gfx@lists.freedesktop.org>
Datum: 6. Oktober 2017 um 18:43
Betreff: Regression: Crash/freeze when resuming from suspend or locked screen

Hello there,

Sorry it is me again with another regression. I just built the latest
amd-staging-drm-next and the issue which was already reported here:
https://github.com/M-Bab/linux-kernel-amdgpu-binaries/issues/29
and which I can confirm is still existing.

The issue is caused occasionally when re-enabling the display from
either suspend or from a locked screen. The frozen image can be black,
a weird colorful pattern or the login screen. Attached you can find the
kernel crash+trace error I just caught.

So far I have no idea when it was exactly introduced. I asked the other
users if they are able to give me a time range I will try to bisect it.

My setup: Xubuntu 17.04, patched amd-staging-drm-next kernel, R9 380

Many regards,
Martin

[-- Attachment #1.2: Type: text/html, Size: 5189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 154 bytes --]

_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: Regression: Crash/freeze when resuming from suspend or locked screen
       [not found]             ` <CY4PR12MB16533EE2F12BC8E8BF9BD4EFF7750-rpdhrqHFk06apTa93KjAaQdYzm3356FpvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
@ 2017-10-10 15:01               ` Zhu, Rex
  0 siblings, 0 replies; 10+ messages in thread
From: Zhu, Rex @ 2017-10-10 15:01 UTC (permalink / raw)
  To: Deucher, Alexander, 'Martin Babutzka',
	amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW


[-- Attachment #1.1: Type: text/plain, Size: 2222 bytes --]

Hi Martin,

Can you try to reproduce this issue with amdgpu.dc=0 when modprobe amdgpu

Best Regards
Rex
________________________________
From: amd-gfx <amd-gfx-bounces-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org> on behalf of Deucher, Alexander <Alexander.Deucher-5C7GfCeVMHo@public.gmane.org>
Sent: Tuesday, October 10, 2017 10:41:29 PM
To: 'Martin Babutzka'; amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: RE: Regression: Crash/freeze when resuming from suspend or locked screen

We haven't had a chance to look into it yet.

Alex

From: amd-gfx [mailto:amd-gfx-bounces-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org] On Behalf Of Martin Babutzka
Sent: Tuesday, October 10, 2017 2:55 AM
To: amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Fwd: Regression: Crash/freeze when resuming from suspend or locked screen


Dear AMD developers,

Are there no comments/questions on this issue or did the mail just got lost in between the flood of patches?

Many regards,
Martin



---------- Ursprüngliche Nachricht ----------
Von: Martin Babutzka <martin.babutzka-BGeptl67XyCzQB+pC5nmwQ@public.gmane.org<mailto:martin.babutzka@online.de>>
An: amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org<mailto:amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>
Datum: 6. Oktober 2017 um 18:43
Betreff: Regression: Crash/freeze when resuming from suspend or locked screen

Hello there,

Sorry it is me again with another regression. I just built the latest
amd-staging-drm-next and the issue which was already reported here:
https://github.com/M-Bab/linux-kernel-amdgpu-binaries/issues/29
and which I can confirm is still existing.

The issue is caused occasionally when re-enabling the display from
either suspend or from a locked screen. The frozen image can be black,
a weird colorful pattern or the login screen. Attached you can find the
kernel crash+trace error I just caught.

So far I have no idea when it was exactly introduced. I asked the other
users if they are able to give me a time range I will try to bisect it.

My setup: Xubuntu 17.04, patched amd-staging-drm-next kernel, R9 380

Many regards,
Martin

[-- Attachment #1.2: Type: text/html, Size: 6132 bytes --]

[-- Attachment #2: Type: text/plain, Size: 154 bytes --]

_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

^ permalink raw reply	[flat|nested] 10+ messages in thread

end of thread, other threads:[~2017-10-10 15:01 UTC | newest]

Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <mailman.10603.1507217137.1832.amd-gfx@lists.freedesktop.org>
     [not found] ` <mailman.10603.1507217137.1832.amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>
2017-10-05 18:26   ` Tonga PRO [Radeon R9 285/380] [1002:6939] blank screen Martin Babutzka
     [not found]     ` <1507228004.5007.1.camel-BGeptl67XyCzQB+pC5nmwQ@public.gmane.org>
2017-10-05 18:28       ` Tom St Denis
2017-10-06 12:37       ` Steven Falco
     [not found]         ` <f52fce30-bdc9-ce80-b50b-4d2d4ffb0b9a-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-10-06 12:57           ` Tom St Denis
     [not found]             ` <c3045ba5-ca9d-fabf-7ef9-ac7d29cdfb93-5C7GfCeVMHo@public.gmane.org>
2017-10-06 13:11               ` Steven Falco
2017-10-06 20:24       ` Steven Falco
2017-10-06 16:43   ` Regression: Crash/freeze when resuming from suspend or locked screen Martin Babutzka
     [not found]     ` <1507308193.2877.4.camel-BGeptl67XyCzQB+pC5nmwQ@public.gmane.org>
2017-10-10  6:55       ` Fwd: " Martin Babutzka
     [not found]         ` <624136700.113676.1507618522363-NM1PAhYDU/Oo9dU1Uvar1Q@public.gmane.org>
2017-10-10 14:41           ` Deucher, Alexander
     [not found]             ` <CY4PR12MB16533EE2F12BC8E8BF9BD4EFF7750-rpdhrqHFk06apTa93KjAaQdYzm3356FpvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2017-10-10 15:01               ` Zhu, Rex

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.